You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2015/04/08 15:29:12 UTC

[jira] [Closed] (AMQ-5635) logging not configureable in activemq-client-api

     [ https://issues.apache.org/jira/browse/AMQ-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQ-5635.
-----------------------------
    Resolution: Incomplete

Cannot reproduce, no config files attached to check users side.  

> logging not configureable in activemq-client-api
> ------------------------------------------------
>
>                 Key: AMQ-5635
>                 URL: https://issues.apache.org/jira/browse/AMQ-5635
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.8.0
>            Reporter: Thorben Schiller
>            Priority: Minor
>
> While using the activemq-client-API in an application it is not possible to customize the logging of the Framework...
> The logging configurations in my log4j.xml do not take effect. 
> I configured:
> <logger name="org.apache.activemq.transport.failover.FailoverTransport">
>         <level value="ERROR" />
> </logger>
> The applications logs:
> [ActiveMQ Task-1] INFO org.apache.activemq.transport.failover.FailoverTransport - Successfully connected to tcp://bmi-evergabe-web-qs01.adesso.de:61616
> log4j-Debugging confirmes that it takes my log4j.xml. It configures:
> - Setting [org.apache.activemq.transport.failover.FailoverTransport] additivity to [true].
> - log4j: Level value for org.apache.activemq.transport.failover.FailoverTransport is  [ERROR].
> - log4j: org.apache.activemq.transport.failover.FailoverTransport level set to ERROR



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)