Learning more about WebSphere Developer Tools Server Tools

Problem (Abstract)

Learning more about server tools is the first step in the troubleshooting process. This topic provides you with educational information that can help you learn more.

Resolving the problem

There are three options to resolving the problem:
  1. Learning more
  2. Troubleshooting
  3. Collecting data

Learning more

Learning more about server tools is the first step in the troubleshooting process. This topic provides you with educational information that can help you learn more.

Getting background information on WebSphere® Application Server

IBM® WebSphere Application Server provides a range of flexible and secure runtime for Java™ enterprise applications, lightweight web applications, and microservices.

An application server is a Java virtual machine (JVM) running user applications. Application servers use Java technology to extend web server capabilities to handle web application requests. An application server makes it possible for a server to generate a dynamic, customized response to a client request. The WebSphere Application Server full profile provides application servers.

WebSphere Developer Tools Server Tools

IBM WebSphere Application Server Developer Tools for Eclipse is a lightweight set of tools for developing, assembling, and deploying Java EE, and OSGi applications to WebSphere Application Server Liberty, and traditional. WebSphere Developer Tools Server Tools is for traditional WebSphere Application Server.

Note that since WebSphere Developer Tools 18.0.0.3, only WebSphere Application Server V8.5.5.x and V9 are supported. To use WebSphere Application Server V8.0 or V7.0, use an earlier version of WebSphere Application Server Developer Tools.

For more details, see:

Troubleshooting WebSphere Developer Tools Server Tools problems

Troubleshooting server tools problems in WebSphere Application Server Developer Tools. This section helps you resolve common issues with this component before calling IBM support.

Common Server Tools Issues and Their Solutions

The following is a list of common issues together with their corresponding solutions:
Table 1. Common issues, symptoms, and resolutions
Issue Symptom Resolution
javax.net.ssl.SSLHandshakeException during local non-loose republish, remote server start or publish

There are problems when attempts to update an non-loose application published from IBM WebSphere Developer Tools to IBM WebSphere Application Server with a secured profile results in the SSLHandshakeException error.

SSLHandshakeException error occurs when try to start a remote server, publish any application onto a started remote server, or a started remote server failed to be detected as started.

The issue has been partially resolved in WebSphere Developer Tools 18.0.0.1 or later. With 18.0.0.1, it is a known issue that a remote server with a SOAP connection type still does not work properly.

For more details, see: https://www.ibm.com/support/knowledgecenter/SSHR6W/com.ibm.websphere.wdt.doc/topics/rconremserv.html.

Follow these instructions to resolve the issue if you want to use SOAP connections for a remote server, or if you are running WebSphere Developer Tools with a non-IM JDK, or if you do not want to upgrade WebSphere Developer Tools to 18.0.0.1 or later: http://www-01.ibm.com/support/docview.wss?uid=swg21634467.
java.lang.NoClassDefFoundError: Could not initialize class com.ibm.ws.ffdc.FFDCFilter When running WebSphere Developer Tools with non-IBM JDK, the issuejava.lang.NoClassDefFoundError: Could not initialize class com.ibm.ws.ffdc.FFDCFilter error occurs during a server start, stop, or publishing process.
It is a known problem and is caused because the non-IBM JRE is missing certain classes. To work around this problem:
  1. Create a folder, and copy <WAS install>/runtimes/com.ibm.ws.orb_VERSION.jar into it.
  2. Add the following line in eclipse.ini: -Djava.endorsed.dirs=<the directory where com.ibm.ws.orb_VERSION.jar was copied to in step 1>
Unable to start a remote server on Windows machine Unable to start a remote server on Windows machine with error message: java.net.ConnectException: CTGRI0001E The application could not establish a connection to <HOSTNAME>.

For WebSphere Developer Tools 18.0.0.3 or earlier, it is a known issue that the remote start with authentication using credentials does not work properly. Alternatively, you can use SSH, for more details, see: https://www.ibm.com/support/knowledgecenter/en/SSHR6W/com.ibm.websphere.wdt.doc/topics/tremote_start.html

System setup for RXA: https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.installation.nd.doc/ae/cins_cim_rxa_requirements.html
Cannot find the specified class com.ibm.websphere.ssl.protocol.SSLSocketFactory
Here is a list of known tools where this SSLSocketFactory error message is displayed:
  • Web Services Wizard retrieving HTTPS WSDL.
  • Web Services Explorer running against a secured WebSphere Application Server.
  • Deploying web services to the Axis runtime environment.
  • Installing Rational®® Asset Manager with an SSL enabled WebSphere Application Server.
  1. Create a custom.java.security file with content: ssl.SocketFactory.provider=  ssl.ServerSocketFactory.provider=
  2. Specify the vm option in the eclipse.ini file: -Djava.security.properties=/path/to/custom.java.security

Alternatively, a solution is also available here: https://www.ibm.com/support/knowledgecenter/SSHR6W/com.ibm.websphere.wdt.doc/topics/rssl_isUseIBMSSLSocketFactory.htm?cp=SSHR6W_8.5.5

What to do next?

If the preceding troubleshooting steps do not solve your problem, see the following section Collecting data to continue investigating.

Collecting data

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

Collect Server Logs:

WebSphere Application Server logs are stored under <PROFILE_DIR>/logs/ffdc and <PROFILE_DIR>/logs/server1.

Collect Server Tool Specific Logs:

To trace the server tooling or server runtime plugins, create and edit the .options file under the Eclipse folder, and add the strings listed in the tables that follow. Note: the V85 is an example for using WebSphere Application Server V8.5.5.x. Change to use v80 for WebSphere Application Server V8.0.0.x or v9 if you are using WebSphere Application Server V9.

Table 2. Problems areas and trace strings to add to the .options file
Problem area to trace Trace strings to add to .options file
Server tools general and performance problems com.ibm.ws.ast.st.v85.core/debug=true com.ibm.ws.ast.st.v85.core/debug/error=true com.ibm.ws.ast.st.v85.core/debug/warning=true com.ibm.ws.ast.st.v85.core/debug/info=true com.ibm.ws.ast.st.v85.core/debug/details=false com.ibm.ws.ast.st.v85.core/debug/ssm=false com.ibm.ws.ast.st.v85.core/debug/launches=false com.ibm.ws.ast.st.common.core/debug=true com.ibm.ws.ast.st.common.core/debug/info=true com.ibm.ws.ast.st.core/debug=true com.ibm.ws.ast.st.core/debug/info=true org.eclipse.wst.server.core/debug=true org.eclipse.wst.server.core/info=true org.eclipse.wst.server.core/finest=true org.eclipse.wst.server.core/finer=true com.ibm.etools.wrd.websphere.core/debug=true com.ibm.etools.wrd.websphere.core/debug/error=true com.ibm.etools.wrd.websphere.core/debug/warning=true com.ibm.etools.wrd.websphere.core/debug/info=true com.ibm.etools.wrd.websphere.core/debug/details=true com.ibm.etools.wrd.websphere.core.util/debug=true com.ibm.etools.wrd.websphere.core.util/debug/error=true com.ibm.etools.wrd.websphere.core.util/debug/warning=true com.ibm.etools.wrd.websphere.core.util/debug/info=true com.ibm.etools.wrd.websphere.core.util/debug/details=false com.ibm.etools.wrd.websphere.v85/debug=true com.ibm.etools.wrd.websphere.v85/debug/error=true com.ibm.etools.wrd.websphere.v85/debug/warning=true com.ibm.etools.wrd.websphere.v85/debug/info=true org.eclipse.wst.server.core/performance=true org.eclipse.wst.server.core/publishing=true
Server tools user interface com.ibm.ws.ast.st.v85.ui/debug=true com.ibm.ws.ast.st.v85.ui/debug/error=true com.ibm.ws.ast.st.v85.ui/debug/warning=true com.ibm.ws.ast.st.v85.ui/debug/info=true com.ibm.ws.ast.st.v85.ui/debug/details=false com.ibm.ws.ast.st.common.ui/debug=true com.ibm.ws.ast.st.common.ui/debug/error=true com.ibm.ws.ast.st.common.ui/debug/warning=true com.ibm.ws.ast.st.common.ui/debug/info=true com.ibm.ws.ast.st.common.ui/debug/details=true com.ibm.ws.ast.st.ui/debug=true com.ibm.ws.ast.st.ui/debug/error=true com.ibm.ws.ast.st.ui/debug/warning=true com.ibm.ws.ast.st.ui/debug/info=true com.ibm.ws.ast.st.ui/debug/details=true org.eclipse.wst.server.ui/debug=true org.eclipse.wst.server.ui/info=true org.eclipse.wst.server.ui/finest=true org.eclipse.wst.server.ui/finer=true
Server connection com.ibm.ws.ast.st.jmx.core/debug=true com.ibm.ws.ast.st.jmx.core/debug/error=true com.ibm.ws.ast.st.jmx.core/debug/warning=true com.ibm.ws.ast.st.jmx.core/debug/info=true com.ibm.ws.ast.st.jmx.core/debug/details=false com.ibm.etools.wrd.websphere.core/debug=true com.ibm.etools.wrd.websphere.core/debug/error=true com.ibm.etools.wrd.websphere.core/debug/warning=true com.ibm.etools.wrd.websphere.core/debug/info=true com.ibm.etools.wrd.websphere.core/debug/details=true com.ibm.etools.wrd.websphere.core.util/debug=true com.ibm.etools.wrd.websphere.core.util/debug/error=true com.ibm.etools.wrd.websphere.core.util/debug/warning=true com.ibm.etools.wrd.websphere.core.util/debug/info=true com.ibm.etools.wrd.websphere.core.util/debug/details=false

Start WebSphere Developer Tools in debug mode to start tracing

Procedure

  1. Ensure that the product is stopped.
  2. Create a .options file containing the necessary plug-in tracing options as instructed in Collecting data. Save this file into the Eclipse installation directory.
  3. Start the product using the following command from the command-line in the product installation directory. For Linux®, use this command: ./eclipse -debug > trace.txt 2>&1. For Windows, use this command: eclipsec.exe -debug > trace.txt 2>&1.

    These commands start WebSphere Developer Tools and enable the problem to be reproduced. The plug-in tracing information is captured in the <install>/trace.txt file which can be provided to IBM support to further diagnose the problem.