Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-4772

(7.0.z) ARTEMIS-697 - AMQ224033: Failed to broadcast connector configs: java.lang.IllegalStateException: channel is closed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 7.0.5.CR1, 7.0.5.GA
    • 7.0.1.CR1
    • ActiveMQ
    • None
    • Hide

      Steps to reproduce:
      – Download EAP 7.1.0.DR4 and unzip - http://download.eng.brq.redhat.com/devel/candidates/JBEAP/JBEAP-7.1.0.DR4/jboss-eap-7.1.0.DR4.zip
      – Start the server

      cd $JBOSS_HOME/bin
sh standalone.sh -c standalone-full-ha.xml

      – Connect from CLI another console in $JBOSS_HOME/bin directory and call :reload

      sh jboss-cli.sh -c
:reload()

      – Check server.log in $JBOSS_HOME/standalone/log for errors

      Show
      Steps to reproduce: – Download EAP 7.1.0.DR4 and unzip - http://download.eng.brq.redhat.com/devel/candidates/JBEAP/JBEAP-7.1.0.DR4/jboss-eap-7.1.0.DR4.zip – Start the server cd $JBOSS_HOME/bin sh standalone.sh -c standalone-full-ha.xml – Connect from CLI another console in $JBOSS_HOME/bin directory and call :reload sh jboss-cli.sh -c :reload() – Check server.log in $JBOSS_HOME/standalone/log for errors
    • EAP 7.0.5

      There is regression against EAP 7.0.0.GA. Server started in full-ha profile throws error to log after :reload call in CLI:

      15:48:37,763 ERROR [org.apache.activemq.artemis.core.server] (Thread-0 (ActiveMQ-scheduled-threads-378241965)) AMQ224033: Failed to broadcast connector configs: java.lang.IllegalStateException: channel is closed
        at org.jgroups.JChannel.checkClosedOrNotConnected(JChannel.java:963) [jgroups-3.6.9.Final-redhat-4.jar:3.6.8.Final-redhat-2]
        at org.jgroups.fork.ForkChannel.send(ForkChannel.java:211) [jgroups-3.6.9.Final-redhat-4.jar:3.6.8.Final-redhat-2]
        at org.apache.activemq.artemis.api.core.jgroups.JChannelWrapper.send(JChannelWrapper.java:130) [artemis-core-client-1.1.0.SP17-redhat-1.jar:1.1.0.SP17-redhat-1]
        at org.apache.activemq.artemis.api.core.JGroupsBroadcastEndpoint.broadcast(JGroupsBroadcastEndpoint.java:58) [artemis-core-client-1.1.0.SP17-redhat-1.jar:1.1.0.SP17-redhat-1]
        at org.apache.activemq.artemis.core.server.cluster.impl.BroadcastGroupImpl.broadcastConnectors(BroadcastGroupImpl.java:190) [artemis-server-1.1.0.SP17-redhat-1.jar:1.1.0.SP17-redhat-1]
        at org.apache.activemq.artemis.core.server.cluster.impl.BroadcastGroupImpl.run(BroadcastGroupImpl.java:199) [artemis-server-1.1.0.SP17-redhat-1.jar:1.1.0.SP17-redhat-1]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_71]
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [rt.jar:1.8.0_71]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [rt.jar:1.8.0_71]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [rt.jar:1.8.0_71]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_71]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_71]
        at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_71]

      Customer impact:
      Customer will see error in log after reloading the server in full-ha profile and server will not be able to create Artemis cluster with other server.

      Workaround:
      Server must be fully restarted.

        1. JBEAP-4772.patch
          1.0 kB

              chaowan@redhat.com Chao Wang
              mnovak1@redhat.com Miroslav Novak
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: