| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| com.ibm.mq.jmqi.JmqiException: CC=2;RC=2009;AMQ9208 |
« View previous topic :: View next topic » |
| Author |
Message
|
| kalam475 |
 Posted: Sun Jan 16, 2022 11:45 pm Post subject: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2009;AMQ9208 |
 |
|
Acolyte
Joined: 16 Jan 2015
Posts: 63
|
We are connecting to IBM MQ from JBOSS using the CCDT file and it will connect to one queue manger which is a part of cluster having 2 full repositories and 2 half & load gets divided into 4 cluster queues. every now and then we are getting the RC=2009. I know it can be of many varied reason from the logs we can deduce some kind of timeout is happening.
I. Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2009;AMQ9208: Error on receive from host '/10.1.18.95:1414 (10.1.18.95)'. [1=-1,2=ffffffff,3=/10.1.18.95:1414 (10.1.18.95),4=TCP]
III. com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ2000: Failed to close queue 'CHGPKG.VALIDATIONREQUEST'.
JMS attempted to close a WebSphere MQ destination, but encountered an error. The destination might already be closed, or another thread may be performing an MQGET while close() is called.
from the above log we can see someone is closing the connection before it is closed in systematic manner.
In MQ error logs we can see
IV. AMQ9209: Connection to host 'plaeaiwalta134 (10.1.50.134)' for channel 'CQM1.SVRCONN' closed.
V. An error occurred receiving data from '10.1.52.43' over TCP/IP. The connection
to the remote host has unexpectedly terminated
TCP/IP connection to channel is getting closed.
Using the MQ V8.0
Can you please guide from where to start the debugging and possible causes of socket timeout we are experiencing. |
|
| Back to top |
|
 |
| hughson |
| Posted: Mon Jan 17, 2022 1:09 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1967
Location: Bay of Plenty, New Zealand
|
You appear to be suffering from a network blip. An outage, even just for a very short time, can take out the socket. When your socket is lost, the channel which is using it closes. This results in the connection, which is communicating over that channel also being closed, and so any attempt to close it again, will result in the error you are seeing.
Talk to your network administrator. Or just reconnect and carry on. Network blips are a fact of life with TCP/IP networks.
Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
