Skip to main content

Versions earlier than Java 1.6

You can apply the WhaTap agent on the versions earlier than Java 1.6. However, some functions are limited.

Java 1.5​

Java 1.5 supports the -javaagent option. However, there are restrictions on information inquiry for external threads, so some functions are limited.

The following functions do not work.

  • Real-time trace on active transactions

  • Stack analysis (Top stack, Unique stack, Active stack)

  • Detailed stack of the thread list

Java 1.4​

Java 1.4 does not have the -javaagent option. Install the WhaTap agent differently. Of course, Java 1.4 must be used for the whatap.agent.jar file.

whatap.java14.tracer-X.Y.Z.jar

Creating boot.jar​

Create boot.jar by using the setup.sh file. If [JAVA_HOME] is not entered, it automatically recognizes the current path as the location of JDK.

$ setup.sh [JAVA_HOME]

setup.sh execution result: whatap.java14.boot-X.Y.Z.jar

Installing in bootclasspath​

Using the bootclasspath option, add the built jar and tracer jar as prepend.

-Xbootclasspath/p:${WHATAP_HOME}/whatap.java14.boot-1.0.2.jar:${WHATAP_HOME}/whatap.java14.tracer-1.0.2.jar

Constraints​

In JDK 1.4, the following functions do not work.

  • Real-time trace on active transactions

  • Stack analysis (Top stack, Unique stack, Active stack)

  • Component version

  • Thread list, heap history

  • Loaded class

  • Open socket

  • Agent dump

Next steps​

  • Open source tracing

    Depending on the framework or open source library used in applications, you may need to add agent options. For example, when using spring-boot-3.x, feign-client-11, or okhttp3-4.4 with a framework or open source, set the options as follows:

    whatap.conf
    weaving=spring-boot-3.0,feign-11,okhttp3-4.4

    For information on how to configure the framework or open source library that suits your application environment, see the following.

  • Checking the installation

    If you have created a project, installed an agent, and applied all JVM options, see the checklist in the following.

  • Installation troubleshooting

    It provides various problems that may occur when installing the agent and specific instructions for resolving them. It provides solutions against various situations, including firewall configuration, SpringBoot and Tomcat JMX configuration, and server configuration using the OSGI framework. For more information, see the following.

  • Agent setting

    It provides various features for monitoring by applying some options to the agent configuration file (whatap.conf). It includes basic configuration, configuration for server connection and data transfer, how to manage the configuration files for multiple application servers, and transaction tracing, and more. For more information, see the following.

  • Starting the monitoring

    After all settings are made, restart the application server. The agent starts collecting data. First, check whether the monitoring data has been collected in Application Dashboard. For more information about Application Dashboard, see the following.