When using the CLI jms-ping command, it only works the first time.
On subsequent occasions, the following error is returned:
remote failure: Unable to create a temporary Connection Factory to the JMS Host
Unable to create connection pool.
A resource named test_jms_adapter-Connection-Pool already exists.
Command jms-ping failed.
The first time the command is run, a connection factory called "test-jms-adapter" is created, visible from the management console.
Manually deleting this connection factory allows the command to be run again, once.
Invoking jms-ping is the recommended way of guaranteeing that an embedded OpenMQ broker is running (it is started lazily), making this issue particularly problematic in certain cases.