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

Hung Thread issue in PRPC deployed in WebSphere App server



Hung Thread Issue in Websphere Application Server. Sometimes user used to receive Hung Threads issue in any of the JVMs, this could lead to outage in the application if it is not checked and timely actions are performed.

Error Messages

[10/16/15 3:30:31:321 MST] 00000004 ThreadMonitor W   CWWSR0605W: Thread "SoapConnectorThreadPool : 6" (000002e5) has been active for 753764 milliseconds and may be hung.  There is/are 25 thread(s) in total in the server that may be hung.
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(
    at java.lang.reflect.Method.invoke(
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invoke_privact(
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(
    at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.invokeEngine(
    at sun.reflect.GeneratedMethodAccessor127.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(
    at java.lang.reflect.Method.invoke(
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(

Steps to Reproduce


Root Cause

Configuration issue in the application server environment causing too many SoapConnectorThreadPool threads are hung in WebSphere Appliation Server. The SoapConnectorThreadPool is used for administrative messages.


Following settings in WebSphere Application server controls max number of threads and can decide whether threads are growable or not after reaching the max number, by default it is true.
Using this constant, you can set the max number of threads in the server, default value is 5.

Using this property you can decide whether threads are growable or not after reaching the max number, by default it is true. Due to this threads are growing in the server, which we need to set false.

Published January 31, 2016 - 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