Troubleshooting Guide › Troubleshooting the Reporting Service › How to Troubleshoot the Reporting Service › Troubleshoot JBoss

Troubleshoot JBoss

The JBoss web application server environment contains the message-driven Java beans (MDBs) that read the data from the Message Queue and write it into the central database. The central database stores reporting data.

To troubleshoot JBoss

1. Verify that JBoss starts correctly, as follows:
   • If you start JBoss from a command prompt, review the initial output when JBoss starts. Verify that the output does not contain any errors.
   • If you start JBoss as a service, use the log files or the tail command to review the initial output when JBoss starts. Verify that the output does not contain any errors.
2. Open the following file and review it for errors, where JBossInstallDir is the directory in which you installed JBoss:

   JBossInstallDir/server/default/log/boot.log

   This file lists the steps that JBoss takes each time it boots the microkernel.

3. Verify that the JAVA_HOME variable is set to the correct location.

   Note: If the JAVA_HOME variable is set to the correct location but JBoss does not resolve the variable, set the JAVA_HOME variable to a lower location, for example, the bin directory under the JDK installation path.

4. Open the following file and review it for errors:

   JBossInstallDir/server/default/log/server.log

   This file lists the actions that JBoss performs in the JBoss web application server environment.

   Note: JBoss creates to new server.log file each time you start it.

5. Verify that JBoss ports do not conflict with ports that are used on other services.
6. (Optional) If the JNP port conflicts with another service, change the JNP port on 1099 to another port, as follows:
   1. Open the following file in a text editor:

      JBossInstallDir/server/default/conf/jboss-service.xml

   2. Change the port number in the following section:

      <!-- The listening port for the bootstrap JNP service. Set this to -1 to run the NamingService without the JNP invoker listening port.-->
      <attribute name="Port">1099</attribute>
      

   3. Save and close the file.
7. (Optional) If the RMI port conflicts with another service, change the RMI port on 1098 to another port, as follows:
   1. Open the following file in a text editor:

      JBossInstallDir/server/default/conf/jboss-service.xml

   2. Change the port number in the following section:

      <!-- The port of the RMI naming service, 0 == anonymous -->
      <!-- attribute name="RmiPort">1098</attribute -->
      <attribute name="RmiPort">1098</attribute>
      

   3. Save and close the file.