Win a copy of Production-Ready Serverless (Operational Best Practices) this week in the Cloud/Virtualization forum!
  • 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
  • Liutauras Vilda
  • Bear Bibeault
  • Jeanne Boyarsky
  • paul wheaton
  • Junilu Lacar
  • Paul Clapham
  • Knute Snortum
Saloon Keepers:
  • Stephan van Hulst
  • Ron McLeod
  • Tim Moores
  • salvin francis
  • Carey Brown
  • Tim Holloway
  • Frits Walraven
  • Vijitha Kumara

Not able to deploy the helloworld ejb in the jboss eap 6.0 server  RSS feed

Posts: 24
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Hi All,

I was trying to deploy my class in jboss eap 6.0 server , but i am getting below error. I have checked the ejb code and xml files but not able to figure out the error .

15:53:50,770 INFO [] (HttpManagementService-threads - 5) JBAS015870: Deploy of deployment "30_FinancialClaims.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"30_FinancialClaims.ear\".\"FinancialClaims.jar\".component.HelloWorldEJB.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"30_FinancialClaims.ear\".\"FinancialClaims.jar\".component.RecatSinglePendingJoiner.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"30_FinancialClaims.ear\".\"FinancialClaims.jar\".component.SntJokerSN.START Missing[JBAS014861: <one or more transitive dependencies>]",
15:53:50,770 INFO [] (MSC service thread 1-1) JBAS011908: Unregister module: Module "deployment.30_FinancialClaims.ear.FinancialClaims.jar:main" from Service Module Loader
15:53:50,770 INFO [] (MSC service thread 1-5) JBAS011908: Unregister module: Module "deployment.30_FinancialClaims.ear:main" from Service Module Loader
15:53:50,830 INFO [] (MSC service thread 1-5) JBAS015877: Stopped deployment FinancialClaims.jar in 65ms
15:53:50,910 INFO [] (MSC service thread 1-7) JBAS015877: Stopped deployment 30_FinancialClaims.ear in 143ms

My ejb classes and configuration XML files are shown below::

:::::::HelloWorldEJBBean .java :::::::::::::::::::::::::

import java.rmi.RemoteException;
import javax.ejb.EJBException;
import javax.ejb.SessionBean;
import javax.ejb.SessionContext;

* Description:This is the Site Key EJB.
* @ejb.bean
* name="HelloWorldEJB"
* type="Stateless"
* local-jndi-name="local/SiteEJB"
* jndi-name="remote/SiteEJB"
* view-type="both"
* transaction-type="Container"
* @ejb.transaction type="Required"
* @ejb.home extends="javax.ejb.EJBHome"
* @ejb.interface extends="javax.ejb.EJBObject"

public class HelloWorldEJBBean implements SessionBean {
private static final long serialVersionUID = 1L;

* @ejb.interface-method view-type="both"
public String SayhelloWorld() throws RemoteException {

return "Hello world, I am an EJB2 session---- test session bean :::::HelloWorldEJBBean";


public void ejbActivate() throws EJBException, RemoteException {}

public void ejbPassivate() throws EJBException, RemoteException {}

public void ejbRemove() throws EJBException, RemoteException {}

public void setSessionContext(SessionContext arg) throws EJBException, RemoteException {}

:::::::ejb-jar.xml is:::::::::::::::::::::::::

<session >
<description><![CDATA[Description:This is the Site Key EJB.]]></description>




<container-transaction >
<method >




Please suggest me whether I have done any mistake in the above files or not.

Sanjeev Kumar

Posts: 194
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Sanjeev,
from what I can see you are deploying an EJB 2.0 to JBoss EAP 6. After a short look at the XML files what is evident is that you are setting jndi name in jboss's XML file which is not allowed any more since JNDI name is determined by the module name/class name/EJB type. See this tutorial about JBoss 7 EJB client. Besides this, unless you have to port legacy code to JBoss 8/WildFly it is definetly better to start using EJB 3.x and not EJB 2.X
Hope it helps
Something about .... going for a swim. With this tiny ad ...
global solutions you can do at home or in your backyard
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!