Operating System - HP-UX
1845948 Members
3234 Online
110250 Solutions
New Discussion

Re: Timed out issue in the java client side

 
Siva_13
Occasional Advisor

Timed out issue in the java client side

Hi,

We are using the java application which tries to connect SonicMQ broker5.0 running on WinNT in order to retrieve the output from the server.

We are getting the following exceptions often when we tried to contact the Sonic MQ broker.

at java.lang.Object.wait(Native Method)
- waiting on <68dcfbd8> (a java.lang.Object)
at java.lang.Object.wait(Object.java:429)
at progress.message.zclient.ClientSender.threadMain(:942)
- locked <68dcfbd8> (a java.lang.Object)
at progress.message.zclient.DebugThread.run(:56)

Could you please help me out to solve this issue.Thanks in advance.

Best Regards,
Siva G.
2 REPLIES 2
sajjan
Occasional Advisor

Re: Timed out issue in the java client side

If you are using java sockets to connect to the server,try to set the time out period in code itself(in clinet side itself).

Sajjan
Siva_13
Occasional Advisor

Re: Timed out issue in the java client side

Hi Sajjan,

Thanks for your reply.We have not used Socket connectivity mechanism.Our producer(user application) has logic to timeout the requests. Time out is the property which can be configurable at the producer end.

To give a background of our project, we are using SonicMQ Enterprise Edition Plus (Version 5.0) in to send and recieve messages using a non-transacted queue. The consumer of messages process the messages and send the response back to the producer. In our production environment the number of requests processed are about 10000 per day approximately. The consumer is a sophasticated java server.

The give you a clear picture of the project, our producer send/receive messages by creating a QueueSession with the help of QueueConnection, then it creates the queue, through which it sends the request to consumer. The consumer creates a queue with the same name as producer side and waits for incoming messages. On receiving the request, the consumer processes the request and replies using temporary queue created automatically by the producer by making use of the JMSReplyTo method in the TextMessage class.

We would like to bring to your notice that recently we upgraded our producer JRE version from 1.3 to 1.4 which uses the SonicMQ client libraries. We did not face this issue while using JRE 1.3. Also we would like to know whether it is an issue at the producer end or broker end. If so, can please let us know how to tackle this for both the cases (either in producer or broker).


We are using following JRE versions in production environment.
Consumer Side : JRE 1.3
Broker Side : JRE 1.3
Producer Side : JRE 1.4

The producer sends and receives the messages using the Sonic MQ broker (which in turn contact the consumer for processing the input request).The problem we are facing is in our production environment is that the requests are timed out at the producer side with the following error message.

ClientSender tux442_4000$CONNECTION$ pdapi" prio=10 tid=00046cb0 nid=219 lwp_id=4995795 in Object.wait() [0x62feb000..0x62feb4f0]
at java.lang.Object.wait(Native Method)
- waiting on <68dcfbd8> (a java.lang.Object)
at java.lang.Object.wait(Object.java:429)
at progress.message.zclient.ClientSender.threadMain(:942)
- locked <68dcfbd8> (a java.lang.Object)
at progress.message.zclient.DebugThread.run(:56)

When we tried to replicate this secenario in our development environment, we did not get the above error but a different timeout error corresponding to the consumer error.

Could you please throw some light on this issue, to resolve the same.Thanks in advance.

Best Regards,
Siva G.