javax.naming.NameNotFoundException while ejb lookup
Question
I am migrating one ejb application from weblogic to jboss. The application is looking for ejb using jndi. I have ejb-jar.xml and jboss.xml into WEB-INF/ as below
jboss.xml
<!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 4.0//EN"
"http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd">
<jboss>
<enterprise-beans>
<session>
<ejb-name>DataAccessEJB</ejb-name>
<jndi-name>HeatMapDataAccessJNDI</jndi-name>
<local-jndi-name>HeatMapDataAccessLocalJNDI</local-jndi-name>
</session>
<session>
<ejb-name>PMSessionFacadeEJB</ejb-name>
<jndi-name>PMSessionFacadeJNDI</jndi-name>
<local-jndi-name>PMSessionFacadeLocalJNDI</local-jndi-name>
</session>
<session>
<ejb-name>RRMSessionFacadeEJB</ejb-name>
<jndi-name>RRMSessionFacadeJNDI</jndi-name>
<local-jndi-name>RRMSessionFacadeLocalJNDI</local-jndi-name>
</session>
<session>
<ejb-name>FIPMSessionFacadeEJB</ejb-name>
<jndi-name>FIPMSessionFacadeJNDI</jndi-name>
<local-jndi-name>FIPMSessionFacadeLocalJNDI</local-jndi-name>
</session>
</enterprise-beans>
</jboss>
ejb-jar.xml
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC
"-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"
"http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<!-- A list of all the session and entity beans packaged within this jar file. -->
<session>
<!-- An arbitrary identifier that's used to match up this description of the bean with the
corresponding entry in the weblogic-ejb-jar.xml file -->
<ejb-name>
DataAccessEJB
</ejb-name>
<!-- The name of the interface implemented by the bean's home object -->
<home>
com.bfm.app.pirptfe.heatmap.ejb.DataAccessHomeInterface
</home>
<!-- The name of the interface implemented by the bean's remote object -->
<remote>
com.bfm.app.pirptfe.heatmap.ejb.DataAccessRemoteInterface
</remote>
<local-home>
com.bfm.app.pirptfe.heatmap.ejb.DataAccessLocalHomeInterface
</local-home>
<local>
com.bfm.app.pirptfe.heatmap.ejb.DataAccessLocalInterface
</local>
<!-- The name of the bean class -->
<ejb-class>
com.bfm.app.pirptfe.heatmap.ejb.DataAccessBean
</ejb-class>
<!-- Is this session bean Stateful or Stateless? -->
<session-type>
Stateless
</session-type>
<!-- If this bean uses any transactions, will these transactions be managed by the Container or
by the Bean itself? -->
<transaction-type>
Container
</transaction-type>
</session>
<session>
<ejb-name>
PMSessionFacadeEJB
</ejb-name>
<home>
com.bfm.app.pirptfe.heatmap.ejb.PMSessionFacadeHome
</home>
<remote>
com.bfm.app.pirptfe.heatmap.ejb.PMSessionFacadeRemote
</remote>
<ejb-class>
com.bfm.app.pirptfe.heatmap.ejb.PMSessionFacadeBean
</ejb-class>
<session-type>
Stateless
</session-type>
<transaction-type>
Container
</transaction-type>
</session>
<session>
<ejb-name>
RRMSessionFacadeEJB
</ejb-name>
<home>
com.bfm.app.pirptfe.heatmap.ejb.RRMSessionFacadeHome
</home>
<remote>
com.bfm.app.pirptfe.heatmap.ejb.RRMSessionFacadeRemote
</remote>
<ejb-class>
com.bfm.app.pirptfe.heatmap.ejb.RRMSessionFacadeBean
</ejb-class>
<session-type>
Stateless
</session-type>
<transaction-type>
Container
</transaction-type>
</session>
<session>
<ejb-name>
FIPMSessionFacadeEJB
</ejb-name>
<home>
com.bfm.app.pirptfe.heatmap.ejb.FIPMSessionFacadeHome
</home>
<remote>
com.bfm.app.pirptfe.heatmap.ejb.FIPMSessionFacadeRemote
</remote>
<ejb-class>
com.bfm.app.pirptfe.heatmap.ejb.FIPMSessionFacadeBean
</ejb-class>
<session-type>
Stateless
</session-type>
<transaction-type>
Container
</transaction-type>
</session>
</enterprise-beans>
</ejb-jar>
When i run my application it load. log shown below
14:08:16,990 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named FIPMSessionFacadeEJB in deployment unit deployment "pirptfe.war" are as follows:
java:global/pirptfe/FIPMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.FIPMSessionFacadeRemote
java:app/pirptfe/FIPMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.FIPMSessionFacadeRemote
java:module/FIPMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.FIPMSessionFacadeRemote
java:jboss/exported/pirptfe/FIPMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.FIPMSessionFacadeRemote
java:global/pirptfe/FIPMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.FIPMSessionFacadeHome
java:app/pirptfe/FIPMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.FIPMSessionFacadeHome
java:module/FIPMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.FIPMSessionFacadeHome
java:jboss/exported/pirptfe/FIPMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.FIPMSessionFacadeHome
The JNDI name used to lookup a service is as below in my code
// The JNDI Names used to lookup a service
private static final String PMSESSIONFACADEEJB_JNDIHOME =
"PMSessionFacadeJNDI";
private static final String RRMSESSIONFACADEEJB_JNDIHOME =
"RRMSessionFacadeJNDI";
private static final String FIPMSESSIONFACADEEJB_JNDIHOME =
"FIPMSessionFacadeJNDI";
When code is trying to lookup for ejb in context using below code, it give exception
serviceName is JNDI name in below code
public EJBHome getEJBHome(int parServiceId)
throws FrontServiceLocatorException {
// Trying to find the JNDI Name for the reqested service
String serviceName = getServiceName(parServiceId);
EJBHome ejbHome = null;
try {
// Checking to see if I can find the EJBHome interface in the cache
if (ejbHomeCashe_.containsKey(serviceName)) {
ejbHome = (EJBHome)ejbHomeCashe_.get(serviceName);
return ejbHome;
} else {
// I could not find the home interface in the cache, look it up
// and then cache it
Context ctx = new InitialContext();
Object jndiRef = ctx.lookup(serviceName);
Object portableObj = PortableRemoteObject.narrow(jndiRef,
getEJBHomeRef(
parServiceId));
ejbHome = (EJBHome)portableObj;
ejbHomeCashe_.put(serviceName, ejbHome);
return ejbHome;
}
} catch (NamingException e) {
throw new FrontServiceLocatorException("Naming exception error in FrontServiceLocator.getEJBHome()",
e);
}
catch (Exception e) {
throw new FrontServiceLocatorException("General exception in FrontServiceLocator.getEJBHome()",
e);
}
}
Exception :
18:40:12,376 ERROR [stderr] (http-localhost-127.0.0.1-8080-1) javax.naming.NameNotFoundException: RRMSessionFacadeJNDI -- service jboss.naming.context.java.RRMSessionFacadeJNDI
18:40:12,376 ERROR [stderr] (http-localhost-127.0.0.1-8080-1) at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97)
18:40:12,392 ERROR [stderr] (http-localhost-127.0.0.1-8080-1) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178)
18:40:12,392 ERROR [stderr] (http-localhost-127.0.0.1-8080-1) at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113)
18:40:12,392 ERROR [stderr] (http-localhost-127.0.0.1-8080-1) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214)
18:40:12,407 ERROR [stderr] (http-localhost-127.0.0.1-8080-1) at javax.naming.InitialContext.lookup(InitialContext.java:411)
18:40:12,407 ERROR [stderr] (http-localhost-127.0.0.1-8080-1) at com.bfm.app.pirptfe.heatmap.web.FrontServiceLocator.getEJBHome(FrontServiceLocator.java:191)
18:40:12,407 ERROR [stderr] (http-localhost-127.0.0.1-8080-1) at com.bfm.app.pirptfe.heatmap.web.CommonalityRRM.process(CommonalityRRM.java:77)
18:40:12,423 ERROR [stderr] (http-localhost-127.0.0.1-8080-1) at com.bfm.app.pirptfe.heatmap.web.CommonalityRRM.doPost(CommonalityRRM.java:54)
18:40:12,423 ERROR [stderr] (http-localhost-127.0.0.1-8080-1) at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
Could someone help me to get it solve.
1 answers
solution1
0 2015-07-29 12:14:05
My problem is not yet resolved but i bit got the answer what i am doing wrong here.
- We have to rename the file with jboss-ejb3.xml instead of jboss.xml
- We can override our ejb-jar.xml using jboss-ejb3.xml
jboss-ejb3.xml
<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:s="urn:security" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd http://java.sun.com/xml/ns/javaee" version="3.1" impl-version="2.0"> <enterprise-beans> <session> <ejb-name>DataAccessEJB</ejb-name> <resource-ref> <res-ref-name>java:app/pirptfe/HeatMapDataAccessJNDI</res-ref-name> <lookup-name>HeatMapDataAccessJNDI</lookup-name> </resource-ref> </session> <session> <ejb-name>PMSessionFacadeEJB</ejb-name> <resource-ref> <res-ref-name>java:app/pirptfe/PMSessionFacadeJNDI</res-ref-name> <lookup-name>PMSessionFacadeJNDI</lookup-name> </resource-ref> </session> <session> <ejb-name>RRMSessionFacadeEJB</ejb-name> <resource-ref> <res-ref-name>java:app/pirptfe/RRMSessionFacadeJNDI</res-ref-name> <lookup-name>RRMSessionFacadeJNDI</lookup-name> </resource-ref> </session> <session> <ejb-name>FIPMSessionFacadeEJB</ejb-name> <resource-ref> <res-ref-name>java:app/pirptfe/FIPMSessionFacadeJNDI</res-ref-name> <lookup-name>FIPMSessionFacadeJNDI</lookup-name> </resource-ref> </session> </enterprise-beans> </jboss:ejb-jar>
Now i am getting below error message
17:32:34,629 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named PMSessionFacadeEJB in deployment unit deployment "pirptfe.war" are as follows: java:global/pirptfe/PMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.PMSessionFacadeHome java:app/pirptfe/PMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.PMSessionFacadeHome java:module/PMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.PMSessionFacadeHome java:jboss/exported/pirptfe/PMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.PMSessionFacadeHome java:global/pirptfe/PMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.PMSessionFacadeRemote java:app/pirptfe/PMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.PMSessionFacadeRemote java:module/PMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.PMSessionFacadeRemote java:jboss/exported/pirptfe/PMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.PMSessionFacadeRemote 17:32:35,787 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "pirptfe.war" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.app.pirptfe.pirptfe.FIPMSessionFacadeJNDIjboss.naming.context.java.module.pirptfe.pirptfe.env.FIPMSessionFacadeJNDIMissing[jboss.naming.context.java.app.pirptfe.pirptfe.FIPMSessionFacadeJNDIjboss.naming.context.java.module.pirptfe.pirptfe.env.FIPMSessionFacadeJNDI]","jboss.naming.context.java.app.pirptfe.pirptfe.PMSessionFacadeJNDIjboss.naming.context.java.module.pirptfe.pirptfe.env.PMSessionFacadeJNDIMissing[jboss.naming.context.java.app.pirptfe.pirptfe.PMSessionFacadeJNDIjboss.naming.context.java.module.pirptfe.pirptfe.env.PMSessionFacadeJNDI]","jboss.naming.context.java.app.pirptfe.pirptfe.RRMSessionFacadeJNDIjboss.naming.context.java.module.pirptfe.pirptfe.env.RRMSessionFacadeJNDIMissing[jboss.naming.context.java.app.pirptfe.pirptfe.RRMSessionFacadeJNDIjboss.naming.context.java.module.pirptfe.pirptfe.env.RRMSessionFacadeJNDI]","jboss.naming.context.java.app.pirptfe.pirptfe.HeatMapDataAccessJNDIjboss.naming.context.java.module.pirptfe.pirptfe.env.HeatMapDataAccessJNDIMissing[jboss.naming.context.java.app.pirptfe.pirptfe.HeatMapDataAccessJNDIjboss.naming.context.java.module.pirptfe.pirptfe.env.HeatMapDataAccessJNDI]"]} 17:32:37,552 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment pirptfe.war in 1773ms 17:32:37,553 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.naming.context.java.module.pirptfe.pirptfe.env.FIPMSessionFacadeJNDI (missing) dependents: [service jboss.naming.context.java.app.pirptfe.pirptfe.FIPMSessionFacadeJNDI] service jboss.naming.context.java.module.pirptfe.pirptfe.env.HeatMapDataAccessJNDI (missing) dependents: [service jboss.naming.context.java.app.pirptfe.pirptfe.HeatMapDataAccessJNDI] service jboss.naming.context.java.module.pirptfe.pirptfe.env.PMSessionFacadeJNDI (missing) dependents: [service jboss.naming.context.java.app.pirptfe.pirptfe.PMSessionFacadeJNDI] service jboss.naming.context.java.module.pirptfe.pirptfe.env.RRMSessionFacadeJNDI (missing) dependents: [service jboss.naming.context.java.app.pirptfe.pirptfe.RRMSessionFacadeJNDI] 17:32:37,584 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.app.pirptfe.pirptfe.FIPMSessionFacadeJNDIjboss.naming.context.java.module.pirptfe.pirptfe.env.FIPMSessionFacadeJNDIMissing[jboss.naming.context.java.app.pirptfe.pirptfe.FIPMSessionFacadeJNDIjboss.naming.context.java.module.pirptfe.pirptfe.env.FIPMSessionFacadeJNDI]","jboss.naming.context.java.app.pirptfe.pirptfe.PMSessionFacadeJNDIjboss.naming.context.java.module.pirptfe.pirptfe.env.PMSessionFacadeJNDIMissing[jboss.naming.context.java.app.pirptfe.pirptfe.PMSessionFacadeJNDIjboss.naming.context.java.module.pirptfe.pirptfe.env.PMSessionFacadeJNDI]","jboss.naming.context.java.app.pirptfe.pirptfe.RRMSessionFacadeJNDIjboss.naming.context.java.module.pirptfe.pirptfe.env.RRMSessionFacadeJNDIMissing[jboss.naming.context.java.app.pirptfe.pirptfe.RRMSessionFacadeJNDIjboss.naming.context.java.module.pirptfe.pirptfe.env.RRMSessionFacadeJNDI]","jboss.naming.context.java.app.pirptfe.pirptfe.HeatMapDataAccessJNDIjboss.naming.context.java.module.pirptfe.pirptfe.env.HeatMapDataAccessJNDIMissing[jboss.naming.context.java.app.pirptfe.pirptfe.HeatMapDataAccessJNDIjboss.naming.context.java.module.pirptfe.pirptfe.env.HeatMapDataAccessJNDI]"]}}}
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.
Related Question
javax.naming.NameNotFoundException:while trying to lookup
javax.naming.NameNotFoundException EJB HelloWorld on WildFly
javax.naming.NameNotFoundException | JNDI lookup
javax.naming.NameNotFoundException on Context lookup Java
javax.naming.NameNotFoundException
javax.naming.NameNotFoundException while debugging in Eclipse
javax.naming.NameNotFoundException after restart windows in EJB
lookup fail “Root exception is javax.naming.NameNotFoundException”
javax.naming.NameNotFoundException: jndiDataSource
javax.naming.NameNotFoundException: jms
Related Tags