Logging on JBoss Messaging Service

Solution Unverified - Updated -

Issue

  • We have been dealing with numerous problems with the JBoss Messaging Service. Our application architecture is heavily reliant on JMS Queues (for asynchronous processing) and JMS Topics (used to push notifications to thick client's).

  • Our client would like to see more logging in the messaging service. Specifically, they would like to see details on:

  1. When messages are sent/published to a Queue or Topic
  2. When messages are consumed from a Queue
  3. When messages are delivered from a Topic to subscribed client

-They would like to enable this logging in Production, so we would need to limit the volume of logs and their impact on performance. Can you recommend a way to focus the trace logging on key Message service components to meet the requirements stated above, possibly class names to set on the log4j category?

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 4.3
    • 5.x
  • JBoss Messaging (JBM)
    • 1.4.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.