3 Replies Latest reply on Apr 25, 2002 2:39 PM by adrian.brock

    JBOSS 3.0.0RC1 Multiple Configurations

      In the past if you wanted to run a different configuration, your would supply the directory name of the configuration after the run.sh command, which would be pasted on the the Main process.

      This doesn't seem to work in this version. At first it did startup, but after careful examination it was actually still using default. I moved that directory and specified my alternate configuration. Now nothing works. Any tips? Has something change?

      I've tried to follow the bread crums but there isn't even a org.jboss.Main in the source code. I don't know if it is automatically generated or what?

      Thanks.

        • 1. Re: JBOSS 3.0.0RC1 Multiple Configurations

          Try

          ./run.sh -help
          run.bat -help

          then

          ./run.sh -c myconfig
          run.bat -c myconfig

          Regards,
          Adrian

          • 2. Re: JBOSS 3.0.0RC1 Multiple Configurations
            sfiltrom

            Starting with different configurations is fine but JBoss isn't running.
            The configuration directories are softlinks from $JBOSS_HOME/server to user directories where the configuration and deployment stuff is. Running ./run.sh -c nearly crashes with lots of exceptions. The complete stdout is on http://user.cs.tu-berlin.de/~sfiltrom/jboss .
            What went wrong? We edited the tomcat4-service.xml to enable cookies but the other files are unchanged
            Thanks!

            • 3. Re: JBOSS 3.0.0RC1 Multiple Configurations

              I can see

              #tomcat4-service.xml#
              tomcat4-service.xml~

              trying to be deployed as the first error.

              I can also see jboss-net.sar and
              webtest.ear trying to be deployed twice?

              There is also something about a scratch directory not
              being useable.

              Shutdown looks broken with NullPointerExceptions.
              This looks more serious. It seems to have lost
              track of the object names?

              Perhaps you can explain the deployment config changes?
              You will also get more info from
              server/myconfig/log/server.log

              Regards,
              Adrian