| Author |
Message
|
| Adreno |
 Posted: Tue Jun 17, 2008 5:29 am Post subject: BIP2623: Unable to open queue 'SYSTEM.BROKER.EXECUTIONGROUP. |
 |
|
Acolyte
Joined: 05 Jul 2007
Posts: 71
|
Hi,
since that morning I´m recieving this error within my broker logs. This error takes place about every 60 minutes and points out, that the SYSTEM.BROKER.EXECUTIONGROUP.QUEUE and the SYSTEM.BROKER.CONTROL.QUEUE couldn ´t be openend.
When I look into my Queue Manager these queues are present and read / writeable. Se details below: Message Broker is 6.1.0.2 on AIX 5.3 with underlying MQ 6.0.2.3. Recreation of the components didn´t fix the problem at all.
Detail:
Jun 17 14:45:39 srvmwqa user:err|error WebSphere Broker v6102[495736]: (BK_VEB001Q.VEB001Q1)[6940]BIP2623E: Unable to open queue 'SYSTEM.BROKER.EXECUTIONGROUP.QUEUE' on WebSphere MQ queue manager 'VEB001Q': completion code 2; reason code 2009. : BK_VEB001Q.55080482-1a01-0000-0080-a39a09443934: /build/S610_P/src/DataFlowEngine/ImbMqManager.cpp: 611: ImbMqConnection::getQueue: ComIbmMQConnectionManager: ComIbmMQConnectionManager
Jun 17 14:45:39 srvmwqa user:err|error WebSphere Broker v6102[495736]: (BK_VEB001Q.VEB001Q1)[6940]BIP2604E: Node failed to open WebSphere MQ queue 'SYSTEM.BROKER.EXECUTIONGROUP.QUEUE' owned by queue manager 'VEB001Q': completion code 2; reason code 2009. : BK_VEB001Q.55080482-1a01-0000-0080-a39a09443934: /build/S610_P/src/DataFlowEngine/ImbMqInputNode.cpp: 879: ImbMqInputNode::readData: ComIbmMQInputNode: InputNode
Jun 17 14:45:41 srvmwqa user:err|error WebSphere Broker v6102[495736]: (BK_VEB001Q.VEB001Q1)[7197]BIP2623E: Unable to open queue 'SYSTEM.BROKER.CONTROL.QUEUE' on WebSphere MQ queue manager 'VEB001Q': completion code 2; reason code 2009. : BK_VEB001Q.55080482-1a01-0000-0080-a39a09443934: /build/S610_P/src/DataFlowEngine/ImbMqManager.cpp: 611: ImbMqConnection::getQueue: ComIbmMQConnectionManager: ComIbmMQConnectionManager
Jun 17 14:45:41 srvmwqa user:err|error WebSphere Broker v6102[495736]: (BK_VEB001Q.VEB001Q1)[7197]BIP2604E: Node failed to open WebSphere MQ queue 'SYSTEM.BROKER.CONTROL.QUEUE' owned by queue manager 'VEB001Q': completion code 2; reason code 2009. : BK_VEB001Q.55080482-1a01-0000-0080-a39a09443934: /build/S610_P/src/DataFlowEngine/ImbMqInputNode.cpp: 879: ImbMqInputNode::readData: ComIbmMQInputNode: InputNode
Any suggestions?
_________________
There are two kinds of people in this world: people who s***, and Chuck Norris... |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Tue Jun 17, 2008 5:37 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
2009 : is connection broker.
first of all check if that queue is present or not....
as it been discussed here in this forum, so search
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| Adreno |
| Posted: Tue Jun 17, 2008 5:50 am Post subject: |
|
|
Acolyte
Joined: 05 Jul 2007
Posts: 71
|
Hi . . . a I already read the topic . . . my the queues are present as I mentioned!
_________________
There are two kinds of people in this world: people who s***, and Chuck Norris... |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Tue Jun 17, 2008 6:07 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
check the channels are up and running all the time...
search for 2009
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| mqmatt |
| Posted: Tue Jun 17, 2008 6:07 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Assuming you're on 6.1, the Config Manager will send a synchronisation request to the broker every hour, which might explain the frequency of the messages.
But this process uses exactly the same interface as all other operational acts. So, are you able to do things like deploy new message flows, start and stop your existing flows, run mqsilist etc.? |
|
| Back to top |
|
|
| Adreno |
| Posted: Tue Jun 17, 2008 6:15 am Post subject: |
|
|
Acolyte
Joined: 05 Jul 2007
Posts: 71
|
Hi,
so my channels are up and running. My message flows are also running and i´m able to deploy ne flows etc.
There are no functional problems and all changes that i make get effective, but every 60 minutes I´m recieving that errors.
_________________
There are two kinds of people in this world: people who s***, and Chuck Norris... |
|
| Back to top |
|
|
| sri_csee1983 |
| Posted: Tue Jun 17, 2008 7:13 am Post subject: |
|
|
Centurion
Joined: 25 Mar 2008
Posts: 125
Location: Chennai,India
|
Hi Adreno,
Is this the broker and QM u r using
BK_VEB001Q VEB001Q1 or that one was test one and deleted from a the ConfigMgr recently?
_________________
With Cheers,
Sri |
|
| Back to top |
|
|
| Adreno |
| Posted: Wed Jun 18, 2008 12:39 am Post subject: |
|
|
Acolyte
Joined: 05 Jul 2007
Posts: 71
|
Exactly,
VEB001Q is my Queue Manager and VEB001Q1 is the execution group my message flow is running on. Normally I would exspect an MQ error in my queue manager logs that tells me, that the maximum number of channels has been reached, but there are no errors.
All works fine but every hour I recieve this messages.
Which channel does the CM use to sync with his broker?
_________________
There are two kinds of people in this world: people who s***, and Chuck Norris... |
|
| Back to top |
|
|
| mqmatt |
| Posted: Wed Jun 18, 2008 2:18 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| Adreno wrote: |
| Which channel does the CM use to sync with his broker? |
Exactly the same channel as all other communication; it's just inter-qmgr communication.
I suggest you raise a PMR. |
|
| Back to top |
|
|
| Adreno |
| Posted: Wed Jun 18, 2008 6:14 am Post subject: |
|
|
Acolyte
Joined: 05 Jul 2007
Posts: 71
|
Thanks so far . . I just closed another PMR  . . . .
I´ll try that!
_________________
There are two kinds of people in this world: people who s***, and Chuck Norris... |
|
| Back to top |
|
|
| cynik |
| Posted: Sun Aug 22, 2010 11:47 pm Post subject: |
|
|
Newbie
Joined: 31 Mar 2009
Posts: 9
|
Hi Adreno, could you please tell me if you have solved described issue? As we have now same problem - every 1 hour we get similar error message (just different MQRC). Besides that everything works fine..
Aug 23 03:06:24 UXMQ10OKPRG user:err|error WebSphere Broker v6107[9896102]: (BRK.AMOS)[7968]BIP2623E: Unable to open queue 'SYSTEM.BROKER.INTER.BROKER.COMMUNICATIONS' on WebSphere MQ queue manager 'CSA_QM': completion code 2; reason code 2042. : BRK.fb7925b7-2601-0000-0080-9f71709e9a95: /build/S610_P/src/DataFlowEngine/ImbMqManager.cpp: 644: ImbMqConnection::getQueue: ComIbmMQConnectionManager: ComIbmMQConnectionManager |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Aug 23, 2010 4:08 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| cynik wrote: |
| As we have now same problem - every 1 hour we get similar error message (just different MQRC). |
How is it the same problem if you're getting a different reason code?? 
2042 is fairly straightforward and a sight easier to diagnose than a 2009.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
