| Author |
Message
|
| samsansam |
 Posted: Fri Mar 13, 2015 7:06 am Post subject: AdoptNewMCA |
 |
|
Apprentice
Joined: 19 Mar 2014
Posts: 41
|
WebSphere MQ system information:
Product :- WebSphere MQ for Solaris (SPARC platform)
Version :- 7.0.1.5
Host Info :- SunOS 5.10
I am thinking to use AdoptNewMCA on our receiver QMGR. Some of our receiver channels keep running at the same time the SDR channels are in retrying.
SDR channels are located on Z/OS , and the receiver located on Solaris. Here is what I am going to add on qm.ini on the receiver QMGR.
AdoptNewMCA=RCVR
AdoptNewMCATimeout=30
AdoptNewMCACheck=ALL
Looking at what I am going to add, is that the right way?
Do I have to use AdoptNewMCA in the Sender QMGR as well?
I understand that AdoptNewMCATimeout is the amount of time, in seconds, that the new channel instance waits for the old channel instance to end. So,
if the old channel instance did not end in 30 seconds, what will happened?
Do I have to change keepalive to yes as well? |
|
| Back to top |
|
 |
| PaulClarke |
| Posted: Fri Mar 13, 2015 7:33 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
That looks about right to me. Of course I would always recommend that you test this kind of thing in a test set-up before deploying into production.
You don't need to add it to your sender queue manager as well.
If after 30 seconds the receiver channel does not stop (suppose it is hung in a channel exit or whatever) then the nre starting channel be rejected. I suspect with 'channel in use'.
You don't have to change keepalive but having keepalive on is rarely a bad idea. It may well help allow the receiver channel to end of its own accord. It also useful for client channels, especially pre-V7.
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| tczielke |
| Posted: Fri Mar 13, 2015 8:06 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
On the z/OS side, it would also be good to validate that you have the Receive Wait Time attributes on your queue manager configured properly, so you are detecting if the partner has went away.
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
| samsansam |
| Posted: Sun Mar 15, 2015 7:21 pm Post subject: |
|
|
Apprentice
Joined: 19 Mar 2014
Posts: 41
|
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Mar 17, 2015 10:19 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Not that I want to counter what Paul has said, but in 19 years of implementing MQ in production environments, I make the following changes to stanzas:
| Code: |
* WMQ Qmgr Stanzas to add/modify
LogBufferPages=4096
# The following lines are added to the default
CHANNELS:
MaxChannels=1000
MaxActiveChannels=1000
AdoptNewMCACheck=ALL
AdoptNewMCA=ALL
AdoptNewMCATimeout=60
TCP:
KeepAlive=Yes |
I would do this for every Qmgr in PROD, PRE PROD, PERFORMANCE... z/OS may differ some. |
|
| Back to top |
|
|
| samsansam |
| Posted: Wed Mar 18, 2015 12:19 pm Post subject: |
|
|
Apprentice
Joined: 19 Mar 2014
Posts: 41
|
JosephGramig thank you for your advise, one thing I need to ask about here:-
AdoptNewMCA=ALL
Our application is connected to F5 and from F5 to the QMGR. The server conn channels on the QMGR have same connection name.
Correct me if I am wrong , I think using AdoptNewMCA=ALL here will be bad idea. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Mar 18, 2015 12:51 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| samsansam wrote: |
| Correct me if I am wrong , I think using AdoptNewMCA=ALL here will be bad idea. |
Why do you think that using AdobtNewMCA=ALL will be a bad idea?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Wed Mar 18, 2015 1:23 pm Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
It is probably good idea to only allow those types of channels you need to be Adopted rather than just saying 'anything'. Then there is no risk of a rogue requester channel 'breaking' your senders for example.
However, samsansam you needn't worry about your client connections since AdoptMCA does not apply to SVRCONNs
Regards,
Paul
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| samsansam |
| Posted: Thu Mar 19, 2015 6:37 am Post subject: |
|
|
Apprentice
Joined: 19 Mar 2014
Posts: 41
|
AdoptNewMCA=SVR,SDR,RCVR,CLUSRCVR,ALL
Oh I see now , SVRCONN will not be impacted if I add AdoptNewMCA=all.
Thank you guys
 |
|
| Back to top |
|
|
|
|
