A connection service using SSL is currently limited to supporting only self-signed server certificates, that is, host-trusted mode.
When a JMS client using the HTTP transport terminates abruptly, for example, using Control-C, the broker takes approximately one minute before releasing the client connection and all the associated resources.
If another instance of the client is started within the one-minute period that tries to use the same ClientID, durable subscription, or queue, a “Client ID is already in use” exception might occur. This exception is just the side effect of the termination process described above. If the client is started after a delay of approximately one minute, no problem should occur.