WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

wsadmin problems in WebSphere Application Server - Ear deployment issues

By Adeoye Omoboya posted Mon April 04, 2022 09:14 AM

  
Follow the steps below to collect data for wsadmin scripting problems that involves deploying an ear file.

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=enabled:com.ibm.ws.scripting.AbstractShell.*=all=enabled:com.ibm.ws.management.*=all=enabled:com.ibm.websphere.management.*=all=enabled:com.ibm.config.eclipse.wtp=fine=enabled:com.ibm.ws.metadata.annotations.*=all=enabled:com.ibm.ws.websvcs.annotations.*=all=enabled


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

Note: If you are executing wsadmin script using "-conntype=none" option, do not perform step 2.

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.config.eclipse.wtp=fine:com.ibm.ws.management.*=all:com.ibm.websphere.management.*=all:com.ibm.ws.metadata.annotations.*=all:com.ibm.ws.websvcs.annotations.*=all:com.ibm.ws.websvcs.*=all:com.ibm.ws.metadata.annotations.*=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. Capture & Analyse 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

You can also share the output with IBM Support Team,if needed to help analyze and trouble-shoot the issue

Thanks


#2019YearinReview
#Liberty
#WebSphere
#WebSphereLiberty
0 comments
5 views

Permalink

https://community.ibm.com/community/user/blogs/adeoye-omoboya/2022/04/04/wsadmin-problems-in-websphere-application-server-e