[jira] Updated: (AMQ-608) Change logging level of some DemandForwardingBridge log messages.

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (AMQ-608) Change logging level of some DemandForwardingBridge log messages.

JIRA jira@activemq.org
     [ http://jira.activemq.org/jira//browse/AMQ-608?page=all ]

Kevin Yaussy updated AMQ-608:
-----------------------------

    Attachment: FailoverTransport.java
                DemandForwardingBridgeSupport.java

Just to push my luck on this one, I've attached the changes again in terms of the most recent SNAPSHOT release... ;-)


> Change logging level of some DemandForwardingBridge log messages.
> -----------------------------------------------------------------
>
>          Key: AMQ-608
>          URL: http://jira.activemq.org/jira//browse/AMQ-608
>      Project: ActiveMQ
>         Type: Improvement

>   Components: Broker
>     Versions: 4.0
>     Reporter: Kevin Yaussy
>  Attachments: DemandForwardingBridge.java, DemandForwardingBridgeSupport.java, FailoverTransport.java, FailoverTransport.java
>
>
> In DemandForwardingBridge, I'd like to be able to see subscription messages (and unsubscription messages), but not "bridging" messages.  Both classes of log messages are log.trace.  Seems like the "bridging" messages should remain trace, as you would want to look at that when you are doing pretty detailed debugging.  However, I'd like to see subscribe/unsubscribe messages all the time.  If those could be either info or debug, that would allow me to turn those on separately.  I realize that I can see what is currently subscribed via the JMX console.  However, seeing the subscribe/unsubscribe messages will allow diagnostics over time - who subscribed when type of questions.
> Mainly, I'm referring to messages logged as trace in:
> DemandForwardingBridge.serviceRemoteConsumerAdvisory
> DemandForwardingBridge.removeDemandSubscription

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.activemq.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira