[ https://jira.jboss.org/jira/browse/JBESB-2699?page=com.atlassian.jira.plu... ] Work on JBESB-2699 started by David Ward. -- 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

[ https://jira.jboss.org/jira/browse/JBESB-2699?page=com.atlassian.jira.plu... ] David Ward commented on JBESB-2699: ----------------------------------- business_ruleservice_ruleAgent, business_ruleservice_stateful, business_rules_service and custom_action run with no problems on as4 and as5. However, wrt business_service: JBoss.org AS 4.2.3.GA Sun JDK 1.5.0_19 Fedora 11 PROBLEM ON 'ant deploy' FROM 'product/install': ... 11:20:14,310 INFO [JmxKernelAbstraction] installing MBean: persistence.units:unitName=org.drools.task with dependencies: 11:20:14,311 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.units:unitName=org.drools.task 11:20:14,319 WARN [ServiceController] Problem starting service persistence.units:unitName=org.drools.task java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled persistence context named: org.drools.task at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:220) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ... 11:20:17,645 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: persistence.units:unitName=org.drools.persistence.jpa State: NOTYETINSTALLED I Depend On: jboss.jca:name=jdbc/testDS1,service=DataSourceBinding ObjectName: persistence.units:unitName=org.drools.task State: FAILED Reason: java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled persistence context named: org.drools.task --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: persistence.units:unitName=org.drools.task State: FAILED Reason: java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled persistence context named: org.drools.task ObjectName: jboss.jca:name=jdbc/testDS1,service=DataSourceBinding State: NOTYETINSTALLED Depends On Me: persistence.units:unitName=org.drools.persistence.jpa ... QUICKSTART STILL RUNS WITHOUT ISSUES. ======================================== JBoss.org AS 5.1.0.GA Sun JDK 1.5.0_19 Fedora 11 PROBLEM ON 'ant deploy' FROM 'product/samples/quickstarts/business_service': ... 11:38:01,095 WARN [HDScanner] Failed to process changes org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): DEPLOYMENTS MISSING DEPENDENCIES: Deployment "jboss.j2ee:ear=Quickstart_business_service.esb,jar=business_service-ejb.jar,name=HelloWorldBean,service=EJB3_endpoint" is missing the following dependencies: Dependency "jboss.j2ee:ear=Quickstart_business_service.esb,jar=business_service-ejb.jar,name=HelloWorldBean,service=EJB3" (should be in state "Configured", but is actually in state "** NOT FOUND Depends on 'jboss.j2ee:ear=Quickstart_business_service.esb,jar=business_service-ejb.jar,name=HelloWorldBean,service=EJB3' **") DEPLOYMENTS IN ERROR: Deployment "jboss.j2ee:ear=Quickstart_business_service.esb,jar=business_service-ejb.jar,name=HelloWorldBean,service=EJB3" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.j2ee:ear=Quickstart_business_service.esb,jar=business_service-ejb.jar,name=HelloWorldBean,service=EJB3' ** at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993) ... QUICKSTART STILL RUNS WITHOUT ISSUES. In summary, deploying the ESB itself into JBoss.org AS 4.2.3.GA has a problem although the quickstart itself still runs, whereas deploying the ESB into JBoss.org AS 5.1.0.GA has no problems, but deploying the quickstart itself has a problem, but again the quickstart itself still runs. -- 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

[ https://jira.jboss.org/jira/browse/JBESB-2699?page=com.atlassian.jira.plu... ] Work on JBESB-2699 started by David Ward. -- 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

[ 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

[ https://jira.jboss.org/jira/browse/JBESB-2699?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2699: ------------------------------------- David, if it is okay with you then I can take these. The AS4 issue sounds familiar and I have vague recollections of investigating something similar with the previous version of drools (the M4 release). IIRC the issue is that the EJB deployer picks up the drools persistence.xml when it is deploying any other EJB jar, it is not specific to our example, and depends on the order of deployment. I should have remembered this last night, apologies. -- 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

[ https://jira.jboss.org/jira/browse/JBESB-2699?page=com.atlassian.jira.plu... ] Kevin Conner reassigned JBESB-2699: ----------------------------------- Assignee: Kevin Conner (was: David Ward) -- 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

[ https://jira.jboss.org/jira/browse/JBESB-2699?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2699: ------------------------------------- It is the same symptom but, unfortunately, the fix for JBESB-2331 is not correct. -- 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

[ https://jira.jboss.org/jira/browse/JBESB-2699?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2699: ------------------------------------- The second issue appears to be a bug in the EJB3EndpointDeployer, looking to see if there is an easy workaround. -- 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

[ https://jira.jboss.org/jira/browse/JBESB-2699?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2699: ------------------------------------- Daniel has suggested a workaround for the second issue, the inclusion of the following jboss-structure.xml. <structure> <context> <path name=""/> <metaDataPath> <path name="META-INF"/> <path name=""/> </metaDataPath> <classpath> <path name=""/> <path name="" suffixes=".jar"/> </classpath> </context> </structure> -- 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