Support Article
Hung threads due to hashmap in IcFlowScopeUtils
SA-16080
Summary
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(HashMap.java:506)
at com.chordiant.web.faces.IcFlowScopeUtils.putObjectInFlowScope(IcFlowScopeUtils.java:146)
at com.chordiant.web.faces.ic.IcFacesDispatcher.start(IcFacesDispatcher.java:172)
at com.chordiant.web.faces.ic.IcFacesDispatcher.start(IcFacesDispatcher.java:147)
at com.chordiant.web.faces.ic.CommonBackingBeanImpl.start(CommonBackingBeanImpl.java:579)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
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.
Resolution
Changed the implementation to use ConcurrentHashMap instead of HashMap.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.