Skip to main content


Firewall configuration checking

If the TCP outbound policy for the WhaTap data collection server has not been set, monitoring data cannot be transferred. Deselect the firewall blocking.

Use the telnet command to check "Connected to IP."

$ telnet 6600
Connected to
Escape character is '^]'.

For the connection server details, select a desired project in WhaTap Monitoring Service, and then check in Management > Agent Installation.

SpringBoot 2.2 or later, Tomcat JMX off

If the embedded Tomcat is used in SpringBoot 2.2 or later, the JMX functions do not work with the default settings. In this case, activate the JMX functions. Related link
server.tomcat.mbeanregistry.enabled=true # tomcat embedded인 경우 #
enabled: true
enabled: true #tomcat embedded

In case of the application server using the OSGI framework

Register any agent package prefix (whatap) in the JVM options for an OSGI framework-based application server.

The application server is available in Jboss EAP 6.0 or later, Jboss AS 7.0 or later, Wildfly 8.0 or later, IBM WebSphere AS 7.0 or later, and such.

JBoss AS, Wildfly, JBoss EAP 6.0 or later

Register a prefix in the following file:




As an JVM option, add the following.
  • If "*" is specified as the default value, no additional setting is required.
  • For the setting location, see WebSphere.

Add the security.policy role as follows:

$WEBSPHERE_HOME/properties/server.policy || $WEBSPHERE_PROFILE_HOME/properties/server.policy
grant codeBase "file:$WHATAP_HOME/-"

Errors of Log Manager

If any Log Manager error occurs in JBoss AS 7.0 or later and JBoss EAP 6.0 or later, add the JVM options.

  • Set the package name of Log Manager in -Djava.util.logging.manager.
  • Set the JBoss Log Manager JAR file in -Xbootclassloader.
# Specify the exact Java VM executable to use.
if [ "x$JBOSS_MODULES_SYSTEM_PKGS" = "x" ]; then

# Specify options to pass to the Java VM.
if [ "x$JAVA_OPTS" = "x" ]; then
JAVA_OPTS="-Xms1303m -Xmx1303m"
JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
JAVA_OPTS="$JAVA_OPTS -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Xbootclasspath/p:/home/vagrant/EAP-7.0.0/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.3.Final-redhat-1.jar"
echo "JAVA_OPTS already set in environment; overriding default settings with values: $JAVA_OPTS"

In case the MBeanServerBuilder error occurs

If any MBeanServerBuilder-related error is output in JBoss 5.0 or earlier, add the JVM options.

# Specify options to pass to the Java VM.
if [ "x$JAVA_OPTS" = "x" ]; then
JAVA_OPTS="-Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000"
JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver"

In case of occurrence of a permission error

If any Java security policy-related error occurs, add the role setting in $JAVA_HOME/jre/lib/security/java.policy.

To apply all roles collectively, add the setting in java.policy as follows:

grant {

In case of occurrence of the error error

Add the setting in java.policy.

grant {
permission {package path seen in the error message}, "read"

In case of occurrence of the java.util.PropertyPermission error

Add the setting in java.policy.

grant {
permission java.util.PropertyPermission {package path see in the error message}, "read"

In case the sigar library cannot be loaded

Check whether the execution role for $WHATAP_HOME/lib1/*.so exists. If no permission, give the execution role.

$ sudo chmod +x *.so

If under $WHATAP_HOME/lib1 of AIX 7, does not exist and the error occurs, copy the file.

Sigar library error on AIX 7

$ cp