14 Replies Latest reply on Jan 3, 2014 3:20 AM by Fakaruddin Ali

    Deployment error in jboss 7

    Fakaruddin Ali Newbie


      Hi All,

      I am migrating ejb2.0 to ejb3.1 and jboss 5.1 to jboss 7.1.1.

      I have migrated to ejb3.1 and successfulyy depolyed in jboss5.1

      But now I am migrating to jboss 7.1.1..I am getting the following error .

      Please help me to reslove the issue.


      Thanks,

      Fakaruddin

       

      5:13:47,438 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
      15:13:47,439 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 2873ms - Started 132 of 207 services (74 services are passive or on-demand)
      15:13:47,509 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found TCPro.ear in deployment directory. To trigger deployment create a file called TCPro.ear.dodeploy
      15:13:47,530 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "TCPro.ear"
      15:13:48,596 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry davisoroffisor-transformations.jar in "/C:/myinstalls/jboss-7.1.1/standalone/deployments/TCPro.ear/davisoroffisor.jar"  does not point to a valid jar for a Class-Path reference.
      15:13:48,598 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry batik.jar in "/C:/myinstalls/jboss-7.1.1/standalone/deployments/TCPro.ear/davisoroffisor.jar"  does not point to a valid jar for a Class-Path reference.
      15:13:48,600 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry JimiProClasses.zip in "/C:/myinstalls/jboss-7.1.1/standalone/deployments/TCPro.ear/davisoroffisor.jar"  does not point to a valid jar for a Class-Path reference.
      15:13:48,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry iText-toolbox.jar in "/C:/myinstalls/jboss-7.1.1/standalone/deployments/TCPro.ear/iText-2.1.4.jar"  does not point to a valid jar for a Class-Path reference.
      15:13:48,605 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry iText-toolbox-2.1.4.jar in "/C:/myinstalls/jboss-7.1.1/standalone/deployments/TCPro.ear/iText-2.1.4.jar"  does not point to a valid jar for a Class-Path reference.
      15:13:48,613 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry bcmail-jdk14-138.jar in "/C:/myinstalls/jboss-7.1.1/standalone/deployments/TCPro.ear/iText-2.1.4.jar"  does not point to a valid jar for a Class-Path reference.
      15:13:48,615 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry bcprov-jdk14-138.jar in "/C:/myinstalls/jboss-7.1.1/standalone/deployments/TCPro.ear/iText-2.1.4.jar"  does not point to a valid jar for a Class-Path reference.
      15:13:48,622 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "TCProWeb.war"
      15:13:48,623 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "API.jar"
      15:13:48,623 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "Domain.jar"
      15:13:48,623 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "Framework.jar"
      15:13:49,329 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry iText-toolbox.jar in "/C:/myinstalls/jboss-7.1.1/standalone/deployments/TCPro.ear/TCProWeb.war/WEB-INF/lib/iText-2.1.4.jar"  does not point to a valid jar for a Class-Path reference.
      15:13:49,330 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry iText-toolbox-2.1.4.jar in "/C:/myinstalls/jboss-7.1.1/standalone/deployments/TCPro.ear/TCProWeb.war/WEB-INF/lib/iText-2.1.4.jar"  does not point to a valid jar for a Class-Path reference.
      15:13:49,332 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry bcmail-jdk14-138.jar in "/C:/myinstalls/jboss-7.1.1/standalone/deployments/TCPro.ear/TCProWeb.war/WEB-INF/lib/iText-2.1.4.jar"  does not point to a valid jar for a Class-Path reference.
      15:13:49,334 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry bcprov-jdk14-138.jar in "/C:/myinstalls/jboss-7.1.1/standalone/deployments/TCPro.ear/TCProWeb.war/WEB-INF/lib/iText-2.1.4.jar"  does not point to a valid jar for a Class-Path reference.
      15:13:49,335 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry lib/jcommon-1.0.0.jar in "/C:/myinstalls/jboss-7.1.1/standalone/deployments/TCPro.ear/TCProWeb.war/WEB-INF/lib/jfreechart-1.0.0.jar"  does not point to a valid jar for a Class-Path reference.
      15:13:49,358 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry commons-logging.jar in "/C:/myinstalls/jboss-7.1.1/standalone/deployments/TCPro.ear/TCProWeb.war/WEB-INF/lib/struts.jar"  does not point to a valid jar for a Class-Path reference.
      15:13:49,362 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.deployment.unit."TCPro.ear".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."TCPro.ear".PARSE: Failed to process phase PARSE of deployment "TCPro.ear"
      at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.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.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
      at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
      Caused by: java.lang.IllegalArgumentException: xercesImpl,xml-apis,fop,batik,avalon-framework,ant,junit,hsqldb,log4j,rhino-Extension-Name
      at java.util.jar.Attributes$Name.<init>(Attributes.java:464) [rt.jar:1.7.0_45]
      at java.util.jar.Attributes.getValue(Attributes.java:116) [rt.jar:1.7.0_45]
      at org.jboss.as.server.deployment.module.ManifestExtensionListProcessor.deploy(ManifestExtensionListProcessor.java:74) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
      at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
      ... 5 more

      15:13:49,579 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "TCPro.ear" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"TCPro.ear\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"TCPro.ear\".PARSE: Failed to process phase PARSE

        • 1. Re: Deployment error in jboss 7
          Wolf-Dieter Fink Master

          Could you show the MANIFEST and the structure of your deployment?

          • 2. Re: Deployment error in jboss 7
            Fakaruddin Ali Newbie

            Hi Thanks for your reply.

            Mainfest is:

            Manifest-Version: 1.0


             

            Application.xml is as follows:

             

            <?xml version="1.0" encoding="UTF-8"?>
            <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">
            <description></description>
            <display-name></display-name>
            <application-name>TCPro</application-name>
            <initialize-in-order>true</initialize-in-order>
            <icon></icon>
            <module>
              <ejb>Octopus.jar</ejb>
            </module>
            <module>
              <ejb>davisoroffisor.jar</ejb>
            </module>
            <module>
              <ejb>ClaimUtility.jar</ejb>
            </module>
            <module>
              <ejb>csvjdbc.jar</ejb>
            </module>
            <module>
              <ejb>jrules-engine.jar</ejb>
            </module>
            <module>
              <ejb>sam.jar</ejb>
            </module>
            <module>
              <ejb>commons-lang-2.0.jar</ejb>
            </module>
            <module>
              <ejb>iText-rtf-2.1.4.jar</ejb>
            </module>
            <module>
              <ejb>iText-2.1.4.jar</ejb>
            </module>
            <module>
              <ejb>uht-authorization-1.1.jar</ejb>
            </module>
            <module>
              <ejb>uht-cache-1.1.jar</ejb>
            </module>
            <module>
              <ejb>uht-exception-3.0.1.jar</ejb>
            </module>
            <module>
              <ejb>smclient.jar</ejb>
            </module>
            <module>
              <ejb>commons-io-2.4.jar</ejb>
            </module>
            <module id="myeclipse.1383107414586">
              <web>
               <web-uri>TCProWeb.war</web-uri>
               <context-root>/TCProWeb</context-root>
              </web>
            </module>
            <module id="myeclipse.1088815291498">
              <ejb>API.jar</ejb>
            </module>
            <module id="myeclipse.1088816781835">
              <ejb>Domain.jar</ejb>
            </module>
            <module id="myeclipse.1088816897806">
              <ejb>Framework.jar</ejb>
            </module>
            </application>

            • 3. Re: Deployment error in jboss 7
              Wolf-Dieter Fink Master

              Not sure, but it looks like a dependency within a MANIFEST

              xercesImpl,xml-apis,fop,batik,avalon-framework,ant,junit,hsqldb,log4j,rhino-Extension-Name

              You might have a look to the different modules and check whether you can find this Attribute.

               

              BTW, you should attach the files to avoid a lot of scrolling   You can do that by edit your comment. Then you find the link to attach files

              • 4. Re: Deployment error in jboss 7
                Fakaruddin Ali Newbie

                Hi Thanks for your reply..

                I have debug the code found like that

                 

                 


                I have debugged..got like  below in Attribute.class of java .For this it is  throwing exception.Me using Myeclipse..

                {rhino-Extension-Name=rhino, Extension-List=xercesImpl,xml-apis,fop,batik,avalon-framework,ant,junit,hsqldb,log4j,rhino, avalon-framework-Implementation-Version=cvs-20020315, Built-By=gpease, avalon-framework-Extension-Name=avalon-framework, fop-Implementation-Version=0.20.4, log4j-Extension-Name=log4j, Package=org, avalon-framework-Implementation-URL=http://www.ibiblio.org/maven/fop/jars/avalon-framework-cvs-20020315.jar, fop-Implementation-URL=http://www.ibiblio.org/maven/fop/jars/fop-0.20.4.jar, ant-Extension-Name=ant, xercesImpl-Extension-Name=xercesImpl, xml-apis-Implementation-URL=http://www.ibiblio.org/maven/xerces/jars/xml-apis.jar, log4j-Implementation-URL=http://www.ibiblio.org/maven/log4j/jars/log4j-1.2.5.jar, Implementation-Vendor=Together - the Workgroup, Implementation-Vendor-Id=, xml-apis-Implementation-Version=, Specification-Title=Tool for tranformation data from one JDBC source to another, xml-apis-Extension-Name=xml-apis, Extension-Name=csvjdbc, hsqldb-Extension-Name=hsqldb, ant-Implementation-Version=1.5.1, Implementation-Version=, batik-Implementation-Version=LATEST, xercesImpl-Implementation-Version=2.4.0, Specification-Vendor=Together - the Workgroup, Manifest-Version=1.0, ant-Implementation-URL=http://www.ibiblio.org/maven/ant/jars/ant.jar, rhino-Implementation-URL=http://www.ibiblio.org/maven/rhino/jars/js.jar, Created-By=Apache Jakarta Maven, batik-Implementation-URL=http://www.ibiblio.org/maven/fop/jars/batik-LATEST.jar, junit-Implementation-Version=3.8.1, hsqldb-Implementation-Version=1.7.1, hsqldb-Implementation-URL=http://www.ibiblio.org/maven/hsqldb/jars/hsqldb-1.7.1.jar, Build-Jdk=1.4.2_06, fop-Extension-Name=fop, rhino-Implementation-Version=, log4j-Implementation-Version=1.2.5, Specification-Version=, batik-Extension-Name=batik, junit-Extension-Name=junit, junit-Implementation-URL=http://www.ibiblio.org/maven/junit/jars/junit-3.8.1.jar, xercesImpl-Implementation-URL=http://www.ibiblio.org/maven/xerces/jars/xercesImpl-2.4.0.jar}

                How thesr are coming in deployment  i am not getting any idea

                • 5. Re: Deployment error in jboss 7
                  Wolf-Dieter Fink Master

                  I suppose this dependencies come from your deployment. They might be added manually or by the build process.

                  Did you check the different deployment descriptors and MANIFEST files?

                  Are you aware of this dependencies? How do you build the artifacts?

                  1 of 1 people found this helpful
                  • 6. Re: Deployment error in jboss 7
                    Fakaruddin Ali Newbie

                    I am using Myeclipse Blue Edition to build artifacts.

                    I am using Application.xml and MANIFEST file which already I have shared.

                    In MYeclipse also, I have removed all workbench settings.

                    in jboss 7 , only modlus that are come of with jboss are there.

                    I have just added only one module for loading ojdbc driver in jboss modules.

                    I am not using jboss-deployement .xml.

                     

                    I do not know why the error is coming

                    • 7. Re: Deployment error in jboss 7
                      Wolf-Dieter Fink Master

                      But I see a lot of ejb modules in your application.xml. I'm not sure whether this is intentional or not and what the modules for.

                      I suppose that commons* and iText* are framework libraries and no ejb-modules, so I would assume that this is the reason.

                      1 of 1 people found this helpful
                      • 8. Re: Deployment error in jboss 7
                        Fakaruddin Ali Newbie

                        Hi

                        I have reomoved unnecessary modules from Appication.xml.

                        Now above error is not coimng some different error regarding missing dependency.

                         

                        I am using Hibernate 3.0 .As per as jboos 7 it implements JPA ..

                        I need to override JPA implementaion..

                        How can I include Hibernate3.0 depenecy in Jboos 7.

                        • 9. Re: Deployment error in jboss 7
                          Wolf-Dieter Fink Master

                          If you want to exclude the provided JBoss modules you need to add the jboss-deployment-structure.xml file and add the implementation you need to the EAR file lib directory.

                          You should read Class Loading in AS7 maybe you can use newer documentation (i.e. WildFly) often you will find better explanation and the features are not different as the 7.1 documents are not updated.

                           

                          If you have dependencies you can add the jar to the lib folder or add it as java module to prevent from analysing during deployment.

                          Hope that help to get it deployed.

                          • 10. Re: Deployment error in jboss 7
                            Fakaruddin Ali Newbie

                            Thank you very much.

                            I have overried the JPA implementaion in Jboss7.'

                            I have included  hibernate3.0 jAR IN EAR LIB folder.

                            It is working.

                            Again , the below error is coming (Above full details error is there)

                            Caused by: java.lang.IllegalArgumentException: xercesImpl,xml-apis,log4j,rhino,fop,batik,avalon-framework,ant,junit,hsqldb-Extension-Name

                            as I have included "Octopus.jar" in ear lib folder.Octopus.jar ia the root couse for the exception,  I was also getting eralier

                            But If I do not include Octopus.jar, it is  througing the below exception

                            Caused by: java.lang.NoClassDefFoundError: org/webdocwf/util/loader/LoaderException

                            at java.lang.Class.getDeclaredFields0(Native Method) [rt.jar:1.7.0_45]

                            at java.lang.Class.privateGetDeclaredFields(Class.java:2397) [rt.jar:1.7.0_45]

                            at java.lang.Class.getDeclaredFields(Class.java:1806) [rt.jar:1.7.0_45]

                            at org.jboss.as.server.deployment.reflect.ClassReflectionIndex.<init>(ClassReflectionIndex.java:57) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]

                            at org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:66) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]

                            ... 10 more

                            Caused by: java.lang.ClassNotFoundException: org.webdocwf.util.loader.LoaderException from [Module "deployment.TCPro.ear.Framework.jar: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.ConcurrentClassLoade

                             

                            Please help me to reslove..

                             

                            Thanks...

                            Fakaruddin

                            • 11. Re: Deployment error in jboss 7
                              Wolf-Dieter Fink Master

                              What is the Octopus.jar? A third part framework or yours?

                              How the meta data look like?

                              • 12. Re: Deployment error in jboss 7
                                Fakaruddin Ali Newbie

                                Hi it is third party jar.

                                The probl is for meta data..

                                it looks like..

                                 

                                Manifest-Version: 1.0
                                Created-By: Apache Jakarta Maven
                                Built-By: gpease
                                Package: org
                                Build-Jdk: 1.4.2_06
                                Extension-Name: Octopus
                                Specification-Version:
                                Specification-Vendor: Together - the Workgroup
                                Specification-Title: Tool for tranformation data from one JDBC source
                                to another
                                Implementation-Version: 3.0
                                Implementation-Vendor: Together - the Workgroup
                                Implementation-Vendor-Id:
                                Extension-List: xercesImpl,xml-apis,log4j,rhino,fop,batik,avalon-frame
                                work,ant,junit,hsqldb
                                xercesImpl-Extension-Name: xercesImpl
                                xercesImpl-Implementation-Version: 2.4.0
                                xercesImpl-Implementation-URL: http://www.ibiblio.org/maven/xerces/jar
                                s/xercesImpl-2.4.0.jar
                                xml-apis-Extension-Name: xml-apis
                                xml-apis-Implementation-Version:
                                xml-apis-Implementation-URL: http://www.ibiblio.org/maven/xerces/jars/
                                xml-apis.jar
                                log4j-Extension-Name: log4j
                                log4j-Implementation-Version: 1.2.5
                                log4j-Implementation-URL: http://www.ibiblio.org/maven/log4j/jars/log4
                                j-1.2.5.jar
                                rhino-Extension-Name: rhino
                                rhino-Implementation-Version:
                                rhino-Implementation-URL: http://www.ibiblio.org/maven/rhino/jars/js.jar
                                fop-Extension-Name: fop
                                fop-Implementation-Version: 0.20.4
                                fop-Implementation-URL: http://www.ibiblio.org/maven/fop/jars/fop-0.20
                                .4.jar
                                batik-Extension-Name: batik
                                batik-Implementation-Version: LATEST
                                batik-Implementation-URL: http://www.ibiblio.org/maven/fop/jars/batik-
                                LATEST.jar
                                avalon-framework-Extension-Name: avalon-framework
                                avalon-framework-Implementation-Version: cvs-20020315
                                avalon-framework-Implementation-URL: http://www.ibiblio.org/maven/fop/
                                jars/avalon-framework-cvs-20020315.jar
                                ant-Extension-Name: ant
                                ant-Implementation-Version: 1.5.1
                                ant-Implementation-URL: http://www.ibiblio.org/maven/ant/jars/ant.jar
                                junit-Extension-Name: junit
                                junit-Implementation-Version: 3.8.1
                                junit-Implementation-URL: http://www.ibiblio.org/maven/junit/jars/juni
                                t-3.8.1.jar
                                hsqldb-Extension-Name: hsqldb
                                hsqldb-Implementation-Version: 1.7.1
                                hsqldb-Implementation-URL: http://www.ibiblio.org/maven/hsqldb/jars/hs
                                qldb-1.7.1.jar

                                 

                                 

                                Thats why the above exception is coimg..

                                • 13. Re: Deployment error in jboss 7
                                  Wolf-Dieter Fink Master

                                  From the MANIFEST specification the extenstion  list ist for applets which need additional resources.

                                  Unfortunately I did not know much about that (frontend stuff)

                                   

                                  I'm not sure whether you need that attributes and the applets, maybe you can remove that from the MANIFEST and it works, you may not need the applets.

                                  It might be that the deployment change a bit from 5 to 6 and it is a JBoss issue that there was no error in JBoss5 or now the error in EAP6.

                                   

                                  You might start a new thread with the appropriate informations.

                                  • 14. Re: Deployment error in jboss 7
                                    Fakaruddin Ali Newbie

                                    Hi,

                                    I have edited the Mainfest file and removed unneccesary Dependency.

                                    It is working fine..

                                    Thanks...for your help..

                                    3.1 session beans I am able to deploy in jboss7

                                    MDB bean , I am deploying..I need to convert JBos messaging to Hornet Queue.

                                    As per Jboss 7 ,not supporting Jboss Messaging, we need to migarte to Hornet..queue.

                                     

                                    If i face any issue, i will let you know.

                                    Again thanks for your time and help.

                                    Thanks,

                                     

                                    Fakaruddin ALi.