Skip to Content
0
Former Member
Apr 06, 2008 at 07:17 AM

PRTMessageListenerException: The listener does not exist

58 Views

Hi All,

We are running EP 7.0 NWO4s on Windows 2003. When the user log on to the portal with the valid qualified URL geting an " 500 Internal Server error with java.lang.null pointer exception message" Before the restart of the server every user able to access the portal properly. But after the restart of the server we are facing this problem. Few months back also we faced the same problem but it is fixed automitically in our next restart of our server. But this time even though how many times we are restarting of the server still the problem exists.

1. The Server is up and running

2. All the J2EE process are running properly

3. Oracle database is up and running

On the Defaulttrace file we noticed few exceptions

-


com.sap.portal.prt.sapj2ee.api.clustercommunication.exceptions.PRTMessageListenerException: The listener does not exist !

com.sap.engine.services.servlets_jsp.server.exceptions.WebUnavailableException: Servlet prt is currently unavailable.

Timeout Service Synchronous Internal Thread: javax.management.InstanceNotFoundException

Processing HTTP request to servlet gateway finished with error.The error is: java.lang.NullPointerException: null

Caused by: javax.servlet.UnavailableException: Initialization of Dispatcher failed

Defaulttrace file Information:

#1.5#00188B874AFD002100000505000023E80004474C5F840A13#1204293252562#

com.sap.engine.services.monitor.common.Template##com.sap.engine.services.monitor.common.Template######

a68a3f70e4d411dcc2e100188b874afd#Timeout Service Synchronous Internal Thread##0#0#Warning##Plain###

javax.management.InstanceNotFoundException: com.sap.default:name=ComponentRuntimeMBean,

SAP_J2EEApplicationPerNode=sap.com/com.sap.netweaver.bc.rf.moni,j2eeType=SAP_ApplicationResourcePerNode,

SAP_J2EEClusterNode=18025994,SAP_J2EECluster=ANV not in repository

at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1291)

at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)

at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:309)

at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getAttribute(BasicMBeanServerInterceptor.java:169)

at com.sap.jmx.provider.ProviderInterceptor.getAttribute(ProviderInterceptor.java:195)

at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)

at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)

at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:234)

at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:522)

at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)

at com.sap.engine.services.monitor.mbeans.Template.pollDynamicData(Template.java:891)

at com.sap.engine.services.monitor.mbeans.Template.handleNotification(Template.java:847)

at com.sap.engine.services.jmx.server.AscynchronousProxyListener.handleNotification(AscynchronousProxyListener.java:51)

at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:94)

at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:61)

at com.sap.engine.services.jmx.timer.j2ee.Timer.sendTimerNotification(Timer.java:432)

at com.sap.engine.services.jmx.timer.j2ee.TimerNotificationEntry.timeout(TimerNotificationEntry.java:69)

at com.sap.engine.services.timeout.TimeoutNode.synchronousRun(TimeoutNode.java:72)

at com.sap.engine.services.timeout.TimeoutManagerImpl.singleThreadRun(TimeoutManagerImpl.java:632)

at com.sap.engine.services.timeout.TimeoutManagerRunner.run(TimeoutManagerRunner.java:18)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)

#

#1.5#00188B874AFD00610000000A000023E80004474C946ED4C0#1204294140410#com.sap.engine.services.prtbridge##

com.sap.engine.services.prtbridge######b8f36600e65511dc9d3000188b874afd#SAPEngine_System_Threadimpl:5

_105##0#0#Error#1#/System/Server#Java###An Error has been occured during PRTBridge operation

EXCEPTION

#1#

com.sap.portal.prt.sapj2ee.api.clustercommunication.exceptions.PRTMessageListenerException: The listener does not exist !

(NotificationSAPJ2EE630)

at com.sap.portal.prt.sapj2ee.core.clustercommunication.MessageContextWrapper.distributeMessage(MessageContextWrapper.java:373)

at com.sap.portal.prt.sapj2ee.bridge.PRTBridgeAccessor.distributeMessage(PRTBridgeAccessor.java:228)

at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.receive(PRTBridgeCommunicationManager.java:568)

at com.sap.engine.core.service630.context.cluster.message.MessageListenerWrapper.process(MessageListenerWrapper.java:126)

at com.sap.engine.core.cluster.impl6.ms.MSMessageQueue.process(MSMessageQueue.java:77)

at com.sap.engine.core.cluster.impl6.ms.MSMessageThread.run(MSMessageThread.java:37)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)

#

#1.5#00188B874AFD003500000030000023E8000447700BC25D6F#1204446466108#

com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#

sap.com/irj#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#

Guest#2####8920f6c0e83211dc960400188b874afd#SAPEngine_Application_Threadimpl:3_4

##0#0#Error#1#/System/Server/WebRequests#Plain###

Processing HTTP request to servlet gateway finished with error.

The error is: java.lang.NullPointerException: null

Exception id: 00188B874AFD00350000002E000023E8000447700BC25C4C#

#1.5#00188B874AFD00560000003E000023E8000447700C764EBA#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain###com.sapportals.portal.prt.dispatcher.DispatcherException: Previous dispatcher initialization failed. Check logs for details.#

#1.5#00188B874AFD00560000003F000023E8000447700C76505A#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:257)#

#1.5#00188B874AFD005600000040000023E8000447700C76509D#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:213)#

#1.5#00188B874AFD005600000041000023E8000447700C7650DA#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.access$300(Dispatcher.java:42)#

#1.5#00188B874AFD005600000042000023E8000447700C765116#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:437)#

#1.5#00188B874AFD005600000043000023E8000447700C765151#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#

#1.5#00188B874AFD005600000044000023E8000447700C765192#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)#

#1.5#00188B874AFD005600000045000023E8000447700C7651CE#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#

#1.5#00188B874AFD005600000046000023E8000447700C765209#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)#

#1.5#00188B874AFD005600000047000023E8000447700C765247#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#

#1.5#00188B874AFD005600000048000023E8000447700C765282#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)#

#1.5#00188B874AFD005600000049000023E8000447700C7652BF#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)#

#1.5#00188B874AFD00560000004A000023E8000447700C7652FB#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)#

#1.5#00188B874AFD00560000004B000023E8000447700C765338#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)#

#1.5#00188B874AFD00560000004C000023E8000447700C765374#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)#

#1.5#00188B874AFD00560000004D000023E8000447700C7653B6#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)#

#1.5#00188B874AFD00560000004E000023E8000447700C7653F3#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)#

#1.5#00188B874AFD00560000004F000023E8000447700C76542E#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)#

#1.5#00188B874AFD005600000050000023E8000447700C76546A#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)#

#1.5#00188B874AFD005600000051000023E8000447700C7654AA#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)#

#1.5#00188B874AFD005600000052000023E8000447700C7654E8#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#

#1.5#00188B874AFD005600000053000023E8000447700C765522#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#

#1.5#00188B874AFD005600000054000023E8000447700C76555C#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#

#1.5#00188B874AFD005600000055000023E8000447700C765598#1204446477889#System.err#sap.com/irj#System.err#Guest#2####90290b10e83211dccc4800188b874afd#SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#

#1.5#00188B874AFD005600000056000023E8000447700C765C20#1204446477905#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/irj#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#Guest#2####90290b10e83211dccc4800188b874afd#

SAPEngine_Application_Threadimpl:3_11##0#0#Error##Plain###

Processing HTTP request to servlet invoker finished with error.

The error is:

com.sap.engine.services.servlets_jsp.server.exceptions.WebUnavailableException: Servlet prt is currently unavailable.

at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:174)

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: javax.servlet.UnavailableException: Initialization of Dispatcher failed

at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:371)

at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:213)

at com.sapportals.portal.prt.dispatcher.Dispatcher.access$300(Dispatcher.java:42)

at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:437)

at java.security.AccessController.doPrivileged(Native Method)

at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)

Please help us to resolve this issue. Its a bit urgent for us. Your suggestions and views would be highly appreciable.

Thanks

Ravi