The Web Dynpro Application xxx has expired for every link.

[former_member50538]

We have just finished installing a new NW 7.0 server and patched it to SP14. I can access http://server:50000/index.html with no problems and I can click on System Information and it gives me the normal page. But if I click on any link that will run an application e.g. “Web Dynpro Content Administrator” and click any of the buttons “Create Jco Destination” or “Check SLD” etc. I get an error

The Web Dynpro Application 'Explorer' has expired. Restart the application using the Refresh button or via the following link Explorer.

Or if I go to Netweaver Adminstration (http://server:50000/nwa), the page loads fine but if I click on any of the links “Administration”, “Configuration” or “Monitoring” I get a similar message.

I have checked all the WebDynpro expiration settings in the Visual Administrator as per note 842635 and everything looks fine.

I checked the log in defaultTrace 2.trc and I can see the error reported as well as a null pointer error.

Does anyone have any advice? I have included the log entries here

#1.5 #005056B75D55006D0000005D000008BC000449D829D0EB7E#1207092670160#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tc_wddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#J2EE_GST_PQ1#0##n/a##b5a76c01004311ddb661005056b75d55#SAPEngine_Application_Thread[impl:3]_23##0#0#Error#1#/System/Server/WebRequests#Plain###application [webdynpro/dispatcher] Processing HTTP request to servlet [dispatcher] finished with error.

The error is: java.lang.NullPointerException: null

Exception id: [005056B75D55006D0000005B000008BC000449D829D0E781]#

#1.5 #005056B75D5500740000005B000008BC000449D82B4A6FBA#1207092694883#com.sap.tc.webdynpro.sessionmanagement#sap.com/tc_wddispwda#com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleExpiration#J2EE_GST_PQ1#0##n/a##c4664b31004311dd9ad8005056b75d55#SAPEngine_Application_Thread[impl:3]_36##0#0#Warning#1#/System/UserInterface#Java###Session unknown: Request with URI= was sent to unknown session. Either request with wrong session parameters was sent, or session has expired before . Current request parameters=. Is termination request=. Request was sent from host with IP=/name=. Hint: see SAP note 842635 for more details on session expiration. RID=

[EXCEPTION]

#8#/webdynpro/dispatcher/sap.com/tc_wdtools/Explorer#Mon Mar 31 14:28:33 EST 2008#{sap-wd-cltwndid=f3174b80004011dd9134005056b75d55, sap-wd-norefresh=X, sap-wd-appwndid=aeb96f60004311dd94e4005056b75d55}#false#10.120.2.65#10.120.2.65#c4664b30004311dd999f005056b75d55#com.sap.tc.webdynpro.clientserver.session.SessionExpiredLongJumpException: Session has expired (current request: follow-up request). Please restart the application. Hint: HttpSession seems to be expired due to user inactivity or application is called with wrong URL parameter (sap-wd-norefresh=X).

at com.sap.tc.webdynpro.clientserver.session.RequestManager.findClientSession(RequestManager.java:259)

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

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:401)

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

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

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

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

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

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

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

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

#

#1.5 #005056B75D5500740000005C000008BC000449D82B4AA3DD#1207092694914#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tc_wddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#J2EE_GST_PQ1#0##n/a##c4664b31004311dd9ad8005056b75d55#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###application [webdynpro/dispatcher] Processing HTTP request to servlet [dispatcher] finished with error. The error is: java.lang.NullPointerException

at com.sap.tc.webdynpro.clientserver.task.SAPSessionProtocolTask.getSessionProtocolParameterFromRequest(SAPSessionProtocolTask.java:103)

at com.sap.tc.webdynpro.clientserver.task.SAPSessionProtocolTask.handleSessionEvents(SAPSessionProtocolTask.java:43)

at com.sap.tc.webdynpro.clientserver.task.Task.getSAPSessionProtocolEvent(Task.java:816)

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

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

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:401)

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

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

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

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

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

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

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

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

[former_member50538]

The problem seemed to be related to cookies being rejected.

Here is the reply from SAP:

"Please refer to note 654982. We think the problem with the rejected

cookies occured because the domain that you use does not satisfy the

requirements of the cookie specification ( see

http://wp.netscape.com/newsref/std/cookie_spec.html).

Any domain with a different extension than "com", "edu", "net", "org",

"gov","mil" or "int" must consist of at least two additional domain

parts.

In your case the fully qualified domain name is

<hidden for security purposes>

It consist of one additional domain part and according note 654982 is

not acceptable.

Please check with your system administrators if you can change the

domain name.

Other possible decision is to change the domain attribute of JSESSIONID

cookie to hostname.domain but this may cause other problems."

[Former Member]

Richard,

Do you have some news about this? I'm having the same issue in my server (SP 13) and is a intermittent error.

Thanks,

Pedro Nunes

[former_member50538]

SAP Support asked me to send HTTP Traces. Then they asked me to donload and redeploy a WebDynpro Session manager. This did not fix the problem and it is back with them.

[former_member50538]

This problem is happening on our Prod and Dev servers. Both systems have been patched to SP14. I found that in the log file there are many references to a null pointer exception. I have logged the problem with OSS and sent SAP all the log files.

I feel that the problem is being caused by the server unable to connect to the SLD but I can't see if the SLD is running corrcectly as I get a "session has expired" erro when I click on the "Administration" link inthe sld screen. I have checked all the authorisation of the SDLDSUSER and initially there were some authorisations missing they have all been assigned now (LcrAdminsitrator etc.).

[Former Member]

Hi Richard,

Did you get any reply from SAP support?

Regards

Rajendra

[Former Member]

Hai,

If any of the JAVA Components is missed during the Patching to SP13.Then the problem comes.Patch it SP14 and check.

[Former Member]

Hi Richard,

I have same problem with nw04s system with SP13.

Regards,

Rajendra