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

Bug 901105 (JBPAPP6-1283)

Summary: Errors during looking at JMS Destinations in web console
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Miroslav Novak <mnovak>
Component: Web ConsoleAssignee: Miroslav Novak <mnovak>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 6.0.0CC: atangrin, brian.stansberry, fnasser, ike.braun, jmesnil, mnovak
Target Milestone: ---   
Target Release: TBD EAP 6   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBPAPP6-1283
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-15 17:01:41 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.xml
none
Screenshot-JBoss Management - Mozilla Firefox.png none

Description Miroslav Novak 2012-10-25 11:31:01 UTC
project_key: JBPAPP6

Looking at deployed queues in  in Runtime -> JMS Destinations throws error:
{code}
Unknown error

Unexpected HTTP response: 500

Request
{
    "address" => [
        ("subsystem" => "messaging"),
        ("hornetq-server" => "default"),
        ("jms-queue" => "testQueue0")
    ],
    "operation" => "read-resource",
    "include-runtime" => true
}

Response

Internal Server Error
{
    "outcome" => "failed",
    "rolled-back" => true,
    "response-headers" => {"process-state" => "reload-required"}
}
{code}

Server log:
{code}
13:25:31,139 ERROR [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 9) JBAS014612: Operation ("read-attribute") failed - address: ([
    ("subsystem" => "messaging"),
    ("hornetq-server" => "default"),
    ("jms-queue" => "testQueue0")
]): java.lang.IllegalArgumentException: newValue is null
	at org.jboss.dmr.ModelNode.set(ModelNode.java:458) [jboss-dmr-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
	at org.jboss.as.messaging.jms.JMSQueueReadAttributeHandler.executeRuntimeStep(JMSQueueReadAttributeHandler.java:113)
	at org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:90) [jboss-as-controller-7.1.3.Final-redhat-3.jar:7.1.3.Final-redhat-3]
	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.3.Final-redhat-3.jar:7.1.3.Final-redhat-3]
	at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.3.Final-redhat-3.jar:7.1.3.Final-redhat-3]
	at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.3.Final-redhat-3.jar:7.1.3.Final-redhat-3]
	at org.jboss.as.messaging.jms.JMSQueueReadAttributeHandler.executeRuntimeStep(JMSQueueReadAttributeHandler.java:128)
	at org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:90) [jboss-as-controller-7.1.3.Final-redhat-3.jar:7.1.3.Final-redhat-3]
	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.3.Final-redhat-3.jar:7.1.3.Final-redhat-3]
	at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.3.Final-redhat-3.jar:7.1.3.Final-redhat-3]
	at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.3.Final-redhat-3.jar:7.1.3.Final-redhat-3]
	at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:473) [jboss-as-controller-7.1.3.Final-redhat-3.jar:7.1.3.Final-redhat-3]
	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.3.Final-redhat-3.jar:7.1.3.Final-redhat-3]
	at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.3.Final-redhat-3.jar:7.1.3.Final-redhat-3]
	at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.3.Final-redhat-3.jar:7.1.3.Final-redhat-3]
	at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:126) [jboss-as-controller-7.1.3.Final-redhat-3.jar:7.1.3.Final-redhat-3]
	at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:111) [jboss-as-controller-7.1.3.Final-redhat-3.jar:7.1.3.Final-redhat-3]
	at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:316) [jboss-as-controller-7.1.3.Final-redhat-3.jar:7.1.3.Final-redhat-3]
	at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:306) [jboss-as-controller-7.1.3.Final-redhat-3.jar:7.1.3.Final-redhat-3]
	at org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:320)
	at org.jboss.as.domain.http.server.DomainApiHandler.doHandle(DomainApiHandler.java:226)
	at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:233)
	at org.jboss.as.domain.http.server.security.SubjectAssociationHandler.handle(SubjectAssociationHandler.java:51)
	at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)
	at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:69)
	at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81)
	at org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:710)
	at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)
	at org.jboss.as.domain.http.server.RealmReadinessFilter.doFilter(RealmReadinessFilter.java:47)
	at org.jboss.as.domain.http.server.DmrFailureReadinessFilter.doFilter(DmrFailureReadinessFilter.java:45)
	at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81)
	at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:682)
	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]
	at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA-redhat-2.jar:2.0.0.GA-redhat-2]
{code}

Attaching standalone-full-ha.xml to reproduce this issue

Comment 1 Miroslav Novak 2012-10-25 11:31:38 UTC
Attachment: Added: standalone-full-ha.xml


Comment 2 Miroslav Novak 2012-10-25 11:33:43 UTC
Attachment: Added: Screenshot-JBoss Management - Mozilla Firefox.png


Comment 3 Heiko Braun 2012-10-25 11:41:13 UTC
jeff, can you check if it relates to the "reload required" state?

Comment 4 Jeff Mesnil 2012-10-25 13:13:47 UTC
this looks like to be the same issue: the attached standalone configuration does not define dead-letter-address or expiry-address for the JMS Queue's corresponding address.

When we set the null value on the ModelNode result, it throws an exception.
I've pulled a request to fix this in btoh master & 7.1 branches

Comment 5 Jeff Mesnil 2012-10-25 13:13:47 UTC
Link: Added: This issue duplicates AS7-5832


Comment 6 Jeff Mesnil 2012-10-26 06:32:54 UTC
AS7-5832 has been resolved in 7.1 branch

Comment 7 Fernando Nasser 2012-10-26 15:19:11 UTC
Is this really resolved?  Fixing the 7.1 branch does not automatically gets it into the build that is being tested by QE.  The fix must be merged into the production branch in Egn Git by ESSC and then whatever component(s) is(are) affected has to be built and that build included in the next hand-off to QE (if any).  Then it is Resolved.

Comment 8 Jeff Mesnil 2012-10-26 15:32:52 UTC
[~fnasser] right, I resolved it too fast. the coding is done and I'll assign it back to miroslav.

Comment 9 Miroslav Novak 2012-10-29 08:34:56 UTC
Hi Jeff, 

I believe that Fernando wanted to say that once this fix is merged to "production branch in Eng Git by ESSC" then this jira can be set as resolved. I'll verify this fix in the next build of EAP 6.0.1 and close it if it's ok. I hope this process did not changed because we're verifying only jiras/fixes which are set as resolved. 

Thanks,

Mirek

Comment 10 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 11 Anne-Louise Tangring 2012-11-13 20:53:14 UTC
Release Notes Docs Status: Removed: Not Required 


Comment 12 Miroslav Novak 2013-02-19 14:43:39 UTC
Verified in EAP 6.1.0.DR4.