ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Issue in Debug Mode

Post new topic  Reply to topic
 Issue in Debug Mode « View previous topic :: View next topic » 
Author Message
Frnd
PostPosted: Thu Jun 16, 2011 3:39 am    Post subject: Issue in Debug Mode Reply with quote

Apprentice

Joined: 04 Jun 2007
Posts: 33

Hi

After having deployed the flow to a local broker, I tried putting a sample message with Debug Mode ON . I am getting an popup Label Updates and in details it is just mentioned " Error". Not able to really understand what could be the problem. I can see the message tree getting updated properly everytime as I traverse the flow. The output has to be written to a file . This is not happening though..(
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Thu Jun 16, 2011 4:59 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Maayong Buntag.

Try putting some Trace Nodes every other node. Each trace node writes to a different file. C:/TEMP/log/1.txt, 2.txt, 3.txt, etc. You will then know from which files get written, and which ones dont, what node in your flow is throwing an error. The pattern you could use in your trace node is ${Root} ${CURRENT_TIMESTAMP}.

Mabuhay.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
mqjeff
PostPosted: Thu Jun 16, 2011 5:19 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Or you could use User Trace instead of debug, which will show the execution of each node and where the error occurs.

And usertrace is a good thing to get in practice with.
Back to top
View user's profile Send private message
rekarm01
PostPosted: Thu Jun 16, 2011 9:31 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 1415

lancelotlinc wrote:
Try putting some Trace Nodes every other node. Each trace node writes to a different file. C:/TEMP/log/1.txt, 2.txt, 3.txt, etc.

... or configure the Trace nodes to write to the user trace.
Back to top
View user's profile Send private message
gotnoid
PostPosted: Sun Aug 28, 2011 4:47 am    Post subject: Facing same issue Reply with quote

Novice

Joined: 20 Nov 2008
Posts: 15

HI I am facing the same issue when I try to dedug plaese let me know if you were able to find a solution.

Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Mon Aug 29, 2011 4:36 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

gotnoid, after you put your Trace nodes in, what did you see? Please post the output of your Trace nodes.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Issue in Debug Mode
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.