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

System becomes unresponsive

SA-32274

Summary



PRPC environment performance decays and intermittantly becomes unresponsive.

Error Messages



at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:112)
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream
(DefaultChannelPipeline.java:791)
at org.jboss.netty.handler.codec.frame.FrameDecoder.exceptionCaught(FrameDecoder.java:377)


Steps to Reproduce



Unknown

Root Cause



This is the Decision Strategy Manager DNODE performance problem.

Resolution



Perform the following local-change:
  1. Do not use Decision Strategy Manager to disable the functionality.
  2. Log in to a Process Commander NODE as [email protected].
  3. Select RECORDS / SYSADMIN / DYNAMIC SYSTEM SETTINGS in the widget area (left side of browser).
  4. Look for the existing key: PRCONFIG/INITSERVICES/DNODE/DEFAULT.
  5. Set this value to FALSE. This value is set to TRUE by default.
  6. Log out of Process Commander.
  7. Shutdown ALL Process Commander Nodes.
  8. Contact the Java Application Administrator. Delete the following file for each Process Commander Node: ${EXPLICIT TEMP DIRECTORY}/PegaRULES_Extract_Marker.txt
  9. Restart All Process Commander Nodes.

Published February 24, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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