Server Startup Problem

Former Member · ‎2006 Feb 23

Hi all,

The server was working fine previously.Webdynpro applications and portal were also being deployed succesfully.

But now when i try to start the server it is getting hung in the final stage of the process.I've checked the log files, it is giving some exception as follows.Please help me with this to resolve the issue.

************************************************

#1.5#00065BCCFF6E001B00000001000008A800040C6E62A3462F#1139568147749#com.sap.engine.services.jmx.MBeanServerInvoker##com.sap.engine.services.jmx.MBeanServerInvoker#######SAPEngine_System_Thread[impl:6]_20##0#0#Warning#1#/System/Server#Java###JMX connector exception occurred while processing external JMX request [ JMX request (java) v1.0 len: 314 | src: cluster target-node: 5957900 req: invoke params-number: 4 params-bytes: 0 | :name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=5957900,SAP_J2EECluster="" null null null ]

[EXCEPTION]

#1#com.sap.engine.services.jmx.exception.JmxConnectorException: Unable to de-serialize request parameters, message [ JMX request (java) v1.0 len: 314 | src: cluster target-node: 5957900 req: invoke params-number: 4 params-bytes: 0 | :name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=5957900,SAP_J2EECluster="" null null null ]

at com.sap.engine.services.jmx.RequestMessage.readParams(RequestMessage.java:526)

at com.sap.engine.services.jmx.RequestMessage.getParams(RequestMessage.java:575)

at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:106)

at com.sap.engine.services.jmx.JmxServiceConnectorServer.receiveWait(JmxServiceConnectorServer.java:173)

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

at com.sap.engine.core.cluster.impl6.ms.MSListenerThread.run(MSListenerThread.java:47)

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

at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:72)

at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:142)

Caused by: javax.management.InstanceNotFoundException: MBean with name com.sap.default:name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=5957900,SAP_J2EECluster=J2E not found in repository

at com.sap.pj.jmx.server.MBeanServerImpl.getClassLoaderFor(MBeanServerImpl.java:1408)

at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getClassLoaderFor(MBeanServerWrapperInterceptor.java:455)

at com.sap.engine.services.jmx.CompletionInterceptor.getClassLoaderFor(CompletionInterceptor.java:567)

at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getClassLoaderFor(BasicMBeanServerInterceptor.java:438)

at com.sap.jmx.provider.ProviderInterceptor.getClassLoaderFor(ProviderInterceptor.java:327)

at com.sap.engine.services.jmx.RedirectInterceptor.getClassLoaderFor(RedirectInterceptor.java:501)

at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getClassLoaderFor(MBeanServerInterceptorChain.java:443)

at com.sap.engine.services.jmx.RequestMessage.readParams(RequestMessage.java:520)

...

Former Member · ‎2007 Aug 29

Try this.

Log into the visual admininistrator with an administrator user.

On the left side, navigate to server - services - Log Configuration

Raise the severity of location "com.sap.engine.services.servlets_jsp.Deploy" to "ALL".

On the left side, navigate to server - services - deploy.

On the right side, choose applications.

Stop the application "com.sap.security.core.admin" and start it again. The start should finish successfully.

-Pankaj

Former Member · ‎2007 May 17

It turns out, after we deactivate debugging (Config tool -> cluster -> instance -> server -> debug tab -> un-check Debuggable services), the error disappears and the system starts up correctly.

Former Member · ‎2007 May 17

I'm experiencing the exact same problem. Our portal was working fine. One of the developers asked me to turn on debugging for him in the configtool and ever since then our J2EE has been unable to startup properly.

Basically, in MMC all nodes are green. In the dev_dispatcher file, it says the Server0 is up and running. However, when we hit the default home page, we get the "dispatcher running but no server connected error".

There are no errors in the work directory. The only error I see is in the default trace for the dispatcher. Which is the following error:

Date : 05/17/2007

Time : 9:23:26:837

Message : JMX connector exception occurred while processing external JMX request [ JMX request (java) v1.0 len: 314 | src: cluster target-node: 4131600 req: invoke params-number: 4 params-bytes: 0 | :name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=4131600,SAP_J2EECluster="" null null null ]

[EXCEPTION]

com.sap.engine.services.jmx.exception.JmxConnectorException: Unable to de-serialize request parameters, message [ JMX request (java) v1.0 len: 314 | src: cluster target-node: 4131600 req: invoke params-number: 4 params-bytes: 0 | :name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=4131600,SAP_J2EECluster="" null null null ]

at com.sap.engine.services.jmx.RequestMessage.readParams(RequestMessage.java:537)

at com.sap.engine.services.jmx.RequestMessage.getParams(RequestMessage.java:586)

at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:90)

at com.sap.engine.services.jmx.JmxServiceConnectorServer.receiveWait(JmxServiceConnectorServer.java:172)

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

at com.sap.engine.core.cluster.impl6.ms.MSListenerThread.run(MSListenerThread.java:47)

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

at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)

at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)

Caused by: javax.management.InstanceNotFoundException: MBean with name com.sap.default:name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=4131600,SAP_J2EECluster=EPL not found in repository

at com.sap.pj.jmx.server.MBeanServerImpl.getClassLoaderFor(MBeanServerImpl.java:1408)

at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getClassLoaderFor(MBeanServerWrapperInterceptor.java:455)

at com.sap.engine.services.jmx.CompletionInterceptor.getClassLoaderFor(CompletionInterceptor.java:576)

at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getClassLoaderFor(BasicMBeanServerInterceptor.java:438)

at com.sap.jmx.provider.ProviderInterceptor.getClassLoaderFor(ProviderInterceptor.java:330)

at com.sap.engine.services.jmx.RedirectInterceptor.getClassLoaderFor(RedirectInterceptor.java:501)

at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getClassLoaderFor(MBeanServerInterceptorChain.java:443)

at com.sap.engine.services.jmx.RequestMessage.readParams(RequestMessage.java:531)

... 8 more

Severity : Warning

Category : /System/Server

Location : com.sap.engine.services.jmx.MBeanServerInvoker

Application :

Thread : SAPEngine_System_Thread[impl:6]_36

Datasource : 1179410029012:D:\usr\sap\EPL\JC00\j2ee\cluster\dispatcher\log\defaultTrace.trc

Message ID : 00188B735FE3001C0000000100000E8C000430AA5F36B4C0

Source Name : com.sap.engine.services.jmx.MBeanServerInvoker

Argument Objs : com.sap.engine.services.jmx.exception.JmxConnectorException: Unable to de-serialize request parameters, message [ JMX request (java) v1.0 len: 314 | src: cluster target-node: 4131600 req: invoke params-number: 4 params-bytes: 0 | :name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=4131600,SAP_J2EECluster="" null null null ]