ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » Channel not restarting fast enough

Post new topic  Reply to topic Goto page Previous  1, 2, 3  Next
 Channel not restarting fast enough « View previous topic :: View next topic » 
Author Message
MichaelDNeale
PostPosted: Wed Nov 10, 2004 5:32 pm    Post subject: Reply with quote

Novice

Joined: 10 Nov 2004
Posts: 13

Thanks for you help.

Is there a place I can see the Admin guide (I have noticed you mentioned it a few times in other places, but have been unable to find it).

csmith28 wrote:
Yes, you may want to investigate the AdoptNewMCA setting that can be placed in the qm.ini file for the remote mqmanager.

See the MQSeries System Administration Guide.
Back to top
View user's profile Send private message
csmith28
PostPosted: Wed Nov 10, 2004 5:39 pm    Post subject: Reply with quote

Grand Master

Joined: 15 Jul 2003
Posts: 1196
Location: Arizona

At the top of this page click on the repository drop down and select documentation or you can download the Admin Guide in .pdf format from the IBM web site.

Oops, looks like they moved it, go here:
http://www.mqseries.net/phpBB2/viewtopic.php?t=18349
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial.
Back to top
View user's profile Send private message
MichaelDNeale
PostPosted: Wed Nov 10, 2004 7:05 pm    Post subject: Some other suggestions Reply with quote

Novice

Joined: 10 Nov 2004
Posts: 13

I have also modified the "extended" attribute to do with heartbeats, still trying....
Back to top
View user's profile Send private message
MichaelDNeale
PostPosted: Wed Nov 10, 2004 8:06 pm    Post subject: SOLVED Reply with quote

Novice

Joined: 10 Nov 2004
Posts: 13

The heartbeat interval needs to be set, and this does not appear to take effect until the queue manager is restarted.
Back to top
View user's profile Send private message
Nigelg
PostPosted: Thu Nov 11, 2004 12:33 am    Post subject: Reply with quote

Grand Master

Joined: 02 Aug 2004
Posts: 1046

HBINT takes effect when the channel is restarted, not when the qmgr does. HBINT has to be set on both the SDR and RCVR sides because the channel uses the larger of the atributes in the channel pair.

It does look like AdoptNewMCA is needed here. The RCVR channel will not time out its recv() until the end of HBINT, and so will continue running until then. The channel cannot restart at the receiver until the previous instance of the channel has ended.
You must be getting some error msgs in the qmgr error logs, like 'channel already running' or 'channel not available' while the channel is retrying.
Back to top
View user's profile Send private message
csmith28
PostPosted: Thu Nov 11, 2004 11:26 am    Post subject: Reply with quote

Grand Master

Joined: 15 Jul 2003
Posts: 1196
Location: Arizona

Michael,

When you unplug that network cable, your Local Sender channel ends abnormally and the MCA (Message Channel Agent) process goes away.

On the remote Server the Receiver channel is still up and the MCA for that channel is waiting to hear from the sending MCA.

When you plug the cable back in a new instance of the Sender channel attempts to start but goes into a RETRY status because the new Sender MCA can not bind with the old Receiver MCA. The length of time it will take for the new Sender channel to reconnect will be determined by your HBINT and KAINT setting that were negotiated during the Binding process.

Using AdoptNewMCA on the remote MQManager will allow the stale Receiver MCA to be stopped making way for the new MCA Sender to Bind with a new instance of the Receiver MCA.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial.
Back to top
View user's profile Send private message
MichaelDNeale
PostPosted: Thu Nov 11, 2004 3:51 pm    Post subject: Reply with quote

Novice

Joined: 10 Nov 2004
Posts: 13

So if I set HBINT to 1 on the receiving system, then this would have the same effect? (it seems to).

I am not entirely sure what HBINT on the receiving does - I gather that if I set the disconnect value to X, then after X * HBINT, it would stop the channel and then be able to connect?
Back to top
View user's profile Send private message
csmith28
PostPosted: Thu Nov 11, 2004 3:58 pm    Post subject: Reply with quote

Grand Master

Joined: 15 Jul 2003
Posts: 1196
Location: Arizona

You'd be better of using the AdopeNewMCA stanza in your qm.ini file.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial.
Back to top
View user's profile Send private message
Nigelg
PostPosted: Fri Nov 12, 2004 1:13 am    Post subject: Reply with quote

Grand Master

Joined: 02 Aug 2004
Posts: 1046

The RCVR channel will end nicely if no heartbeat flow is received 2 * HBINT (if HBINT < 60) or HBINT + 60 (HBINT >= 60) seconds after the last data flow across the channel. This is how WMQ detects when the SDR has ended, if TCP has not already informed the RCVR. A new instance of the channel can then be started without using AdoptNewMCA. If a new instance wants to start during that time, then there will be a 'Channel in use' error returned to the SDR.

This is not the same as DISCINT. The channel will stop, to INACTIVE status, if no msg has arrived on the xmitq in DISCINT seconds.

It is not really very sensible to set HBINT very low. Doing so will cause the SDR channel to interrupt the MQGET from the xmitq every HBINT seconds to send the heartbeat flow and await for the response from the RCVR.

I agree with Chris above, that you should set HBINT to a reasonable value, say 60, and use AdoptNewMCA.
Back to top
View user's profile Send private message
MichaelDNeale
PostPosted: Mon Nov 15, 2004 5:40 pm    Post subject: Reply with quote

Novice

Joined: 10 Nov 2004
Posts: 13

Thanks for all your help, this is a great forum.

I agree, I think setting the HBINT (from what little I know) is not the way to go. I assume that it would increase network chatter a lot.

The AdoptNewMCA sounds like the way to go, but I am a little confused about the options:

I am thinking that SDR or ALL would be the one to use?

(from the manual:

NO
The AdoptNewMCA feature is not required. This is the default.
SVR Adopt server channels.
SDR Adopt sender channels.
RCVR Adopt receiver channels.
CLUSRCVR Adopt cluster receiver channels.
ALL
)

Thanks.
Back to top
View user's profile Send private message
csmith28
PostPosted: Mon Nov 15, 2004 6:06 pm    Post subject: Reply with quote

Grand Master

Joined: 15 Jul 2003
Posts: 1196
Location: Arizona

I would us ALL.

Just remember that AdoptNewMCA needs to be set up on the remote MQManager for RCVR at the very least.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial.
Back to top
View user's profile Send private message
MichaelDNeale
PostPosted: Mon Nov 15, 2004 7:04 pm    Post subject: Reply with quote

Novice

Joined: 10 Nov 2004
Posts: 13

But I assume ALL means RCVR or SDR? So ALL should suffice?

Just remember that AdoptNewMCA needs to be set up on the remote MQManager for RCVR at the very least.[/quote]
Back to top
View user's profile Send private message
csmith28
PostPosted: Mon Nov 15, 2004 7:24 pm    Post subject: Reply with quote

Grand Master

Joined: 15 Jul 2003
Posts: 1196
Location: Arizona

yes
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial.
Back to top
View user's profile Send private message
oz1ccg
PostPosted: Tue Nov 16, 2004 2:21 pm    Post subject: Reply with quote

Yatiri

Joined: 10 Feb 2002
Posts: 628
Location: Denmark

ANd when we're talking about triggering, a TRIGINT() set to something usefull can also help....

If TRIGINT() is set to default (lot of 9's) You'll only get the first trigger, and if there are something in the XMITQ, you have to start the channel manually (if not the retrycount can help).

If you set TRIGINT() to somthing more reasonable, I'm typicly using 60000 which is 1 minute, this helps starting channels, and makes poorly written applications perform ok.

Just my $0.02
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT.
Back to top
View user's profile Send private message Send e-mail Visit poster's website MSN Messenger
JLRowe
PostPosted: Tue Nov 16, 2004 2:38 pm    Post subject: Reply with quote

Yatiri

Joined: 25 May 2002
Posts: 664
Location: South East London

Set AdoptNewMCA to ALL, the receiver channel still thinks the old channel instance is connected and will not accept a new connection until it the heartbeat interval has expired. You can also set both heartbeat intervals to low values (if there is a mismatch between sender and receiver, the largest is used).
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2, 3  Next Page 2 of 3

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » Channel not restarting fast enough
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.