IBM Support

MustGather: ws_ant problems on WebSphere Application Server

Troubleshooting


Problem

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

Resolving The Problem


ws_ant specific MustGather information
IBM supports the Application Server ant task commands from the com.ibm.websphere.ant.tasks package. For more detailed information about Ant issues, refer to the Apache organization Web site.

Simplify the ANT build script by creating a new build.xml with only the command that fails. Since most ANT scripts run wsadmin, you should enable wsadmin tracing as well. Also, server side tracing may be beneficial as well:

  1. If your wsadmin script (Java™ Command Language (JACL), JavaScript or Jython) fails to work:
    1. Determine the exact command that fails in your script and create a simple script example.

    2. Stop all servers and clear the entire log directory for each server. The log directory for each server can be found in the following location for each profile:

      profile_root/{profile_name}/logs/

    3. Enable tracing in wsadmin:
      1. Modify the wsadmin.properties file located in the following directory:

        install_root/profiles/profile_name/properties/

      2. Uncomment the following line by removing the "#":

        com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled

  2. If wsadmin connects to a server process, enable tracing on that server.
    1. Set trace string on the deployment manager in network deployment environment or on server1 in a base/express environment. If the trace is set in the configuration tab as a startup trace, a restart will be required, if the trace string is set in the runtime tab, there will be no need for a restart of the server. Trace string should include the following:

      'Admin=all'

    2. Make sure the trace output Maximum File Size limit is large (20 MB recommended) and the Maximum Number of Historical Files is greater than 5.

      For additional information on enabling tracing, see the following technote: Setting up a trace.

  3. Run your script with the "-debug" and "-logfile" options. The following is an example command:

    WAS_PROFILE/bin/ws_ant –f <build file> -version -diagnostics -verbose -debug -logfile <filename>

  4. Collect the following files to send to IBM support:
    • build.xml
    • Run the Collector Tool. See the appropriate Information Center for additional information on running the Collector Tool.

  5. Open a PMR with IBM by performing one of the following:
  6. Send the diagnostic information to IBM support, using the instructions in this technote: Exchanging information with IBM Technical Support for problem determination.

For a listing of all technotes, downloads, and educational materials specific to ws_ant, search the WebSphere Application Server support site.

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Administrative Scripting Tools (for example: wsadmin or ANT)","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.0;8.5.5;8.5;8.0;7.0;6.1;6.0","Edition":"Base;Express;Network Deployment","Line of Business":{"code":"LOB45","label":"Automation"}},{"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:
15 June 2018

UID

swg21196231

Page Feedback