Bug 781190 (SOA-3692)

Summary: HornetQ breaks deployment of datasources within an ESB archive
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Filip Nguyen <fnguyen>
Component: JBoss MessagingAssignee: Default User <jbpapp-maint>
Status: CLOSED NOTABUG QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.2.0 GACC: fnguyen, kevin.conner, ldimaggi
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-3692
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-10 15:45:26 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:
Attachments:
Description Flags
Quickstart_helloworld.esb
none
server.log none

Description Filip Nguyen 2012-01-09 14:48:54 UTC 
Steps to Reproduce: See reproducer or reproduce manually: 

 # Create ESB archive with *-ds.xml file. Use the DefaultDS, just rename it to DefaultDS2.
 # Deploy the ESB
 # Try to deploy the *-ds.xml file manually without error
Workaround Description: Deploy datasources directly into the deploy folder
project_key: SOA

When HornetQ is installed and running it is not possible to deploy a datasource by inserting it into an ESB archive. The attached reproducer should work with a production profile.
Comment 1 Filip Nguyen 2012-01-09 14:49:43 UTC 
Attachment: Added: Quickstart_helloworld.esb
Comment 2 Filip Nguyen 2012-01-09 14:51:57 UTC 
Steps to Reproduce: Removed:  # Create ESB archive with *-ds.xml file. Use the DefaultDS, just rename it to DefaultDS2.
 # Deploy the ESB
 # Try to deploy the *-ds.xml file manually without error Added: See reproducer or reproduce manually: 

 # Create ESB archive with *-ds.xml file. Use the DefaultDS, just rename it to DefaultDS2.
 # Deploy the ESB
 # Try to deploy the *-ds.xml file manually without error
Comment 3 Len DiMaggio 2012-01-09 16:57:14 UTC 
Filip - can you attach a server.log?  What is the exact error?  Thx!
Comment 4 Filip Nguyen 2012-01-10 09:02:02 UTC 
I will attach the server log, but there is no error. The datasource just isn't deployed as if it was not detected at all.
Comment 5 Filip Nguyen 2012-01-10 09:54:02 UTC 
Link: Added: This issue is related to JBQA-5561
Comment 6 Filip Nguyen 2012-01-10 10:10:03 UTC 
Server log produced by the reproducer. There is in fact an error in the log, but just because I added a dependency on the datasource. If there wasn't the dependency there would be no error.
Comment 7 Filip Nguyen 2012-01-10 10:10:03 UTC 
Attachment: Added: server.log
Comment 8 Kevin Conner 2012-01-10 14:56:37 UTC 
This sounds like SOA-1606
Comment 9 Kevin Conner 2012-01-10 15:01:35 UTC 
IIRC the issue arises when you have a single -service.xml included in the archive, the workaround is to add a dummy service.xml to force it down a different path.

In this archive it looks like there is only one dummy-service.xml, try removing it and redeploying to see if it addresses the issue.
Comment 10 Filip Nguyen 2012-01-10 15:44:17 UTC 
Thanks Kevin, you are right. Hornetq adds the hornetq-jms.xml while jbm adds jbm-queue-service (doubling *-service.xml) files which made a difference while I was trying this.
Comment 11 Filip Nguyen 2012-01-10 15:45:26 UTC 
SOA-1606