Troubleshooting

This section describes possible problems with an HTTP or HTTPS connection and provides guidance on how to handle them.

Server or Broker Failure

If the Web server fails and is restarted, all connections are restored and there is no effect on clients. However, if the broker fails and is restarted, an exception is thrown and clients must re-establish their connections.

If both the Web server and the broker fail, and the broker is not restarted, the Web server restores client connections and continues waiting for a broker connection without notifying clients. To avoid this situation, always make sure the broker is restarted.

Client Failure to Connect Through the Tunnel Servlet

If an HTTPS client cannot connect to the broker through the tunnel servlet, do the following:

If a Client Cannot Connect

1. Start the servlet and the broker.

2. Use a browser to manually access the servlet through the HTTPS tunnel servlet URL.

3. Use the following administrative commands to pause and resume the connection:

   imqcmd pause svc -n httpsjms -u admin imqcmd resume svc -n httpsjms -u admin

   When the service resumes, an HTTPS client should be able to connect to the broker through the tunnel servlet.