Author |
Message
|
vsk |
Posted: Wed Oct 22, 2003 6:19 am Post subject: Messages getting stuck in transmission queue |
|
|
Novice
Joined: 25 Apr 2003 Posts: 24
|
We have a MQ sender channel setup between our Queue Manager and the Client Queue Manager. The MQ setup on both production and development is exactly the same . Only the names for channels and Queue Managers are different.
We have been sending messages in development environment and the messages flow through fine. But in production the messages get stuck in our transmission queue at sporadic intervals. The disconnect interval for the MQ sender channel is 10 mins.
Here is the scenario
=============
We send 5 messages , MQ channel starts up and the messages are sent across. Again after 2 mins say , we send another chunk of 4 messages. Due to some unidentified problem either in network or MQ the MQ cannel gets ended abnormally(this is from the MQ error logs) and these messages dont get out of our transmission Queue. Again 2 more new messages arrive which trigger the MQ channel. Now the prvious 4 messages and the 2 new messages get sent out without any problems. This happens at sporadic intervals through out the day.
We think that it is a networking issue and had put sniffers throught the network but didn't find anything yet in the sniffer trace that say's the network is down during that time the channel ends abnormally. Also we confirmed with the client that their receiver channel is up all the time.
If anyone has gone through this ,or know the solution please help.
Below is the snapshot from the MQ error log.
AMQ9202: Remote host 'tandem (11.15.16.17)'not
available, retry later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host
'tandem (11.15.16.17) (1414)' was not successful. However the
error may be a transitory one and it may be possible to successfully allocate a
TCP/IP conversation later.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is
145 (X'91'). The reason for the failure may be that this host cannot reach the
destination host. It may also be possible that the listening program at host
'tandem(11.15.16.17) (1414)' was not running. If this is the
case, perform the relevant operations to start the TCP/IP listening program,
and try again.
----- amqccita.c : 973 --------------------------------------------------------
10/22/03 09:39:28
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'ABC.C1' ended abnormally. |
|
Back to top |
|
 |
Michael Dag |
Posted: Wed Oct 22, 2003 6:58 am Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
Quote: |
Here is the scenario
=============
We send 5 messages , MQ channel starts up and the messages are sent across. Again after 2 mins say , we send another chunk of 4 messages. Due to some unidentified problem either in network or MQ the MQ cannel gets ended abnormally(this is from the MQ error logs) and these messages dont get out of our transmission Queue. Again 2 more new messages arrive which trigger the MQ channel. Now the prvious 4 messages and the 2 new messages get sent out without any problems. This happens at sporadic intervals through out the day |
This IMHO is exactly what MQSeries (oops... WebSphere MQ) is for!
With regard to your problem... is there a firewall involved, killing tcp sessions and thus killing your channels for no apparent MQ reason? (just a guess....)
Michael |
|
Back to top |
|
 |
vsk |
Posted: Wed Oct 22, 2003 7:05 am Post subject: |
|
|
Novice
Joined: 25 Apr 2003 Posts: 24
|
There is a firewall involved but from the sniffer traces we have there doesn't seem to be any kind of problem. We put sniifer at all the possible places we could but didn't find any disconnect. |
|
Back to top |
|
 |
Michael Dag |
Posted: Wed Oct 22, 2003 7:17 am Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
what is the 'disconnect' idle sessions parameter on your firewall? I have heard this many times (that's why I thought of the firewall in the first place). The firewall will clean up as much as possible and if the interval on your firewall is less then the interval on your channel, your channel gets 'killed'... |
|
Back to top |
|
 |
vsk |
Posted: Wed Oct 22, 2003 7:36 am Post subject: |
|
|
Novice
Joined: 25 Apr 2003 Posts: 24
|
The sender channel disconnect interval is 10 mins and the firewall idle session disconnect interval is 90 mins. |
|
Back to top |
|
 |
vsk |
Posted: Wed Oct 22, 2003 1:04 pm Post subject: |
|
|
Novice
Joined: 25 Apr 2003 Posts: 24
|
Just to add the HBINT value is 300.
And production configuration is same as in development
Thanks,
Vinayak |
|
Back to top |
|
 |
|