There is no such timeout on the broker side.
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - http://fusesource.com
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Tue, Jun 7, 201
Good question. Only thing I can say is that it's a reasonably large XML
packet being posted. I will try to find the size of it in a debug session.
Is there a timeout period during a send perhaps that should be tweaked?
On 7 June 2011 11:59, Dejan Bosanac wrote:
> Hi James,
>
> this exception ju
Hi James,
this exception just means that the client closed the connection to the
broker unexpectedly. It would be helpful if you could find a way to
reproduce what you're seeing.
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and mes
Got a Stomp client that just reported "Server not responding". Logs from
AMQ:
2011-06-07 09:45:15,087 | DEBUG | Setting up new connection id:
ID:ubuntu-33097-1307336686696-
5:54, address: /127.0.0.1:36529 |
org.apache.activemq.broker.TransportConnection | ActiveMQ Tr
ansport: tcp:///127.0.0.1:3652
