Bex Web times out

[Former Member]

Hello,

Sometimes we get the following message in Bex Web

NFO: Maximum idle time between navigation steps was exceeded and the session was ended; restart the BEx Web application

Do you know what could be the timeout parameter involved ?

Thanks

Samuel

[Former Member · Accepted solution]

Hello

Go to transaction SMICM

Press the services button in the header

The list of Port and the maximum alive time will appear. Change this time for your requirement

The list will show the port name of the network in which your WAD is running on.Confirm with this admin

Regards

N Ganesh

[Former Member]

Hello,

Althoug the time out in the icm is currently 1 hour, users have confirmed us that when they execute queries wait until answer, if they try to manipulate after the execution has finished (not inmediately but sure less than one hour after launching the query) the system show a time out.

Best regards

Samuel

[former_member184494]

Samuel,

Is it through Portal or directly on BI ? check the portal timeouts also ?

also check the response times while using BeX

Arun

[floK]

Hi folks,

We have exactly same problem. The message we receive is:

INFO: Maximum idle time between navigation steps was exceeded and the session was ended; restart the BEx Web application.

This error occur exactly after 1 hour but in this our there is no user inactivity :(.

Our Timeout Settings:

SSO Timeout (anmeldung): 8 hours

SessionTimeout (overall): 1 hour

irj Portal Timeout: 1 hour.

ICM Timeout: 1 hour.

SICF Bex Timout --> 00:00:00 (never)

Yes I could increase size to 5 hour, but I want no workarround for this issue, Im looking for a fix :(.

Are there any ideas? I see the fallowing message in the Logfile:

Kategorie: /Applications/BI

Ort: com.sap.ip.bi.webapplications.runtime.impl.Page

Anwendung: sap.com/irj

Host: hostname

Knoten: Server 0 1_22460

Exception caught: java.lang.NullPointerException

java.lang.NullPointerException

at com.sap.ip.bi.webapplications.runtime.base.PageObject.raiseEvent(PageObject.java:764)

at com.sap.ip.bi.webapplications.runtime.base.PageObject.destroy(PageObject.java:520)

at com.sap.ip.bi.webapplications.runtime.base.ItemRenderer.destroy(ItemRenderer.java:46)

at com.sap.ip.bi.webapplications.runtime.impl.Page.destroyPageObject(Page.java:4621)

at com.sap.ip.bi.webapplications.runtime.impl.Page.destroyPageObjects(Page.java:6538)

at com.sap.ip.bi.webapplications.runtime.impl.Page.destroy(Page.java:6682)

at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.destroyPage(Controller.java:601)

at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.destroyInternal(Controller.java:1054)

at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.timeout(Controller.java:1109)

at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.ControllerCollector.destroyInternal(ControllerCollector.java:138)

at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.ControllerCollector.timeout(ControllerCollector.java:170)

at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.ControllerCollector.valueUnbound(ControllerCollector.java:230)

at com.sap.engine.services.servlets_jsp.server.runtime.context.WebEvents.sessionValueUnbound(WebEvents.java:410)

at com.sap.engine.services.servlets_jsp.server.runtime.context.WebEvents.sessionValueUnbound(WebEvents.java:404)

at com.sap.engine.services.servlets_jsp.server.runtime.client.ApplicationSession.invalidateSession(ApplicationSession.java:331)

at com.sap.engine.services.servlets_jsp.server.runtime.client.ApplicationSession.validate(ApplicationSession.java:177)

at com.sap.engine.services.servlets_jsp.server.runtime.client.ApplicationSession.isValid(ApplicationSession.java:377)

at com.sap.engine.services.servlets_jsp.server.runtime.context.ApplicationContext.checkMap(ApplicationContext.java:377)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.checkRequest(HttpHandlerImpl.java:68)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:873)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(AccessController.java:215)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

Error while ending a BI application; see SAP Notes 937697 and 948490

Thanks,

Best regards

Florian

[Former Member]

Were you ever able to tackle this problem? Please share the resolution with all of us.

[Former Member]

Hello,

In fact this problem was not reproducable. We had it sometimes.

This never occures anymore but we implemented java patches, abap notes... So it's impossible to give a clear picture of the solution.

Best regards

Sam