If you are installing standalone Message Queue 3.7 UR2 (from a zipped file) please note that the broker cannot be automatically installed as a Windows service. To install the broker as a Windows service, use the imqsvcadmin install command.
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 Ctrl-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 and if it tries to use the same ClientID, durable subscription, or queue, it might receive a “Client ID is already in use” exception. This is not a real problem; it is just the side effect of the termination process described above. If the client is started after a delay of approximately one minute, everything should work fine.