2 Replies Latest reply on Dec 9, 2008 8:56 PM by peterj

    Jboss shutdown.sh dependency on client library

      We wanted to bundle JBoss with the minimal set of files and with this intent we moved the client folder within jboss
      Also we removed the unused "domain" folder within the server directory.

      With this the JBoss stared up fine, but the shutdown script seems to have a dependency on $JBOSS_HOME/client/jbossall-client.jar

      And the shutdown script did throw
      NoClassDefFoundError for org.jboss.system.server.ServerImplMBean

      Any reason for the server shutdown script to have a client library dependency?



        • 1. Re: Jboss shutdown.sh dependency on client library
          noelo

          I think the shutdown process makes a jmx call into the app server to shut it down cleanly..

          • 2. Re: Jboss shutdown.sh dependency on client library
            peterj

            The shutdown app is a JBoss client, hence the reason it uses the JARs in the client directory. You could figure out the exact set of JARs required and provide only those in the "client" directory. The jbossall-client.jar is a super JAR that contain the contents of most of the other JAR files in the client directory, so you could replace it by a series of individual JARs. Or you could just provide jbossall-client.jar.