Affects Version/s: A-MQ 7.0.0.ER17
Fix Version/s: None
Artemis service is not logging anything when started from second instance of broker on the same machine. There is no exception in the logs, etc. The only indication of a failure is the start script itself failing with proper ecode. Log is completely empty.
When started using artemis run: NPE.
Still no update about real problem of another broker being up and having bound needed ports.
How AMQ6 behaves under same scenario:
1) start broker1 -> everything is ok
2) start broker2 ->
- start-script ecode 0
- Binding exceptions are written in logs
- Every 10 seconds this broker tries to bind ports and start
3) shutdown broker1. broker2 finally binds needed ports and is happily up.