JBossDeveloper

"kukeltje" wrote:
I'm no jboss service /.sar specialist, but afaik, it should wait until the datasource is deployed.

At least is does this for JBoss AS 5 in distro/src/main/files/install/src/jboss/config.jboss5/deploy/jbpm/jbpm-service.sar/jbpm-service-jboss-beans.xml

for 4 in distro/src/main/files/install/src/jboss/config.jboss4/deploy/jbpm/jbpm-service.sar/jboss-beans.xml this seams missing. Can you try adding something similar in this file and see if it works then.

Adding a

<depends>JbpmDS</depends>

and adding something like:

[codejboss.jca:service=DataSourceBinding,name=java:/JbpmDS

ouch.... sorry typo

<depends>jboss.jca:service=DataSourceBinding,name=JbpmDS</depends>

Yes, I tried that, and it still has issues. Here's the relevant bean definition. (I tried the mbean name both the way you specified, and the way it shows up in JMX console.) Also, I've tried with and without the dataSource property specified in addition to the dependency.

 <bean name="org.jbpm:service=ProcessEngine"
 class="org.jbpm.integration.spi.JBPMService">
 <property name="serverConfig"><inject bean="org.jbpm:service=ServerConfig"/></property>
<!--
 <property name="dataSource">
 <inject bean="jboss.jca:service=DataSourceBinding,name=JbpmDS" />
 </property>
-->
 <depends>jboss.jca:name=JbpmDS,service=DataSourceBinding</depends>
 </bean>

--- MBeans waiting for other MBeans ---
ObjectName: jboss.beans:service=JBossBeanDeployment,name='jbpm-service.sar#jbpm-service.beans'
 State: FAILED
 Reason: org.jboss.deployment.DeploymentException: Cannot start AbstractKernelDeployment@17b51e8{name=file:/opt/jboss/jboss-4.2.3.GA/server/TDS/deploy/jbpm/jbpm-service.sar/jbpm-service.beans/META-INF/jboss-beans.xml installed=true beans=[AbstractBeanMetaData@13e6577{name=org.jbpm:service=KernelLocator bean=org.jbpm.integration.util.KernelLocator properties=[kernel] constructor=null}, AbstractBeanMetaData@1776d65{name=org.jbpm:service=ProcessEngine bean=org.jbpm.integration.spi.JBPMService properties=[serverConfig] constructor=null demands=[jboss.jca:name=JbpmDS,service=DataSourceBinding]}, AbstractBeanMetaData@1af1934{name=org.jbpm:service=ServerConfig bean=org.jbpm.integration.jboss4.mgmt.ServerConfig properties=[webServiceHost] constructor=null}]}; - nested throwable: (java.lang.IllegalStateException: Incompletely deployed:

*** DEPLOYMENTS MISSING DEPENDENCIES:
org.jbpm:service=ProcessEngine -> org.jbpm:service=ServerConfig{Configured:Installed}, jboss.jca:name=JbpmDS,service=DataSourceBinding{Create:NOT FOUND}, jboss.jca:name=JbpmDS,service=DataSourceBinding{Start:NOT FOUND}
)

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.beans:service=JBossBeanDeployment,name='jbpm-service.sar#jbpm-service.beans'
 State: FAILED
 Reason: org.jboss.deployment.DeploymentException: Cannot start AbstractKernelDeployment@17b51e8{name=file:/opt/jboss/jboss-4.2.3.GA/server/TDS/deploy/jbpm/jbpm-service.sar/jbpm-service.beans/META-INF/jboss-beans.xml installed=true beans=[AbstractBeanMetaData@13e6577{name=org.jbpm:service=KernelLocator bean=org.jbpm.integration.util.KernelLocator properties=[kernel] constructor=null}, AbstractBeanMetaData@1776d65{name=org.jbpm:service=ProcessEngine bean=org.jbpm.integration.spi.JBPMService properties=[serverConfig] constructor=null demands=[jboss.jca:name=JbpmDS,service=DataSourceBinding]}, AbstractBeanMetaData@1af1934{name=org.jbpm:service=ServerConfig bean=org.jbpm.integration.jboss4.mgmt.ServerConfig properties=[webServiceHost] constructor=null}]}; - nested throwable: (java.lang.IllegalStateException: Incompletely deployed:

*** DEPLOYMENTS MISSING DEPENDENCIES:
org.jbpm:service=ProcessEngine -> org.jbpm:service=ServerConfig{Configured:Installed}, jboss.jca:name=JbpmDS,service=DataSourceBinding{Create:NOT FOUND}, jboss.jca:name=JbpmDS,service=DataSourceBinding{Start:NOT FOUND}
)

You have the content of the depends tag in a different order then what I posted. Might make a big difference. Can you give that a try?

oops, sorry, I now only re-read your first line that you tried it in the 'correct' order as well. Same error then?

hmm... might be that the 'waitÃng' on dependent services only takes place when the jboss-service.xml is used and not the jboss-beans.xml. I'll try to look into this a little further.

Putting things in the jboss-service.xml might be an option, but I cannot find a replacement for the property/inject elements.

files of jboss 4 are still in the sources, but it is not supported.

Thanks for the information. I was not aware that JBoss 4.x wasn't supported. Will have to move forward with 5 then.

Regards,

Pat