[esb-issues] [JBoss JIRA] Commented: (JBESB-2699) Verify quickstarts business_ruleservice_ruleAgent -> custom_action

[ https://jira.jboss.org/jira/browse/JBESB-2699?page=com.atlassian.jira.plu... ] David Ward commented on JBESB-2699: ----------------------------------- As for the as4 problem with business_service, inside drools-process-task-5.0.1.jar, there is a persistence.xml that specifies an in-memory H2 database, and doesn't specifiy a jta-data-source. What's confusing about this is *why* is this causing a problem during server start-up of a pre-existing as4 installation (where the esb was added via "cd product install ; ant deploy") and the jbossesb-server-4.6 that was generated as part of "cd product ; ant dist". It's not like one has a different persistence.xml than the other. The jars are identical: $ pwd ; ls -l drools-process-task-5.0.1.jar ; sum drools-process-task-5.0.1.jar /home/dward/repos/jbossesb/trunk/product/build/jbossesb-server-4.6/server/default/deploy/jbrules.esb -rw-rw-r--. 1 dward dward 171306 2009-07-07 15:44 drools-process-task-5.0.1.jar 23776 168 $ pwd ; ls -l drools-process-task-5.0.1.jar ; sum drools-process-task-5.0.1.jar /home/dward/pkgs/jboss/AS/jboss-4.2.3.GA/server/default/deploy/jbrules.esb -rw-rw-r--. 1 dward dward 171306 2009-07-07 16:48 drools-process-task-5.0.1.jar 23776 168 I think I need someone who is more familiar with the configuration/deployment of as4+esb+jbrules and as5+esb+ejb3 to look at this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira