Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Server log shows frequent Read



Originally submitted as Event Strategy Manager on Pega 7.2.1

When sending JSON requests through Java API, exceptions appear.


Error Messages

- Exception Could not write response entitiy to output stream
Caused by: Read timed out

[] (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 java.lang.NoClassDefFoundError: Could not initialize class
  at com.pega.dsm.dnode.impl.server.BasicAuthenticationHandler.sendHttpResponse( [dnode-7.2.1.jar:]
  at com.pega.dsm.dnode.impl.server.BasicAuthenticationHandler.exceptionCaught( [dnode-7.2.1.jar:]
  at [netty-3.9.3.Final.jar:]
  at [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.


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':
Suggest Edit

Published December 17, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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

Pega Community 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
Contact us