1 Reply Latest reply on Aug 6, 2003 8:30 AM by Adrian Brock

    Communication problem

    levmt Newbie

      Hi all,
      Recently we started experiance various problem with our software on the server side. These problems usually create some sort of communication
      breakdown between server and client application. Some TCP connection is either reset or can not be establish accordingly to the server-side log.
      We have a very strong suspition that the problem is related to the JMS callback. We could partially reproduce the problem by not returning from
      onMessage function of MessageListener for significant amount of time and heavily utilizing CPU on the client side.
      2003-07-31 19:57:06,806 WARN [org.jboss.mq.il.oil.OILServerILService] Connection failure (1).
      java.net.SocketException: Connection reset by peer: Connection reset by peer
      at java.net.SocketInputStream.socketRead0(Native Method)
      at java.net.SocketInputStream.read(SocketInputStream.java:116)
      at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
      at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
      at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2118)
      at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2301)
      at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2368)
      at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2440)
      at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2589)
      at java.io.ObjectInputStream.readByte(ObjectInputStream.java:837)
      at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:190)
      at java.lang.Thread.run(Thread.java:536)

      Thank you
      Lev