| Author |
Message
|
| JohnMichael |
 Posted: Thu Mar 22, 2007 1:50 pm Post subject: Problem with Broker (broker is not running) |
 |
|
Acolyte
Joined: 28 Feb 2007
Posts: 55
|
I am having a single execution group named as NEW in my broker(v6)
and while checking using mqsibrowse command its showing two as '$SYS_mqsi' and 'NEW'
C:\IBM\MQSI\6.0>mqsibrowse
BIP8121W: Lists the contents of a components persistent store.
Syntax:
mqsibrowse componentName -t persistentStoreTable
Command Options:
'componentName' Name of the component to browse
'-t persistentStoreTable' the persistent store table to browse.
BIP8007E: Mandatory argument missing.
When using this command interface the user should supply the mandatory argument.
Correct and reissue the command.
C:\IBM\MQSI\6.0>mqsibrowse WBRK6_DEFAULT_BROKER -t BROKERAAEG
+--------------------------------------+----------------------------------------
------------+---------------+--------------+-----------+--------------+---------
-----+-------------+------------------+-----------------------------------------
---------+--------------------------------------------------+
| ExecGroupUUID | ExecGroupLabel
| RetryInterval | PubSubServer | ProcessId | ProcessState | DynamicS
tate | DynamicSync | ProcArchitecture | MsgId
| CntlGrpMsgId |
+--------------------------------------+----------------------------------------
------------+---------------+--------------+-----------+--------------+---------
-----+-------------+------------------+-----------------------------------------
---------+--------------------------------------------------+
| 82a6e590-12b3-11d3-81a2-00203506a68e | $SYS_mqsi
| 3 | 1 | 2400 | 3 | 3
| 4 | 32 | 00000000000000000000000000000000000
00000000000000000000000000000 | 000000000000000000000000000000000000000000000000
0000000000000000 |
| 316f077e-1101-0000-0080-ecaf6abec068 | NEW
| 3 | 0 | 2620 | 0 | 1
| 2 | 32 | 414d51205742524b365f44454641554cd0a
403462000080b0000000000000000 | 000000000000000000000000000000000000000000000000
0000000000000000 |
+--------------------------------------+----------------------------------------
------------+---------------+--------------+-----------+--------------+---------
-----+-------------+------------------+-----------------------------------------
---------+--------------------------------------------------+
BIP8071I: Successful command completion.
and while trying to deploy through console using mqsideploy command I am getting the error.
Error in console is : -
C:\IBM\MQSI\6.0>MQSIDEPLOY -i localhost -p 2414 -q WBRK6_DEFAULT_QUEUE_MANAGER -
b WBRK6_DEFAULT_BROKER -e NEW -a new_bar.bar
BIP1044I: Connecting to the Configuration Manager's queue manager...
BIP1045I: Connecting to the Configuration Manager...
BIP1039I: Deploying BAR file 'C:\IBM\MQSI\6.0\new_bar.bar' to broker 'WBRK6_DEFA
ULT_BROKER' (execution group 'NEW') ...
BIP8041E: Unable to open the selected file 'new_bar.bar'.
The file selected could not be opened for read or write.
Ensure that, if specified as input, the file exists and not also for output; and
that the file path is valid in any cases. Also ensure that the file is not lock
ed by another user.
Error in Event Viewer is : -
( WBRK6_DEFAULT_BROKER ) Execution Group '$SYS_mqsi' failed to return an internal configuration 'Start' message response within a 60 second time period.
The internal configuration message response could not be retrieved. The Execution Group therefore failed to move to the state described by the internal configuration message.
Investigate why the Execution Group internal configuration message response was not returned within the allowed time period by reviewing messages issued to the system log. Additionally, you can increase (or decrease) the timeout by using the mqsichangebroker option, ConfigurationDelayTimeout. This will not resolve any underlying problem with a deployed configuration message, but can be used to reduce the response turnaround time or allow for large and complex deployments. Resolve any problems described in the system log. This 'internal configuration' operation will be retried automatically, if you continue to see this message you should investigate the reason for the Execution Groups failure to respond.
So can any one resolve me this problem. |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Thu Mar 22, 2007 2:20 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
BIP8041E: Unable to open the selected file 'new_bar.bar'.
does this file exist in: C:\IBM\MQSI\6.0 ?
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| JohnMichael |
| Posted: Fri Mar 23, 2007 12:58 pm Post subject: I have placed file that that location C:\IBM\MQSI\6.0 |
|
|
Acolyte
Joined: 28 Feb 2007
Posts: 55
|
I have placed file that that location C:\IBM\MQSI\6.0
then after deploying I am getting the error in event viewer as : -
WBRK6_DEFAULT_BROKER ) Broker 'WBRK6_DEFAULT_BROKER' (UUID '146f6c80-1101-0000-0080-895b274b3bc5') was unable to retrieve an internal configuration response message for execution group ''default'' within the 60 second Configuration Timeout.
The execution group did not respond within the Configuration Timeout period. A negative response is returned to the Configuration Manager for this execution group. The Configuration Timeout is the maximum length of time that an execution group is allowed to apply a deployed configuration change. By default the Configuration Timeout period is 300 seconds. You can increase (or decrease) the timeout by using the mqsichangebroker option, ConfigurationTimeout. This will not resolve any underlying problem with the deployed message, but can be used to reduce the response turnaround time or increase it to allow for large and complex deployments.
Investigate why the execution group was unable to respond before being timed out. Use the system log messages to determine if there is a problem with the execution group. You should check that your system is not running short of resources, for example, you may need to increase the WebSphere log size. Reducing the complexity of the deploy by reducing the number of execution groups may also help to alleviate this problem. Correct the problem and redeploy the broker's configuration from the Message Brokers Toolkit, mqsideploy command or Config Manager Proxy. If there are no other failure diagnostics then you should consider increasing the Configuration Timeout, increase this value in units of 300 until this message no longer occurs. Contact your IBM support center if you are unable to resolve the problem. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Mar 23, 2007 1:53 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
So did you increase the timout value?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| JohnMichael |
| Posted: Mon Mar 26, 2007 4:13 am Post subject: |
|
|
Acolyte
Joined: 28 Feb 2007
Posts: 55
|
| Yes, Increased time out value of configurationTimeout from 300 to 400 and other configurationDelayTimeout from 60 to 100 |
|
| Back to top |
|
|
| yuj |
| Posted: Tue Mar 27, 2007 10:37 am Post subject: |
|
|
Novice
Joined: 19 Mar 2007
Posts: 10
|
| johnmichael.nittala wrote: |
| Yes, Increased time out value of configurationTimeout from 300 to 400 and other configurationDelayTimeout from 60 to 100 |
Where is your broker's qmgr? Have you found anything from the broker qmgr's errlog? You may also want to check the channel between the CM's qmgr and the broker's qmgr. Pay attention to anything jamed or not in sync. Does restart the CM help? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Mar 28, 2007 1:58 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And of course to receive the answer the broker MUST be running... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
