SLF4J finds the two bindings below, but not the log4j2 binding (
*log4j-slf4j-impl-2.0.jar*).
So first you need to add the log4j2 slf4j impl dependency.
Second the classpath will still have the two jars below that also provide a
binding. So whichever comes first in the classpath is the binding us
I don't think there is any problem with that jar, the issue is that I am
trying to use log4j 2 but the dependency jar that I am using is using log4j
1. When I switch back to log4j 1 everything works fine. Is there a way to
avoid this compatibility issue? Not sure how others that have similar
issue
The problem is in activemq-all-5.9.0.jar. I suggest you contact the activemq
team.
Sent from my iPhone
> On 2014/04/03, at 2:53, Gary Gregory wrote:
>
> activemq-all-5.9.0.jar
-
To unsubscribe, e-mail: log4j-user-unsubscr..
; at
> > >
> >
> org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:616)
> > > at
> > >
> >
> org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:602)
> > > at
> > >
> > >
> >
> org.apache.log4
>
> org.mule.tck.junit4.AbstractMuleTestCase.(AbstractMuleTestCase.java:71)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > On Tue, Apr 1, 2014 at 12:41 PM, Gary Gregory > >wrote:
> >
> > > On Tue, Apr 1, 2014 at 3:13 PM, Mohit Anchlia
gt; How do I reload configuration?
> >
> >
> > Please see:
> > -
> >
> >
> https://logging.apache.org/log4j/2.x/manual/configuration.html#AutomaticReconfiguration
> > -
> >
> >
> https://logging.apache.org/log4j/2.x/log4j-core/apidocs/org/apache/logging/l
> > You would be better served using version 2 which we are actively
> working
> > > on.
> > >
> > > Gary
> > >
> > > Original message
> > > From: Mohit Anchlia
> > > Date:04/01/2014 15:01 (GMT-05:00)
> > > To: Log4J
014 at 12:09 PM, Gary Gregory >wrote:
>
> > You would be better served using version 2 which we are actively working
> > on.
> >
> > Gary
> >
> > Original message
> > From: Mohit Anchlia
> > Date:04/01/2014 15:01 (GMT-05
ge
> From: Mohit Anchlia
> Date:04/01/2014 15:01 (GMT-05:00)
> To: Log4J Users List
> Subject: Unit testing log4j JMS Appender
>
> I am trying to unit test log4j with jms appender, however even before I
> bring up the jms embedded broker service log4j.properties
You would be better served using version 2 which we are actively working on.
Gary
Original message
From: Mohit Anchlia
Date:04/01/2014 15:01 (GMT-05:00)
To: Log4J Users List
Subject: Unit testing log4j JMS Appender
I am trying to unit test log4j with jms appender
I am trying to unit test log4j with jms appender, however even before I
bring up the jms embedded broker service log4j.properties get loaded and it
fails to connect to the broker. Is there a way to reload log4j after the
broker is up?
Configure log4j on any sample project and the enable JMS appender for the
same. Logging should be done against a file and then against pre-defined
queue.
--
View this message in context:
http://old.nabble.com/log4j-JMS-appender-tp31970722p31970722.html
Sent from the Log4j - Users mailing list
12 matches
Mail list logo
