JMSException:weblogic.rjvm.PeerGoneException

Rigga

Hi

Whenever we have network fault between message producer and consumer we get following exception :

JMSException:weblogic.messaging.dispatcher.DispatcherException: weblogic.rjvm.PeerGoneException: No message was received for: '240' seconds

We are using Websphere MQ 7 on Solaris.
We have included wlthint3client.jar in our classpath.

It takes 240 seconds to report the fault.

How can we configure this this?
How can we reduce it to 2 mins?

The error which we are getting is for t3 connection.
I guess we need to set the property of this connection but how that I am not sure.
JMS provider is WMQ7 on Solaris.
We have included wlthint3client.jar in our classpath.
The exception which we are getting is correct although misleading

I am new to websphere MQ.


Please let me know if I have missed something.

Nigel Deakin-Oracle

906163 wrote:
Hi

Whenever we have network fault between message producer and consumer we get following exception :

JMSException:weblogic.messaging.dispatcher.DispatcherException: weblogic.rjvm.PeerGoneException: No message was received for: '240' seconds

We are using Websphere MQ 7 on Solaris.
We have included wlthint3client.jar in our classpath.

It takes 240 seconds to report the fault.

How can we configure this this?
How can we reduce it to 2 mins?

The error which we are getting is for t3 connection.
I guess we need to set the property of this connection but how that I am not sure.
JMS provider is WMQ7 on Solaris.
We have included wlthint3client.jar in our classpath.
The exception which we are getting is correct although misleading

I am new to websphere MQ.

Are you trying to access IBM's WebSphere MQ from an application running in Oracle's WebLogic application server? This forum is for general JMS questions. Please ask in a forum specific to one of those products. The Oracle WebLogic JMS forum is at 3833

Nigel

Rigga

Thanks.

I am new to this forum so I was not aware of it.