Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-8153 Upgrade HornetQ for EAP 5.2.0
  3. JBPAPP-8731

IllegalStateException: Cannot access JMS Server, core server is not yet active during shutting down of backup server

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • EAP_EWP 5.2.0
    • EAP_EWP 5.1.2
    • HornetQ
    • None
    • Release Notes
    • Hide
      In circumstances where a JMS server backup is started and then the backup server is shutdown before the backup goes live, an <literal>IllegalStateException</literal> can be thrown (on the backup server). This is because any calls to create new connection factories and destinations for the backup server are cached and, if the server is shut down, EAP will attempt to undeploy them only to find they don't exist. This issue has been corrected with a patch that caches the relevant shutdown commands (just as is done with the start commands) so that they do not get executed until the server is active.
      Show
      In circumstances where a JMS server backup is started and then the backup server is shutdown before the backup goes live, an <literal>IllegalStateException</literal> can be thrown (on the backup server). This is because any calls to create new connection factories and destinations for the backup server are cached and, if the server is shut down, EAP will attempt to undeploy them only to find they don't exist. This issue has been corrected with a patch that caches the relevant shutdown commands (just as is done with the start commands) so that they do not get executed until the server is active.
    • Documented as Resolved Issue
    • NEW

      This issue relates only to one-off JBPAPP-8396.

      When backup server is gracefully shut-downed then lots of IllegalStateException occurs in console log:

      ^C04:35:37,589 INFO  [ServerImpl] Runtime shutdown hook called, forceHalt: true
04:35:37,593 WARN  [HornetQConnectionFactoryDeployment] Error destroying ConnectionFactory: InVMConnectionFactory
java.lang.IllegalStateException: Cannot access JMS Server, core server is not yet active
	at org.hornetq.jms.server.impl.JMSServerManagerImpl.checkInitialised(JMSServerManagerImpl.java:1508)
	at org.hornetq.jms.server.impl.JMSServerManagerImpl.shutdownConnectionFactory(JMSServerManagerImpl.java:1342)
	at org.hornetq.jms.server.impl.JMSServerManagerImpl.destroyConnectionFactory(JMSServerManagerImpl.java:1326)
	at org.jboss.as.integration.hornetq.deployers.pojo.HornetQConnectionFactoryDeployment.stop(HornetQConnectionFactoryDeployment.java:60)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       ....

        1. backup-server.log
          63 kB
        2. jboss-eap-hornetq-5.1.2-installer-jbpapp-8396.zip
          8.88 MB
        3. production-backup.zip
          286 kB

              rhn-support-jbertram Justin Bertram
              mnovak1@redhat.com Miroslav Novak
              Scott Thomas Scott Thomas (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: