On Wed, Jan 14, 2009 at 10:39 AM, Richard Dunn <gnup...@mac.com> wrote:
>
> 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)

Do you have a configuration with a logger that makes use of the
org.apache.log4j.net.JMSAppender as noted above? Based on the output
above, it looks like the logger's name is 'jms'.

Bruce
-- 
perl -e 'print 
unpack("u30","D0G)u8...@4vyy9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'

Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/

Blog: http://bruceblog.org/

Reply via email to