| Author |
Message
|
| jk |
 Posted: Thu Sep 07, 2006 5:55 am Post subject: MQ Channel remains active |
 |
|
Apprentice
Joined: 09 Jan 2002
Posts: 36
|
Hi,
I am using MQ 5.3 and MQ Classes for Java as my client. The client application is running on a Websphere 6.0.2 Application Server. The problem is that after the client application picks a message, closes the queue and disconnects the MQManager, the channel connection remains active and is never closed unless the application server shuts down. As new clients arrive, new channel connections are created but never closed until the max number of active connections is reached.
Any ideas why the channel remains open after calling the close and disconnect methods?
Thanks in advance |
|
| Back to top |
|
 |
| vennela |
| Posted: Thu Sep 07, 2006 8:33 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| I think you need to search for TCPKeepAlive and AdoptNewMCA in the forum and set them in your qm.ini (or wherever that's done depending on your MQ platform) |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Sep 07, 2006 4:39 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
AdoptNewMCA is only going to apply to non CLient channels, and I think JK is saying the SVRCONN channel (a client channel) is what's left hanging.
KeepAlive can help, but only if the connection really is orphaned.
| Quote: |
The problem is that after the client application picks a message, closes the queue and disconnects the MQManager, the channel connection remains active and is never closed unless the application server shuts down. |
Sounds to me that either you are not doing a succesful MQDISC as far as the QM is concerned, or you have some sort of connection pool, where you disconnect ends its "connection", but the connection really is maintained and thrown into a pool. And new instances don't dip into the pool, but rather make a new connection???
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Sep 07, 2006 5:58 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I just think you need to upgrade your MQ install to get the most recent version of the 5.3 Java classes....
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jk |
| Posted: Wed Sep 13, 2006 4:09 am Post subject: |
|
|
Apprentice
Joined: 09 Jan 2002
Posts: 36
|
Hi All,
thanks for the responses.
the problem is now fixed.
it was because the disconnect was not being called on the right QMgr object. A coding error that was overlooked for such a long time
Thanks |
|
| Back to top |
|
|
| MQSDevr |
| Posted: Thu Oct 05, 2006 3:44 am Post subject: It happens to all of us =) |
|
|
Newbie
Joined: 05 Oct 2006
Posts: 1
Location: South Africa
|
Hi,
Had the same error, it was an instance of the connection object not being terminated as it was declared twice and the incorrect one closed.
Take care. |
|
| Back to top |
|
|
|
|
