Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-602

Artemis service/start script is not reporting correct errors, when second instance is started on same host

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Minor 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 ->

      1. start-script ecode 0
      2. Binding exceptions are written in logs
      3. Every 10 seconds this broker tries to bind ports and start
        3) shutdown broker1. broker2 finally binds needed ports and is happily up.

              rh-ee-ataylor Andy Taylor
              mtoth@redhat.com Michal Toth
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: