1 2 Previous Next 22 Replies Latest reply on Mar 9, 2012 10:30 AM by thinksteep thinksteep Branched to a new discussion.

    Jboss4.2.3 to Jboss7.1 migration issue

    thinksteep thinksteep Novice

      Hi All,

       

      We are trying to upgrade to jboss7.1 from jboss4.2.3 as soon as we deployed EAR it is failing. Below is stack trace. NOTE: I did replace names with yyy, just to hide our organization name.

       

      Our EAR deployment works fine in 4.2.3.

       

      EAR structure is:

       

      NameYYYAdmin

      -----yyybusiness.jar

      -----yyyservices.jar

      -----yyyadmin.war

      -----lib

      -----META-INF

             -----application.xml

             -----MANIFEST (Only organization related info, no classpath)

       

       

      DcsFileUploadServlet.java is servlet developed by us and is insidd yyyadmin.war lib with name yyyweb.jar

       

       

       

      17:09:13,729 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "yyybusiness.jar"

      17:09:13,729 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "yyyservices.jar"

      17:09:13,729 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "yyyadmin.war"

      17:09:13,827 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.GlassFishInjectionProvider:com.sun.enterprise.InjectionManager' for service type 'com.sun.faces.spi.injectionprovider'

      17:09:13,829 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Tomcat6InjectionProvider:org.apache.catalina.util.DefaultAnnotationProcessor' for service type 'com.sun.faces.spi.injectionprovider'

      17:09:13,830 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Jetty6InjectionProvider:org.mortbay.jetty.plus.annotation.InjectionCollection' for service type 'com.sun.faces.spi.injectionprovider'

      17:09:13,848 WARN  [org.jboss.as.ee] (MSC service thread 1-8) JBAS011071: Invalid signature for method decode annotated with javax.annotation.PostConstruct on class org.ajax4jsf.context.AjaxContextImpl, signature must be 'void methodName(InvocationContext ctx)'

      17:09:14,301 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named StatefulTestBean in deployment unit subdeployment "yyyservices.jar" of deployment "NameYYYAdmin.ear" are as follows:

       

          java:global/NameYYYAdmin/yyyservices/StatefulTestBean!com.yyy.stateful.ejb.test.StatefulTestBean

          java:app/yyyservices/StatefulTestBean!com.name.stateful.ejb.test.StatefulTestBean

          java:module/StatefulTestBean!com.name.stateful.ejb.test.StatefulTestBean

          java:global/NameYYYAdmin/yyyservices/StatefulTestBean

          java:app/yyyservices/StatefulTestBean

          java:module/StatefulTestBean

       

      17:09:14,307 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named AgentsActionsBean in deployment unit subdeployment "yyyservices.jar" of deployment "NameYYYAdmin.ear" are as follows:

       

       

      17:09:14,448 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named ConfigBean in deployment unit subdeployment "yyybusiness.jar" of deployment "NameYYYAdmin.ear" are as follows:

       

          java:global/NameYYYAdmin/yyybusiness/ConfigBean!com.name.yyy.beans.admin.config.ConfigLocal

          java:app/yyybusiness/ConfigBean!com.name.yyy.beans.admin.config.ConfigLocal

          java:module/ConfigBean!com.name.yyy.beans.admin.config.ConfigLocal

          java:global/NameYYYAdmin/yyybusiness/ConfigBean!com.name.yyy.beans.admin.config.ConfigRemote

          java:app/yyybusiness/ConfigBean!com.name.yyy.beans.admin.config.ConfigRemote

          java:module/ConfigBean!com.name.yyy.beans.admin.config.ConfigRemote

          java:jboss/exported/NameYYYAdmin/yyybusiness/ConfigBean!com.name.yyy.beans.admin.config.ConfigRemote

      ........................

      ......................

       

      17:09:14,486 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.deployment.subunit."NameYYY.ear"."yyyadmin.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."NameYYYAdmin.ear"."yyyadmin.war".POST_MODULE: Failed to process phase POST_MODULE of subdeployment "yyyadmin.war" of deployment "NameYYYAdmin.ear"

          at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_16]

          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_16]

          at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_16]

      Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011093: Could not load component class com.name.yyy.webapp.servlets.DcsFileUploadServlet

          at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:113)

          at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:54)

          at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]

          ... 5 more

      Caused by: java.lang.ClassNotFoundException: com.name.yyy.webapp.servlets.DcsFileUploadServlet from [Module "deployment.NameYYYAdmin.ear.yyyadmin.war:main" from Service Module Loader]

          at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.1.GA]

          at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA]

          at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA]

          at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA]

          at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA]

          at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:111)

          ... 7 more

       

      17:09:14,491 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named FileBean in deployment unit subdeployment "yyybusiness.jar" of deployment "NameYYYAdmin.ear" are as follows:

       

          java:global/NameYYYAdmin/yyybusiness/FileBean!com.name.yyy.beans.admin.file.FileRemote

          java:app/yyybusiness/FileBean!com.name.yyy.beans.admin.file.FileRemote

          java:module/FileBean!com.name.yyy.beans.admin.file.FileRemote

          java:jboss/exported/NameYYYAdmin/yyybusiness/FileBean!com.name.yy.beans.admin.file.FileRemote

          java:global/NameYYYAdmin/yyybusiness/FileBean!com.name.yyy.beans.admin.file.FileLocal

          java:app/yyybusiness/FileBean!com.name.yyy.beans.admin.file.FileLocal

          java:module/FileBean!com.name.yyy.beans.admin.file.FileLocal

         

          ...............

          ..............

         

          17:09:14,660 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named AlertActionBean in deployment unit subdeployment "yyybusiness.jar" of deployment "NameYYYAdmin.ear" are as follows:

       

       

      17:09:14,881 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "NameYYYAdmin.ear" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"NameYYYAdmin.ear\".\"yyyadmin.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"NameYYYAdmin.ear\".\"yyyadmin.war\".POST_MODULE: Failed to process phase POST_MODULE of subdeployment \"yyyadmin.war\" of deployment \"NameYYYAdmin.ear\""},"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.comp.NameYYYAdmin.yyybusiness.RolesBean.Validatorjboss.naming.context.java.comp.NameYYYAdmin.yyybusiness.RolesBeanMissing[jboss.naming.context.java.comp.NameYYYAdmin.yyybusiness.RolesBean.Validatorjboss.naming.context.java.comp.NameYYYAdmin.yyybusiness.RolesBean]",

      "jboss.naming.context.java.comp.NameYYYAdmin.yyybusiness.RolesBean.ValidatorFactoryjboss.naming.context.java.comp.NameYYYAdmin.yyybusiness.RolesBeanMissing[jboss.naming.context.java.comp.NameYYYAdmin.yyybusiness.RolesBean.ValidatorFactoryjboss.naming.context.java.comp.NameYYYAdmin.yyybusiness.RolesBean]"

       

       

      All these EJB beans are in yyyservices.jar.

       

      Could someone help me with how can I resolve and proceed further?

       

      Thanks for your time.

        • 1. Re: Jboss4.2.3 to Jboss7.1 migration issue
          jaikiran pai Master

          DcsFileUploadServlet.java is servlet developed by us and is insidd yyyadmin.war lib with name yyyweb.jar

          You mean yyyadmin.war/lib? That's not a valid location. It should be in yyyadmin.war/WEB-INF/lib.

          • 2. Re: Jboss4.2.3 to Jboss7.1 migration issue
            thinksteep thinksteep Novice

            Hi Jaikiran,

            Thanks for quick reply. It is inside yyyadmin.war/WEB-INF/lib.

            • 3. Re: Jboss4.2.3 to Jboss7.1 migration issue
              Prasad Deshpande Expert

              Can you please paste you application.xml file? Also what kind of module yyybusiness.jar is?

              • 4. Re: Jboss4.2.3 to Jboss7.1 migration issue
                thinksteep thinksteep Novice

                Here is original one:

                <?xml version="1.0" encoding="UTF-8"?>

                <!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"

                   "http://java.sun.com/dtd/application_1_3.dtd">

                <application>

                    <display-name>yyy</display-name>

                 

                    <module>

                        <web>

                            <web-uri>yyyadmin.war</web-uri>

                            <context-root>/yyy</context-root>

                        </web>

                    </module>

                    <module>

                        <ejb>yyybusiness.jar</ejb>       

                    </module>

                    <module>

                        <ejb>yyyservices.jar</ejb>       

                    </module>

                    <library-directory>lib</library-directory>

                 

                </application>

                 

                 

                I tried it changing like below too. Same error.

                 

                <application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

                             version="6"

                             xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd">

                     <application-name>yyyy</application-name>

                     <initialize-in-order>true</initialize-in-order>

                     <module>

                        <ejb>yyybusiness.jar</ejb>       

                    </module>

                    <module>

                        <ejb>yyyservices.jar</ejb>       

                    </module>

                    <library-directory>lib</library-directory>

                    <module>

                        <web>

                            <web-uri>yyydmin.war</web-uri>

                            <context-root>/yyy</context-root>

                        </web>

                    </module>

                 

                 

                </application>

                 

                yyybusiness.jar is ejb/hibernate module.

                 

                Thanks for your time and help.

                • 5. Re: Jboss4.2.3 to Jboss7.1 migration issue
                  Prasad Deshpande Expert

                      <module>

                          <ejb>yyyservices.jar</ejb>       

                      </module>

                  Yes, you should upgrade application.xml to have EE5/6 std.. Is that really an EJB module? I mean does it really contains ejb's? Also, could you please attach your server.logs to this?

                  • 6. Re: Jboss4.2.3 to Jboss7.1 migration issue
                    thinksteep thinksteep Novice

                    Hi Prasad,

                     

                    Yes it is indeed ejb module. I am in process of getting server logs for new application.xml, give me 5 minutes.

                     

                    Thanks for your time.

                    • 7. Re: Jboss4.2.3 to Jboss7.1 migration issue
                      thinksteep thinksteep Novice

                      Hi Prasad,

                       

                      More info about yyyservice.jar is, it has only two classes, one is stateless ejb defined as webserivce and another class is RMI interface. This structure working fine in 4.2.3a

                       

                      Thank you,

                      • 8. Re: Jboss4.2.3 to Jboss7.1 migration issue
                        Prasad Deshpande Expert

                        Not sure, but it's talkling about missing .yyybusiness.RolesBean.Validator & yyybusiness.RolesBean.ValidatorFactory. Is RolesBean using Hibernate JPA? If yes, I think by default validator is turned on in Hibernate 4.0 onwards & that is what it could be looking for.. could you please check?

                        • 9. Re: Jboss4.2.3 to Jboss7.1 migration issue
                          thinksteep thinksteep Novice

                          Here is server.log with new application.xml

                           

                          12:34:31,239 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry serializer.jar in "/C:/jboss-as-7.1.0.Final/bin/content/NameyyyAdmin.ear/lib/xalan-2.7.0.jar"  does not point to a valid jar for a Class-Path reference.

                          12:34:31,241 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry activation.jar in "/C:/jboss-as-7.1.0.Final/bin/content/NameyyyAdmin.ear/lib/mail-1.4.jar"  does not point to a valid jar for a Class-Path reference.

                          12:34:31,244 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jaxb-xjc.jar in "/C:/jboss-as-7.1.0.Final/bin/content/NameyyyAdmin.ear/lib/jaxws-tools.jar"  does not point to a valid jar for a Class-Path reference.

                          12:34:31,246 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry relaxngDatatype.jar in "/C:/jboss-as-7.1.0.Final/bin/content/NameyyyAdmin.ear/lib/jaxws-tools.jar"  does not point to a valid jar for a Class-Path reference.

                          12:34:31,252 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "yyyservices.jar"

                          12:34:31,252 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "yyybusiness.jar"

                          12:34:31,252 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "yyyadmin.war"

                          12:34:31,352 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.GlassFishInjectionProvider:com.sun.enterprise.InjectionManager' for service type 'com.sun.faces.spi.injectionprovider'

                          12:34:31,355 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Tomcat6InjectionProvider:org.apache.catalina.util.DefaultAnnotationProcessor' for service type 'com.sun.faces.spi.injectionprovider'

                          12:34:31,357 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Jetty6InjectionProvider:org.mortbay.jetty.plus.annotation.InjectionCollection' for service type 'com.sun.faces.spi.injectionprovider'

                          12:34:31,378 WARN  [org.jboss.as.ee] (MSC service thread 1-5) JBAS011071: Invalid signature for method decode annotated with javax.annotation.PostConstruct on class org.ajax4jsf.context.AjaxContextImpl, signature must be 'void methodName(InvocationContext ctx)'

                          12:34:31,793 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named StatefulTestBean in deployment unit subdeployment "yyyservices.jar" of deployment "NameyyyAdmin.ear" are as follows:

                           

                              java:global/application name/yyyservices/StatefulTestBean!com.name.stateful.ejb.test.StatefulTestBean

                              java:app/yyyservices/StatefulTestBean!com.name.stateful.ejb.test.StatefulTestBean

                              java:module/StatefulTestBean!com.name.stateful.ejb.test.StatefulTestBean

                              java:global/application name/yyyservices/StatefulTestBean

                              java:app/yyyservices/StatefulTestBean

                              java:module/StatefulTestBean

                           

                          12:34:31,802 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named AgentsActionsBean in deployment unit subdeployment "yyyservices.jar" of deployment "NameyyyAdmin.ear" are as follows:

                           

                           

                          12:34:31,970 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named ConfigBean in deployment unit subdeployment "yyybusiness.jar" of deployment "NameyyyAdmin.ear" are as follows:

                           

                              java:global/application name/yyybusiness/ConfigBean!com.name.yyy.beans.admin.config.ConfigLocal

                              java:app/yyybusiness/ConfigBean!com.name.yyy.beans.admin.config.ConfigLocal

                              java:module/ConfigBean!com.name.yyy.beans.admin.config.ConfigLocal

                              java:global/application name/yyybusiness/ConfigBean!com.name.yyy.beans.admin.config.ConfigRemote

                              java:app/yyybusiness/ConfigBean!com.name.yyy.beans.admin.config.ConfigRemote

                              java:module/ConfigBean!com.name.yyy.beans.admin.config.ConfigRemote

                              java:jboss/exported/application name/yyybusiness/ConfigBean!com.name.yyy.beans.admin.config.ConfigRemote

                           

                          12:34:31,982 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named FirewallBean in deployment unit subdeployment "yyybusiness.jar" of deployment "NameyyyAdmin.ear" are as follows:

                           

                              java:global/application name/yyybusiness/FirewallBean!com.name.yyy.beans.admin.firewall.FirewallLocal

                              java:app/yyybusiness/FirewallBean!com.name.yyy.beans.admin.firewall.FirewallLocal

                              java:module/FirewallBean!com.name.yyy.beans.admin.firewall.FirewallLocal

                              java:global/application name/yyybusiness/FirewallBean!com.name.yyy.beans.admin.firewall.FirewallRemote

                              java:app/yyybusiness/FirewallBean!com.name.yyy.beans.admin.firewall.FirewallRemote

                              java:module/FirewallBean!com.name.yyy.beans.admin.firewall.FirewallRemote

                              java:jboss/exported/application name/yyybusiness/FirewallBean!com.name.yyy.beans.admin.firewall.FirewallRemote

                             

                              ...............

                             

                              ................

                             

                             

                              12:34:31,997 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.subunit."NameyyyAdmin.ear"."yyyAdmin.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."NameyyyAdmin.ear"."yyyAdmin.war".POST_MODULE: Failed to process phase POST_MODULE of subdeployment "yyyAdmin.war" of deployment "NameyyyAdmin.ear"

                              at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]

                              at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

                              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

                              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_16]

                              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_16]

                              at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_16]

                          Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011093: Could not load component class com.name.yyy.webapp.servlets.DcsFileUploadServlet

                              at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:113)

                              at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:54)

                              at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]

                              ... 5 more

                          Caused by: java.lang.ClassNotFoundException: com.name.yyy.webapp.servlets.DcsFileUploadServlet from [Module "deployment.NameyyyAdmin.ear.yyyAdmin.war:main" from Service Module Loader]

                              at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)

                              at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)

                              at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)

                              at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)

                              at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)

                              at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:111)

                              ... 7 more

                           

                          12:34:32,005 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named HomeBean in deployment unit subdeployment "yyybusiness.jar" of deployment "NameyyyAdmin.ear" are as follows:

                           

                              java:global/application name/yyybusiness/HomeBean!com.name.yyy.beans.admin.home.HomeLocal

                              java:app/yyybusiness/HomeBean!com.name.yyy.beans.admin.home.HomeLocal

                              java:module/HomeBean!com.name.yyy.beans.admin.home.HomeLocal

                              java:global/application name/yyybusiness/HomeBean!com.name.yyy.beans.admin.home.HomeRemote

                              java:app/yyybusiness/HomeBean!com.name.yyy.beans.admin.home.HomeRemote

                              java:module/HomeBean!com.name.yyy.beans.admin.home.HomeRemote

                              java:jboss/exported/application name/yyybusiness/HomeBean!com.name.yyy.beans.admin.home.HomeRemote

                           

                          12:34:32,026 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named ThresholdBean in deployment unit subdeployment "yyybusiness.jar" of deployment "NameyyyAdmin.ear" are as follows:

                           

                              java:global/application name/yyybusiness/ThresholdBean!com.name.yyy.beans.admin.threshold.ThresholdRemote

                              java:app/yyybusiness/ThresholdBean!com.name.yyy.beans.admin.threshold.ThresholdRemote

                              java:module/ThresholdBean!com.name.yyy.beans.admin.threshold.ThresholdRemote

                              java:jboss/exported/application name/yyybusiness/ThresholdBean!com.name.yyy.beans.admin.threshold.ThresholdRemote

                              java:global/application name/yyybusiness/ThresholdBean!com.name.yyy.beans.admin.threshold.ThresholdLocal

                              java:app/yyybusiness/ThresholdBean!com.name.yyy.beans.admin.threshold.ThresholdLocal

                              java:module/ThresholdBean!com.name.yyy.beans.admin.threshold.ThresholdLocal

                             

                              ..........

                              ............

                             

                              12:34:32,193 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named PasswordsBean in deployment unit subdeployment "yyybusiness.jar" of deployment "NameyyyAdmin.ear" are as follows:

                           

                              java:global/application name/yyybusiness/PasswordsBean!com.name.yyy.beans.admin.user.PasswordsLocal

                              java:app/yyybusiness/PasswordsBean!com.name.yyy.beans.admin.user.PasswordsLocal

                              java:module/PasswordsBean!com.name.yyy.beans.admin.user.PasswordsLocal

                              java:global/application name/yyybusiness/PasswordsBean!com.name.yyy.beans.admin.user.PasswordsRemote

                              java:app/yyybusiness/PasswordsBean!com.name.yyy.beans.admin.user.PasswordsRemote

                              java:module/PasswordsBean!com.name.yyy.beans.admin.user.PasswordsRemote

                              java:jboss/exported/application name/yyybusiness/PasswordsBean!com.name.yyy.beans.admin.user.PasswordsRemote

                           

                          12:34:32,199 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named AlertActionBean in deployment unit subdeployment "yyybusiness.jar" of deployment "NameyyyAdmin.ear" are as follows:

                           

                           

                          12:34:32,430 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "NameyyyAdmin.ear" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"NameyyyAdmin.ear\".\"yyyAdmin.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"NameyyyAdmin.ear\".\"yyyAdmin.war\".POST_MODULE: Failed to process phase POST_MODULE of subdeployment \"yyyAdmin.war\" of deployment \"NameyyyAdmin.ear\""},"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.comp.\"application name\".yyybusiness.ViewBean.ValidatorFactoryjboss.naming.context.java.comp.\"application name\".yyybusiness.ViewBeanMissing[jboss.naming.context.java.comp.\"application name\".yyybusiness.ViewBean.ValidatorFactoryjboss.naming.context.java.comp.\"application name\".yyybusiness.ViewBean]","jboss.naming.context.java.comp.\"application name\".yyybusiness.HomeBean.ValidatorFactoryjboss.naming.context.java.comp.\"application name\".yyybusiness.HomeBeanMissing[jboss.naming.context.java.comp.\"application name\".yyybusiness.HomeBean.ValidatorFactoryjboss.naming.context.java.comp.\"application name\".yyybusiness.HomeBean]","jboss.naming.context.java.comp.\"application name\".yyybusiness.PasswordsBean.Validatorjboss.naming.context.java.comp.\"application name\".yyybusiness.PasswordsBeanMissing[jboss.naming.context.java.comp.\"application name\".yyybusiness.PasswordsBean.Validatorjboss.naming.context.java.comp.\"application name\".yyybusiness.PasswordsBean]"

                          • 10. Re: Jboss4.2.3 to Jboss7.1 migration issue
                            thinksteep thinksteep Novice

                            1) Yes, you are correct, RolesBean using Hibernate JPA. How can turnoff default validator, infact we are not upgraded to Hibernate4. How can I proceed to overcome this?

                            2)  I am worried about ClassNotFoundException also. Any pointers on that issue also?

                            • 11. Re: Jboss4.2.3 to Jboss7.1 migration issue
                              Prasad Deshpande Expert

                              ok, let's try to narrow down the problem area..

                               

                              I have a feeling that this error is related to JPA/Hibernate use..

                               

                              1. Hibernate 4 is the default version that comes with jboss 7.1.. if you want to override that with hibernate 3, then you'll need to put hibernate 3 jar files in your ear/lib directory. If you are using JPA 2.0 then you can set <validation-mode>NONE</validation-mode> in your persistence.xml. But that depends on whether you are using Hibernate as JPA or simply ORM. I'd suggest, try putting hibernate3 jars in your ear/lib to override jboss hibernate4 jars.

                               

                              2. If that doesn't work then, try deploying modules one by one.. as in firstly ear containing just EJB's.. if that deploys, then add WAR module to ear.

                               

                              Another thing, posting server.logs like above may not be much helpful.. could you please attach entire server.logs to this thread (I understand you don't want to disclose your organisation name.. you can replace that with something else..)?

                              • 12. Re: Jboss4.2.3 to Jboss7.1 migration issue
                                thinksteep thinksteep Novice

                                Thanks Prasad!

                                 

                                I have added hibernate3 jars to ear/lib

                                 

                                Scenario1)

                                Just deployed only yyybusiness.jar as part of EAR and it went fine with out any errors

                                 

                                2) Deployed yyyservices.jar and yyybusiness.jar as EAR, deleted yyyadmin.war from EAR.  I got error something specific to logging manager related to my application. I am trying to change my code for now to ignore logging related to stuff. By the way how can I upload server.log file here? I couldn't find any option to do file upload.

                                 

                                Thank you,

                                • 13. Re: Jboss4.2.3 to Jboss7.1 migration issue
                                  jaikiran pai Master

                                  Post the output of

                                   

                                  jar -tf yyyAdmin.war

                                   

                                  and

                                   

                                  jar -tf yyybusiness.jar

                                   

                                  where yyybusiness.jar is the jar that's in .war/WEB-INF/lib

                                  • 14. Re: Jboss4.2.3 to Jboss7.1 migration issue
                                    Prasad Deshpande Expert

                                    2) Deployed yyyservices.jar and yyybusiness.jar as EAR, deleted yyyadmin.war from EAR.  I got error something specific to logging manager related to my application. I am trying to change my code for now to ignore logging related to stuff. By the way how can I upload server.log file here? I couldn't find any option to do file upload.

                                    there is a link on the top-right corner of the editor where you post message that says "Use advanced editor", click on that & that should give you file uploader at the bottom of the message post editor.

                                    1 2 Previous Next