Java error in Broker log. Can Anyone help?

Beeb

Member
Dear All,

From time to time we have this error in the broker log:

[08/09/09@09:19:29.817+0200] P-005016 T-C-0109 1 UB ---------- Cannot write response message. (8420)
[08/09/09@09:19:29.817+0200] P-005016 T-C-0109 1 UB ---------- java.net.SocketException: Connection reset by peer: socket write error
[08/09/09@09:19:29.817+0200] P-005016 T-C-0109 1 UB ---------- at java.net.SocketOutputStream.socketWrite0(Native Method)
[08/09/09@09:19:29.817+0200] P-005016 T-C-0109 1 UB ---------- at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
[08/09/09@09:19:29.817+0200] P-005016 T-C-0109 1 UB ---------- at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
[08/09/09@09:19:29.817+0200] P-005016 T-C-0109 1 UB ---------- at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
[08/09/09@09:19:29.817+0200] P-005016 T-C-0109 1 UB ---------- at java.io.BufferedOutputStream.write(BufferedOutputStream.java:104)
[08/09/09@09:19:29.817+0200] P-005016 T-C-0109 1 UB ---------- at com.progress.ubroker.util.MsgOutputStream.writeMsgbuf(MsgOutputStream.java:223)
[08/09/09@09:19:29.817+0200] P-005016 T-C-0109 1 UB ---------- at com.progress.ubroker.util.MsgOutputStream.writeMsg(MsgOutputStream.java:115)
[08/09/09@09:19:29.817+0200] P-005016 T-C-0109 1 UB ---------- at com.progress.ubroker.broker.ubClientThread.sendClientRsp(ubClientThread.java:1921)
[08/09/09@09:19:29.817+0200] P-005016 T-C-0109 1 UB ---------- at com.progress.ubroker.broker.ubASclientThread.processDequeueLast(ubASclientThread.java:271)
[08/09/09@09:19:29.817+0200] P-005016 T-C-0109 1 UB ---------- at com.progress.ubroker.broker.ubClientThread.processEvent(ubClientThread.java:1038)
[08/09/09@09:19:29.817+0200] P-005016 T-C-0109 1 UB ---------- at com.progress.ubroker.broker.ubClientThread.mainline(ubClientThread.java:305)
[08/09/09@09:19:29.817+0200] P-005016 T-C-0109 1 UB ---------- at com.progress.ubroker.broker.ubClientThread.run(ubClientThread.java:231)

The most logical answer would be: you have network trouble. But we can be quite sure that isn't the case.
Our appserver was running on 10.1.B but we migrated recently to 10.1.C. (Database is still running on 10.1.B)

Can Anybody help?

Thanks a lot for your suggestion

Elise Daans
 
Back
Top