IBM Support

MustGather: wsadmin problems in WebSphere Application Server - Configuration modification 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.

Resolving The Problem

Tab navigation

Types of Issues:

Tab navigation

Follow the steps below to collect data for wsadmin scripting problems that involve configuration modifications only.
 

Note: If your wsadmin script does not work with MBeans, it is recommended to use "-conntype NONE" option which does not connect to the dmgr process.

 

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=enabled

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

2. 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
3. Run the collector tool against the profiles.

4. 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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"ARM Category":[],"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"},{"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Java SDK","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
29 February 2024

UID

swg21140940

Page Feedback