Red Hat Bugzilla – Bug 779213
Multiple quickstarts fail on ER3 - DEPLOYMENTS IN ERROR: Deployment "jboss.esb.vfszip...
Last modified: 2012-02-28 13:46:38 EST
Date of First Response: 2009-11-17 11:10:20
Seeing this on multiple Quickstarts:
Caused by Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): DEPLOYMENTS MISSING DEPENDENCIES: Deployment "jboss.esb:service=QuickstartDatabaseInitializer" is missing the following dependencies: Dependency "jboss.jca:name=QuickstartDB,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=QuickstartDB,service=DataSourceBinding' **") DEPLOYMENTS IN ERROR: Deployment "jboss.esb.vfszip:/qa/home/ldimaggi/redhat_svn/qa/tests/quickstarts/tests/output/lib/Quickstart_helloworld_hibernate_action.esb/" is in error due to the following reason(s): java.lang.NullPointerException Deployment "jboss.jca:name=QuickstartDB,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=QuickstartDB,service=DataSourceBinding'
With the helloworld* QS's all the SQL, hibernate, EJB3 quickstarts are failing.
Looks like this is the same issue as https://jira.jboss.org/jira/browse/JBESB-2956
Link: Added: This issue depends JBESB-2956
helloworld_ejb3. helloworld_hibernate_action, helloworld_sql_action, helloworld_tx_sql_action
(among the helloworld* quickstarts at least - haven't run all tests yet)
Daniel has logged an app server issue against this, JBAS-7438, but we can look at working around this if it is not addressed in EAP.
As far as I am aware there are only four quickstarts that may be affected by this, helloworld_hibernate_action, helloworld_sql_action, helloworld_tx_sql_action and jms_transacted.
Link: Added: This issue depends JBAS-7438
BTW what is helloworld_ejb3?
Link: Added: This issue depends JBESB-3070
Link: Added: This issue is duplicated by SOA-1771
Link: Added: This issue is related to JBQA-2762
As far as I can tell the only quickstart that is effected by this is currently helloworld_tx_sql_action. The other quickstarts mentioned about have jms destination definition files and they will work for that reason.
For the helloworld_tx_sql_action is simply creating an empty dummy-service.xml a valid "fix" for this issue?
JBESB-3070 is not intended to "fix" the issue, just to workaround it. As such the dummy service.xml file is good enough.
using dummy.xml workaround
Verified in ER8.