JMX Connection Exception while clicking review in a Leave Request

[Former Member]

Hi All,

This might well seem so ODD. But this happening.

We have one ESS user, whose leave request application after clicking the Review button in the first Page is throwing the

INTERNAL SERVER ERROR 500.

Upon investigation, I found the below exeption for that server instance:

Com.sap.engine.services.jmx.exception.JmxConnectorException: Sending message synchronously failed, target Node XXXXXX [JMX request (java) v1.0 len:500| src: cluster target node

In turn, it throws the below mentioned Timed out exception:

 Com.sap.engine.frame.cluster.message.ResponseTimedOutException: Participant XXXXX did not return a response in the specified timeout of 100,000 ms

And hence the Internal Server error 500.

Any guess, what might be the problem witht he JMX Connection?

Anybody faced a similar issue?

We are in NW Portal 7.0 with Java WD based ESS.

BR,

Uday

[Former Member]

Rama,

The exception "ResponseTimedOutException: Participant XXXXX did not return..." indicates that a request was send to another server node, with ID XXXXX. You should investigate in the log files of the server node what happened.

It could be that the request takes more than 100 seconds to process, and you need to increase the timeout.

Or it could be that some error occures during the processing of the request, and a response is never returned.

The exception is generic and from the information that you provided it is not possible to tell.

Regards,

Ventsi Tsachev

[Former Member]

Thanks Ventsi for the quick reply,

As explained in my earlier post, the Server Node is throwing a JMX error first and then in turn, the same node throws this TImed out Error, since no info from the JMX architecture within the stipulated Response TIme out Setting.

As it is very clear as of now that, the actual issue occurs in JMX, any idea, how to analze further in uncovering the issue?

BR,

Uday