can you run with -Dlog4j.debug (set the system property) to see where
the log4j configuration is coming from?

It may be that the wireFormatNegotiator is trying to log a message
which is trying to start a jms connection which uses
wireFormatNegotiator etc. Chicken and egg.
logging for activemq needs to be disabled if it is used as a default appender.
Possibly you have this configured but your log4j configuration is not
being picked up.

-Dlog4j.debug should help diagnose this as it will use System.err to
output what it is up to while it gets initialised.

2009/1/14 Richard Dunn <gnup...@mac.com>:
>
> I am also having this problem, but the problem only occurs in one scenario -
> in my appfuse based spring web application. If I use the same versions of
> activemq and log4j in my other web applications (older traditional
> jsp/servlet webapps) everything works fine. I am currently using activemq
> 5.1, 5.2, 5.3 (beta versions) and log4j 1.2.15 and I get error listed in
> just the spring application. The same versions of activemq and log4j work
> fine with non-spring. I am wondering if this may be due to the introduction
> of the slf4j as part of the spring.
>
> This all is rather distressing for me as I see evidence of this problem on
> many lists and see mention of this in
> https://issues.apache.org/activemq/browse/AMQ-1473, but no resolutions.
>
> Too much has been committed already in our JMSAppender based logging
> infrastructure (which works well in all but spring) and our spring based
> webapp to easily back out of either.
>
> log4j:WARN No appenders could be found for logger
> (org.apache.activemq.transport.WireFormatNegotiator).
> log4j:WARN Please initialize the log4j system properly.
> log4j:ERROR Error while activating options for appender named [jms].
> javax.jms.JMSException: Wire format negotiation timeout: peer did not send
> his wire format.
>        at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:62)
>        at
> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1206)
>        at
> org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1289)
>        at
> org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:295)
>        at
> org.apache.activemq.ActiveMQConnection.createTopicSession(ActiveMQConnection.java:998)
>        at 
> org.apache.log4j.net.JMSAppender.activateOptions(JMSAppender.java:217)
>        at 
> org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:257)
>        at
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:133)
>        at
> org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:97)
>        at
> org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:689)
>        at
> org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:647)
>        at
> org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:544)
>        at
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:440)
>        at
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:476)
>        at
> org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:471)
>        at org.apache.log4j.LogManager.<clinit>(LogManager.java:125)
>        at 
> org.slf4j.impl.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:73)
>        at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:88)
>        at
> org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:155)
>        at
> org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:131)
>        at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:645)
>
> --
> View this message in context: 
> http://www.nabble.com/Log4J-ActiveMQ-JMS-Appender-tp18840199p21461090.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>



-- 
http://blog.garytully.com

Open Source SOA
http://FUSESource.com

Reply via email to