Bug 831513 - Impossible to create JMS destination with default settings
Summary: Impossible to create JMS destination with default settings
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Plugins
Version: 4.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: RHQ 4.5.0
Assignee: Heiko W. Rupp
QA Contact: Mike Foley
URL:
Whiteboard:
: 838667 (view as bug list)
Depends On:
Blocks: 831516
TreeView+ depends on / blocked
 
Reported: 2012-06-13 07:59 UTC by Heiko W. Rupp
Modified: 2013-09-01 10:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 831516 (view as bug list)
Environment:
Last Closed: 2013-09-01 10:09:49 UTC
Embargoed:


Attachments (Terms of Use)
Proposed patch (8.06 KB, patch)
2012-06-13 08:11 UTC, Heiko W. Rupp
hrupp: review? (ian.springer)
Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EMBJOPR-368 0 None None None Never

Description Heiko W. Rupp 2012-06-13 07:59:01 UTC
Take EAP 5.1.2 in to inventory, try to create a JMS Queue or Topic by only giving the required name and JNDIName.

This will fail on EAP 5.1.2 with

vfsfile:/devel/jboss-eap-5.1/jboss-as/server/default/deploy/java__myQ2-service.xml -> org.jboss.deployment.DeploymentException: Error configuring attribute DLQ

Same for ExpiryQueue and ServerPeer.


Workaround is to have the user deliver those properties

Patch is to add those settings as 'value' attribute like this:

<c:simple-property required="false" name="expiryQueue" default="jboss.messaging.destination:service=Queue,name=ExpiryQueue">

<c:simple-property required="false" name="DLQ" default="jboss.messaging.destination:service=Queue,name=DLQ">

<c:simple-property required="false" name="serverPeer" default="jboss.messaging:service=ServerPeer">

Comment 2 Heiko W. Rupp 2012-06-13 08:11:33 UTC
Created attachment 591399 [details]
Proposed patch

Comment 3 Heiko W. Rupp 2012-06-13 13:22:26 UTC
master 4fcfaf0e28be1

Comment 4 Larry O'Leary 2012-07-20 19:18:15 UTC
*** Bug 838667 has been marked as a duplicate of this bug. ***

Comment 5 Heiko W. Rupp 2013-09-01 10:09:49 UTC
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.


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