Java Probes on WebSphere

When adding a Java probe to a JVM startup command line of WebSphere, it is possible that there is a missing instrumentation in Diagnostics UI instrumentation charts. If there are problems during the launch of the probe’s process, it will not show active (green status) in the Health View menu from the probe. In case the probe service has started correctly locally and it appears in the Health View as active, it will be required to check the probe.log file located in the <probe_installation_folder>/log folder.

This guide show how to handle specific issues when instrumenting applications hosted in WebSphere.

Usually, when working with problematic Java probes and WebSphere the following error shows up:

java.lang.NoClassDefFoundError: javax/xml/ws/soap/SOAPBinding

The below steps are useful to fix these eventual instrumentation issues:

Check if the probe is working on top of the latest patches available.

Check if instrumentation defined in auto_detect.points can be viewed in the Diagnostics charts. If custom layers do not show:

Open server.err file from the log folder of the server for memory errors in the format:

log4j:ERROR Failed to flush writer, There is not enough space on the disk

If this is the case, instrumentation will have to be modified in order to consume less resources in disk.

Go to the "etc" folder on the Java probe, ie. <Diagnostics_Install_folder>\JavaAgent\DiagnosticsAgent\etc folder.

Open the file called "" and increase the value defined by class.methods.max.size

Change the properties below in the etc\

probe.pull.max.threads = 12




Search SEVERE error messages in the probe.log file, related to class or classes *.Bindings.*

This is related to access permissions to some private classes.

Edit etc/ file and search for line starting with the parameter and add the problematic classes.

Restart Application and Diagnostics Servers.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s