Posted: Wed Aug 10, 2011 2:10 pm Post subject: Trace Nodes in MultiThread Environment
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?
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.
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