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

Bug 838666 (EMBJOPR-368)

Summary: [jboss-as-5] Queues and Topics do not provide some required default plug-in configuration values
Product: [JBoss] JBoss Operations Network Reporter: Larry O'Leary <loleary>
Component: Plugin -- JBoss EAP 5Assignee: Stefan Negrea <snegrea>
Status: CLOSED NEXTRELEASE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: urgent    
Version: JON 3.0.1CC: snegrea
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: EmbJopr_1_3_4_SP6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 838667 (view as bug list) Environment:
Last Closed: 2012-09-17 20:09:53 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:
Bug Depends On: 831516    
Bug Blocks: 795918    
Attachments:
Description Flags
Log excerpt from agent log showing complete stack/failure for queue creation none

Description Larry O'Leary 2012-07-09 18:05:52 UTC 
Created attachment 597125 [details]
Log excerpt from agent log showing complete stack/failure for queue creation

Description of problem:
Try to create a queue or topic with only the two required properties name and JNDIName. This will fail with "vfsfile:/devel/jboss-eap-5.1/jboss-as/server/default/deploy/java__myT-service.xml -> org.jboss.deployment.DeploymentException: Error configuring attribute DLQ" 

Same happens for ExpiryQueue and ServerPeer.


Version-Release number of selected component (if applicable):
JON 3.1.0

How reproducible:
Always

Steps to Reproduce:
1. From the EAP 5 resource / Resources / JBoss Messaging - Inventory > Child Resources sub-tab, select Create Child -> Queue
2. Specify a resource name and click Next
3. Specify a queue Name and JNDI Name and click Finish
  
Actual results:
Creation of queue is scheduled but fails due to (complete log excerpt attached):

*** DEPLOYMENTS IN ERROR: Name -> Error

vfsfile:/opt/jboss/eap/jboss-eap-5.1.2/jboss-eap-5.1/jboss-as/server/all/deploy/_queue_TestQueue-service.xml -> org.jboss.deployment.DeploymentException: Error configuring attribute DLQ


DEPLOYMENTS IN ERROR:
  Deployment "vfsfile:/opt/jboss/eap/jboss-eap-5.1.2/jboss-eap-5.1/jboss-as/server/all/deploy/_queue_TestQueue-service.xml" is in error due to the following reason(s): javax.management.MalformedObjectNameException: Key properties cannot be empty



Expected results:
Creation of queue is scheduled and successfully deployed after specifying minimum required configuration properties.


Additional info:
This issue was originally identified in https://issues.jboss.org/browse/EMBJOPR-368 with the following recommended solution:

Those 3 properties need default values set 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 1 Stefan Negrea 2012-07-20 19:06:17 UTC 
AdminConsole_5_1 branch commit:
http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commit;h=c18fa2c5ef2ec3cb684ad89a036ec29d572268c9
Comment 2 JBoss JIRA Server 2012-07-20 19:28:12 UTC 
Larry O'Leary <loleary> updated the status of jira EMBJOPR-368 to Resolved
Comment 3 Larry O'Leary 2012-09-17 20:09:53 UTC 
As per https://issues.jboss.org/browse/EMBJOPR-368 this issue has been resolved and is included in Embedded JOPR 1.3.4.SP6 being shipped with EAP 5.2.0.