Hello All,
We have a queue running in HornetQ 2.4.0 (embedded within Wildfly), with a
Proton-J 0.12.0 client periodically connecting to this queue.
If HornetQ stops or becomes unavailable when the Proton-J client is running,
the Proton-J client continually generates exceptions similar to that below
(very rapidly).
The issue is that the IOException generated exception is handled in
MessengerImpl's processActive() by generating an "Error processing connection"
message in the logs, rather
than recv() throwing an exception and hence the higher level program logic is
unable to react to the problem.
Is this a bug or am I missing something important?
Thank you,
Matthew
java.io.IOException: An existing connection was forcibly closed by the remote
host
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
at sun.nio.ch.IOUtil.read(IOUtil.java:197)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
at
org.apache.qpid.proton.driver.impl.ConnectorImpl.read(ConnectorImpl.java:129)
at
org.apache.qpid.proton.driver.impl.ConnectorImpl.process(ConnectorImpl.java:94)
at
org.apache.qpid.proton.messenger.impl.MessengerImpl.processActive(MessengerImpl.java:738)
at
org.apache.qpid.proton.messenger.impl.MessengerImpl.waitUntil(MessengerImpl.java:895)
at
org.apache.qpid.proton.messenger.impl.MessengerImpl.waitUntil(MessengerImpl.java:844)
at
org.apache.qpid.proton.messenger.impl.MessengerImpl.recv(MessengerImpl.java:446)
at
org.apache.qpid.proton.messenger.impl.MessengerImpl.recv(MessengerImpl.java:451)
...
at java.lang.Thread.run(Thread.java:745)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
