I'm migrating from jboss 6 to 7 , I've followed the steps indicated by the redhat people on their page, I've also used windup as a tool to see conflicts in my application that can occur when going from one version of jboss to the other.
Apparently everything compiles well, however when I lift the jboss 7 I get the following error:
13:55:39,415 ERROR [Proyectik] (ServerService Thread Pool -- 70) : javax.naming.NameNotFoundException: java:app/sistema-hospitalario-app/DataServiceImpl
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) [wildfly-naming-7.0.0.GA-redhat-2.jar:7.0.0.GA-redhat-2]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) [wildfly-naming-7.0.0.GA-redhat-2.jar:7.0.0.GA-redhat-2]
at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) [wildfly-naming-7.0.0.GA-redhat-2.jar:7.0.0.GA-redhat-2]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) [wildfly-naming-7.0.0.GA-redhat-2.jar:7.0.0.GA-redhat-2]
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) [wildfly-naming-7.0.0.GA-redhat-2.jar:7.0.0.GA-redhat-2]
at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0_131]
at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0_131]
at ec.com.hdlv.sishos.app.factory.SistemaHospitalarioFactory.getDataService(SistemaHospitalarioFactory.java:278) [sistema-hospitalario-app-1.0.0.jar:]
at ec.com.hdlv.sishos.app.utiles.CatalogoUtil.getCatalogoByNombreCatalogoPadreByCodigoInterno(CatalogoUtil.java:59) [sistema-hospitalario-app-1.0.0.jar:]
at ec.com.hdlv.sishos.app.enumeracion.EstadioEnum.<init>(EstadioEnum.java:16) [sistema-hospitalario-app-1.0.0.jar:]
at ec.com.hdlv.sishos.app.enumeracion.EstadioEnum.<clinit>(EstadioEnum.java:9) [sistema-hospitalario-app-1.0.0.jar:]
What strikes me is that the name of the EJB java: app / hospitable-system-app / DataServiceImpl if it is listed when raising the jboss a few lines before, and I can even see it from the jndi tree in the administration console:
09:52:55,337 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'DataServiceImpl' in deployment unit 'subdeployment "sistema-hospitalario-app-1.0.0.jar" of deployment "sistema-hospitalario-ear.ear"' are as follows:
java:global/sistema-hospitalario-ear/sistema-hospitalario-app/DataServiceImpl!ec.com.hdlv.utilitario.dao.commons.service.DataService
java:app/sistema-hospitalario-app/DataServiceImpl!ec.com.hdlv.utilitario.dao.commons.service.DataService
java:module/DataServiceImpl!ec.com.hdlv.utilitario.dao.commons.service.DataService
java:global/sistema-hospitalario-ear/sistema-hospitalario-app/DataServiceImpl
java:app/sistema-hospitalario-app/DataServiceImpl
java:module/DataServiceImpl
I do not know why this error occurs, is there something I'm missing in the configuration?
The application to be deployed is a EAR that has the following structure:
EAR
JAR (EJB 3)
WAR (JSF)
Someone who can help me would greatly appreciate it.