| Author |
Message
|
| apohorai |
 Posted: Mon Feb 16, 2009 3:36 am Post subject: BIP2623E: Unable to open queue - reason code 2018 |
 |
|
Apprentice
Joined: 15 Mar 2006
Posts: 26
Location: Budapest/Munich
|
Guys,
I'm a bit confused if this an MQ or WMB problem. Anyway, post it to here.
Maybe this is just a coincidence, but after we installed AIX53 ML0706-8044 we keeps getting this error in the WBIMB (6.0.0.0) trace log and cluster log. This happening only with some of the high volume queues in random times.Sometimes the problem solves itself, but sometimes we need to restart broker. We have no performance or resource issues. Before AIX ML we had no problem like this at all. I can't find anything in the MQ(6.0.2.3) logs.
Any idea?
Cheers,
Attila
2009-02-16 09:48:24.620346 20047 Error BIP2623E: Unable to open queue ''QL.TRQ.TLR.BKR.01'' on WebSphere MQ queue manager ''PBKRNG01'': completion
code 2; reason code 2018.
A message flow node failed to open the indicated WebSphere MQ message queue. The error codes relate to the MQOPEN call.
Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to esta
blish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
If the open failed because the queue manager or queue did not exist, define these objects to WebSphere MQ. If the failure of the open was because incorrect
object names were specified, correct the message flow configuration and attempt to redeploy the message broker. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Feb 16, 2009 3:46 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
You may not have performance or resource issues, but is the queue manager at or near MaxConn?
Have you considered applying maintenance to the broker runtime?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| apohorai |
| Posted: Mon Feb 16, 2009 4:08 am Post subject: |
|
|
Apprentice
Joined: 15 Mar 2006
Posts: 26
Location: Budapest/Munich
|
Vitor,
Maybe you're right. Now it seems it's an MQ problem, sorry guys.
In the qm.ini we definied 400 channels
Channels:
MaxChannels=400
MaxActiveChannels=350
Max handles are 256 MAXHANDS(256)
Just checked the active channels and currently have 256 ...
Is one execution group/broker considered as one job? Is it helps if I increase the max handles?
And about the patch. Just installed and being test on a copy of the prod box.
Cheers |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Feb 16, 2009 4:58 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Upgrade your MQ to 6.0.2.5 a lot less grief that way... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Tibor |
| Posted: Mon Feb 16, 2009 10:05 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
Hi Poha,
| apohorai wrote: |
| Is it helps if I increase the max handles? |
Yes it can but a restarting is needed after changing this parameter.
If you are wondering the handlers owned by the execution group, run this:
dis qs(*) type(handle) all where(appltag lk 'DataFlowEngine*')
Tibor |
|
| Back to top |
|
|
| apohorai |
| Posted: Wed Feb 18, 2009 1:34 am Post subject: |
|
|
Apprentice
Joined: 15 Mar 2006
Posts: 26
Location: Budapest/Munich
|
|
| Back to top |
|
|
| meaton78 |
| Posted: Mon May 04, 2009 5:50 pm Post subject: |
|
|
Centurion
Joined: 16 Oct 2008
Posts: 100
|
| Thanks for the follow up reply. We just ran into the same issue going from TL6 to TL8 and that link you provided was what we needed to do to fix the issue as well. |
|
| Back to top |
|
|
|
|
