[esb-issues] [JBoss JIRA] Commented: (JBESB-2956) helloworld_tx_sql_action quickstart deploy error on AS 5

helloworld_tx_sql_action quickstart deploy error on AS 5 -------------------------------------------------------- Key: JBESB-2956 URL: https://jira.jboss.org/jira/browse/JBESB-2956 Project: JBoss ESB Issue Type: Bug Security Level: Public(Everyone can see) Components: Examples Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.7 When deploying the quickstart the following error is displayed in the console: 15:04:33,294 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.esb.vfszip:/opt/jboss/as/bundles/jboss-5.1.0.GA/server/default/deploy/Quickstart_helloworld_TX_SQL_action.esb/" is missing the following dependencies: Dependency "<UNKNOWN jboss.esb.vfszip:/opt/jboss/as/bundles/jboss-5.1.0.GA/server/default/deploy/Quickstart_helloworld_TX_SQL_action.esb/>" (should be in state "PreInstall", but is actually in state "** UNRESOLVED Demands 'jboss.esb:service=HelloworldTxSqlDatabaseInitializer' **") Deployment "jboss.esb:service=HelloworldTxSqlDatabaseInitializer" is missing the following dependencies: Dependency "jboss.jca:name=HelloworldTxSqlDB,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=HelloworldTxSqlDB,service=DataSourceBinding' **") DEPLOYMENTS IN ERROR: Deployment "<UNKNOWN jboss.esb.vfszip:/opt/jboss/as/bundles/jboss-5.1.0.GA/server/default/deploy/Quickstart_helloworld_TX_SQL_action.esb/>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.esb:service=HelloworldTxSqlDatabaseInitializer' ** Deployment "jboss.jca:name=HelloworldTxSqlDB,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=HelloworldTxSqlDB,service=DataSourceBinding' ** at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993) at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939) at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:369) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:142) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) The problem seems to be timing related. What I mean is that this quickstart is similar other quickstart that deploy a database as a part of the .esb deployment. This works well in the others but I think this is just by chance. If you add a JMS queue definition to this quickstart then it will work just fine. I think that the extra time that it take to deploy the queue gives the db enough time to start and be bound. There might be way to add dependencies to this but I've not been succesful doing so.