Skip to Content
author's profile photo Former Member
Former Member

Webdynpro iview problem not launching

Hi Experts,

We developed an web dynpro application and deployed properly.

but when we are unable to launch the web dynpro iview. on the trace file we got the following information.

pl help us to fix this

nzakleafn049_SPQ_19663151#phaniku#767c57109ee211dc9cc60015c5e6effa#SAPEngine_Application_Thread[impl:3]_26##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.

The error is: com.sap.engine.services.servlets_jsp.server.exceptions.InvalidSessionException: Method [getMaxInactiveInterval()] is called in an invalid session.

Exception id: [0015C5E6EFFA00650000002100000D2C0004401B911CE06F]#

#1.5#0015C5E6EFFA00630000003500000D2C0004401B911CE929#1196387049827#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#2##nzakleafn049_SPQ_19663151#phaniku#767c57109ee211dc9cc60015c5e6effa#SAPEngine_Application_Thread[impl:3]_28##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.

The error is: com.sap.engine.services.servlets_jsp.server.exceptions.InvalidSessionException: Method [getMaxInactiveInterval()] is called in an invalid session.

Exception id: [0015C5E6EFFA00630000003300000D2C0004401B911CE147]#

#1.5#0015C5E6EFFA00600000002B00000D2C0004401B911CEC1F#1196387049827#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#Guest#2##nzakleafn049_SPQ_19663151#phaniku#767c57109ee211dc9cc60015c5e6effa#SAPEngine_Application_Thread[impl:3]_31##0#0#Error##Plain###Processing HTTP request to servlet [dispatcher] finished with error. The error is: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: The connection is closed.

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:203)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)

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

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

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

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

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(Native Method)

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

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Caused by: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: The connection is closed.

at com.sap.engine.services.servlets_jsp.server.runtime.client.ServletOutputStreamImpl.ensureClientAvailable(ServletOutputStreamImpl.java:560)

at com.sap.engine.services.servlets_jsp.server.runtime.client.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:409)

at com.sap.engine.services.servlets_jsp.server.runtime.client.ServletOutputStreamImpl.close(ServletOutputStreamImpl.java:521)

at com.sap.tc.webdynpro.basesrvc.util.NonClosingOutputStream.finalizeStream(NonClosingOutputStream.java:41)

at com.sap.tc.webdynpro.serverimpl.core.adapter.AbstractHttpResponseAdapter.finalizeResponse(AbstractHttpResponseAdapter.java:147)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.finalizeRequest(RequestManager.java:579)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:201)

... 18 more

#

#1.5#0015C5E6EFFA00600000002D00000D2C0004401B911CF097#1196387049827#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#2##nzakleafn049_SPQ_19663151#phaniku#767c57109ee211dc9cc60015c5e6effa#SAPEngine_Application_Thread[impl:3]_31##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.

The error is: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: The connection is closed.

Adv Thanks

Pl its urgent---Points should be awarded for helpful answers

Regards

Phani

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Nov 30, 2007 at 10:35 AM

    Hi,

    Did you call the method getMaxInactiveInterval() in your code?If so try to create the session first and then call the method.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.