Agent Builder "Test Connection" for JMX RMI connection to WebSphere fails with "java.lang.NoClassDefFoundError" .
The following WebSphere Server connection error may be seen as a result of improper configuration setup:
- during connection using Agent Builder "Test Connection" or
- during Agent Builder agent runtime.
The error message can be found in the KQZ_JMX_trace.log. If you get connection problems during Agent Builder JMX agent runtime, the log file is saved in the ITMHOME/logs directory. If you are encountering connectivity issues while working with Agent Builder, the log file is saved in the Agent Builder /workspace directory):
Caused by: java.lang.NoClassDefFoundError: javax.activation.DataSource
at java.lang.J9VMInternals.verifyImpl(Native Method)
at java.lang.Class.forNameImpl(Native Method)
Agent Builder environment or Agent Builder Runtime parameters are not set correctly. Files are missing.
Resolving the problem
Using SOAP or RMI connection should work fine as long you have all required jars/libs in your WAS base path and WAS class path available. It should be fine for local WAS connection and remote connection as well. You will find the required files in your WebSphere installation:
[root@tivdemo logs]# ls -l /opt/IBM/WebSphere/AppServer/
drwxr-xr-x 5 root root 4096 May 22 2009 lib
-rw-r--r-- 1 root root 12697600 Feb 14 07:48 lib.tar
drwxr-xr-x 5 root root 4096 Dec 16 2008 logs
drwxr-xr-x 5 root root 4096 Dec 15 2008 optionalLibraries
drwxr-xr-x 6 root root 4096 Jun 8 2009 plugins
drwxr-xr-x 5 root root 4096 May 21 2009 profiles
drwxr-xr-x 6 root root 4096 Dec 15 2008 profileTemplates
drwxr-xr-x 7 root root 4096 May 21 2009 properties
drwxr-xr-x 2 root root 4096 Dec 16 2008 runtimes
Normally lib, runtimes and plugins directories are used and needed for Agent Builder and WAS Server communications. If you work remotely, copy the content of these directories to your local box where Agent Builder is running and set both "WAS base path" and “WAS class path” accordingly.
Reconfigure the Agent Builder Agent using "itmcmd config -A <pc>".
Where "<pc>" is the agent product code.
You will be prompted for the base and class path.
Set the paths to the location of the Websphere lib, runtime and plugins directories.