I will look into this over the weekend and will let you know. My client and
server are both using a single connection (I'm using a
SingleConnectionFactory), the client only uses one session, the server uses
a session per thread. It's when the server is run with 6 or more threads I
get problems.
I'll give it a try over the weekend and will let you know.
Thanks
rajdavies wrote:
>
> do the errors exist on the latest 4.2 snapshot?
>
--
View this message in context:
http://www.nabble.com/Async-Exception%3A-Broken-Pipe-tf3160498.html#a8776795
Sent from the ActiveMQ - User mailing list
do the errors exist on the latest 4.2 snapshot?
On 2 Feb 2007, at 17:44, Paul French wrote:
These two other posts seem related and have not been responded to,
I would
appreciate any advice since I'm snookered at the moment..
http://www.nabble.com/onAsyncException-and-Broken-Pipe-proble
These two other posts seem related and have not been responded to, I would
appreciate any advice since I'm snookered at the moment..
http://www.nabble.com/onAsyncException-and-Broken-Pipe-problem-t1664826.html#a4511552
http://www.nabble.com/stopping-master-bridge%2C-negociation-timeout---out
Placing the broker on another idendepent machine made no difference. I ran
the broker in DEBUG and here is some of the relevant output. I really need
some help here since I cannot scale the application as required.
DEBUG TransportConnection- Setting up new connection:
org.apache.act
[
So first off, ActiveMQ supports auto-reconnection to avoid things
hanging if for whatever reason a socket is closed by your OS /
hardware /network
http://activemq.apache.org/how-can-i-support-auto-reconnection.html
Also each Connection created in ActiveMQ tends to create a socket and
a thread on
