Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 901100 (JBPAPP6-1268)

Summary: NPE during start of backup server
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Miroslav Novak <mnovak>
Component: HornetQAssignee: Clebert Suconic <clebert.suconic>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 6.0.1CC: atangrin, mnovak, toross
Target Milestone: ---   
Target Release: TBD EAP 6   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBPAPP6-1268
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-15 17:02:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
standalone-full-ha-backup.xml
none
standalone-full-ha-live.xml none

Description Miroslav Novak 2012-10-24 13:17:19 UTC
project_key: JBPAPP6

There is NPE during start of backup server:
{code}
14:47:41,116 INFO  [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (Activation for server HornetQServerImpl::serverUUID=f56b8f5d-1dd6-11e2-b82c-ebd67d71ec3a) Started Netty Acceptor version 3.2.6.Final-redhat-2-20df069 192.168.40.2:5455 for CORE protocol
14:47:41,120 WARN  [org.hornetq.core.server.cluster.impl.ClusterConnectionImpl] (Thread-0 (HornetQ-server-HornetQServerImpl::serverUUID=f56b8f5d-1dd6-11e2-b82c-ebd67d71ec3a-1912078839)) Unable to announce backup, retrying: HornetQException[errorCode=3 message=Timed out waiting to receive initial broadcast from cluster]
	at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:717) [hornetq-core-2.2.22.Final-redhat-1.jar:2.2.22.SNAPSHOT (HQ_2_2_22_AS7_Final, 122)]
	at org.hornetq.core.client.impl.ServerLocatorImpl.connect(ServerLocatorImpl.java:594) [hornetq-core-2.2.22.Final-redhat-1.jar:2.2.22.SNAPSHOT (HQ_2_2_22_AS7_Final, 122)]
	at org.hornetq.core.server.cluster.impl.ClusterConnectionImpl$2.run(ClusterConnectionImpl.java:485) [hornetq-core-2.2.22.Final-redhat-1.jar:2.2.22.SNAPSHOT (HQ_2_2_22_AS7_Final, 122)]
	at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) [hornetq-core-2.2.22.Final-redhat-1.jar:2.2.22.SNAPSHOT (HQ_2_2_22_AS7_Final, 122)]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.6.0_24]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_24]
	at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]

14:47:41,122 INFO  [org.hornetq.core.server.impl.HornetQServerImpl] (Activation for server HornetQServerImpl::serverUUID=f56b8f5d-1dd6-11e2-b82c-ebd67d71ec3a) Backup Server is now live
14:47:42,122 WARN  [org.hornetq.core.server.cluster.impl.ClusterConnectionImpl] (Thread-3 (HornetQ-server-HornetQServerImpl::serverUUID=f56b8f5d-1dd6-11e2-b82c-ebd67d71ec3a-1912078839)) Unable to announce backup, retrying: java.lang.NullPointerException
	at org.hornetq.core.server.cluster.impl.ClusterConnectionImpl$2.run(ClusterConnectionImpl.java:485) [hornetq-core-2.2.22.Final-redhat-1.jar:2.2.22.SNAPSHOT (HQ_2_2_22_AS7_Final, 122)]
	at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) [hornetq-core-2.2.22.Final-redhat-1.jar:2.2.22.SNAPSHOT (HQ_2_2_22_AS7_Final, 122)]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.6.0_24]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_24]
	at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]
{code}

NPE is periodically logged which makes it unreadable. It stops when live server is started. 

How to reproduce:
{code}
Download and unzip EAP 6.0.1.ER3  (http://download.devel.redhat.com/devel/candidates/JBEAP/6.0.1.ER3/jboss-eap-6.0.1.ER3.zip)
Create server1 and server2 directories and copy unzipped jboss-eap-6.0 into them
Replace standalone-full-ha.xml in server1/jboss-eap-6.0/standalone/configuration/standalone-full-ha.xml by standalone-full-ha-live.xml (attached to this jira)
Replace standalone-full-ha.xml in server2/jboss-eap-6.0/standalone/configuration/standalone-full-ha.xml by standalone-full-ha-backup.xml (attached to this jira)
Start server 1: sh standalone.sh -c standalone-full-ha.xml -b 127.0.0.1 and SHUTDOWN it
Start server 2: sh standalone.sh -c standalone-full-ha.xml -b 127.0.0.2 and exceptions occuer
{code}

Comment 1 Miroslav Novak 2012-10-24 13:17:44 UTC
Attachment: Added: standalone-full-ha-backup.xml
Attachment: Added: standalone-full-ha-live.xml


Comment 2 Miroslav Novak 2012-10-24 13:25:38 UTC
Link: Added: This issue is related to JBPAPP-10067


Comment 3 Anne-Louise Tangring 2012-11-01 17:41:28 UTC
This issue is listed as Major or below and as such is not targetted for the EAP 6.0.1 release, now that we are in Blocker or Critical issue only mode. Should this be reconsidered, please contact the EAP PM team.

Comment 4 Anne-Louise Tangring 2012-11-13 20:53:12 UTC
Docs QE Status: Removed: NEW 


Comment 5 Miroslav Novak 2013-01-03 14:20:07 UTC
Link: Added: This issue Cloned to JBPAPP6-1756


Comment 6 Miroslav Novak 2013-02-19 08:56:40 UTC
This issue is fixed in EAP 6.1.0.DR4. Setting status to verified.