| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQJI027: The queue has been closed |
« View previous topic :: View next topic » |
| Author |
Message
|
| Al Pacino |
 Posted: Fri Dec 15, 2006 9:25 am Post subject: MQJI027: The queue has been closed |
 |
|
Centurion
Joined: 19 Aug 2005
Posts: 114
|
Hi there ,
We have xmitter which uses 2 servers through a load-balancer , the xmitter puts messages on remote queues on either server 1 or 2 . On server 1 , the xmitter is putting the message on the remote queue fine , however when it tries to put a message on the remote queue on server 2 , we get the following error :
12/15/2006; 12:15:12] transmitOrders Exception on cust=90005437 order= 1619534 Message=MQException writing message for order=1619534 cust=90005437
Msg=MQJE001: An MQException occurred: Completion Code 2, Reason 2019
MQJI027: The queue has been closed
Both remote queues are set up the same way and not sure where the problem is. We are using 5.3 CSD 10 on Windows 2003 , any advices are appreciated.
_________________
"We can't solve problems by using the same kind of thinking we used
when we created them." |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Dec 15, 2006 9:31 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Upgrade both client machines to CSD12. Java is buggy in several CSDs lower than that.
Secondly, make sure that you're using connections in the right threads in the right way.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Al Pacino |
| Posted: Fri Dec 15, 2006 9:58 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2005
Posts: 114
|
It would nice I can just upgrade the CSD level , but it is not that simple. I am trying to figure what can cause such an issue to happen for one server but not other when you have the same exact remote queues on both with the same configuration and connection.. etc
_________________
"We can't solve problems by using the same kind of thinking we used
when we created them." |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Fri Dec 15, 2006 11:17 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
It could be anything. I feel sure that the MQ configuration isn't the issue here. Looks more like clonky applications code to me.
Are both applications identical? Did a thread crap out on one box? Is it always the same record that causes the error? Can you redrive that same message on the other machine? What is the CPU/Memory usage like on the 'bad' box compared with the other box? Any FDC's cut? Any thing in the event logs? Any monitoring software getting involved (network and MQ)?
There are going to be lots of areas to investigate.  |
|
| 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
|
|
|
|
