servlet error intermittently after starting

[former_member482483]

Hi,

I am running SAP Netweaver Web AS 6.40 and encountered some intermittent problem running my servlet after restarting the Web AS.

When trying to access the servlet I encountered the http error 500. The only way to resolve this is to try restart the Web AS again and it will be ok.

From the std_server0.out log, I noticed there was this error :

#1.5 #0003BAA8E7A3002A0000000000004EA90004C6C8F62BF528#1344466332677#/System/Server/SLDService##com.sap.sldserv.SldServerFrame####n/a##b138cbb9e1ab11e1c6d00003baa8e7a3#SAPEngine_System_Thread[impl:5]_8##0#0#Warning#1#com.sap.sldserv.SldServerFrame#Plain###Communication configuration is incomplete. No data transfer possible until corrected.#

#1.5 #0003BAA8E7A300220000000000004EA90004C6C8E63838F5#1344466065045#/System/Server#sap.com/SQLTrace#com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents#Guest#0##n/a##11b3782be1ab11e1c51c0003baa8e7a3#SAPEngine_Application_Thread[impl:3]_30##0#0#Warning#1#com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents#Plain###application [OpenSQLMonitors] Cannot load Servlet com.sap.sql.ui.tabstat.TableStatisticsMonitorServlet

The error is: com.sap.engine.frame.core.load.SAPClassNotFoundException: com.sap.sql.ui.tabstat.TableStatisticsMonitorServletnull#

#1.5 #0003BAA8E7A300280000000000004EA90004C6C8E9DC0D04#1344466126107#/System/Server##com.sap.engine.services.deploy####n/a##3618cf39e1ab11e18e5d0003baa8e7a3#SAPEngine_System_Thread[impl:5]_75##0#0#Error#1#com.sap.engine.services.deploy#Java#deploy_5029#com.sap.engine.services.deploy.DeployResourceBundle#Exception in operation {0} with application {1}.#2#startApp#sap.com/tc~slm~interfaces#

#1.5 #0003BAA8E7A300280000000300004EA90004C6C8E9DC1FB5#1344466126118#/System/Server##com.sap.engine.services.deploy####n/a##3618cf39e1ab11e18e5d0003baa8e7a3#SAPEngine_System_Thread[impl:5]_75##0#0#Error#1#com.sap.engine.services.deploy#Plain###Operation startApp over application sap.com/tc~slm~interfaces finished with errors on server 309349150. For more detailed information see traces of Deploy Service.#

#1.5 #0003BAA8E7A300280000000500004EA90004C6C8E9E8CE8D#1344466126949#/System/Server##com.sap.engine.services.ejb.EJBAdmin####n/a##3618cf39e1ab11e18e5d0003baa8e7a3#SAPEngine_System_Thread[impl:5]_75##0#0#Warning#1#com.sap.engine.services.ejb.EJBAdmin#Plain###ejb-local-ref with ejb-ref-name ejb/sap.com/slm/JNetDataProviderBean cannot be linked. Please check values of tags!#

#1.5 #0003BAA8E7A300280000000600004EA90004C6C8E9EAC5A1#1344466127078#/System/Server##com.sap.engine.services.ejb.EJBAdmin####n/a##3618cf39e1ab11e18e5d0003baa8e7a3#SAPEngine_System_Thread[impl:5]_75##0#0#Warning#1#com.sap.engine.services.ejb.EJBAdmin#Plain###ejb-local-ref with ejb-ref-name ejb/sap.com/slm/SDCSPCallerBean cannot be linked. Please check values of tags!#

#1.5 #0003BAA8E7A300280000000700004EA90004C6C8EA39464A#1344466132223#/System/Server##com.sap.engine.services.deploy####n/a##3618cf39e1ab11e18e5d0003baa8e7a3#SAPEngine_System_Thread[impl:5]_75##0#0#Error#1#com.sap.engine.services.deploy#Java#deploy_5029#com.sap.engine.services.deploy.DeployResourceBundle#Exception in operation {0} with application {1}.#2#startApp#sap.com/tc~mobile~admin~ea#

#1.5 #0003BAA8E7A300280000000A00004EA90004C6C8EA395C46#1344466132229#/System/Server##com.sap.engine.services.deploy####n/a##3618cf39e1ab11e18e5d0003baa8e7a3#SAPEngine_System_Thread[impl:5]_75##0#0#Error#1#com.sap.engine.services.deploy#Plain###Operation startApp over application sap.com/tc~mobile~admin~ea finished with errors on server 309349150. For more detailed information see traces of Deploy Service.#

#1.5 #0003BAA8E7A300280000000C00004EA90004C6C8EA398EC3#1344466132241#/System/Server##com.sap.engine.services.deploy####n/a##3618cf39e1ab11e18e5d0003baa8e7a3#SAPEngine_System_Thread[impl:5]_75##0#0#Error#1#com.sap.engine.services.deploy#Java#deploy_5035#com.sap.engine.services.deploy.DeployResourceBundle#Application {0} cannot be started. Reason: it has hard reference to resource {1} with type {2}, which is not active on the server.#3#sap.com/tc~mobile~admin~ea#tc_SL_SDM_Client#library#

#1.5 #0003BAA8E7A300200000000100004EA90004C6C8EAB42C3B#1344466140266#/System/Server##com.sap.engine.services.deploy####n/a##3e8937e5e1ab11e18cf90003baa8e7a3#SAPEngine_System_Thread[impl:5]_39##0#0#Error#1#com.sap.engine.services.deploy#Java#deploy_5070#com.sap.engine.services.deploy.DeployResourceBundle#Already started operation with application {0} in the cluster. No other operation with this application is allowed at the moment.#1#sap.com/com.sap.engine.services.webservices.tool#

#1.5 #0003BAA8E7A300200000000400004EA90004C6C8EB15B914#1344466146670#/System/Server##com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)####n/a##3e8937e5e1ab11e18cf90003baa8e7a3#SAPEngine_System_Thread[impl:5]_39##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader library:tc~logging on the system, but will register reference for furture usage.#2#sap.com/tc~slm~slmapp#library:tc~logging#

#1.5 #0003BAA8E7A300280000000F00004EA90004C6C8EB16C4E1#1344466146737#/System/Server##com.sap.engine.services.deploy####n/a##3618cf39e1ab11e18e5d0003baa8e7a3#SAPEngine_System_Thread[impl:5]_75##0#0#Error#1#com.sap.engine.services.deploy#Plain###Error occurred while initially starting application sap.com/tc~mobile~admin~ea:Application sap.com/tc~mobile~admin~ea cannot be started. Reason: it has hard reference to resource tc_SL_SDM_Client with type library, which is not active on the server.#

#1.5 #0003BAA8E7A300200000000500004EA90004C6C8EB41AF85#1344466149551#/System/Server##com.sap.engine.services.ejb.EJBAdmin####n/a##3e8937e5e1ab11e18cf90003baa8e7a3#SAPEngine_System_Thread[impl:5]_39##0#0#Warning#1#com.sap.engine.services.ejb.EJBAdmin#Plain###ejb-local-ref with ejb-ref-name ejb/sap.com/slm/JNetDataProviderBean cannot be linked. Please check values of tags!#

#1.5 #0003BAA8E7A300200000000600004EA90004C6C8EB43E6F1#1344466149697#/System/Server##com.sap.engine.services.ejb.EJBAdmin####n/a##3e8937e5e1ab11e18cf90003baa8e7a3#SAPEngine_System_Thread[impl:5]_39##0#0#Warning#1#com.sap.engine.services.ejb.EJBAdmin#Plain#

#1.5 #0003BAA8E7A3002A0000000000004EA90004C6C8F62BF528#1344466332677#/System/Server/SLDService##com.sap.sldserv.SldServerFrame####n/a##b138cbb9e1ab11e1c6d00003baa8e7a3#SAPEngine_System_Thread[impl:5]_8##0#0#Warning#1#com.sap.sldserv.SldServerFrame#Plain###Communication configuration is incomplete. No data transfer possible until corrected.#

#1.5 #0003BAA8E7A3002B0000000100004EA90004C6C9D38E6778#1344470046893#/System/Server/WebRequests#sap.com/RSMEOnlineEAR#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#0##n/a##57111597e1b411e1a8d10003baa8e7a3#SAPEngine_Application_Thread[impl:3]_33##0#0#Error#1#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Plain###application [RSMEOnline] Processing HTTP request to servlet [invoker] finished with error.

The error is: java.lang.NullPointerException: null

Exception id: [0003BAA8E7A3002B0000000000004EA90004C6C9D38E6183]#

#1.5 #0003BAA8E7A3002C0000000100004EA90004C6C9D38E8BB2#1344470046903#/System/Server/WebRequests#sap.com/RSMEOnlineEAR#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#0##n/a##57128576e1b411e19cd20003baa8e7a3#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Plain###application [RSMEOnline] Processing HTTP request to servlet [invoker] finished with error.

The error is: java.lang.NullPointerException: null

Exception id: [0003BAA8E7A3002C0000000000004EA90004C6C9D38E8928]#

Any idea what this error means?

Thanks.

std_server0.out.txt.zip

[Former Member]

Hello

It seems that J2EE Engine Web Services Container Service has not started on the server node:

service webservices ================= ERROR =================

The new size of the heap is also full: ParNew: 261120K->87040K(261120K)

I suggest you that verify heap settings first using note 723909, please re-start the cluster and try to reproduce the issue. Is it reproducable? 

Kind regards