• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Devaka Cooray
  • Knute Snortum
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Bear Bibeault
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Ron McLeod
  • Piet Souris
  • Frits Walraven
  • Ganesh Patekar
  • Tim Holloway
  • salvin francis

ear deployment fails with JBAS014771: Services with missing/unavailable dependencies  RSS feed

Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi, 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"/>
<remote-outbound-connection name="dayrhehdsd001" outbound-socket-binding-ref="remote-ejb-dayrhehdsd001" username="ejb" security-realm="ejb-security-realm">
<property name="SASL_POLICY_NOANONYMOUS" value="false"/>
<property name="SSL_ENABLED" value="false"/>
<outbound-socket-binding name="remote-ejb-dayrhehdsd001">
<remote-destination host="" port="4447"/>

In my jboss-ejb-client.xml file, i have:
<jboss-ejb-client xmlns="urn:jboss:ejb-client:1.0">
<remoting-ejb-receiver outbound-connection-ref="dayrhehdsd001"/>


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 server dayrhehdsd001 in jboss-ejb-client.xml and the standalone.xml, 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. I have verified that the IP address associated for the new server dayrhehdsd001 is correct, also the port 4747 is open. I do not see anything in particular obvious error.

Security on the FE server where dtu.ear gets deployed must be alright since the .ear deployment works with some servers such as nalnxapp154, nalnxapp110 with their appropriate entries in jboss-ejb-client.xml + standalone.xml.

The remote servers working (nalnxapp154, nalnxapp110) and non working (dayrhehdsd001) are configured ditto. on the remote servers the .jar files in deployment directory gets deployed without any problem.

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-
You showed up just in time for the waffles! And this tiny ad:
how do I do my own kindle-like thing - without amazon
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!