| Author |
Message
|
| ravella |
 Posted: Fri Sep 16, 2011 3:38 am Post subject: mqsireportproperties |
 |
|
Newbie
Joined: 05 Sep 2011
Posts: 9
|
Hi,
I'm getting the following error while try to retrieve properties of executiongroup....
$ mqsireportproperties GISF_INTERFACE_BROKER -e EG4 -o AllMessageFlows -r
BIP2087E: Broker GISF_INTERFACE_BROKER was unable to process the internal configuration message.
The entire internal configuration message failed to be processed successfully.
Use the messages following this message to determine the reasons for the failure. If the problem cannot be resolved after reviewing these messages, contact your IBM Support center. Enabling service trace may help determine the cause of the failure.
BIP2066E: Broker GISF_INTERFACE_BROKER (UUID aa3db76d-1a01-0000-0080-b4dcfc11782a) was unable to retrieve an internal configuration response message for execution group 'EG4' within the 360 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 i
t 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 diagnost
ics 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.
BIP8036E: Negative response received.
This command sends an internal configuration message to the broker, the response received indicated that the internal configuration message was unsuccessful.
Check that the WebSphere MQ transport is available. Check the system log for further information. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Sep 16, 2011 4:35 am Post subject: Re: mqsireportproperties |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ravella wrote: |
| I'm getting the following error while try to retrieve properties of executiongroup.... |
Congratulations. Was there a question? 
Assuming the question is "what can I do to get the command working?", the obvious response is "what happened when you tried the advice in the error message?"
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| MrSmith |
| Posted: Fri Sep 16, 2011 4:41 am Post subject: |
|
|
Master
Joined: 20 Mar 2008
Posts: 215
|
the advice for clarity being:
| Quote: |
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 diagnost
ics then you should consider increasing the Configuration Timeout, increase this value in units of 300 until this message no longer occurs. |
 |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Sep 16, 2011 4:49 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
And checking the system log for issues generally, and with that EG specifically
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Sep 16, 2011 6:08 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I've just tried in on an EG with a few flows and another one with a lot more flows deployed (29). THere is an appreciable delay in the second operation. This is ovbiously while the command gets all the data from broker.
Sadly the mqsireport properties (on 6.1.0.9) does not allow a timeout to be specified.
You could try reporting on the flows in the EG (mqsilist) and then reporting on each one in turn.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| ravella |
| Posted: Sat Sep 17, 2011 1:51 am Post subject: |
|
|
Newbie
Joined: 05 Sep 2011
Posts: 9
|
Can u let me know where the error log OR log for configuration manager will be generated???
There are only 2 msg flows running in that EG and also there are no issues with the log size.....
Also are there any commands to check what are the execution groups that are interacting with particular configManager? |
|
| Back to top |
|
|
|
|
