On 11-06-08 02:21 PM, forums_at_java.net wrote:
> Am I right cluster should restore in case of failure?
yes.
> What can be the reason
> of refused connections?
The below ConnectException looks like the broker is not running. Please
check the broker log and GlassFish server log if running in GlassFish.
> Is it good practice to stop-start
> connection-session-producer in case of any JMS exception?
>
Connection.stop only stops message delivery to consumers in your
application. Depending on the cause of exception and location, you
may want to close/recreate the connection. Please see more information
on exception handling in MQ Java Developer's Guide,
http://download.oracle.com/docs/cd/E18930_01/html/821-2440/gcbkz.html
http://download.oracle.com/docs/cd/E18930_01/html/821-2440/aeqdx.html#gczqs
amy
> Logs contain the following exceptions:
>
> On producing side
>
> JMSException: [C4001]: Write packet failed. - cause:
> java.net.SocketException: Broken pipe
>
> [C4003]: Error occurred on connection creation [192.168.0.156:27677]. -
> cause: java.net.ConnectException: Connection refused
>
> [I500]: Caught JVM Exception: java.net.SocketException: Socket closed
>
> javax.jms.IllegalStateException: [C4059]: Cannot perform operation,
> session
> is closed.
>
>
>
> Exception occurred while trying to connect to peer server's machine :
> Connection refused
>
> On receiving side
>
> [C4001]: Write packet failed. - cause: java.net.SocketException: Socket
> closed
>
> [C4063]: Cannot perform operation, consumer is closed.
>
>
>
>
> --
>
> [Message sent by forum member 'alex2001']
>
> View Post: http://forums.java.net/node/810856
>
>