-
Story
-
Resolution: Unresolved
-
Minor
-
None
-
A-MQ 7.0.0.ER17
-
None
-
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.
0,root@r7x0_mtoth opt]$ /opt/jboss-amq-7-snap/bin/artemis-service start Starting artemis-service Could not start artemis-service [1,root@r7x0_mtoth opt]$
When started using artemis run: NPE.
[130,root@r7x0_mtoth opt]$ /opt/jboss-amq-7-snap/bin/artemis run Error: Exception thrown by the agent : java.lang.NullPointerException [1,
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.
- relates to
-
ENTMQBR-997 Provide a way to run AMQ 7 as system service (across all supported OS environments)
- Closed
-
ENTMQBR-524 Artemis-service is not returning correct error codes / does not detect broker failures
- Closed