James,
I get OutOfMemoryError's in activemq log. Do you think this might be the reason to throw wireformat exception to my clients? Exception in thread "ActiveMQ Transport: tcp:///172.19.18.141:57219" java.lang.OutOfMemoryError: Java heap space Exception in thread "ActiveMQ Transport: tcp:///172.19.18.141:57220" java.lang.OutOfMemoryError: Java heap space Exception in thread "ActiveMQ Transport: tcp:///172.19.18.141:57221" java.lang.OutOfMemoryError: Java heap space Exception in thread "ActiveMQ Transport: tcp:///172.19.18.141:57222" java.lang.OutOfMemoryError: Java heap space Thanks, Suri James.Strachan wrote: > > So you're definitely not using any multicast or discovery at all - so > if you get exceptions either the broker has failed / been killed or > there's something wonky with your network (firewall or router issues?) > > You can get around this by using failover... > http://incubator.apache.org/activemq/failover-transport-reference.html > > e.g. use the client side URI... > > failover:tcp://172.19.18.141:61616. > > -- View this message in context: http://www.nabble.com/Exception-on-client-connection-tf2669782.html#a7607816 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
