| Author |
Message
|
| ruimadaleno |
 Posted: Tue Jun 02, 2015 2:58 am Post subject: Find execution group name by uuid |
 |
|
Master
Joined: 08 May 2014
Posts: 274
|
Hi all,
we are monitoring the errors throw by every execution group in console.txt (in this install there are several execution groups, so , several console.txt files).
The console.txt files are written to the "broker repository" (please correct if i am wrong), each execution group gets a folder were the console.txt file "lives".
So in our environment we have:
| Quote: |
M:\BRKESB01A\Shared\mqsi\components\BRKESB01A\6f64d8dd-3b01-0000-0080-a1e585d1c154
M:\BRKESB01A\Shared\mqsi\components\BRKESB01A\11a47355-4b01-0000-0080-959c9f749b12
M:\BRKESB01A\Shared\mqsi\components\BRKESB01A\38bb7255-4b01-0000-0080-b46735ec68d2
M:\BRKESB01A\Shared\mqsi\components\BRKESB01A\42dd6d55-4b01-0000-0080-92e85a373821
|
The question here is:
looking to a console.txt file how can i know the execution group name it belongs to ?
How can translate the execution group UUID to execution group name ?
how can i find that folder M:\BRKESB01A\Shared\mqsi\components\BRKESB01A\38bb7255-4b01-0000-0080-b46735ec68d2
is the repository for execution group "blablabla" ?
The same info (UUID) is displayed in console.txt
| Quote: |
THREAD_CLEANUP CALLED FOR TID 0x1514 (5396)
THREAD_CLEANUP CALLED FOR TID 0x15A0 (5536)
2015-05-02 01:26:09.957 Execution group started. UUID is: 'a7cd6f55-4b01-0000-0080-8951d05129e3'. Broker is: BRKESB01A
THREAD_CLEANUP CALLED FOR TID 0x2508 (9480)
THREAD_CLEANUP CALLED FOR TID 0x16C0 (5824)
THREAD_CLEANUP CALLED FOR TID 0x1FB8 (8120)
THREAD_CLEANUP CALLED FOR TID 0x16E0 (5856)
THREAD_CLEANUP CALLED FOR TID 0x383C (14396)
THREAD_CLEANUP CALLED FOR TID 0x3BD8 (15320)
THREAD_CLEANUP CALLED FOR TID 0x1380 (4992)
THREAD_CLEANUP CALLED FOR TID 0x19C0 (6592)
THREAD_CLEANUP CALLED FOR TID 0x2764 (10084)
THREAD_CLEANUP CALLED FOR TID 0x172C (5932)
THREAD_CLEANUP CALLED FOR TID 0x14AC (5292)
THREAD_CLEANUP CALLED FOR TID 0x5B0 (1456)
THREAD_CLEANUP CALLED FOR TID 0x2668 (9832)
THREAD_CLEANUP CALLED FOR TID 0x3678 (13944)
THREAD_CLEANUP CALLED FOR TID 0x2924 (10532)
2015-05-07 23:33:54.769001 Execution group started. UUID is: 'a7cd6f55-4b01-0000-0080-8951d05129e3'. Broker is: BRKESB01A
|
my environment: WMB 8.0.0.4 running on windows 2008 server R2
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
 |
| KIT_INC |
| Posted: Tue Jun 02, 2015 10:37 am Post subject: |
|
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
Can you tell us what version of WMB you are using and what platform you are running on. Console.txt is not something that I am familiar with.
If you do a mqsilist -d2 brokername it will list out uuid of all the execution group that is running under the broker. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jun 02, 2015 11:16 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Console.txt is the Windows equivalent of the DFE on unix stdout and stderr files.
It generally shouldn't be reviewed on a regular basis, and I think it would be a poor idea to monitor it's contents.
It can be occasionally useful in certain specific troubleshooting situations.
You should never let your JCN or .NET programmers write to stdout or stderr. |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Wed Jun 03, 2015 12:31 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
| KIT_INC wrote: |
Can you tell us what version of WMB you are using and what platform you are running on. Console.txt is not something that I am familiar with.
If you do a mqsilist -d2 brokername it will list out uuid of all the execution group that is running under the broker. |
we are running WMB 8.0.0.4 on windows 2008 server R2
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Wed Jun 03, 2015 12:37 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
| mqjeff wrote: |
Console.txt is the Windows equivalent of the DFE on unix stdout and stderr files.
It generally shouldn't be reviewed on a regular basis, and I think it would be a poor idea to monitor it's contents.
It can be occasionally useful in certain specific troubleshooting situations.
You should never let your JCN or .NET programmers write to stdout or stderr. |
Thank you for your pointers. I agree with you, we never allow developers to write to stdout or sdterr. I don't want to monitor the console.txt files on a regular basis, the info it contains is mainly used in PMR info gathering. It would be helpful for my team to quickly identify the execution group from the console.txt
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 03, 2015 5:11 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I agree it would be helpful.
The way to achieve that is to file an RFE...
After confirming that this behavior does not exist in v10...  |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jun 03, 2015 5:14 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| ruimadaleno wrote: |
| It would be helpful for my team to quickly identify the execution group from the console.txt |
Have you thought about writing a little java program using the CMP API?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Tue Jun 09, 2015 1:10 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
i'd like to thank you all for your answers, as pointed by KIT_INC an mqsilist will do the trick 
| Quote: |
E:\IBM\MQSI\8.0.0.1\bin>mqsilist BRKxxx -d2
-----------------------------------
BIP1286I: Execution group 'default' on broker 'BRKxxx' is running.
Number of message flows that are enabled to run: '27'.
Number of applications that are enabled to run: '27'.
Process ID: '5644'
UUID: '045f122d-3b01-0000-0080-b76d274c9b1a'
Short description: ''
Long description: ''
-----------------------------------
BIP1286I: Execution group 'eg_utility_01' on broker 'BRKxxx' is running
Number of message flows that are enabled to run: '4'.
Number of applications that are enabled to run: '4'.
Process ID: '5736'
UUID: '08ac49ed-4a01-0000-0080-f34a3748a9c2'
Short description: ''
Long description: ''
-----------------------------------
BIP1286I: Execution group 'eg_utility_02' on broker 'BRKxxx' is running
Number of message flows that are enabled to run: '4'.
Number of applications that are enabled to run: '4'.
Process ID: '3080'
UUID: '36795455-4b01-0000-0080-81a73585878d'
Short description: ''
Long description: ''
-----------------------------------
BIP1286I: Execution group 'eg_apps_02' on broker 'BRKxxx' is running.
Number of message flows that are enabled to run: '4'.
Number of applications that are enabled to run: '4'.
Process ID: '5104'
UUID: 'c39b5755-4b01-0000-0080-bace988cbc2c'
Short description: ''
Long description: ''
-----------------------------------
BIP1286I: Execution group 'eg_apps_04' on broker 'BRKxxx' is running.
Number of message flows that are enabled to run: '3'.
Number of applications that are enabled to run: '3'.
Process ID: '5616'
UUID: '8fd85a55-4b01-0000-0080-efbe957dde07'
Short description: ''
Long description: ''
-----------------------------------
BIP1286I: Execution group 'eg_batch_01' on broker 'BRKxxx' is running.
Number of message flows that are enabled to run: '5'.
Number of applications that are enabled to run: '5'.
Process ID: '6160'
UUID: '73035c55-4b01-0000-0080-ea88ba3455b5'
Short description: ''
Long description: ''
-----------------------------------
BIP1286I: Execution group 'eg_apps_03' on broker 'BRKxxx' is running.
Number of message flows that are enabled to run: '4'.
Number of applications that are enabled to run: '4'.
Process ID: '2116'
UUID: '1716b3d4-4d01-0000-0080-c6ee41d9b870'
Short description: ''
Long description: ''
BIP8071I: Successful command completion.
|
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Jun 09, 2015 1:17 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
The way I find the UUID is just to use a command like
ps -ef | grep <EGNAME>
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
|
|
