1 Reply Latest reply on Feb 7, 2017 5:28 AM by omid pourhadi

    Facing Issue while Migrating From Jboss7.1 to EAP 6.4

    Vinay Tadvi Newbie

      Hello All,

       

      We have upgraded below mentioned technologies from its lower version , Also we are migrating the server from Jboss 7.1 to EAP 6.4. We are facing issue after the Deployment while launching our application.

       

      Environment Details :

      Oracle JDK 1.6 to 1.8

      Jboss 7.1 to EAP 6.4.0

      Maven Build-2.2.1 to 3.3.9

      Packaging- .ear

      Technologies Used : Seam 2.1.2 to 2.3.1

      Hibernate 3.2 to 4.2

      JSF 1.2 to 2.1

      Webservices not upgraded.

       

      From Seam :

      We are using Jboss-seam-2.3.1.Final.jar

      Seam-ui.jar

      Seam-excel.jar

      Seam-mail.jar

      From the logs we can see seam component is not initialising EnitityManager. We saw that there is an issue with Seam EntityManager in our application. But the same can be seen succefully in Jboss 7.1 logs.

      Please assist us to resolve it.

      Please refer to the Attached Files for reference :

      1)EAP-6.4 logs(We are getting issue for this)

                a) Logs after launching the application(In TRACE mode)

                b) Logs of EAP 6.4 server for deployment(In TRACE mode)

      2)Components.xml

      3)Persistence.xml

      4)Jboss-7.1 logs(Successful logs)

      5)Java Classes(InformationDaoImpl and InformationDaoBase) which are having exceptions in the logs

       

      Please let us know if anything further is needed to review.

       

      Thanks

      Vinay

        • 1. Re: Facing Issue while Migrating From Jboss7.1 to EAP 6.4
          omid pourhadi Apprentice

          it is hard to tell what's wrong but as far as your log shows there something related to jboss el check your lib folder if there is

           

          • el-api-1.0.jar
          • jboss-el-1.0_02.CR6.jar

           

          then check your jboss-deployment-structure.xml

           

          <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1">
            <deployment>
                  <dependencies>
                    <module name="org.apache.log4j" export="true"/>
                    <module name="org.apache.commons.logging" export="true"/>
                    <module name="org.apache.commons.collections" export="true"/>
                    <module name="org.slf4j" export="true"/>
                    <module name="org.hibernate" export="true"/>
                    <module name="org.hibernate.validator" export="true"/>
                    <module name="org.dom4j" export="true" />
                    <module name="javax.faces.api" export="true"/>
                    <module name="com.sun.jsf-impl" export="true"/>          
                  </dependencies>
            </deployment>
          </jboss-deployment-structure>
          
          

           

          I also suggest you try a sample seam 2.3 project with all upgraded technologies that you are using then test your migrated project in this case you can compare.

           

          I'm not sure if EAP/Seam fully support jdk8 and I think it's better to use wildfly.