Skip to Content
author's profile photo Former Member
Former Member

JMX Connection Exception while clicking review in a Leave Request

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

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Dec 09, 2011 at 07:23 PM

    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

    Add a comment
    10|10000 characters needed characters exceeded

    • 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

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.