IBM Support

MustGather: wsadmin problems in WebSphere Application Server - MBean operation issues

Troubleshooting


Problem

Collecting data for problems with the IBM WebSphere Application Server wsadmin component. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.

Symptom

Tab navigation

Types of Issues:

Tab navigation

Follow the steps below to collect data for wsadmin scripting problems that involve MBean operations.
 

Note: The [install_root] below represents the install location of WebSphere Application Server.

1. Enable tracing in wsadmin:


Modify the wsadmin.properties file located in the following directory:

install_root/profiles/profile_name/properties/

Replace following line:
  • #com.ibm.ws.scripting.traceString=com.ibm.*=all

With this line:
  • com.ibm.ws.scripting.traceString=com.ibm.ws.scripting.*=all:com.ibm.ws.management.*=all:com.ibm.websphere.management.*=all


2. Enable tracing for the server process that wsadmin connects to.

If you are unfamiliar with how to enable server side tracing, see the instructions How to setup a Trace

Configure the following trace string for both dmgr and nodeagent processes:
  • *=info:com.ibm.ws.management.*=all:com.ibm.websphere.management.*=all


3. Recreate the problem.

Note: If wsadmin process hangs on UNIX platforms, when wsadmin hangs, execute three kill -3 pid commands, two minutes apart, on the wsadmin Process ID (PID).

If you need help on how to collect javacores, please see the following article:
IBM Problem determination for javacore files from WebSphere Application Server
http://www-01.ibm.com/support/docview.wss?uid=swg21181068


4. Run the collector tool against the profiles.

5. Send the following:
  • Any javacore files created for AIX, Linux and Windows. Note any issues on the machine and network during the hang.
  • Collector output jars
  • The script file that you executed
  • The command that you used to invoke the script

What to do next:

Once you have collected the preceding information, you can open a PMR with IBM by calling 1-800-IBM-SERV, or by submitting electronically. If you already have a PMR for this issue, you can submit the diagnostic information to IBM support.



 

[{"Type":"MASTER","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"ARM Category":[{"code":"a8m50000000Cd5LAAS","label":"WebSphere Application Server traditional-All Platforms-\u003ESystem Management-\u003ETraditional WAS-\u003EAdmin Scripting Tools"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5.5;9.0.0;9.0.5"}]

Document Information

Modified date:
20 May 2024

UID

swg21992782

Page Feedback