4 Replies Latest reply on May 11, 2018 10:56 PM by jaikiran pai

    EJB's Appear not be Deploying in Wildfly 12

    Paul Carroll Newbie

      Hello, I recently tried to migrate from Wildfly 11 to 12.  I used the wildfly migration tool to migrate my application from 11 to 12.

       

      When I start Wildfly, it appears that my EJB's are not being deployed.  In Wildfly 11, I would receive some out put in the log similar to the following.

       

      INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-7) WFLYEJB0473: JNDI bindings for session bean named 'MyManager' in deployment unit 'subdeployment "my-ejb.jar" of deployment "myEar.ear"' are as follows:
      
      
        java:global/myapp/my-ejb/MyManager!com.mycompany.mypkg.api.MyManagerRemote
        java:app/my-ejb/MyManager!com.mycompany.mypkg.api.MyManagerRemote
        java:module/MyManager!com.mycompany.mypkg.api.MyManagerRemote
        java:jboss/exported/myapp/my-ejb/MyManager!com.mycompany.mypkg.api.MyManagerRemote
        java:global/myapp/my-ejb/MyManager!com.mycompany.mypkg.api.MyManager
        java:app/my-ejb/MyManager!com.mycompany.mypkg.api.MyManager
        java:module/MyManager!com.mycompany.mypkg.api.MyManager
      

       

      I do not see those messages for each of my EJB's in the Wildfly 12 log.  I also open the Management Console and navigate to the JNDI View and do not find any of the EJB's present in the view.

       

      My application is an exploded EAR in the wildfly-12.0.0.Final\standalone\deployments directory.  I do not see any errors in the log during startup.  Is there a slight difference between Wildfly 11 and 12 where more configuration is required in 12 to deploy the EJB's?

       

      If you need more information, please let me know.

       

      Thanks.