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

Bug 825755

Summary: Deploying if RichFaces showcase on EAP ER 8 does not initialize JMS correctly, therefore a4j:push is broken
Product: [Retired] JBoss Enterprise WFK Platform 2 Reporter: Juraj Huska <jhuska>
Component: RichFacesAssignee: Marek Novotny <mnovotny>
Status: CLOSED CURRENTRELEASE QA Contact: Pavol Pitonak <ppitonak>
Severity: urgent Docs Contact:
Priority: high    
Version: 2.0.0.ER6CC: jhuska, kpiwko, lfryc, ppitonak
Target Milestone: ---   
Target Release: 2.0.0.ER7   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-22 07:32:40 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
The patch for the issue none

Description Juraj Huska 2012-05-28 11:45:28 UTC
Description of problem:
When deploying richfaces showcase on EAP ER 8, then following error is thrown when it is about to initialize JMS:

13:28:04,305 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014613: Operation ("read-resource") failed - address: ([("subsystem" => "messaging")]) - failure description: "JBAS014807: Management resource '[(\"subsystem\" => \"messaging\")]' not found"

The showcase is deployed fully, however, a4j:push is not working in all demos. It is the same when deploying on the EAP ER 7. Note that it works for EAP ER6. It is the same when deploying community version of RichFaces showcase on EAPs.

Version-Release number of selected component (if applicable):
RichFaces 4.2.2.Final-redhat-1

Comment 1 Lukáš Fryč 2012-05-30 10:31:31 UTC
Reproduced.

The issue can be fixed by using the JBoss AS feature to load JMS destinations from *-jms.xml descriptor.

Comment 2 Lukáš Fryč 2012-05-30 10:34:24 UTC
Created attachment 587674 [details]
The patch for the issue

Comment 3 Marek Novotny 2012-05-30 12:58:31 UTC
applied the patch

Comment 4 Juraj Huska 2012-06-04 13:33:54 UTC
I have verified that the issue is not occurring anymore.