| Author |
Message
|
| ivanachukapawn |
 Posted: Wed Jan 03, 2007 1:14 pm Post subject: Trace node |
 |
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
I wired each MQInput terminal (failure, out, catch) to a Trace Node. I configured each trace node to write to a file. I specified the full path name of each file in a directory which already exists.
When I queue a message it is consumed by the message flow. However, no trace file is created. Lets face it, I'm going to feel like an idiot when one of you guys tells me whats wrong here. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Jan 03, 2007 1:18 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You did redeploy your flow after wiring in the trace node?
You did re-add your flow to the BAR file before re-deploying after wiring in the trace node? Or create a new BAR file?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ivanachukapawn |
| Posted: Wed Jan 03, 2007 1:29 pm Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
OK. That does it. I'm definitely in that category I mentioned earlier.
I did redeploy after wiring in the Trace nodes.
But I didn't create a new bar or re-add the flow to the existing bar.
thanks for bearing with me.
regards,
ivana |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jan 03, 2007 1:34 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
See, if you had gotten training, you would have avoided this embarrasment... 
Also, the 6.0.2 update of the Toolkit will update your Bar files for you.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| pathipati |
| Posted: Wed Jan 03, 2007 5:32 pm Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
And make sure Auto Build is also never turned off..  |
|
| Back to top |
|
|
| ivanachukapawn |
| Posted: Thu Jan 04, 2007 7:31 am Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
| Autobuild was turned on and I'm running 6.0.2 Toolkit. So I gather the bar should be automatically updated when I save changes to the message flow/message set. Regardless, I created a new bar and deployed it. The deployed message flow has the MQInput Node failure, out, and catch terminals each wired to trace nodes configured to write files to a pre-existing directory. When I queue a message it is consumed by the message flow but no trace files are created. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jan 04, 2007 7:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What does mqsilist show for the broker?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jan 04, 2007 7:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Also, what is the open input count on the queue?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ivanachukapawn |
| Posted: Thu Jan 04, 2007 7:48 am Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
mqsilist <brokerName> shows 6 execution groups (4 of which are default) running one of which is the execution group I deployed the message flow to.
Open Input count for the queue is 6.
Application connections to the queue manager are many. 4 of which are for one of the default dataflow engines. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jan 04, 2007 7:50 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So you see four copies of an execution group with the same name?
If so, you have phantom execution groups. Go into the Toolkit, delete the default execution group and deploy the topology. Stop the broker. Start the broker. confirm that you don't have any copies of the deleted execution group. Recreate the EG and redeploy.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| pathipati |
| Posted: Thu Jan 04, 2007 8:36 am Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
| You can also use Java Proxy API to delete the Execution groups and to create new one. |
|
| Back to top |
|
|
| ivanachukapawn |
| Posted: Thu Jan 04, 2007 9:40 am Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
interesting situation. I deleted the default execution group. Only one execution group remaining in this broker. I deployed the broker topology complete. I stopped the broker. I started the broker. I mqsilisted the broker and viewed :
the desired execution group - 1 thread
the default execution group - 3 threads
At this point haven't I done what I need to do in order to get rid of default EG threads? |
|
| Back to top |
|
|
| pathipati |
| Posted: Thu Jan 04, 2007 9:50 am Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
Try using Java Proxy API to delete the default eg.
Any way for testing your message flow create any new Execution group. |
|
| Back to top |
|
|
| jeevan |
| Posted: Thu Jan 04, 2007 10:06 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
try using command line Utility. I has same problem and nothing could remove until use command at command line.
mqsideleteexecu............. see the details syntax in info centre |
|
| Back to top |
|
|
| ivanachukapawn |
| Posted: Thu Jan 04, 2007 10:18 am Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
Jeevan,
I tried mqsideleteexecutiongroup -b TESTBROKER -e default -i localhost -p 1414 -q TESTCONFIGQMGR
and got 'Execution Group not found'
'Either the execution group 'default' was not found in the Configuration Manager repository for broker 'TESTBROKER' or you do not have the required permissions to view it.'
Well, I didn't expect the repository to contain the default EG because I deployed a broker topology which had the default EG removed.
Nevertheless - mqsilist TESTBROKER displays:
BIP8130I: Execution Group: default - 2168 |
|
| Back to top |
|
|
|
|
