6 Replies Latest reply on Jan 31, 2012 4:17 AM by Mehul Kapadia

    Unable to find class path entry ClassPathEntryImpl

    Rasa Here Novice

      Hi

       

      I am upgrading my jboss from 4.0 to 5.1.0 GA and when i start app server i am getting the following error

       

       

      org.jboss.deployers.spi.DeploymentException: Unable to find class path entry ClassPathEntryImpl{path=Myapps/AppDependencies/Test1.jar}

       

      I saw many post for this error but not found any solution.

       

      Thanks and Regards

      Rasa

        • 1. Re: Unable to find class path entry ClassPathEntryImpl
          jaikiran pai Master

          Please post the entire exception stacktrace and some more details about your application packaging.

          • 2. Re: Unable to find class path entry ClassPathEntryImpl
            Rasa Here Novice

            Hi,

             

             

            see here i changed the file names and pasted the error

            ERROR [org.jboss.system.server.profileservice.repository.ProfileDeployAction] (main) Failed to add deployment: TestOrder-1.0.jar
            org.jboss.deployers.spi.DeploymentException: Unable to find class path entry ClassPathEntryImpl{path=MyApps/DependJars/TestApps-1.0.jar} from TestOrder-1.0.jar
            at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
            at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:188)
            at org.jboss.deployers.structure.spi.helpers.AbstractStructureBuilder.populateContext(AbstractStructureBuilder.java:82)
            at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:89)
            at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:1004)
            at org.jboss.deployers.plugins.main.MainDeployerImpl.determineDeploymentContext(MainDeployerImpl.java:440)
            at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:390)
            at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:300)
            at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.addDeployment(MainDeployerAdapter.java:86)
            at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:61)
            at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
            at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
            at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
            at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
            at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
            at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
            at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
            at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
            at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
            at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
            at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
            at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
            at org.jboss.Main.boot(Main.java:221)
            at org.jboss.Main$1.run(Main.java:556)
            at java.lang.Thread.run(Thread.java:619)
            Caused by: java.io.IOException: Child not found MyApps/DependJars/TestApps-1.0.jar for DelegatingHandler@32927169[path=MyApps/DependJars/TestOrder-1.0.jar context=file:/D:/jboss-5.1.0.GA/server/default/deploy/ real=file:/D:/jboss-5.1.0.GA/server/default/deploy/MyApps/DependJars/TestOrder-1.0.jar], available children: [ZipEntryHandler@27246550[path=MyApps/DependJars/TestOrder-1.0.jar/META-INF context=file:/D:/jboss-5.1.0.GA/server/default/deploy/ real=file:/D:/jboss-5.1.0.GA/server/default/deploy/MyApps/DependJars/TestOrder-1.0.jar/META-INF], ZipEntryHandler@15443063[path=MyApps/DependJars/TestOrder-1.0.jar/beanRefFactory.xml context=file:/D:/jboss-5.1.0.GA/server/default/deploy/ real=file:/D:/jboss-5.1.0.GA/server/default/deploy/MyApps/DependJars/TestOrder-1.0.jar/beanRefFactory.xml], ZipEntryHandler@8038683[path=MyApps/DependJars/TestOrder-1.0.jar/com context=file:/D:/jboss-5.1.0.GA/server/default/deploy/ real=file:/D:/jboss-5.1.0.GA/server/default/deploy/MyApps/DependJars/TestOrder-1.0.jar/com]]
            at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:461)
            at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:184)
            ... 23 more

             

             

            Package structure is like

             

            in deploy we have one folder MyApps inside that we have an ear file which contains some servlet files. and there is other 3 directories with the name DependJars, Lib and Conf. Conf contains database configuration files (.properties), lib contains the library files and the Depend jar contains the differnt modules for e.g TestOrder-1.0.jar , TestApps.jar.

             

            Please let me know anything else you want me to give to resole this issue.

             

            The same packaging is working perfectly in 4.0.5 Ga version with 1.4 and 1.5 jdk.

             

            Thanks and Regards

            Rasa

            • 3. Re: Unable to find class path entry ClassPathEntryImpl
              jaikiran pai Master

              Rasa Here wrote:

               

              Hi,

               

               


              Package structure is like

               

              in deploy we have one folder MyApps inside that we have an ear file which contains some servlet files. and there is other 3 directories with the name DependJars, Lib and Conf. Conf contains database configuration files (.properties), lib contains the library files and the Depend jar contains the differnt modules for e.g TestOrder-1.0.jar , TestApps.jar.

               

              Like I have said before, just dumping the jars in some folders isn't a replacement for proper packaging. It doesn't matter whether it was working in 4.0.5 or not. If you don't get the packaging right, then I'm sure that you are going to run into more and more weird issues.

               

              Rasa Here wrote:

               

              Hi,

               

               

              see here i changed the file names and pasted the error

              ERROR [org.jboss.system.server.profileservice.repository.ProfileDeployAction] (main) Failed to add deployment: TestOrder-1.0.jar
              org.jboss.deployers.spi.DeploymentException: Unable to find class path entry ClassPathEntryImpl{path=MyApps/DependJars/TestApps-1.0.jar} from TestOrder-1.0.jar
              at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
              at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:188)
              at org.jboss.deployers.structure.spi.helpers.AbstractStructureBuilder.populateContext(AbstractStructureBuilder.java:82)
              at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:89)
              at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:1004)
              at org.jboss.deployers.plugins.main.MainDeployerImpl.determineDeploymentContext(MainDeployerImpl.java:440)
              at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:390)
              at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:300)
              at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.addDeployment(MainDeployerAdapter.java:86)
              at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:61)
              at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
              at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
              at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
              at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
              at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
              at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
              at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
              at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
              at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
              at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
              at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
              at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
              at org.jboss.Main.boot(Main.java:221)
              at org.jboss.Main$1.run(Main.java:556)
              at java.lang.Thread.run(Thread.java:619)

              I'm not sure whether that is a real error or whether it's because of a side-effect of your packaging. Anyway, does any of your jar files have a MANIFEST.MF which contain a Class-Path or a Main-Class attribute? If yes, remove those attributes from the MANIFEST.MF.

              1 of 1 people found this helpful
              • 4. Re: Unable to find class path entry ClassPathEntryImpl
                Rasa Here Novice

                jar files have a MANIFEST.MF which contain a Class-Path or a Main-Class attribute? If yes, remove those attributes from the MANIFEST.MF.

                I did this and now it is not thorwing any error. But i just want to ask the reason behind this.

                 

                And also i need a help from you to get the packaging standard. This apps is being used since last 4 years. So i dnt know whether they will allow me to change but, still i will try.

                • 5. Re: Unable to find class path entry ClassPathEntryImpl
                  Mehul Kapadia Newbie

                  Hi Rasa,

                   

                  I am also running into the same Issue, Did you get solution for this Issue ?.

                   

                  Please share the solution if you have already solve this.

                   

                  Really appriciate your help.

                   

                   

                  Regards,

                  Mehul Kapadia

                  • 6. Re: Unable to find class path entry ClassPathEntryImpl
                    Mehul Kapadia Newbie

                    Hi JaiKiran,

                     

                    I am also running into the same Issue. Could you please explain reason for the solution you have mentioned in the post ??. 

                     

                    jaikiran pai wrote:

                    I'm not sure whether that is a real error or whether it's because of a side-effect of your packaging. Anyway, does any of your jar files have a MANIFEST.MF which contain a Class-Path or a Main-Class attribute? If yes, remove those attributes from the MANIFEST.MF.

                     

                    Why I am asking is we dont have any control over whether thirdparty jars have Class-Path, Main-Class attribute in their Jar's MANIFEST.mf file, and hence it would be manual step at my end. and Its hard to convince the client about it and also we have checksum running on the third party jars which will anyway fail even if I alter even a single character in the thirdparty jar.

                     

                    I have reaise the JIRA Issue for this too : https://issues.jboss.org/browse/JBAS-9470

                     

                    I really appriciate your help here.

                     

                     

                     

                    Regards,

                    Mehul Kapadia