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 threads due to hashmap in IcFlowScopeUtils



Hung Thread due to hashmap in IcFlowScopeUtils error.

Error Messages

WSVR0605W: Thread "WebContainer : 2" (00000c71) has been active for 628955 milliseconds and may be hung.  There is/are 1 thread(s) in total in the server that may be hung.
    at java.util.HashMap.put(
    at com.chordiant.web.faces.IcFlowScopeUtils.putObjectInFlowScope(
    at com.chordiant.web.faces.ic.IcFacesDispatcher.start(
    at com.chordiant.web.faces.ic.IcFacesDispatcher.start(
    at com.chordiant.web.faces.ic.CommonBackingBeanImpl.start(
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(

Steps to Reproduce

Run concurrent threads in load environment to access any specific workflow.

Root Cause

Usage of HashMap in multi-threaded environment could cause Hung Thread.


Changed the implementation to use ConcurrentHashMap instead of HashMap.

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