| Author |
Message
|
| Gemz |
 Posted: Mon Apr 28, 2008 9:21 am Post subject: Message pile up in SYSTEM.QUEUE |
 |
|
Centurion
Joined: 14 Jan 2008
Posts: 124
|
hi,
In unix today MQ was stopped due to disk space. Now we have increase the disk space and i have restarted configuration manager, queue manager and broker.
But now Messages are piling up in SYSTEM.BROKER.ADMIN.REPLY and SYSTEM.BROKER.CONFIG.QUEUE.
Now I am not able connect to that broker using tool kit.
pls 
Thanks |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Apr 28, 2008 9:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I would guess that ConfigMgr didn't start up.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Gemz |
| Posted: Mon Apr 28, 2008 9:57 am Post subject: |
|
|
Centurion
Joined: 14 Jan 2008
Posts: 124
|
jeff,
But Configuration manager is running, while giving the process status command in unix. what might be the problem. I restarted it too....
Thanks |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Apr 28, 2008 10:10 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Is it running without error?
Just because the process is there...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Gemz |
| Posted: Mon Apr 28, 2008 10:20 am Post subject: |
|
|
Centurion
Joined: 14 Jan 2008
Posts: 124
|
| You mean in the system log? |
|
| Back to top |
|
|
| AkankshA |
| Posted: Mon Apr 28, 2008 8:46 pm Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
SYSTEM.BROKER.ADMIN.REPLY is the target for response messages that the broker sends to the Configuration Manager.
and
SYSTEM.BROKER.CONFIG.QUEUE is the Target for messages that the toolkit sends to the Configuration Manager
So your broker and toolkit are not able to communifcate with config manager...
ensure that the channels are upa nd running and so the components...
else have a look at system logs...
_________________
Cheers |
|
| Back to top |
|
|
| Gemz |
| Posted: Tue Apr 29, 2008 1:57 am Post subject: |
|
|
Centurion
Joined: 14 Jan 2008
Posts: 124
|
Hi,
I checked the channel status. It shpws the following message. From this channels are running.
AMQ8417: Display Channel Status details.
CHANNEL(SYSTEM.BKR.CONFIG) CHLTYPE(SVRCONN)
CONNAME(IP Address ) CURRENT
RQMNAME( ) STATUS(RUNNING)
SUBSTATE(MQGET) XMITQ( )
In system log i could see that executable bipconfigmgr terminated, exit code 106 and The Configuration Manager's repository is not available for use.. What could be the reason and how can we solve this problem?
| Quote: |
System Log :
Apr 29 10:45:37 adcapgisu02 user:info WebSphere Broker v6100[1245326]: (WBRK61_DEFAULT_CONFIGURATION_MANAGER)[1]BIP2001I: The WebSphere Message Brokers service has started at version 6100; process ID 1609892. : WBRK61_DEFAULT_CONFIGURATION_MANAGER.service: /build/S000_P/src/AdminAgent/ControlProcess/rios_aix_4/ImbControlService.cpp: 345: ImbControlService::StartNewAA: :
Apr 29 10:45:40 adcapgisu02 user:info WebSphere Broker v6100[1609892]: (WBRK61_DEFAULT_CONFIGURATION_MANAGER)[1]BIP1230S: The Configuration Manager's repository is not available for use. : WBRK61_DEFAULT_CONFIGURATION_MANAGER.agent: /build/S000_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 633: ConfigurationManager.initialize: WBRK61_DEFAULT_CONFIGURATION_MANAGER: WBRK61_DEFAULT_CONFIGURATION_MANAGER
Apr 29 10:45:40 adcapgisu02 user:err|error WebSphere Broker v6100[1245326]: (WBRK61_DEFAULT_CONFIGURATION_MANAGER)[1]BIP2015E: The WebSphere Message Brokers service detected that executable bipconfigmgr terminated, exit code 106. : WBRK61_DEFAULT_CONFIGURATION_MANAGER.service: /build/S000_P/src/AdminAgent/ControlProcess/rios_aix_4/ImbControlService.cpp: 438: ImbControlService::GetAAexitCode: :
Apr 29 10:45:40 adcapgisu02 user:info WebSphere Broker v6100[1245326]: (WBRK61_DEFAULT_CONFIGURATION_MANAGER)[1]BIP2001I: The WebSphere Message Brokers service has started at version 6100; process ID 1663182. : WBRK61_DEFAULT_CONFIGURATION_MANAGER.service: /build/S000_P/src/AdminAgent/ControlProcess/rios_aix_4/ImbControlService.cpp: 345: ImbControlService::StartNewAA: :
Apr 29 10:45:44 adcapgisu02 user:info WebSphere Broker v6100[1663182]: (WBRK61_DEFAULT_CONFIGURATION_MANAGER)[1]BIP1230S: The Configuration Manager's repository is not available for use. : WBRK61_DEFAULT_CONFIGURATION_MANAGER.agent: /build/S000_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 633: ConfigurationManager.initialize: WBRK61_DEFAULT_CONFIGURATION_MANAGER: WBRK61_DEFAULT_CONFIGURATION_MANAGER
Apr 29 10:45:44 adcapgisu02 user:info WebSphere Broker v6100[1245326]: (WBRK61_DEFAULT_CONFIGURATION_MANAGER)[1]BIP2001I: The WebSphere Message Brokers service has started at version 6100; process ID 1183794. : WBRK61_DEFAULT_CONFIGURATION_MANAGER.service: /build/S000_P/src/AdminAgent/ControlProcess/rios_aix_4/ImbControlService.cpp: 345: ImbControlService::StartNewAA: :
Apr 29 10:45:47 adcapgisu02 user:info WebSphere Broker v6100[1183794]: (WBRK61_DEFAULT_CONFIGURATION_MANAGER)[1]BIP1230S: The Configuration Manager's repository is not available for use. : WBRK61_DEFAULT_CONFIGURATION_MANAGER.agent: /build/S000_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 633: ConfigurationManager.initialize: WBRK61_DEFAULT_CONFIGURATION_MANAGER: WBRK61_DEFAULT_CONFIGURATION_MANAGER |
|
|
| Back to top |
|
|
| AkankshA |
| Posted: Tue Apr 29, 2008 2:06 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
| which version of MB are u using..? |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 29, 2008 2:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| AkankshA wrote: |
| which version of MB are u using..? |
| Gemz wrote: |
| Apr 29 10:45:37 adcapgisu02 user:info WebSphere Broker v6100 |
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Apr 29, 2008 3:15 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
stop the config mgr. Make sure there is no SQL process attached to its DB open (cloudscape). Restart the config mgr.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Gemz |
| Posted: Tue Apr 29, 2008 7:51 am Post subject: |
|
|
Centurion
Joined: 14 Jan 2008
Posts: 124
|
Hi,
We got repository not found error in the system log. So we re-created a configuration manager and added the existing broker to it.
Now the problem is resolved.
Thanks  |
|
| Back to top |
|
|
|
|
