5 Replies Latest reply on Aug 14, 2008 2:39 PM by Peter Johnson

    JBoss-eap-4.3 default server errors JARDeployer w/tmp dir ja

    diego bowen Newbie

      I have just installed jboss-eap-4.3 and using the default server with the folloiwng minor changes:

      1. Changed /server/default/deploy/jmx-console.war/WEB-INF/jboss-web.xml
      <jboss-web>
      <contex-root>diego</context-root>
      </jboss-web>

      2. Changed /server/default/deploy/jmx-console.war/index.xml
      Diego was here

      Then in JBOSS_HOME is appropriately defined pointing to /usr/local/jboss/jboss-as and I run the following in $JBOSS_HOME/bin/

      ./run.sh –c default –u admin –p admin

      -bash-3.00$ ./run.sh -c default -u admin -p admin
      =========================================================================

      JBoss Bootstrap Environment

      JBOSS_HOME: /usr/local/jboss/jboss-as

      JAVA: /usr/local/java/bin/java

      JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true

      CLASSPATH: /usr/local/jboss/jboss-as/bin/run.jar:/usr/local/java/lib/tools.jar

      =========================================================================

      17:48:09,859 INFO [Server] Starting JBoss (MX MicroKernel)...
      17:48:09,860 INFO [Server] Release ID: JBoss [EAP] 4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA date=200801031548)
      17:48:09,861 INFO [Server] Home Dir: /usr/local/jboss-eap-4.3/jboss-as
      17:48:09,861 INFO [Server] Home URL: file:/usr/local/jboss-eap-4.3/jboss-as/
      17:48:09,865 INFO [Server] Patch URL: file:/usr/local/jboss-eap-4.3/jboss-as/bin/admin/
      17:48:09,865 INFO [Server] Server Name: default
      17:48:09,865 INFO [Server] Server Home Dir: /usr/local/jboss-eap-4.3/jboss-as/server/default
      17:48:09,865 INFO [Server] Server Home URL: file:/usr/local/jboss-eap-4.3/jboss-as/server/default/
      17:48:09,865 INFO [Server] Server Log Dir: /usr/local/jboss-eap-4.3/jboss-as/server/default/log
      17:48:09,865 INFO [Server] Server Temp Dir: /usr/local/jboss-eap-4.3/jboss-as/server/default/tmp
      17:48:09,866 INFO [Server] Root Deployment Filename: jboss-service.xml
      17:48:10,108 INFO [ServerInfo] Java version: 1.5.0_15,Sun Microsystems Inc.
      17:48:10,108 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_15-b04,Sun Microsystems Inc.
      17:48:10,108 INFO [ServerInfo] OS-System: Linux 2.6.9-55.ELsmp,i386
      17:48:10,406 INFO [Server] Core system initialized
      17:48:12,152 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
      17:48:12,154 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
      17:48:12,562 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
      17:48:12,562 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
      17:48:12,773 INFO [TransactionManagerService] Starting recovery manager
      17:48:12,855 INFO [TransactionManagerService] Recovery manager started
      17:48:12,855 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
      17:48:13,164 WARN [JARDeployer] Failed to add deployable jar: file:/usr/local/jboss-eap-4.3/jboss-as/server/default/tmp/deploy/tmp28865._jboss-annotations-ejb3.jar
      java.util.zip.ZipException: error in opening zip file
      at java.util.zip.ZipFile.open(Native Method)

      I get a lot more of this type of errors then at the end.......

      --- Incompletely deployed packages ---
      org.jboss.deployment.DeploymentInfo@3adf93c3 { url=file:/usr/local/jboss-eap-4.3/jboss-as/server/default/deploy/jboss-messaging.sar/._connection-factories-service.xml }
      deployer: org.jboss.deployment.SARDeployer@2acc65
      status: null
      state: FAILED
      watch: file:/usr/local/jboss-eap-4.3/jboss-as/server/default/deploy/jboss-messaging.sar/._connection-factories-service.xml
      altDD: null
      lastDeployed: 1218674895221
      lastModified: 1218674895000
      mbeans:

      org.jboss.deployment.DeploymentInfo@31464888 { url=file:/usr/local/jboss-eap-4.3/jboss-as/server/default/deploy/jboss-messaging.sar/ }
      deployer: org.jboss.deployment.SARDeployer@2acc65
      status: null
      state: FAILED
      watch: file:/usr/local/jboss-eap-4.3/jboss-as/server/default/deploy/jboss-messaging.sar/META-INF/jboss-service.xml
      altDD: null
      lastDeployed: 1218674895222
      lastModified: 1199400610000
      mbeans:

      org.jboss.deployment.DeploymentInfo@94a9ff6a { url=file:/usr/local/jboss-eap-4.3/jboss-as/server/default/deploy/jbossws.sar/._jbossws.beans }
      deployer: org.jboss.kernel.deployment.jboss.JBossBeanDeployer@52d1a4
      status: null
      state: FAILED
      watch: file:/usr/local/jboss-eap-4.3/jboss-as/server/default/deploy/jbossws.sar/._jbossws.beans
      altDD: null
      lastDeployed: 1218674895243
      lastModified: 1218674895000
      mbeans:

      org.jboss.deployment.DeploymentInfo@fe114543 { url=file:/usr/local/jboss-eap-4.3/jboss-as/server/default/deploy/jbossws.sar/ }
      deployer: org.jboss.deployment.SARDeployer@2acc65
      status: null
      state: FAILED
      watch: file:/usr/local/jboss-eap-4.3/jboss-as/server/default/deploy/jbossws.sar/META-INF/jboss-service.xml
      altDD: null
      lastDeployed: 1218674895243
      lastModified: 1199400612000
      mbeans:

      org.jboss.deployment.DeploymentInfo@62029671 { url=file:/usr/local/jboss-eap-4.3/jboss-as/server/default/deploy/management/console-mgr.sar/._console-mgr-classes.jar }
      deployer: null
      status: null
      state: FAILED
      watch: file:/usr/local/jboss-eap-4.3/jboss-as/server/default/deploy/management/console-mgr.sar/._console-mgr-classes.jar
      altDD: null
      lastDeployed: 1218674895272
      lastModified: 1218674895000
      mbeans:

      org.jboss.deployment.DeploymentInfo@e821be3c { url=file:/usr/local/jboss-eap-4.3/jboss-as/server/default/deploy/management/console-mgr.sar/ }
      deployer: org.jboss.deployment.SARDeployer@2acc65
      status: null
      state: FAILED
      watch: file:/usr/local/jboss-eap-4.3/jboss-as/server/default/deploy/management/console-mgr.sar/META-INF/jboss-service.xml
      altDD: null
      lastDeployed: 1218674895272
      lastModified: 1199400608000
      mbeans:


      17:48:18,798 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
      17:48:18,813 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
      17:48:18,821 INFO [Server] JBoss (MX MicroKernel) [4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA date=200801031548)] Started in 8s:954ms

      the first error regarding not being able to handle "tmp28865._jboss-annotations-ejb3.jar" above, here is how that file looks:

      -bash-3.00$ pwd
      /usr/local/jboss-eap-4.3/jboss-as/server/default/tmp/deploy
      -bash-3.00$ ls -la tmp28865._jboss-annotations-ejb3.jar
      -rw-r--r-- 1 webadmin eng 193 Aug 13 17:48 tmp28865._jboss-annotations-ejb3.jar
      -bash-3.00$


      Any suggestions....I had Jboss-4.0.5 and did the same thing and it worked fine...thanks

        • 1. Re: JBoss-eap-4.3 default server errors JARDeployer w/tmp di
          Peter Johnson Master

          You have JBOSS_HOME set to:

          JBOSS_HOME: /usr/local/jboss/jboss-as

          But that is not where it is located, later in the console log I see:

          17:48:09,861 INFO [Server] Home Dir: /usr/local/jboss-eap-4.3/jboss-as

          Try correcting JBOSS_HOME and see if that helps.

          Also, make sure that the user account running EAP has full rights to the /usr/local/jboss-eap-4.3 directory and all its subdirectories.

          If none of the above helps, download and install JBossEAP again. I often see these kinds of unusual errors when the download is corrupted. (Too bad an md5 or sha-256 checksum are not provided with the EAP download - then you could verify that the download is not corrupt.)

          • 2. Re: JBoss-eap-4.3 default server errors JARDeployer w/tmp di
            diego bowen Newbie

            Thanks PeterJ for the comments... I downloaded another copy of jboss-eap-4.3 and did the following:

            I have jboss sym linked to /usr/local/jboss-eap-4.3/jboss-as
            jboss -> jboss-eap-4.3/jboss-as

            JBOSS_HOME defined such that:

            -bash-3.00$ echo $JBOSS_HOME
            /usr/local/jboss
            -bash-3.00$ cd $JBOSS_HOME
            -bash-3.00$ pwd
            /usr/local/jboss
            -bash-3.00$ ls
            bin client copyright.txt docs jar-versions.xml JBossORG-EULA.txt lgpl.html lib server
            -bash-3.00$

            And i chown -R for this particular user so that it own everything.

            ./run.sh -c default
            =========================================================================

            JBoss Bootstrap Environment

            JBOSS_HOME: /usr/local/jboss

            JAVA: /usr/local/java/bin/java

            JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true

            CLASSPATH: /usr/local/jboss/bin/run.jar:/usr/local/java/lib/tools.jar

            =========================================================================

            08:43:46,053 INFO [Server] Starting JBoss (MX MicroKernel)...
            08:43:46,054 INFO [Server] Release ID: JBoss [EAP] 4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA date=200801031548)
            08:43:46,055 INFO [Server] Home Dir: /usr/local/jboss-eap-4.3/jboss-as
            08:43:46,055 INFO [Server] Home URL: file:/usr/local/jboss-eap-4.3/jboss-as/
            08:43:46,056 INFO [Server] Patch URL: null
            08:43:46,056 INFO [Server] Server Name: default
            08:43:46,056 INFO [Server] Server Home Dir: /usr/local/jboss-eap-4.3/jboss-as/server/default
            08:43:46,057 INFO [Server] Server Home URL: file:/usr/local/jboss-eap-4.3/jboss-as/server/default/
            08:43:46,057 INFO [Server] Server Log Dir: /usr/local/jboss-eap-4.3/jboss-as/server/default/log
            08:43:46,057 INFO [Server] Server Temp Dir: /usr/local/jboss-eap-4.3/jboss-as/server/default/tmp
            08:43:46,057 INFO [Server] Root Deployment Filename: jboss-service.xml
            08:43:46,292 INFO [ServerInfo] Java version: 1.5.0_15,Sun Microsystems Inc.
            08:43:46,292 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_15-b04,Sun Microsystems Inc.
            08:43:46,292 INFO [ServerInfo] OS-System: Linux 2.6.9-55.ELsmp,i386
            08:43:46,575 INFO [Server] Core system initialized
            08:43:48,221 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
            08:43:48,223 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
            08:43:48,608 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
            08:43:48,608 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
            08:43:48,812 INFO [TransactionManagerService] Starting recovery manager
            08:43:48,890 INFO [TransactionManagerService] Recovery manager started
            08:43:48,890 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
            08:43:49,203 WARN [JARDeployer] Failed to add deployable jar: file:/usr/local/jboss-eap-4.3/jboss-as/server/default/tmp/deploy/tmp52237._jboss-annotations-ejb3.jar
            java.util.zip.ZipException: error in opening zip file
            at java.util.zip.ZipFile.open(Native Method)

            08:43:54,617 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

            --- Incompletely deployed packages ---
            org.jboss.deployment.DeploymentInfo@3adf93c3 { url=file:/usr/local/jboss-eap-4.3/jboss-as/server/default/deploy/jboss-messaging.sar/._connection-factories-service.xml }
            deployer: org.jboss.deployment.SARDeployer@1309e87
            status: null
            state: FAILED
            watch: file:/usr/local/jboss-eap-4.3/jboss-as/server/default/deploy/jboss-messaging.sar/._connection-factories-service.xml
            altDD: null
            lastDeployed: 1218728631182
            lastModified: 1218728631000
            mbeans:

            org.jboss.deployment.DeploymentInfo@31464888 { url=file:/usr/local/jboss-eap-4.3/jboss-as/server/default/deploy/jboss-messaging.sar/ }
            deployer: org.jboss.deployment.SARDeployer@1309e87
            status: null
            state: FAILED
            watch: file:/usr/local/jboss-eap-4.3/jboss-as/server/default/deploy/jboss-messaging.sar/META-INF/jboss-service.xml
            altDD: null
            lastDeployed: 1218728631182
            lastModified: 1199400610000
            mbeans:
            ........................

            org.jboss.deployment.DeploymentInfo@be571e13 { url=file:/usr/local/jboss-eap-4.3/jboss-as/server/default/deploy/jmx-console.war/ }
            deployer: MBeanProxyExt[jboss.web:service=WebServer]
            status: null
            state: FAILED
            watch: file:/usr/local/jboss-eap-4.3/jboss-as/server/default/deploy/jmx-console.war/WEB-INF/web.xml
            altDD: null
            lastDeployed: 1218728634613
            lastModified: 1218728088000
            mbeans:


            08:43:54,679 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
            08:43:54,693 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
            08:43:54,700 INFO [Server] JBoss (MX MicroKernel) [4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA date=200801031548)] Started in 8s:641ms


            • 3. Re: JBoss-eap-4.3 default server errors JARDeployer w/tmp di
              Peter Johnson Master

              Try without the symbolic link for jboss_home.

              • 4. Re: JBoss-eap-4.3 default server errors JARDeployer w/tmp di
                diego bowen Newbie

                That produced the same errors...quick question though regarding the download on jboss-eap-4.3 itself….I’m downloading jboss-eap-4.3 from the JBOSS's custumer support Portal using Mac OS X, then placing it on a Linux box. Would that cause a problem? The reason I ask is that when I attempt downloading the above at home on my Mac OS X and running it I don’t have the same problems.

                • 5. Re: JBoss-eap-4.3 default server errors JARDeployer w/tmp di
                  Peter Johnson Master

                  How did you transfer from Mac OS X to Linux? Via FTP? If so, did you use binary transfer mode? If not, the default text transfer more is almost guaranteed to corrupt every binary file.

                  As long as you do a binary transfer, no problem. For example, I download EAP to my Vista desktop and then used Samba on Linux to connect to Vista, transfered EAP to LInux, unzipped it, and then ran it.

                  One way to check - use a zip utility (I use the capability built into Knoqueror) to examine the jar file in question. Or attempt to use jar to unjar the file. If you get errors, then the file is corrupt.