Community
Participate
Working Groups
Build Identifier: Under WebSphere I get permanently the following message in the log file. That messages give the impression that something is wrong. What ist please the exact explanation ? How can I supress it ? 00000048 SystemOut O -649221393 00000019 ThreadMonitor W WSVR0605W: Thread "WebContainer : 1" (00000046) has been active for 754369 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung. 00000046 ThreadMonitor W WSVR0606W: Thread "WebContainer : 1" (00000046) was previously reported to be hung but has completed. It was active for approximately 2551808 milliseconds. There is/are 0 thread(s) in total in the server that still may be hung. 00000019 ThreadMonitor W WSVR0605W: Thread "WebContainer : 1" (00000046) has been active for 679827 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung. 00000019 ThreadMonitor W WSVR0605W: Thread "WebContainer : 0" (00000045) has been active for 676748 milliseconds and may be hung. There is/are 2 thread(s) in total in the server that may be hung. Reproducible: Always Steps to Reproduce: 1. Deploying a RAP Application with a war under WebSphere (including the ServletBrigde) 2. Look into the SystemOut.log logfile
RAP has threads running for a long time in the background. WebSphere detects such threads and marks them to be hung. This can be ignored. But to ensure that this is not another problem, I need some more information. - Which version of WebSphere (Application Server?) do you use? - Could you please attach a thread dump after such log message occured? How to create a thread dump: ============================ 1. Navigate to cd <WAS_ROOT>/profiles/<PROFILE_NAME>/bin/ 2. Connect to deployment manager using wsadmin script wsadmin <DMGR_HOST> <PORT> -conntype SOAP -username <USERNAME> -password <PASSWORD> 3. Set object variable wsadmin> jvm = AdminControl.completeObjectName('type=JVM,process=server1,node=<NODE>*') 4. Create ThreadDump: wsadmin>$AdminControl invoke $jvm dumpThreads 5. Heap or thread dump will be saved to <WAS_ROOT>/profiles/<PROFILE_NAME>/ directory with with respective naming convention
Since there has been no feedback for more than three months, I'm going to close this bug now. Serge, you're welcome to reopen this bug when you can provide more information. Alternatively, you may also try out the new JEE compatibility mode (see ApplicationConfiguration#setOperationMode()), but this does not work for workbench applications.
