1391840 – [GSS](6.4.z) HQ224000: Failure in initialisation: java.lang.NullPointerException

Bug 1391840 - [GSS](6.4.z) HQ224000: Failure in initialisation: java.lang.NullPointerException

Summary: [GSS](6.4.z) HQ224000: Failure in initialisation: java.lang.NullPointerException

Keywords:
Status:	CLOSED CURRENTRELEASE
Alias:	None
Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	JMS
Sub Component:
Version:	6.4.11
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	CR1
Target Release:	EAP 6.4.13
Assignee:	Tom Ross
QA Contact:	Peter Mackay
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:	eap6413-payload 1390788 1392870
TreeView+	depends on / blocked

Reported:	2016-11-04 08:33 UTC by Tom Ross
Modified:	2020-05-14 15:23 UTC (History)
CC List:	4 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Clones:	1392870 (view as bug list)
Environment:
Last Closed:	2017-02-03 16:41:40 UTC
Type:	Bug
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Apache JIRA	ARTEMIS-822	0	None	None	None	2016-12-09 11:05:25 UTC
Red Hat Issue Tracker	HORNETQ-1542	0	Major	Open	HQ224000: Failure in initialisation: java.lang.NullPointerException	2018-11-21 09:49:56 UTC

Description Tom Ross 2016-11-04 08:33:59 UTC

HornetQ message broker thrown java.lang.NullPointerException when trying to load page from disk:

11:00:49,821 ERROR [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ224000: Failure in initialisation: java.lang.NullPointerException
	at org.hornetq.core.paging.cursor.impl.PageSubscriptionImpl.reloadPageCompletion(PageSubscriptionImpl.java:208) [hornetq-server-2.3.25.SP14-redhat-1.jar:2.3.25.SP14-redhat-1]
	at org.hornetq.core.persistence.impl.journal.JournalStorageManager.loadMessageJournal(JournalStorageManager.java:1883) [hornetq-server-2.3.25.SP14-redhat-1.jar:2.3.25.SP14-redhat-1]
	at org.hornetq.core.server.impl.HornetQServerImpl.loadJournals(HornetQServerImpl.java:1806) [hornetq-server-2.3.25.SP14-redhat-1.jar:2.3.25.SP14-redhat-1]
	at org.hornetq.core.server.impl.HornetQServerImpl.initialisePart2(HornetQServerImpl.java:1610) [hornetq-server-2.3.25.SP14-redhat-1.jar:2.3.25.SP14-redhat-1]
	at org.hornetq.core.server.impl.HornetQServerImpl.access$1400(HornetQServerImpl.java:182) [hornetq-server-2.3.25.SP14-redhat-1.jar:2.3.25.SP14-redhat-1]
	at org.hornetq.core.server.impl.HornetQServerImpl$SharedStoreLiveActivation.run(HornetQServerImpl.java:2331) [hornetq-server-2.3.25.SP14-redhat-1.jar:2.3.25.SP14-redhat-1]
	at org.hornetq.core.server.impl.HornetQServerImpl.start(HornetQServerImpl.java:452) [hornetq-server-2.3.25.SP14-redhat-1.jar:2.3.25.SP14-redhat-1]
	at org.hornetq.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:490) [hornetq-jms-server-2.3.25.SP14-redhat-1.jar:2.3.25.SP14-redhat-1]
	at org.jboss.as.messaging.jms.JMSService.doStart(JMSService.java:158) [jboss-as-messaging-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
	at org.jboss.as.messaging.jms.JMSService.access$000(JMSService.java:60) [jboss-as-messaging-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
	at org.jboss.as.messaging.jms.JMSService$1.run(JMSService.java:96) [jboss-as-messaging-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_112]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_112]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_112]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_112]
	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_112]
	at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1]

Comment 1 Radovan STANCEL 2016-12-06 08:07:25 UTC

PR https://github.com/hornetq/hornetq/pull/2106

PR was also merged

Comment 2 Radovan STANCEL 2016-12-09 11:05:26 UTC

7.1 and WF branch are solved by ARTEMIS-822.
7.0 is not containing the issue - confirmed by Tom Ross and Clebert

Comment 3 Peter Mackay 2017-01-30 08:07:45 UTC

Verified with EAP 6.4.13.CP.CR2

Comment 4 Petr Penicka 2017-02-03 16:41:40 UTC

Released with EAP 6.4.13 on Feb 02 2017.

Note You need to log in before you can comment on or make changes to this bug.