2 Replies Latest reply on Feb 13, 2006 2:00 PM by alchemista

    JBoss MainDeployer doesn't pick up exploded JAR on my Linux

    alchemista

      I have an exploded EJB JAR as one of my deployment items.

      I have RH Enterprise Linux systems that are deploying the EJB fine, the MainDeployer detects the .jar directory and deploys it as an EJB

      The uname -a is:
      Linux myhost 2.4.21-20.ELsmp #1 SMP Wed Aug 18 20:46:40 EDT 2004 i686 i686 i386 GNU/Linux


      However, I have a Fedora Core 1 machine where the MainDeployer is not even trying to deploy this directory. It's not giving an error, it's just never even trying to deploy it. The directory structure is exactly the same, the JBoss and Java versions are exactly the same as the RH systems.

      The Fedora machine is:

      Linux baldeagle 2.4.22-1.2115.nptlsmp #1 SMP Wed Oct 29 15:30:09 EST 2003 i686 i686 i386 GNU/Linux


      Both machines are using JDK 1.4.2_07



      Why would MainDeployer not even try to deploy an exploded JAR file on one machine while it does fine on another?

      I'm stumped.

        • 1. Re: JBoss MainDeployer doesn't pick up exploded JAR on my Li
          alchemista

          I've traced this farther down into URLDeploymentScanner. When I enable trace for the URLDeploymentScanner, it never shows it trying to deploy my exploded JAR (which is the problem).

          I can't see any reason why this should fail. Yes, my directory has a dot in it, but it should still be added as a URL to check.

          Very frustrating.

          • 2. Re: JBoss MainDeployer doesn't pick up exploded JAR on my Li
            alchemista

            Cause was found and seemingly unrelated. My HSQLDB data files were corrupted somehow. I had almost 1GB of data in them.

            When I was debugging with jdb, I noticed that the HSQLDB service was trying to be deployed before my exploded JAR. The deploying of the HSQLDB service was never finishing because of a huge delay, thus my files were never getting deployed since they were to be deployed after HSQLDB.

            Hope this helps someone else! I did this via a low-level jdb debug since it was on a remote Linux machine, would've been nicer within Eclipse.