| Description | "There are times in our production environment where the push job stops in the middle of a socket connection and the timeouts that are setup on the HttpUrlConnection don't seem to kick in. It always seems to be on the push job and on the retrieval of the ack after a push has completed. The following is a thread dump from a register. ""pushjob"" (TID:0x0A34AD00, sys_thread_t:0x0AC816A8, state:R, native ID:0x00004954) prio=5 at java/net/SocketInputStream.socketRead0(Native Method) at java/net/SocketInputStream.read(SocketInputStream.java:155) at java/io/BufferedInputStream.fill(BufferedInputStream.java:229) at java/io/BufferedInputStream.read1(BufferedInputStream.java:267(Compiled Code)) at java/io/BufferedInputStream.read(BufferedInputStream.java:324(Compiled Code)) at sun/net/www/http/HttpClient.parseHTTPHeader(HttpClient.java:658) at sun/net/www/http/HttpClient.parseHTTP(HttpClient.java:607) at sun/net/www/protocol/http/HttpURLConnection.getInputStream(HttpURLConnection.java:966) at java/net/HttpURLConnection.getResponseCode(HttpURLConnection.java:379) at org/jumpmind/symmetric/transport/http/HttpOutgoingTransport.readResponse(HttpOutgoingTransport.java:138) at org/jumpmind/symmetric/service/impl/PushService.pushToNode(PushService.java:114(Compiled Code))" |
|---|