| Author |
Message
|
| gbbailey |
 Posted: Tue Nov 07, 2006 5:55 am Post subject: mqsichangetrace BIP2062E |
 |
|
Apprentice
Joined: 12 May 2006
Posts: 27
Location: London, UK
|
It's a bad WBIMB day at the office.
I can't turn on user trace. This is a different environment from my toolkit problems reported in another post. I get the following error messasge for mqsireporttrace and the same error messasge for mqsichangetrace.
| Quote: |
E:\gbb>mqsireporttrace UKUK_ESB_BKR_P_1 -u -e TSF
BIP2087E: Broker UKUK_ESB_BKR_P_1 was unable to process the internal configuration message.
The entire internal configuration message failed to be processed successfully.
The internal configuration message failed to be processed, use the messages following this message to determ
ons for the failure.
BIP2062E: Broker UKUK_ESB_BKR_P_1 (UUID 5b6bb7c1-0e01-0000-0080-c11903c213fd) execution group 'TSF' (UUID fa
0000-0080-fca0e1a7f4e4) detected that the deployed configuration message received contained an invalid XML t
The configuration message received could not be applied to the broker's configuration. This could occur for
e following reasons: (a) The configuration message XML tag directs an execution group to be created but the
oup already exists. (b) The configuration message XML tag directs an execution group to be changed but the e
up does not exist. The configuration message is rejected.
Use the Message Brokers Toolkit, mqsideploy command or Config Manager Proxy to redeploy to the execution gro
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
nfiguration message was unsuccessful.
Check that the WebSphere MQ transport is available. Check the system log for further information. |
Now I can manually deploy bar files to the execution group TSF from the toolkit. Additionally I have (apparently) turned on user trace from the tookit by right clicking and checking user trace; although I've never used the feature before, and it doesn't appear to actually be doing anything. When I run messasges through the system and do an mqsireadlog (which works), it gets back an empty message.
This is in Windows. v6.0.0.2. |
|
| Back to top |
|
 |
| hs |
| Posted: Tue Nov 07, 2006 7:19 am Post subject: |
|
|
Novice
Joined: 03 Jun 2005
Posts: 17
|
Have you tried the following ?
mqichangetrace <BROKERNAME> -u -e <EXECUTIONGRPNAME> -f <MSGFLOWNAME> -l debug -r
mqsireadlog <BROKERNAME> -u -e <EXECUTIONGRPNAME> -o trace.xml
mqsiformatlog -i trace.xml -o trace.txt
The trace file should be located in the directory that you are running these commands from.
_________________
IBM Certified System Administrator - WebSphere MQ V5.3 |
|
| Back to top |
|
|
| gbbailey |
| Posted: Tue Nov 07, 2006 7:47 am Post subject: |
|
|
Apprentice
Joined: 12 May 2006
Posts: 27
Location: London, UK
|
I haven't tried setting a trace against a specific message flow. Only on the execution groups as a whole.
The readlog/formatlog stuff appears to be working - so it would seem that it's only the communication with the config manager that is a problem. |
|
| Back to top |
|
|
| hs |
| Posted: Tue Nov 07, 2006 8:08 am Post subject: |
|
|
Novice
Joined: 03 Jun 2005
Posts: 17
|
Your configmgr may be out of sync with the broker.
Try a complete deploy topology configuration.
_________________
IBM Certified System Administrator - WebSphere MQ V5.3 |
|
| Back to top |
|
|
| gbbailey |
| Posted: Wed Nov 08, 2006 5:13 am Post subject: |
|
|
Apprentice
Joined: 12 May 2006
Posts: 27
Location: London, UK
|
| We upgraded WMQ to 6.0.2.0 (from 6.0.1.1) and with a reboot this fixed the problem. Not sure whether it was the upgrade or the reboot though. |
|
| Back to top |
|
|
|
|
