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 » Trace Nodes in MultiThread Environment

Post new topic  Reply to topic
 Trace Nodes in MultiThread Environment « View previous topic :: View next topic » 
Author Message
amitkothari18
PostPosted: Wed Aug 10, 2011 2:10 pm    Post subject: Trace Nodes in MultiThread Environment Reply with quote

Novice

Joined: 12 Feb 2011
Posts: 24

Hi,

I need some help to understand the behavior of Trace nodes in a multi threaded broker environment. Will that be a problem if two instances of a msgflow try to write to same trace file, how is that handled by WMB?

Also, will the same behavior apply to multiple brokers running same flows with Trace nodes writing to same location and same files?

All the help is really appreciated!!

WMBv6.1.0.8

Thanks
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Aug 11, 2011 4:02 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Trace nodes are intended as diagnostic aids and therefore don't typically run in mutli-threaded, high throughput environments. They're a cumbersome and resource hungry means of logging messages.

If you're writing to an external file, 2 instances writing to the same file will be handled by the OS not by WMB and whatever file-collision mechanism the OS has (if any) will come into play. Typically one instance will get an I/O error and crash. If they're writing to the broker log, then the trace information won't collide but will be intervieved.

Likewise multiple brokers have their own internal logs so the Trace output will go there if logged internally. If they're using external files then my comments above apply.

I can't think of a good reason to use Trace nodes like this. The only reason I can think of is the one I gave up top (message logging) and that's not a good reason. What are you attempting to achieve here?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Trace Nodes in MultiThread Environment
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.