Transports and Interfaces: Siebel Enterprise Application Integration > Java Message Service 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 in the file system.
• CheckJNDIContext. Creates a JNDI InitialContext based on parameters (context factory class, URL) in resource file jndi.properties.

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

• CheckJNDIObjects. Retrieves administered objects (connection factory, queue, topic) from JNDI.
• CheckJMSServer. Invokes JMS methods directly and simply.

  If SendQueue is specified, it 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.

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

Table 12 contains more details of the arguments for use with the JMS Transport. The arguments listed are used by all three methods.