ear deployment fails with JBAS014771: Services with missing/unavailable dependencies
ppgandhi11 Apr 26, 2015 6:54 AMHi, I am unable to deploy the ear file. I do not have any databases involved.
I have following entry in my standalone.xml
:
:
<subsystem xmlns="urn:jboss:domain:remoting:1.1">
<connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/>
<outbound-connections>
<remote-outbound-connection name="dayrhehdsd001" outbound-socket-binding-ref="remote-ejb-dayrhehdsd001" username="ejb" security-realm="ejb-security-realm">
<properties>
<property name="SASL_POLICY_NOANONYMOUS" value="false"/>
<property name="SSL_ENABLED" value="false"/>
</properties>
</remote-outbound-connection>
:
:
<outbound-socket-binding name="remote-ejb-dayrhehdsd001">
<remote-destination host="10.7.79.183" port="4447"/>
</outbound-socket-binding>
In my jboss-ejb-client.xml file, i have:
<jboss-ejb-client xmlns="urn:jboss:ejb-client:1.0">
<client-context>
<ejb-receivers>
<remoting-ejb-receiver outbound-connection-ref="dayrhehdsd001"/>
</ejb-receivers>
</client-context>
</jboss-ejb-client>
__
Interestingly, if i remove this dayrhehdsd001, with a legitimate server name (e.g. nalnxapp154), it works. Also, it works with few additional servers when the entries same as above is added. My goal is to add a new server to the list (dayrhehdsd001). currently the dtu.ear gets deployed successfully with the nalnxapp154, but as soon as I add the entry for additional server in jboss-ejb-client.xml and the standalone.xml for new server, the dtu.ear fails with the error.
What am I missing? are the working server names coming from some other place where I need to adjust the entry for the new server I want to add? I scanned through entire source code and covered all the places for the new server name, still it fails during ear deployment.
below is the failure message. dayrhehdsd001 is my server name.
{"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014771: Services with missing/unavailable dependencies" => [
"jboss.naming.context.java.comp.dtu.dtu.LoginServiceBean.ValidatorFactory is missing [jboss.naming.context.java.comp.dtu.dtu.LoginServiceBean]",
"jboss.naming.context.java.comp.dtu.dtu.JobConfigSessionBean.Validator is missing [jboss.naming.context.java.comp.dtu.dtu.JobConfigSessionBean]",
"jboss.naming.context.java.comp.dtu.dtu.UserProfileSessionBean.Validator is missing [jboss.naming.context.java.comp.dtu.dtu.UserProfileSessionBean]",
"jboss.naming.context.java.comp.dtu.dtu.LoginServiceBean.Validator is missing [jboss.naming.context.java.comp.dtu.dtu.LoginServiceBean]",
"jboss.naming.context.java.comp.dtu.dtu.JobServiceBean.ValidatorFactory is missing [jboss.naming.context.java.comp.dtu.dtu.JobServiceBean]",
"jboss.naming.context.java.comp.dtu.dtu.FileServiceBean.Validator is missing [jboss.naming.context.java.comp.dtu.dtu.FileServiceBean]",
"jboss.naming.context.java.comp.dtu.dtu.JobServiceBean.Validator is missing [jboss.naming.context.java.comp.dtu.dtu.JobServiceBean]",
"jboss.naming.context.java.comp.dtu.dtu.ValidationServiceBean.Validator is missing [jboss.naming.context.java.comp.dtu.dtu.ValidationServiceBean]",
"jboss.naming.context.java.comp.dtu.dtu.FileLayoutSessionBean.Validator is missing [jboss.naming.context.java.comp.dtu.dtu.FileLayoutSessionBean]",
"jboss.ejb3.dd-based-ejb-client-context.\"dtu.ear\" is missing [jboss.remoting.endpoint.subsystem.outbound-connection.dayrhehdsd001]",
"jboss.naming.context.java.comp.dtu.dtu.ValidationServiceBean.ValidatorFactory is missing [jboss.naming.context.java.comp.dtu.dtu.ValidationServiceBean]",
"jboss.naming.context.java.comp.dtu.dtu.FileServiceBean.ValidatorFactory is missing [jboss.naming.context.java.comp.dtu.dtu.FileServiceBean]",
"jboss.naming.context.java.comp.dtu.dtu.UserProfileSessionBean.ValidatorFactory is missing [jboss.naming.context.java.comp.dtu.dtu.UserProfileSessionBean]",
"jboss.naming.context.java.comp.dtu.dtu.FileLayoutSessionBean.ValidatorFactory is missing [jboss.naming.context.java.comp.dtu.dtu.FileLayoutSessionBean]",
"jboss.naming.context.java.comp.dtu.dtu.JobConfigSessionBean.ValidatorFactory is missing [jboss.naming.context.java.comp.dtu.dtu.JobConfigSessionBean]"
]}}}
both the servers nalnxapp154 and dayrhehdsd001 seems to have similar jboss setup. The dtu.ear gets deployed on a different Front End server.
Any help is greatly appreciated. Thanks. Prashant-