8 Replies Latest reply on Aug 7, 2008 11:14 AM by Peter Johnson

    Deploying ZIP/JAR files issue

    Alexey Raskin Newbie

      Hi all,
      during deploying ZIP or JAR files I obtain the exception (see below). Other files are being deployed fine. But zip or jar not. It says "Could not deploy sub deployment.." and "could not be opened..". I checked that files exist in specified in log folder and can be opened as valid ZIP/JAR formats. So now I don't have any idea what the problem is. Please help.



      2008-07-30 22:23:27,467 DEBUG [main] [org.jboss.deployment.scanner.URLDeploymentScanner] Failed to deploy: org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL@b8b2ef67{ url=file:/C:/build-capri/eds-server/deploy, deployedLastModified=0 }
      org.jboss.deployment.DeploymentException: Could not deploy sub deployment 1996_update.zip of deployment file:/C:/build-capri/eds-server/deploy; - nested throwable: (org.jboss.deployment.DeploymentException: url file:/C:/build-capri/eds-server/deploy/Raw+Data+Load/dataload/xml/1996_update.zip could not be opened, does it exist?)
      at org.jboss.deployment.SubDeployerSupport.deployUrl(SubDeployerSupport.java:557)
      at org.jboss.deployment.SubDeployerSupport.addDeployableFiles(SubDeployerSupport.java:451)
      at org.jboss.deployment.SubDeployerSupport.addDeployableFiles(SubDeployerSupport.java:462)
      at org.jboss.deployment.SubDeployerSupport.addDeployableFiles(SubDeployerSupport.java:462)
      at org.jboss.deployment.SubDeployerSupport.addDeployableFiles(SubDeployerSupport.java:462)
      at org.jboss.deployment.SubDeployerSupport.processNestedDeployments(SubDeployerSupport.java:369)
      at org.jboss.deployment.SubDeployerSupport.init(SubDeployerSupport.java:284)
      at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
      at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
      at $Proxy9.deploy(Unknown Source)
      at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:417)
      at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
      at $Proxy4.start(Unknown Source)
      at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
      at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
      at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
      at $Proxy5.deploy(Unknown Source)
      at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
      at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
      at org.jboss.Main.boot(Main.java:200)
      at org.jboss.Main$1.run(Main.java:508)
      at java.lang.Thread.run(Unknown Source)
      Caused by: org.jboss.deployment.DeploymentException: url file:/C:/build-capri/eds-server/deploy/Raw+Data+Load/dataload/xml/1996_update.zip could not be opened, does it exist?
      at org.jboss.deployment.DeploymentInfo.(DeploymentInfo.java:214)
      at org.jboss.deployment.SubDeployerSupport.deployUrl(SubDeployerSupport.java:552)


      thanks,
      Alexey

        • 1. Re: Deploying ZIP/JAR files issue
          Alexey Raskin Newbie

          The ZIP/JARS I try to deploy are valid formats and I can easily open it with other tools

          • 2. Re: Deploying ZIP/JAR files issue
            jaikiran pai Master

            Post the output of

            jar -tf 1996_update.zip


            • 3. Re: Deploying ZIP/JAR files issue
              Alexey Raskin Newbie

              This command listed all files contained in the archive, but I had to correct initial command you typed and I specifed full path to jar.exe and .zip archive to execute this command. So it seems that archive itself OK and the issue is in "deployUrl" method. Is there a way to look sources of these files to understand what the error is i.e. probably it's issue of CLASSPASS variable or something like this.

              Please, note that all other files located in deploy folder i.e. (not archive files) are deploying fine, meaning I see exceptions only for JAR/ZIP files.

              And another note is that JAR/ZIP files are actually deployed OK to server but with this strange exception. So I just don't know the nature of this exception, what JBoss is trying to do. Why it tries to open it, and why fails.

              • 4. Re: Deploying ZIP/JAR files issue
                Peter Johnson Master

                The location of the file is no exactly what I would expect:

                C:/build-capri/eds-server/deploy/Raw+Data+Load/dataload/xml/1996_update.zip

                Typically, the directory structure is server/xxx/deploy. Did you update the URLlist, and if so, what did youy update it to?

                Also, this part of the path is suspect: Raw+Data+Load. Is this really "Raw Data Load", with spaces? If so, either move the ZIP file into a path without space or rename the directory so it no longer has spaces. Spaces in paths can give some Java libraries fits. (If the directory really does contain the plus signs, try removing them and see if it helps.)

                The sources are available from the same web page where you downloaded the binary.

                Finally, what version of JBossAS are you using.

                By the way, Jaikiran asked you to run the jar utility to ensure that the ZIP file was readable. In the past we have encountered people who use various other utilities (such a WinRAR) to create ZIP files and those files were incompatible with Java.

                • 5. Re: Deploying ZIP/JAR files issue
                  Alexey Raskin Newbie

                  Hi Guys,

                  "PeterJ" wrote:
                  The location of the file is no exactly what I would expect:

                  C:/build-capri/eds-server/deploy/Raw+Data+Load/dataload/xml/1996_update.zip

                  Typically, the directory structure is server/xxx/deploy. Did you update the URLlist, and if so, what did youy update it to?

                  We have:
                  <attribute name="URLs">
                  deploy/,file:/C:/build-capri/eds-server/deploy
                  </attribute>
                  setting in jboss-service.xml file

                  So all content of 'deploy' folder should be deployed with sub-folders.

                  "PeterJ" wrote:

                  Also, this part of the path is suspect: Raw+Data+Load. Is this really "Raw Data Load", with spaces? If so, either move the ZIP file into a path without space or rename the directory so it no longer has spaces. Spaces in paths can give some Java libraries fits. (If the directory really does contain the plus signs, try removing them and see if it helps.)

                  Ooopsss!
                  Yes, you are right, this is the issue! I replaced '+' in the folder name to '_' and it woks now!
                  Do you know why '+' is so bad in folder's name in case of un-ZIP-ing? It worked in previous versions of JBoss.

                  "PeterJ" wrote:

                  The sources are available from the same web page where you downloaded the binary.

                  Finally, what version of JBossAS are you using.

                  We have recently upgraded to JBoss 4.2.2.GA

                  "PeterJ" wrote:

                  By the way, Jaikiran asked you to run the jar utility to ensure that the ZIP file was readable. In the past we have encountered people who use various other utilities (such a WinRAR) to create ZIP files and those files were incompatible with Java.

                  No, Zip ok. The command with jar utility displayed a full list of files contained in the .zip archive. So I run the following:
                  C:\>c:\jdk1.5.0_11\bin\jar.exe -tf C:\build-capri\eds-server\deploy\Raw+Data+load\dataload\xml\1996_update.zip

                  Note that it's old, yet with '+' signs path.

                  thank you,
                  Alexey

                  • 6. Re: Deploying ZIP/JAR files issue
                    Peter Johnson Master

                    The deployers have undergone a lot of changes in the 4.2.x releases, with 5.0 introducing even more changes so at times there are issues that crop up. Without looking at the code I could not say why the "+" would cause a problem. Perhaps someone on the JBoss team could comment on whether this is a bug and if a JIRA ir warranted.

                    • 7. Re: Deploying ZIP/JAR files issue
                      Alexey Raskin Newbie

                      Guys,
                      thank you for your help!

                      How can I contact somebody from JBoss support team?

                      • 8. Re: Deploying ZIP/JAR files issue
                        Peter Johnson Master

                        One sure-fire way to get their attention is to open a JIRA. Be sure to reference this forum post when you do.