I think this problem will go away if you use the latest 5.1 snapshot
- please let us know if this is not the case
On 8 Apr 2008, at 10:45, Hatta wrote:
Hi Dil,
Yes, I have received the same thing. I have browse thru all the
related
issue in AMQ 5.0.0 but non avail.
Appreciate a response from the team about this matter.
This log can be really disturbing when the solution goes to
production.
Regards
Hatta
Dil wrote:
Did somebody see this Warning exception while using active MQ 5 when
sending asynchronous messages?
this is exception i am getting on producer class after some time of
its
running.
the url for broker is :
tcp://localhost:61616?trace=true&wireFormat.maxInactivityDuration=-1
10:44:44,427 WARN ActiveMQConnection:1653 - Async exception with no
exception listener: java.net.SocketException: socket closed
java.net.SocketException: socket closed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at
org
.apache
.activemq
.transport
.tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:50)
at
org
.apache
.activemq
.transport
.tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:58)
at java.io.DataInputStream.readInt(Unknown Source)
at
org
.apache
.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
at
org
.apache
.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:
192)
at
org
.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:
184)
at
org
.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:
172)
at java.lang.Thread.run(Unknown Source)
--
View this message in context:
http://www.nabble.com/ActiveMQConnection%3A1653---Async-exception-with-no-exception-listener%3A-java.net.SocketException%3A-socket-closed-tp16323372s2354p16553555.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
