Hide Forgot
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.
Attachment: Added: Quickstart_helloworld.esb
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
Filip - can you attach a server.log? What is the exact error? Thx!
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.
Link: Added: This issue is related to JBQA-5561
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.
Attachment: Added: server.log
This sounds like SOA-1606
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.
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.
SOA-1606