Transports and Interfaces: Siebel Enterprise Application Integration > EAI JMS Transport >

Troubleshooting for the JMS Transport

Several diagnostic methods are present in the EAI JMS Transport to assist in troubleshooting CLASSPATH, JNDI, and problems connecting to the JMS server:

• CheckClasspath. Iterates through the JVM's classpath, checking for the existence of each directory in the file system.

  NOTE:  The length of the classpath is limited to 1024 characters. However, it might be truncated when displayed in the user interface and srvrmgr command-line interface. To see the entire classpath, examine the log file. For information on logging, see About Logging for the JMS Transport.

• CheckJNDIContext. Creates a JNDI InitialContext based on parameters (context factory class, URL) in the jndi.properties file.

  Lists the parameters and the entries found in the context, as well as the names and classes of the administered objects.

• CheckJNDIObjects. Retrieves administered objects (connection factory, queue, topic) from JNDI.

  If CheckJNDIObjects finishes without errors, then JNDI binding is proper.

  If CheckJNDIObjects finishes with errors, then it means that the JNDI binding has not been done properly. Rebind the JNDI objects or check the jndi.properties file to see if the provider URL is pointing to the correct location.

• CheckJMSServer. Invokes JMS methods directly and simply. If SendQueue is specified, CheckJMSServer sends a message and then receives a message. If SendQueue is not specified and Topic is, it then creates a durable subscriber, publishes a message, receives it, and then unsubscribes.

  If CheckJMSServer finishes without errors, then both the queuing system and JMS are communicating properly.

  If CheckJMSServer finishes with errors, it means that the JMS queue in the queuing system is not functioning properly. Check the corresponding queue in the queuing system.

• CheckAll. Executes all checks: CheckClasspath, CheckJNDIContext, CheckJNDIObjects, CheckJMSServer.

Table 19 contains more details on arguments used with some of the JMS Transport debugging methods. The arguments listed are used by all three methods.