3 Replies Latest reply on Oct 15, 2004 6:54 AM by adrian.brock

Spurious exception with 4.0.0

pilhuhn Oct 14, 2004 6:38 AM

While my (simple) app is able to send and receive and also to trigger a MDB, the server shows the following exception:

2004-10-14 12:36:20,035 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin ReadTas
k.run
2004-10-14 12:36:20,035 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin WriteTa
sk.run
2004-10-14 12:36:20,035 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created Objec
tOutputStream
2004-10-14 12:36:20,105 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created Objec
tInputStream
2004-10-14 12:36:20,135 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler]
Setting up the UILClientIL Connection
2004-10-14 12:36:20,135 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler]
The UILClientIL Connection is set up
2004-10-14 12:36:20,556 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler]
Exiting on IOE
java.net.SocketException: Connection reset
 at java.net.SocketInputStream.read(SocketInputStream.java:168)
 at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
 at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
 at org.jboss.util.stream.NotifyingBufferedInputStream.read(NotifyingBuff
eredInputStream.java:67)
 at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java
:2133)
 at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(Object
InputStream.java:2313)
 at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStre
am.java:2380)
 at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream
.java:2452)
 at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputSt
ream.java:2601)
 at java.io.ObjectInputStream.readByte(ObjectInputStream.java:845)
 at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:27
9)
 at java.lang.Thread.run(Thread.java:534)
2004-10-14 12:36:20,556 DEBUG [org.jboss.mq.il.uil2.SocketManager] End ReadTask.
run
2004-10-14 12:36:20,566 DEBUG [org.jboss.mq.il.uil2.SocketManager] End WriteTask
.run

This is with a stock 4.0.0 server, default server config and the queue/testQueue.

1. Re: Spurious exception with 4.0.0

genman Oct 14, 2004 7:27 PM (in response to pilhuhn)

Turn off DEBUG to hide the "spurious" exceptions.
Actions
2. Re: Spurious exception with 4.0.0

pilhuhn Oct 15, 2004 2:06 AM (in response to pilhuhn)

Yeah, thath hides them. But Exceptions are .. well Exceptions - Condidtions that are not normal.
Actions
3. Re: Spurious exception with 4.0.0

adrian.brock Oct 15, 2004 6:54 AM (in response to pilhuhn)

This is perfectly normal. Exceptions happen all the time when dealing with
distributed frameworks. In this case it is just the close processing:

1) Client side tells the server it is closing
2) Server cleans up client state
3) Client closes the socket connection
4) Server catches socket closed error (connection reset),
server logs at DEBUG and redoes (2) just in case it is not
a clean shutdown by the client - the client might miss step (1)
and we don't trust it.
5) Server ends the communication threads.
Actions

Go to original post