Jms queue error weblogic.jms.common.jmsexception

Rated 3.97/5 based on 511 customer reviews

The IBM Web Sphere MQ Reason Code 2009 (MQRC_CONNECTION_BROKEN) may occur when an application tries to connect to a Web Sphere MQ queue manager. Preventing the firewall from terminating connections Configure the Connection Pool and Session Pool settings for the QCF that is configured in Web Sphere Application Server so that Web Sphere can remove connections from the pool before they are dropped by the firewall.Often this occurs when the Application Server tries to use an MQ connection is QCF pool. An explicit action caused the socket to be closed by one end. Change the value of Min Connections to 0 and set the Unused Timeout to half the number of seconds as the firewall timeout.

jms queue error weblogic.jms.common.jmsexception-81

Consider an integration test where one sends a message to a distributed destination and would have to create X queue browsers to determine whether or not the message is present.

A connection broken error could be caused by the firewall not letting the keepalive packets through.

An explicit action can cause this An action such as stopping the queue manager or restarting the queue manager would also cause Reason Code 2009.

What that means is that a Queue Browser created for a distributed destination will only be able to browse messages on the member it gets pinned to and not the whole queue.

One can try to create X number of queue browsers based of the number of servers in the provider URL, for example, "t3://localhost:8002, localhost:8003", and hope that no two queue browsers will pin to the same destination, i.e., at the mercy of Weblogic round robin if possible.

Leave a Reply