User development, A new message was posted in the thread "Unable to trace the message logs":
http://community.jboss.org/message/525268#525268 Author : Alok G Profile : http://community.jboss.org/people/alokgswamy Message: -------------------------------------------------------------- 1.6. Message tracingh2. 1.6. Message tracing It is possible to trace any and all Messages sent through the JBoss SOA Platform. This is often required for a number of reasons, including audit trail and debugging. Messages must be uniquely identified using the MessageID field of the Message header in order to be traced. This is referred to in the Programmers Guide. This is the only way in which Messages can be uniquely identified within the JBoss SOA Platform. By default, JBoss SOA components (e.g., gateways, ServiceInvoker and load balancing) log all interactions with Messages using standard logger messages. The log messages will contain the header information associated with the Message, enabling correlation across multiple SOA Platform instances. These messages can be identified by looking for the following in your output: header: [ To: EPR: PortReference < <wsa:Address ftp://foo.bar/> >, From: null, ReplyTo: EPR: PortReference < <wsa:Address http://bar. foo/> >, FaultTo: null, Action: urn:dowork, MessageID: urn:foo/bar /1234, RelatesTo: null ] Furthermore, you can enable a logging MetaData Filter, whose only role is to issue log messages whenever a Message is either input to an SOA Platform component, or output from it. This filter, org.jboss.internal.soa.esb.message.filter.TraceFilter, can be placed within the Filter section of the JBossESB configuration file, in conjunction with any other filters: it has no effect on the input or output Message. Whenever a Message passes through this filter, you will see the following log at info level: TraceFilter.onOutput ( header: [ To: EPR: PortReference < <wsa:Add ress ftp://foo.bar/> >, From: null, ReplyTo: EPR: PortReference < <wsa:Address http://bar.foo/> >, FaultTo: null, Action: urn:dowork , MessageID: urn:foo/bar/1234, RelatesTo: null ] ) TraceFilter.onInput ( header: [ To: EPR: PortReference < <wsa:Addr ess ftp://foo.bar/> >, From: null, ReplyTo: EPR: PortReference < < wsa:Address http://bar.foo/> >, FaultTo: null, Action: urn:dowork, MessageID: urn:foo/bar/1234, RelatesTo: null ] ) TraceFilter will only log if the property org.jboss.soa.esb.messagetrace is set to on/ON. The default setting is off/OFF. If enabled it will log all Messages that pass through it. However you may enable finer grained control over which Messages are logged and which are ignored. To do this make sure that the property org.jboss.soa.esb.permessagetrace is set to on/ON. Those Messages with a property of org.jboss.soa.esb.message.unloggable set to yes/YES will now be ignored by this filter. I am working on message tracing in jboss, i want to log the message to server.logs In which file do i need to set the filters on to get the message tracing on i am currently using jboss-soa-p.4.3.0 version plz do help me Regards, Alok G -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/525268#525268
_______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
