Red Hat Bugzilla – Bug 831513
Impossible to create JMS destination with default settings
Last modified: 2013-09-01 06:09:49 EDT
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">
Created attachment 591399 [details]
*** Bug 838667 has been marked as a duplicate of this bug. ***
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.