cancel
Showing results for 
Search instead for 
Did you mean: 

"Unable to de-serialize response" exception when quering mbeans

Former Member
0 Kudos

Does anybody know what does it mean?

Thanks

-


Unable to de-serialize response, message [ JMX exception (java) v1.0 | | com.sap.engine.services.jmx.exception.JmxConnectorException: Sending message synchronously failed, target node 4001, message [ JMX request (java) v1.0 len: 149 | src: 2 target-node: 4001 req: queryNames params-number: 2 params-bytes: 0 | ] ]

com.sap.engine.services.jmx.exception.JmxConnectorException: Unable to de-serialize response, message [ JMX exception (java) v1.0 | | com.sap.engine.services.jmx.exception.JmxConnectorException: Sending message synchronously failed, target node 4001, message [ JMX request (java) v1.0 len: 149 | src: 2 target-node: 4001 req: queryNames params-number: 2 params-bytes: 0 | ] ]

at com.sap.engine.services.jmx.ClusterInterceptor.queryNames(ClusterInterceptor.java:1031)

at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:109)

at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:58)

at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:268)

at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:165)

at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:102)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)

at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello,

I have the same problem after the SP2 -> SP9 migration.

Do you have any idea about how to solve it?

Best regards

Mert

Former Member
0 Kudos

Hi,

That's Probably you using the worng Objectname when trying to connect.

Pleace put the query code so i can look at it.

Regards,

Pavel Sheynkman.

SAP BASIS Consultant.

Former Member
0 Kudos

Hi Pavel,

have the same problem with SP15.

java.lang.reflect.UndeclaredThrowableException

at $Proxy1.deploy(Unknown Source)

at com.sap.engine.services.deploy.gui.DeployingTask.run(DeployingTask.java:133)

at java.lang.Thread.run(Thread.java:770)

Caused by: com.sap.engine.services.jmx.exception.JmxConnectorException: Sending message synchronously failed, target node 6663450, message [ JMX request (java) v1.0 len: 575 | src: 2 target-node: 6663450 req: invoke params-number: 4 params-bytes: 0 | ]

at com.sap.engine.services.jmx.JmxServiceConnectorServerInvoker.invokeMbs(JmxServiceConnectorServerInvoker.java:65)

at com.sap.engine.services.jmx.MessageClientSecurityWrapper.invokeMbs(MessageClientSecurityWrapper.java:39)

at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:196)

at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)

at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)

at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)

at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)

at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)

at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)

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(AccessController.java:219)

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

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

Caused by: com.sap.engine.frame.cluster.message.ResponseTimedOutException: Participant 6,663,450 did not return a response in the specified timeout of 100,000 ms.

at com.sap.engine.core.cluster.impl6.lazy.AnswerObject.getResult(AnswerObject.java:88)

at com.sap.engine.core.cluster.impl6.lazy.LazyConnection.sendRequest(LazyConnection.java:223)

at com.sap.engine.core.cluster.impl6.lazy.LazyConnectorImpl.sendRequest(LazyConnectorImpl.java:171)

at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.ms_sendRequest(ClusterManagerImpl.java:2449)

at com.sap.engine.core.service630.context.cluster.message.MessageContextImpl.sendAndWaitForAnswer(MessageContextImpl.java:93)

at com.sap.engine.services.jmx.JmxFrame.sendAndWaitForAnswer(JmxFrame.java:695)

at com.sap.engine.services.jmx.JmxServiceConnectorServerInvoker.invokeMbs(JmxServiceConnectorServerInvoker.java:47)

... 15 more

this happens when deploy an one of our company application within Visual Admin.

Thanks in advanced,

alfseins