Question
Ncs
SG
Last activity: 24 Sep 2019 13:55 EDT
java.io.IOException: UT000128: Remote peer closed connection before all data could be read
Hi All,
We are consistently getting the following error in our logs, though we havent seen any adverse effect besides compounding log file size. Anybody else encountered error below or have any solution to fine tune env?
Hi All,
We are consistently getting the following error in our logs, though we havent seen any adverse effect besides compounding log file size. Anybody else encountered error below or have any solution to fine tune env?
13:08:18,614 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) java.io.IOException: UT000128: Remote peer closed connection before all data could be read
13:08:18,991 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) at io.undertow.conduits.FixedLengthStreamSourceConduit.exitRead(FixedLengthStreamSourceConduit.java:338) ~[undertow-core-1.3.21.Final-redhat-1.jar!/:1.3.21.Final-redhat-1]
13:08:19,058 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) at io.undertow.conduits.FixedLengthStreamSourceConduit.read(FixedLengthStreamSourceConduit.java:255) ~[undertow-core-1.3.21.Final-redhat-1.jar!/:1.3.21.Final-redhat-1]
13:08:19,058 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) at org.xnio.conduits.ConduitStreamSourceChannel.read(ConduitStreamSourceChannel.java:127) ~[xnio-api-3.3.6.Final-redhat-1.jar!/:3.3.6.Final-redhat-1]
13:08:19,058 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) at io.undertow.channels.DetachableStreamSourceChannel.read(DetachableStreamSourceChannel.java:209) ~[undertow-core-1.3.21.Final-redhat-1.jar!/:1.3.21.Final-redhat-1]
13:08:19,058 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) at io.undertow.server.HttpServerExchange$ReadDispatchChannel.read(HttpServerExchange.java:2235) ~[undertow-core-1.3.21.Final-redhat-1.jar!/:1.3.21.Final-redhat-1]
13:08:19,058 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) at org.xnio.channels.Channels.readBlocking(Channels.java:294) ~[xnio-api-3.3.6.Final-redhat-1.jar!/:3.3.6.Final-redhat-1]
13:08:19,058 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) at io.undertow.servlet.spec.ServletInputStreamImpl.readIntoBuffer(ServletInputStreamImpl.java:170) ~[undertow-servlet-1.3.21.Final-redhat-1.jar!/:1.3.21.Final-redhat-1]
13:08:19,059 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) at io.undertow.servlet.spec.ServletInputStreamImpl.read(ServletInputStreamImpl.java:146) ~[undertow-servlet-1.3.21.Final-redhat-1.jar!/:1.3.21.Final-redhat-1]
13:08:19,060 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) at com.pega.pegarules.web.impl.HttpUtilities.getPostBytes(HttpUtilities.java:570) ~[prwebj2ee.jar:?]
We are using JBOSS 7.0, Pega7.3.1, SQL Server 2016 platform
***Edited by Moderator Marissa to update categories***
***Edited by Moderator: Pallavi to update SR Details***
Accepted Solution
Pegasystems Inc.
IN
Hello!
On reviewing the SR, we see that the issue was resolved by applying HFix-50285
Thank you,
Pegasystems Inc.
US
This error may occur when your server lost the socket connection with the client mainly due to a timeout or by forcefully closing the connection in either end. Can you also check the below link.
Ncs
SG
Hi,
Thanks but I have read this article before, I'm more interested on how this connection is used in PEGA. As we are just about to develop and don't have an application yet. It is then likely that its the PEGA Platform who is having this issue.
Is there a way to fine tune/configure JBOSS or PEGA to resolve this?
Regards
Pegasystems Inc.
IN
Hello,
Apologies for the delay in responding. On discussing this internally, it was determined that an SR might be the best route to take this further. Please create an SR and let us know the SR number back here for tracking.
Regards,
Pegasystems Inc.
IN
Hello @sudhaharr,
I was unable to determine if an SR was created for the above issue. Suggest you to create a new post.
Regards,
Accepted Solution
Pegasystems Inc.
IN
Hello!
On reviewing the SR, we see that the issue was resolved by applying HFix-50285
Thank you,
Pegasystems Inc.
IN
Hi,
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write Post button here. Once created, please reply back here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.