| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Receiver channel always running |
« View previous topic :: View next topic » |
| Author |
Message
|
| mgrabinski |
 Posted: Mon Aug 12, 2002 3:13 am Post subject: Receiver channel always running |
 |
|
Master
Joined: 16 Oct 2001
Posts: 246
Location: Katowice, Poland
|
Hi gurus!
I have a channel SDR-RCVR. I can control only the receiving end. When the connection brokes, the SDR goes into RETRYING state (normal) and the RCVR stays in RUNNING state (normal). When the connection is restored, the SDR will not go into RUNNING and at receiving end I can see plenty of messages "CSQX514E Channel <chl_name> is active", which means that the channel cannot be started because it's already RUNNING.
Also normal... but problematic
At this moment most of you woud reply "use HBINT", wouldn't you? The problem is I do use HBINT (5 mins), but it doesn't help. As I understand HBINT, after 5 mins of silence on the link, the receiver should send a kind of ping to the sender, and if it doesn't reply, the RCVR should go into INACTIVE state. Then, after restoring comms, the SDR would start it in normal way. Is my understanding correct? Why does my receiver stay permamently in RUNNING state?
What can I do except of restarting the channel initiator?
Thanks in advance for any input
_________________
Marcin Grabinski <>< |
|
| Back to top |
|
 |
| mrlinux |
| Posted: Mon Aug 12, 2002 3:53 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Actually you want to add to your qm.ini or regsistry settings
ADOPTMCA, this will allow the rcving qmgr to start another receiver.
http://publibfp.boulder.ibm.com/epubs/html/amqzag03/amqzag03tfrm.htm
Channels
Use the Channels queue manager properties page, or the Channels stanza in the qm.ini file, to specify information about channels.
MaxChannels=100|number
The maximum number of channels allowed. The default is 100.
MaxActiveChannels=MaxChannels_value
The maximum number of channels allowed to be active at any time. The default is the value specified on the MaxChannels attribute.
MaxInitiators=3|number
The maximum number of initiators.
MQIBINDTYPE=FASTPATH|STANDARD
The binding for applications:
FASTPATH
Channels connect using MQCONNX FASTPATH; there is no agent process.
STANDARD
Channels connect using STANDARD.
PipeLineLength=1|number
The maximum number of concurrent threads a channel will use. The default is 1. Any value greater than 1 is treated as 2.
When you use pipelining, configure the queue managers at both ends of the channel to have a PipeLineLength greater than 1. Note: Pipelining is only effective for TCP/IP channels.
AdoptNewMCA=NO|SVR|SDR|RCVR|CLUSRCVR|ALL|FASTPATH
If WebSphere MQ receives a request to start a channel, but finds that an amqcrsta process already exists for the same channel, the existing process must be stopped before the new one can start. TheAdoptNewMCA attribute allows you to control the end of an existing process and the startup of a new one for a specified channel type.
If you specify the AdoptNewMCA attribute for a given channel type, but the new channel fails to start because the channel is already running:
The new channel tries to stop the previous one by requesting it to end.
If the previous channel server does not respond to this request by the time the AdoptNewMCATimeout wait interval expires, the process (or the thread) for the previous channel server is ended.
If the previous channel server has not ended after step 2, and after the AdoptNewMCATimeout wait interval expires for a second time, WebSphere MQ ends the channel with a CHANNEL IN USE error.
Specify one or more values, separated by commas or blanks, from the following list:
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
Adopt all channel types except FASTPATH channels.
FASTPATH
Adopt the channel if it is a FASTPATH channel. This happens only if the appropriate channel type is also specified, for example, AdoptNewMCA=RCVR,SVR,FASTPATH. Attention!
The AdoptNewMCA attribute might behave in an unpredictable fashion with FASTPATH channels. Exercise great caution when enabling the AdoptNewMCA attribute for FASTPATH channels.
AdoptNewMCATimeout=60|1 - 3600
The amount of time, in seconds, that the new process waits for the old process to end. Specify a value in the range 1 - 3600. The default value is 60.
AdoptNewMCACheck=QM|ADDRESS|NAME|ALL
The type of checking required when enabling the AdoptNewMCA attribute. If possible, perform all three of the following checks to protect your channels from being shut down, inadvertently or maliciously. At the very least, check that the channel names match.
Specify one or more values, separated by commas or blanks, to tell the listener process to:
QM
Check that the queue manager names match.
ADDRESS
Check the communications address. For example, the TCP/IP address.
NAME
Check that the channel names match.
ALL
Check for matching queue manager names, the communications address, and for matching channel names.
AdoptNewMCACheck=NAME,ADDRESS is the default for FAP1, FAP2, and FAP3, while AdoptNewMCACheck=NAME,ADDRESS,QM is the default for FAP4 and later.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Mon Aug 12, 2002 4:38 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
This is my absolute favorite, RCVR channels... I personally NEVER use them because they don't allow me to try to start the channel from thre receiver end.
I've been using REQUESTER-SENDER channels instead, because they allow me to initiate communication from both ends. Quite smart 
And together with ADOPTMCA it's allmost bulletproof.... 
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 |
|
|
| PeterPotkay |
| Posted: Mon Aug 12, 2002 5:02 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Marcin, the Heartbeat should be putting your RCVR into an inactive state after 5 minutes, if both sides of the channel have 5 minutes coded (300). If the values are different between the SNDR and the RCVR, then the larger of the two will be used.
Can you check what the sender's heartbeat interval is?
Also, do both the sender's and reciever's platforms support heartbeat?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mgrabinski |
| Posted: Mon Aug 12, 2002 9:25 pm Post subject: |
|
|
Master
Joined: 16 Oct 2001
Posts: 246
Location: Katowice, Poland
|
Joergen:
I share your opinion on RQSTR and RCVR, but in this case RQSTR wasn't possible - our partner has a hobby of changing IP addresess  so I let them start the communications.
Peter:
That's not the case. Both sides have HBINT of 300 and both sides support it. In the meantime I've read your discussion with Joergen and Jeff in the "instalation/configuration" forum. It's given me a great insight into the problem of RCVR running for too long. Thanks!
I've decided to follow your advice and changed the ADOPTMCA parameter.
_________________
Marcin Grabinski <>< |
|
| 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
|
|
|
|
