Cannot Write Response Message

Posted by James Palmer on 19-Jun-2015 11:12

Getting a few of these in the broker log of our AppServer:

[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB ----------- Cannot write response message. (8420)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB ----------- java.net.SocketException: Connection reset by peer: socket write error
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB ----------- 	at java.net.SocketOutputStream.socketWrite0(Native Method)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB ----------- 	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB ----------- 	at java.net.SocketOutputStream.write(SocketOutputStream.java:159)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB ----------- 	at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB ----------- 	at java.io.BufferedOutputStream.write(BufferedOutputStream.java:121)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB ----------- 	at com.progress.ubroker.util.MsgOutputStream.writeMsgbuf(MsgOutputStream.java:223)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB ----------- 	at com.progress.ubroker.util.MsgOutputStream.writeMsg(MsgOutputStream.java:115)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB ----------- 	at com.progress.ubroker.broker.ubClientThread.sendClientRsp(ubClientThread.java:2218)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB ----------- 	at com.progress.ubroker.broker.ubASclientThread.processDequeueLast(ubASclientThread.java:530)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB ----------- 	at com.progress.ubroker.broker.ubClientThread.processEvent(ubClientThread.java:1215)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB ----------- 	at com.progress.ubroker.broker.ubClientThread.mainline(ubClientThread.java:438)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB ----------- 	at com.progress.ubroker.broker.ubClientThread.run(ubClientThread.java:359)


Any thoughts what it could be? 

Progress 11.5 on Win 2012 R2. It's a stateless AppServer. I can't see anything else in other log files that stick out as obviously being related. We had something similar on our old 11.2 box, but that also came with Java heapspace issues which we don't seem to be getting. Heapspace is set to -Xmx256m anyway. 

OpenEdge RDBMS - Forum

All Replies

Posted by Libor Laubacher on 19-Jun-2015 11:20

The client using/being connected to the appserver has gone.
There were some data from the appserver to be sent back to it.
Since the client was gone, it could not have been sent, hence cannot write response message and the rest.
 
Check server.log as well, but my guess would be that the client using appserver crashed or X’d his/her session
 
[collapse]
From: James Palmer [mailto:bounce-jdpjamesp@community.progress.com]
Sent: Friday, June 19, 2015 6:13 PM
To: TU.OE.RDBMS@community.progress.com
Subject: [Technical Users - OE RDBMS] Cannot Write Response Message
 
Thread created by James Palmer

Getting a few of these in the broker log of our AppServer:

[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB ----------- Cannot write response message. (8420)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB ----------- java.net.SocketException: Connection reset by peer: socket write error
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB -----------      at java.net.SocketOutputStream.socketWrite0(Native Method)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB -----------      at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB -----------      at java.net.SocketOutputStream.write(SocketOutputStream.java:159)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB -----------      at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB -----------      at java.io.BufferedOutputStream.write(BufferedOutputStream.java:121)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB -----------      at com.progress.ubroker.util.MsgOutputStream.writeMsgbuf(MsgOutputStream.java:223)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB -----------      at com.progress.ubroker.util.MsgOutputStream.writeMsg(MsgOutputStream.java:115)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB -----------      at com.progress.ubroker.broker.ubClientThread.sendClientRsp(ubClientThread.java:2218)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB -----------      at com.progress.ubroker.broker.ubASclientThread.processDequeueLast(ubASclientThread.java:530)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB -----------      at com.progress.ubroker.broker.ubClientThread.processEvent(ubClientThread.java:1215)
[15/06/19@17:08:19.813+0100] P-015908 T-C-0010 1 UB -----------      at com.progress.ubroker.broker.ubClientThread.mainline(ubClientThread.java:438)
[/collapse]

Posted by TheMadDBA on 19-Jun-2015 11:21

A few things that come to mind...

Do you have a firewall in place?

Other network issues?

Can you find any related protrace files?

Posted by James Palmer on 22-Jun-2015 02:50

[mention:44a028c96ca44788b729e5185220e84a:e9ed411860ed4f2ba0265705b8793d05] that makes sense.

[mention:bd94ed2843f848d2a02b5599fd55d498:e9ed411860ed4f2ba0265705b8793d05] No protrace files. No firewall that I know if.

Posted by TheMadDBA on 22-Jun-2015 11:34

Any protrace files would be on the client side (if any).

Libor made a good suggestion... especially since I seem to remember you run async appserver requests from the client side.

Posted by James Palmer on 22-Jun-2015 16:12

Thanks - yeah Libor's suggestion makes a lot of sense.

This thread is closed