Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-7606 NullPointerException during failback - EAP/HornetQ in collocated/dedicated topology
  3. JBPAPP-7612

NullPointerException during starting EAP/HornetQ in collocated/dedicated topology

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Obsolete
    • Major
    • TBD EAP 5
    • EAP_EWP 5.1.2 CR1, EAP_EWP 5.1.2 CR2, EAP_EWP 5.1.2, EAP_EWP 5.2.0 ER1
    • HornetQ
    • None
    • Release Notes
    • Hide
      An issue with HornetQ cluster nodes in a dedicated/colocated topology has been identified where a Null Parameter Exception can occur if the nodes are started at the same time. The cause appears to be a timing issue with topology messages passed between the nodes. The workaround is to start the nodes sequentially.
      Show
      An issue with HornetQ cluster nodes in a dedicated/colocated topology has been identified where a Null Parameter Exception can occur if the nodes are started at the same time. The cause appears to be a timing issue with topology messages passed between the nodes. The workaround is to start the nodes sequentially.
    • Documented as Known Issue

    Description

      During start of EAP servers in dedicated/colocated topology sometimes happens that there is npe on one of the servers. Hudson job:
      https://hudson.qa.jboss.com/hudson/view/EAP5/view/HornetQ-Perf/job/eap51-hornetq-failover-dedicated-jms-client-jvmkill/42/console-messaging-21/ - this is log from backup server for server A, server A live is on messaging-19

      Server log:
      [JBoss] 04:44:14,692 INFO [JMSServerManagerImpl] Running cached command for createConnectionFactory for NettyThroughputConnectionFactory
      [JBoss] 04:44:14,721 INFO [NettyAcceptor] Started Netty Acceptor version 3.2.3.Final-r1 messaging-21:5445 for CORE protocol
      [JBoss] 04:44:14,728 INFO [NettyAcceptor] Started Netty Acceptor version 3.2.3.Final-r1 messaging-21:5455 for CORE protocol
      [JBoss] 04:44:14,734 WARN [ClientSessionFactoryImpl] Failed to connect to server.
      [JBoss] 04:44:14,741 INFO [HornetQServerImpl] Backup Server is now live
      [JBoss] 04:44:15,512 WARN [ServerLocatorImpl] did not connect the cluster connection to other nodes
      [JBoss] java.lang.NullPointerException
      [JBoss] at org.hornetq.core.client.impl.ClientSessionFactoryImpl.<init>(ClientSessionFactoryImpl.java:185)
      [JBoss] at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:735)
      [JBoss] at org.hornetq.core.client.impl.ServerLocatorImpl.connect(ServerLocatorImpl.java:594)
      [JBoss] at org.hornetq.core.client.impl.ServerLocatorImpl$3.run(ServerLocatorImpl.java:558)
      [JBoss] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100)
      [JBoss] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      [JBoss] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      [JBoss] at java.lang.Thread.run(Thread.java:662)

      Issue is under investigation and is possible to reproduce it (with some effort) using reproducer attached in JBPAPP-7606.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-7606 NullPointerException during failback - EAP/HornetQ in collocated/dedicated topology

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              csuconic@redhat.com Clebert Suconic
              mnovak1@redhat.com Miroslav Novak
              Russell Dickenson Russell Dickenson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: