3 Replies Latest reply on Aug 24, 2010 4:53 AM by Frank Henry

    Unable to trace the message logs

    Alok G Newbie

      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

      Alok G
        • 1. Re: Unable to trace the message logs
          Yong Hao Gao Master

          I think you can modify jboss-log4j.xml under <your-messaging-server-config>/conf directory.

          • 2. Re: Unable to trace the message logs
            Brent Sordyl Newbie

            The org.jboss.soa.esb.messagetrace property needs to be defined in the filters properties section:


            <properties name="filters">      

               <property name="org.jboss.soa.esb.filter.1" value="org.jboss.internal.soa.esb.message.filter.MetaDataFilter"/>            
               <property name="org.jboss.soa.esb.filter.2" value="org.jboss.internal.soa.esb.message.filter.GatewayFilter"/>        
            <!-- add the logging MetaData Filter for message tracing -->        
               <property name="org.jboss.soa.esb.filter.3" value="org.jboss.internal.soa.esb.message.filter.TraceFilter"/>     

            <!-- enable global message tracing -->        
               <property name="org.jboss.soa.esb.messagetrace" value="ON"/>    

            • 3. Re: Unable to trace the message logs
              Frank Henry Novice

              I have the same needs for jboss-messaging 1.4

              Currently I have a generic listener that can be configured to listen to multiple topics. While this is ok, I cannot use it for Queues.


              Due to the nature of jboss-messaging, I think it would be a vital addition.