-
1. Re: Cannot subscribe to this destination: Broken pipe
adrian.brock Jun 25, 2003 6:52 AM (in response to delboypass)Stacktrace, jboss version?
Any number of sessions can exist against a connection, but you will typically get a bottleneck
if this is a socket.
Using multiple senders/receivers on the same session
causes problems if you want to do things with
the session like commit.
Regards,
Adrian -
2. Re: Cannot subscribe to this destination: Broken pipe
delboypass Jun 25, 2003 7:25 AM (in response to delboypass)JBoss version 3.0.4
Dont have a stack trace.
All i have in the exception string
Cannot subscribe to this destination: Broken Pipe
(java.io.IOException: Broken pipe)
The exception is being thrown when is trying to initialise
a QueueSession and a QueueReciever.
Is there anyway of fixing a broken pipe?? and what throws it?
Ill try to get a stack tracew but ill probably have to wait a day for it to fall over again. -
3. Re: Cannot subscribe to this destination: Broken pipe
adrian.brock Jun 25, 2003 12:20 PM (in response to delboypass)Broken pipe is an OS message, it is wrapped
in an IOException by the VM.
If it is due to a socket exception, you should be
able to trap it by adding an exception listener
to the connection.
Regards,
Adrian -
4. Re: Cannot subscribe to this destination: Broken pipe
delboypass Jun 26, 2003 5:24 AM (in response to delboypass)Cheers adrian, ill try that.
I put an onExceptionListener is yesterday anyway because it was probably needing one so hopefully that will start to catch it but hasnt had the same problems yet.