| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Tracing the Workbench |
« View previous topic :: View next topic » |
| Author |
Message
|
| dda |
 Posted: Tue Jun 06, 2006 7:00 pm Post subject: Tracing the Workbench |
 |
|
Newbie
Joined: 06 Jun 2006
Posts: 2
|
I need to trace the workbench of Message Broker V6.
According to the documentation, a command of the style:
mqsichangetrace workbench -l debug
should do the trick.
However, commands that use the COMPONENT "workbench" allo seem to fail with:
BIP8013E: Component does not exist.
A component may only be used if it has first been created.
No user action required.
Is workbench trace broken? Non-existent? |
|
| Back to top |
|
 |
| pottas |
| Posted: Tue Jun 06, 2006 10:19 pm Post subject: |
|
|
Disciple
Joined: 27 Oct 2005
Posts: 185
Location: South Africa
|
Hi dda,
Quote from the docs:
| Quote: |
You can initiate, modify, or terminate user tracing for a broker, or initiate, modify, or terminate service tracing for a broker, a Configuration Manager, or the User Name Server (identified by component name). You cannot use this command to initiate service tracing for the workbench.
|
...and then further on in hte same doc:
| Quote: |
On Windows platforms, Linux, and UNIX systems, you can also start and stop tracing activity for execution groups and message flows using the facilities of the workbench. See User trace for more information.
|
Alternatively, if you want to do a trace in a specific message flow, you can use Trace nodes:
| Quote: |
Purpose
Use the Trace node to generate trace records that can incorporate text, message content, and date and time information, to help you to monitor the behavior of the message flow.
You can write the records to the user trace file, another file, or the local error log (which contains error and information messages written by all other WebSphere Message Broker components). If you write traces to the local error log, you can issue a message from the default message catalog supplied with WebSphere Message Broker, or you can create your own message catalog.
The operation of the Trace node is independent of the setting of user tracing for the message flow in which it resides. In particular, records written by the Trace node to the user trace log are written even if user trace is not currently active for the message flow.
|
Hope this gives you some direction at least.
pottas |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Jun 07, 2006 12:28 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| I need to trace the workbench of Message Broker V6. |
Why do you need to trace the workbench? Pottas is right - there's no way to do it using mqsichangetrace, or any other IBM-supplied utility. The workbench is an Eclipse application written in Java, so there are certainly ways of getting trace information from the JVM. But you would be better off telling us what the problem is before you go down that route. |
|
| Back to top |
|
|
| dda |
| Posted: Wed Jun 07, 2006 10:08 am Post subject: Long Build Times |
|
|
Newbie
Joined: 06 Jun 2006
Posts: 2
|
Kimbert,
I was wanting to diagnose some LONG build times which a customer is experiencing. Since then I have discovered that turning off ESQL validation reduces the build (or clean) time for the project from 4 HOURS to 1 minute.
I would nevertheless like to trace what's happening (and where we run out of puff in the 4 HOUR version).
The product documentation says that mqsichangetrace requires a COMPONENT, and that one of the things a COMPONENT can be is the literal "workbench".
Anyway, regardless of the doc, you are correct... it does not work. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
