500 Internal server error - java.lang.NullPointerException: null

[Former Member]

While trying to access the initial login screen of EP, we face this '500 Internal server error - java.lang.NullPointerException: null' issue very randomly. It appears sometimes and when opened from new browser we get the login screen sometimes. It is not a problem that reproduces always. On the screen where the error appears, we refresh any number of times, no help, the error remains the same, but when we open in a new window, it might give the login screen or end up with this error.

We have 4 Dialog Instances and a Cisco load balancer.

Upon repeated redirection to a particular instance and particular server node(https://<hostname>:<port>/irj/portal;sapj2ee_irj= XXX) from the trace files, I could get the following information :-

-

---

#0019BBEB9F4C00190000409700001707000478F21B0BBACE#1258881142025#com.sap.tc.webdynpro.sessionmanagement#sap.com/tc_wddispwda#com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleThrowable#2449#32347##n/a##245825a0d74711de92700019bbeb9f4c#SAPEngine_Application_Thread[impl:3]_12##0#0#Error#1#/System/UserInterface#Java###Exception occured during processing of Web Dynpro application . The causing exception is nested. [EXCEPTION] #2#sap.com/pb/PageBuilder#java.lang.NullPointerException # #1.5_#0019BBEB9F4C00190000409800001707000478F21B0BD29A#1258881142031#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tc_wddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#2449#32347##n/a##245825a0d74711de92700019bbeb9f4c#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain###application [webdynpro/dispatcher] Processing HTTP request to servlet [dispatcher] finished with error. The error is: java.lang.NullPointerException # #1.5_#0019BBEB9F4C00190000409A00001707000478F21B0C5FDE#1258881142068#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tc_wddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#2449#32347##n/a##245825a0d74711de92700019bbeb9f4c#SAPEngine_Application_Thread[impl:3]_12##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: [0019BBEB9F4C00190000409800001707000478F21B0BD29A]# #1.5_#0019BBEB9F4C00310000372500001707000478F21D348764#1258881178254#com.sap.security.core.server.destinations.service.DestinationServiceImpl#sap.com/tc_wddispwda#com.sap.security.core.server.destinations.service.DestinationServiceImpl.getDestination#5180#32285##juepp01_EPP_16040550#5180#392ddb50d74711de87f40019bbeb9f4c#SAPEngine_Application_Thread[impl:3]_10##0#0#Error#1#/System/Security/destinations#Java###An error occurred while reading the destination , type . The error was .#3#sap_inbox$WebFlowConnector#RFC#<Localization failed: ResourceBundle='com.sap.exception.io.IOResourceBundle', ID='No such destination sap_inbox$WebFlowConnector of type RFC exists ', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key No such destination sap_inbox$WebFlowConnector of type RFC exists #

#1.5_#0019BBEB9F4C00310000372600001707000478F21D34893F#1258881178255#System.err#sap.com/tc_wddispwda#System.err#5180#32285##juepp01_EPP_16040550#5180#392ddb50d74711de87f40019bbeb9f4c#SAPEngine_Application_Thread[impl:3]_10##0#0#Error##Plain###java.lang.Exception: Problem occured while creating JCO client for destination: sap_inbox#

#1.5_#0019BBEB9F4C00310000372700001707000478F21D34A80D#1258881178262#System.err#sap.com/tc_wddispwda#System.err#5180#32285##juepp01_EPP_16040550#5180#392ddb50d74711de87f40019bbeb9f4c#SAPEngine_Application_Thread[impl:3]_10##0#0#Error##Plain### at com.sap.netweaver.bc.uwl.utils.r3.R3SystemInfo.createJCOClient(R3SystemInfo.java:67)#

#1.5_#0019BBEB9F4C00310000372800001707000478F21D34A887#1258881178263#System.err#sap.com/tc_wddispwda#System.err#5180#32285##juepp01_EPP_16040550#5180#392ddb50d74711de87f40019bbeb9f4c#SAPEngine_Application_Thread[impl:3]_10##0#0#Error##Plain### at com.sap.netweaver.bc.uwl.utils.r3.R3SystemInfo.hasFunctionModule(R3SystemInfo.java:591)#

-

---

Kindly advise as to what could be the issue..

[Former Member]

Restarting SAP on the affected node is helping to fix this issue. But again its the same restart that is originating the issue sometimes. Not sure why this happens.

[Former Member]

Hi, either the problem should come always for us to be able to trouble shoot it or should not come at all.

Now since it comes sometimes, i feel that you surely are using more than one app. servers in your enviroment and some of them are not fine.

I received this error when i accidently had deleted my sso ticket pairs in the visual admin.

First troubleshoot by login to individual app servers where the issue is coming. after that check the certificate-cert key pair in keystore admin. you can also delete them and make new ticket pairs..

If this does not help, replace your login page with the standard sap login page par com.sap.portal.runtime.logon.par.

This should certainly troubleshoot u

cheers,

Ankur

[shankar_agarwal]

Hi

Check your UWL configuration.Is there an undefined system there?Also chk all the JCO connection in Portal whether thry are running?

regards

[Former Member]

The configurations and connections are clean . The login page does appear 8 out of 10 times the URL is played, but the rest 20 % it hits ' 500 Internal server error' page. The system is well up and running. But few end users of the 30,000 do complain of they ending up with this error.

[hofmann]

Hi,

is it working on all your server nodes? Maybe the 20% is occuring when the user is working on a "bad" servernode.

br,

Tobias

[Former Member]

I tried to trace out the bad node/s if any by playing the URL to each individual node using (https://hostname:port/irj/portal;sapj2ee_irj=NODE ID ) and came up with a couple of bad nodes in a particular instance. I wait for a couple of minutes and check again for the same identified URLs on a new browser and the login page appears. That is what I meant the issue is not constantly appearing in any particular node. but rather shifting between nodes and that too randomly.