Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Rajasekhar U (RajasekharU0829) CGI
CGI
IN
RajasekharU0829 Member since 2013 102 posts
CGI
Posted: Feb 26, 2018
Last activity: Mar 26, 2019
Posted: 26 Feb 2018 3:20 EST
Last activity: 26 Mar 2019 14:51 EDT
Closed

ClientAbortException: java.io.IOException: JBWEB002011: Socket read failed

Pega 7.2.2

We are getting below error in Production logs. Please help in resolving ASAP.

2018-02-22 07:59:40,178 [.25.130.134:8109-505] [ ] [ ] [ ] ( web.impl.WebStandardImpl) ERROR - XX.XX.XX.XX: Problem retrieving input data:

ClientAbortException: java.io.IOException: JBWEB002011: Socket read failed

at org.apache.catalina.connector.InputBuffer.realReadBytes(InputBuffer.java:371)

at org.apache.tomcat.util.buf.ByteChunk.substract(ByteChunk.java:422)

at org.apache.catalina.connector.InputBuffer.read(InputBuffer.java:393)

at org.apache.catalina.connector.CoyoteInputStream.read(CoyoteInputStream.java:193)

at com.pega.pegarules.web.impl.HttpUtilities.getPostBytes(HttpUtilities.java:558)

at com.pega.pegarules.web.impl.HttpUtilities.extractRequest(HttpUtilities.java:268)

at com.pega.pegarules.web.impl.WebStandardImpl.makeEtierRequest(WebStandardImpl.java:528)

at com.pega.pegarules.web.impl.WebStandardImpl.doPost(WebStandardImpl.java:378)

at sun.reflect.GeneratedMethodAccessor75.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:370)

at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:411)

Show More

Pega 7.2.2

We are getting below error in Production logs. Please help in resolving ASAP.

2018-02-22 07:59:40,178 [.25.130.134:8109-505] [ ] [ ] [ ] ( web.impl.WebStandardImpl) ERROR - XX.XX.XX.XX: Problem retrieving input data:

ClientAbortException: java.io.IOException: JBWEB002011: Socket read failed

at org.apache.catalina.connector.InputBuffer.realReadBytes(InputBuffer.java:371)

at org.apache.tomcat.util.buf.ByteChunk.substract(ByteChunk.java:422)

at org.apache.catalina.connector.InputBuffer.read(InputBuffer.java:393)

at org.apache.catalina.connector.CoyoteInputStream.read(CoyoteInputStream.java:193)

at com.pega.pegarules.web.impl.HttpUtilities.getPostBytes(HttpUtilities.java:558)

at com.pega.pegarules.web.impl.HttpUtilities.extractRequest(HttpUtilities.java:268)

at com.pega.pegarules.web.impl.WebStandardImpl.makeEtierRequest(WebStandardImpl.java:528)

at com.pega.pegarules.web.impl.WebStandardImpl.doPost(WebStandardImpl.java:378)

at sun.reflect.GeneratedMethodAccessor75.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:370)

at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:411)

at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:224)

at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:273)

at com.pega.pegarules.internal.web.servlet.WebStandardBoot.doPost(WebStandardBoot.java:121)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149)

at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.event(JBossWebContext.java:91)

at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.invoke(JBossWebContext.java:72)

at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:420)

at org.jboss.as.web.session.ClusteredSessionValve.handleRequest(ClusteredSessionValve.java:134)

at org.jboss.as.web.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:99)

at org.jboss.as.web.session.JvmRouteValve.invoke(JvmRouteValve.java:92)

at org.jboss.as.web.session.LockingValve.invoke(LockingValve.java:64)

at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:150)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344)

at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:490)

at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:420)

at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926)

at java.lang.Thread.run(Thread.java:748)

Caused by: java.io.IOException: JBWEB002011: Socket read failed

at org.apache.coyote.ajp.AjpProcessor.read(AjpProcessor.java:1128)

at org.apache.coyote.ajp.AjpProcessor.readMessage(AjpProcessor.java:1206)

at org.apache.coyote.ajp.AjpProcessor.receive(AjpProcessor.java:1145)

at org.apache.coyote.ajp.AjpProcessor$SocketInputBuffer.doRead(AjpProcessor.java:1271)

at org.apache.coyote.Request.doRead(Request.java:438)

at org.apache.catalina.connector.InputBuffer.realReadBytes(InputBuffer.java:361)

... 37 more


Show Less
To see attachments, please log in.
System Administration

Posted: 6 years ago
Posted: 27 Feb 2018 4:22 EST
Sudhakar Reddy Yaparla (YSudhakarReddy) JPMorgan Chase & Company
JPMorgan Chase & Company
US

Hi,

I suspect there is some failure at the server that is causing this. Could you find anything relevant in the server logs?

And try to identify the in which scenario, you are getting this exception ?

To see attachments, please log in.
Posted: 6 years ago
Posted: 28 Feb 2018 11:34 EST
Bhushan Patil (BHUSHANPATIL) AIG Bhushan Patil
AIG
US

reverted following chnages to fix ajax issue in JBOSS 6.3; however don't know root cause and how to reconfigure? do we have solution 

 

Change the protocol to NIO:
<connector name="http"
protocol="org.apache.coyote.http11.Http11NioProtocol"
scheme="http" socket-binding="http"/>


Enter the following line in the <jboss-web> section:
<enable-websockets>true</enable-websockets>

To see attachments, please log in.
Posted: 6 years ago
Posted: 8 Jun 2018 9:35 EDT
Rajasekhar U (RajasekharU0829) CGI
CGI
IN

Requested JBOSS team to review and make following changes in JBOSS

Change the protocol to NIO:
<connector name="http"
protocol="org.apache.coyote.http11.Http11NioProtocol"
scheme="http" socket-binding="http"/>

Enter the following line in the <jboss-web> section:
<enable-websockets>true</enable-websockets>

Waiting for response.......

To see attachments, please log in.
Posted: 5 years ago
Posted: 14 Nov 2018 18:58 EST
Allie Park (parkj4) PEGA Senior Software Engineer, Services Engineering
Pegasystems Inc.
US

Hi Rajesh, has this change solved the issue?

We are seeing similar exceptions in a 7.4 environment and the stack traces exactly match. (Referencing SR-C73695)

To see attachments, please log in.
Posted: 5 years ago
Posted: 22 Mar 2019 16:19 EDT
Abikash Kumar Sharma (AbikashSharma) Capgemini Abikash Kumar Sharma
Capgemini
SE
Hi Parkj - Which application server you are using? I'm also facing the same issue when I updated the protocol to nio . Strangely its happening for Https only not for http. I'm using jboss eap6.4.10. I found a post from Red Hat which provides a solution. https://access.redhat.com/solutions/2982131 The solution is available from Jboss eap 6.4.14
To see attachments, please log in.
Posted: 5 years ago
Posted: 26 Mar 2019 14:51 EDT
Abikash Kumar Sharma (AbikashSharma) Capgemini Abikash Kumar Sharma
Capgemini
SE
Today I updated jboss to 6.4.20. Now, the file uploading with https nio connector works perfectly. No client abort exception while uploading file with https.
To see attachments, please log in.

Related content:

Question Solved

Filesystem serialization failed for requestor java.io.IOException: No space left on device

Question Solved

java.io.IOException Stream closed

Question

java.io.IOException: No space left on device - notification

Question

java.io.IOException: No space left on device

Question

java.io.IOException: Separation boundary was not specified error

Question

java.util.concurrent.ExecutionException: java.io.IOException: The specified network name is no longer available.

Question Solved

java.io.IOException: UT000128: Remote peer closed connection before all data could be read

Discussion

"Problem accessing key store java.io.IOException: Invalid keystore format

Question Solved

java.io.IOException: Async IO operation failed (3), reason: RC: 107 Transport endpoint is not connected

Question

Getting java.io.IOException:Async IO operation failed(3),reason: RC:76 A socket must be already connected. in Logs

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice