Business Intelligence (BusinessObjects)
Page tree
Skip to end of metadata
Go to start of metadata

 

Additional Debugging Information

 

You can use JConsole to troubleshoot failed JMX connections or failed JMX validations in the BI Support Tool.  Do the following:

  1. Go to a client where you have Oracle JDK 8 installed (or just download it from Oracle and install it on the same client where the BI Support Tool is installed)

  2. Create a new text file somewhere on this client and save it as logging.properties.  Then add the following text to logging.properties and save the changes.  In this example, I am saving my logging.properties in the location C:\temp1\logging.properties

    handlers = java.util.logging.ConsoleHandler

    .level = INFO

    java.util.logging.ConsoleHandler.level=FINEST

    java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter

    javax.management.level=FINEST

    javax.management.remote.level=FINEST

  3. Open a command prompt and browse to the location where you have the Oracle JDK 8 installed (in this example C:\Program Files\Java\jdk1.8.0_111) then browse to the bin folder 


  4. Run the following command to start JConsole in debug mode

    jconsole.exe -debug -J-Djava.util.logging.config.file=C:\temp1\logging.properties service:jmx:rmi:///jndi/rmi://YOURTOMCATHOSTNAME:8008/jmxrmi

    Where YOURTOMCATHOSTNAME is your Tomcat hostname and 8008 is the JMX port that Tomcat is listening on



     

  5. JConsole will start with a debug window.  The debug window will provide additional clues as to why the connection is failed
     
  • No labels