[esb-issues] [JBoss JIRA] Updated: (JBESB-1009) Message Trace: The ability to follow the path of a message through the system

Message Trace: The ability to follow the path of a message through the system ----------------------------------------------------------------------------- Key: JBESB-1009 URL: http://jira.jboss.com/jira/browse/JBESB-1009 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Documentation, Management Affects Versions: 4.2 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2.1 IR1 A very common request is to know the path followed by a message and its final resting place. This is particularly important in a federated architecture (multiple ESB nodes, hosting different services) where routing, filtering and the DLQ and redelivery service may be involved. The ESB already performs logging so this is more a matter of testing & documentation so that an administrator knows what knobs to turn and what levers to pull to enable system-wide logging of inflight messages. - The tracing should also include which EPR was selected during load-balancing, fail-over, by the ServiceInvoker, etc. The expectation is that if a message fails to reach its final destination it is important to know which EPR specifically was the problem. The log should be human readable. The most common use case is that a message will arrive in the ESB's Dead Letter Queue/Service (not the underlying JMS provider) and we (the system admin) will need to be able to backtrack it to the action, service and EPR (service instance) that had the failure. Related requests: - Tracing on a message by message basis, some are tracked others are not. - Ideally this is something that can be turned on or off at runtime without interruption to the inflight messages