| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| compatibility issues between Solaris and Tandem MQ. |
« View previous topic :: View next topic » |
| Author |
Message
|
| Mlin |
 Posted: Mon Jul 22, 2002 5:53 am Post subject: compatibility issues between Solaris and Tandem MQ. |
 |
|
Novice
Joined: 13 May 2002
Posts: 12
|
Hi,
I have MQSeries 5.2 with CSD 2 running on Solaris 2.8 on one end and MQ2.2.01 running on HP Non Stop on the other end. Somehow when the sender channel on HP disconnects (after interval expired), the queue manager on Solaris doesn't detect it and still reports the channel as "running". If the MCA on HP attempts to start the channel, it goes into retry. The only way to get out of this problem is to stop the receiver channel with mode force and start it.
An error is logged on the Solaris queue manager indicating that the channel is in use.
The following was recorded on the Tandem queue manager:
AMQ9558: Remote Channel is not currently available. EXPLANATION: The channel program ended because the channel 'M1MQ01.TO.EAMSHUB01' is not currently available on the remote system. This could be because the channel is disabled or that the remote system does not have sufficient resources to run a further channel. ACTION: Check the remote system to ensure that the channel is available to run and retry the operation.
Has anyone seen this before and any recommendation on how to resolve the issue. Thanks.
Lin |
|
| Back to top |
|
 |
| mrlinux |
| Posted: Mon Jul 22, 2002 6:18 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Yes this is an old problem, there is a resolution, setting called
AdoptMCA. What is basically does is if there is a new connection request
from the same channel it will drop the old one and start a new one.
From manual
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 |
|
|
| Mlin |
| Posted: Mon Jul 22, 2002 9:22 am Post subject: |
|
|
Novice
Joined: 13 May 2002
Posts: 12
|
Jeff, thanks for response. This option is only available on the new version of MQ, are there any settings required on the Tandem side?
Thanks
Mlin |
|
| Back to top |
|
|
| mrlinux |
| Posted: Mon Jul 22, 2002 9:51 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
This is available on v5.2 also, I just reference the new manuals,
Since the reciever is on Solaris, this is where it needs to be set
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| mqonnet |
| Posted: Tue Jul 23, 2002 5:10 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
MLIN, what Level are you on HP. 2201 GA or any CSD's. If you dont have the CSD already installed, that would be highly recommended, because there are many issues that got resolved relating to channels on Mq NSK 2201.
Also bear in mind that you got to wait till the HBINT value is elapsed before both sdr and rcvr try to communicate. This only if your SDR is restarted/goes into retry automatically. But if you try to issue a START CHANNEL command, it should pick up the rcvr and start the channel.
My 0.02 cents..
Cheers.
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| 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
|
|
|
|
