Support Article

Server log shows frequent java.net.SocketTimeoutException: Read

SA-31301

Summary



Originally submitted as Event Strategy Manager on Pega 7.2.1

When sending JSON requests through Java API, exceptions appear.

 


Error Messages



- Exception
com.pega.pegarules.pub.services.InboundMappingException: Could not write response entitiy to output stream
.....................................
Caused by: java.net.SocketTimeoutException: Read timed out


[org.jboss.netty.channel.DefaultChannelPipeline] (New I/O worker #4) An exception was thrown by a user handler while handling an exception event ([id: 0x1bbc590f, /<IP_address>:<port> => /<IP_address>:7003] EXCEPTION: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.netty.channel.ChannelFutureListener): java.lang.NoClassDefFoundError: Could not initialize class org.jboss.netty.channel.ChannelFutureListener
  at com.pega.dsm.dnode.impl.server.BasicAuthenticationHandler.sendHttpResponse(BasicAuthenticationHandler.java:135) [dnode-7.2.1.jar:]
  at com.pega.dsm.dnode.impl.server.BasicAuthenticationHandler.exceptionCaught(BasicAuthenticationHandler.java:62) [dnode-7.2.1.jar:]
  at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:112) [netty-3.9.3.Final.jar:]
  at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.9.3.Final.jar:].............

Steps to Reproduce



a) Start sending json request to stream data flow through java API.
b) Check the Data flow after sending 25,000 records.


Root Cause



This is likely to be caused by a conflict between the jars shipped within JBoss and the ones provided by PRPC.

Resolution



In order to avoid the loading of the JBoss version of the jar, follow the guidelines in the below link to modify the jboss-deployment-structure.xml to exclude the Netty module from JBoss. The module is 'org.jboss.netty':

https://developer.jboss.org/message/637818#637818
 

Published December 12, 2016 - Updated December 16, 2016

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.