You might want to disable the multicast features in your activemq.xml
- it could be folks are running different versions of ActiveMQ on your
LAN which are connecting with each other
On 11/20/06, suri009 <[EMAIL PROTECTED]> wrote:
I get this exception when my client try to connect to broker in a different
machine. My client does not get this exception every time, but they get once
in every 4 attempts. Clients are testing the system so they are doing
connect/disconnects. Do i need to change any configuration to avoid this
exception?
Is my below configuration of activemq broker, publisher and subscriber
correct?
<transportConnectors>
<transportConnector name="default"
uri="tcp://170.19.18.141:61616?soTimeout=10000&connectionTimeout=30000"
discoveryUri="multicast://172.19.18.157"/>
</transportConnectors>
client (Topic subscriber) is connecting using uri:
tcp://170.19.18.141:61616?wireFormat.maxInactivityDuration=0
Server (Topic Publisher) is connecting using uri:
failover:(tcp://172.19.18.157:61616)?jms.useAsyncSend=true&wireFormat.maxInactivityDuration=0
javax.jms.JMSException: Wire format negociation timeout: peer did not send
his w
ire format.
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSuppo
rt.java:58)
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnect
ion.java:1125)
at
org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(Activ
eMQConnection.java:1203)
at
org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnecti
on.java:272)
at
org.apache.activemq.ActiveMQConnection.createTopicSession(ActiveMQCon
nection.java:904)
at
com.baa.tg.commons.jms.JmsMessageReceiver.initialize(JmsMessageReceiv
er.java:101)
at
com.baa.tg.commons.jms.JmsMessageReceiver.startReceiver(JmsMessageRec
eiver.java:58)
at com.test.tg.client.awt.JFMain$3.run(JFMain.java:249)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchTh
read.java:242)
at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThre
ad.java:163)
at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
Caused by: java.io.IOException: Wire format negociation timeout: peer did
not se
nd his wire format.
at
org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatN
egotiator.java:82)
at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.ja
va:45)
at
org.apache.activemq.transport.ResponseCorrelator.asyncRequest(Respons
eCorrelator.java:67)
at
org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorr
elator.java:72)
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnect
ion.java:1115)
... 17 more
--
View this message in context:
http://www.nabble.com/Exception-on-client-connection-tf2669782.html#a7444710
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
James
-------
http://radio.weblogs.com/0112098/
