918131 – NullPointerException on :write-attribute(name=block-on-acknowledge,value=true)

Bug 918131 - NullPointerException on :write-attribute(name=block-on-acknowledge,value=true)

Summary: NullPointerException on :write-attribute(name=block-on-acknowledge,value=true)

Keywords:
Status:	CLOSED CURRENTRELEASE
Alias:	None
Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	JMS
Sub Component:
Version:	6.1.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	high
Target Milestone:	ER4
Target Release:	EAP 6.1.0
Assignee:	Jeff Mesnil
QA Contact:
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2013-03-05 14:55 UTC by Dmytro Pogrebniuk
Modified:	2013-07-23 18:45 UTC (History)
CC List:	5 users (show)
Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type:	Bug
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Issue Tracker	AS7-6699	0	Major	Resolved	AS7 messaging resources throws NPE when hornetq-server is a backup	2013-08-23 14:23:36 UTC

Description Dmytro Pogrebniuk 2013-03-05 14:55:40 UTC

Description of problem:
NullPointerException on :write-attribute(name=block-on-acknowledge,value=true)

Version-Release number of selected component (if applicable):
6.1.0.DR4

Steps to Reproduce:
1.cd subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory/
2.:write-attribute(name=block-on-acknowledge,value=true)
  
Additional info:
[0m[31m15:41:04,991 ERROR [org.jboss.as.controller.management-operation] JBAS014612: Operation ("write-attribute") failed - address: ([
    ("subsystem" => "messaging"),
    ("hornetq-server" => "default"),
    ("connection-factory" => "RemoteConnectionFactory")
]): java.lang.NullPointerException
	at org.jboss.as.messaging.jms.ConnectionFactoryWriteAttributeHandler.applyOperationToHornetQService(ConnectionFactoryWriteAttributeHandler.java:139)
	at org.jboss.as.messaging.jms.ConnectionFactoryWriteAttributeHandler.applyUpdateToRuntime(ConnectionFactoryWriteAttributeHandler.java:92)
	at org.jboss.as.controller.AbstractWriteAttributeHandler$1.execute(AbstractWriteAttributeHandler.java:131) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
	at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
	at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
	at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
	at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:142) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
	at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:112) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
	at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [jboss-as-protocol-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
	at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [jboss-as-protocol-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_38]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_38]
	at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_38]
	at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final]

Comment 1 Jeff Mesnil 2013-03-06 17:17:59 UTC

I can not reproduce it. if I run the standalone-full.xml configuration, the attribute is correctly written.

What's the result of the /subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory:read-resource(include-runtime=true) operation?

Comment 2 Dmytro Pogrebniuk 2013-03-07 09:25:21 UTC

HornetQ configuration:

<backup>true</backup>

All actions were performed between 1st and 2nd stage of initialization(when backup is waiting to become live).

Comment 3 Jeff Mesnil 2013-03-08 17:37:49 UTC

I have reproduced the issue and it is more general issue with passive hornetq-server (ie HornetQ server that are configured as backup and waiting for failover).

The JIRA issue contains the description of the issue

Comment 4 JBoss JIRA Server 2013-03-18 10:48:45 UTC

Jeff Mesnil <jmesnil> made a comment on jira AS7-6699

PR for master branch

Comment 5 JBoss JIRA Server 2013-03-25 16:28:22 UTC

Jeff Mesnil <jmesnil> made a comment on jira AS7-6699

PR merged in master branch

Comment 7 Radim Hatlapatka 2013-04-08 15:53:47 UTC

Verified for EAP 6.1.0 ER4

Comment 11 mark yarborough 2013-07-23 18:45:43 UTC

Details inside vpn: https://post-office.corp.redhat.com/mailman/private/eap-pm-list/2013-July/msg00105.html

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