| Summary: | Under WebSphere I have warning message in the log file | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Serge Démoulin <serge_demoulin68> |
| Component: | Other | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | minor | ||
| Priority: | P3 | CC: | ralf.zahn |
| Version: | 1.3 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Serge Démoulin
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. |