Wonder if we should just filter out our own log messages in the JMS
appender, that way users can never get bitten by this problem.
On Fri, Aug 7, 2009 at 5:00 AM, Gary Tully wrote:
> great. thanks for completing the loop on this by sharing your solution :-)
>
> 2009/8/7 Kinski
>
> >
> > I added
great. thanks for completing the loop on this by sharing your solution :-)
2009/8/7 Kinski
>
> I added the suffix to the brokerURL
>
> I.e.
>
> log4j.appender.JMS.ProviderURL=tcp://localhost:61616?wireFormat.cacheEnabled=false
>
> but this made no difference.
>
> then finally found my needle in
I added the suffix to the brokerURL
I.e.
log4j.appender.JMS.ProviderURL=tcp://localhost:61616?wireFormat.cacheEnabled=false
but this made no difference.
then finally found my needle in the haystack with this nugget of
information..
http://www.nabble.com/Log4J-ActiveMQ-JMS-Appender-td18840199.h
Is there any way you can post your complete log4j.properties file, i am
getting "Wire format negotiation timeout: peer did not send his wire format"
error even after I followed your suggestion and added
"?wireFormat.cacheEnabled=false" to the providerurl
Tom Johnson wrote:
>
> I think I finally
I think I finally found a solution. In the ProviderURL of the appender
adding "?wireFormat.cacheEnabled=false" let the log4j JMSAppender talk to an
ActiveMQ topic.
I.e.
log4j.appender.JMS.ProviderURL=tcp://localhost:61616?wireFormat.cacheEnabled=false
--
View this message in context:
http://
It happens every time I've tried it. Not sure if this matters, but I am
using Log4j 1.2.15.
--
View this message in context:
http://www.nabble.com/ActiveMQ-5-and-Log4j-JMSAppender-error-tp14622389s2354p14667052.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I dont think so, I doubt youll get much help there.does it ALWAYS happen
or just sometimes? The reason I mention that is that we have gotten this
exception before with a spring based JMS listeners trying to connect to a
TCP AMQ broker URL and both were AMQ 4.1.1 out of the box. However, it was
All the client and server jars are from the ActveMQ installation.
Disabling the firewall has no effect on the problem.I've written a test
JMS app that produces and consumes an ObjectMessage in the topic which works
just fine.
Maybe this should be posted in a log4j forum.
Hiram Chirin
You should make sure you use matching versions of the ActiveMQ client
and server jars. The error indicates that the client connected but
did not receive the expected response from the JMS server. Are you
sure you connected to the right port and there are no firewall rules
that would cause problem
