Application Server 7
  1. Application Server 7
  2. AS7-1752

Starting multiple standalone servers from the same install is not clean

    Details

    • Type: Task Task
    • Status: Resolved Resolved (View Workflow)
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: 7.0.0.Final, 7.0.1.Final
    • Fix Version/s: 7.1.0.Final
    • Component/s: Server
    • Labels:
      None
    • Similar Issues:
      Show 10 results 

      Description

      It should be easy to copy the standalone dir to another dir (say, "serverB" in the same level in the FS tree) and launch a second server using ./standalone.sh -Djboss.server.base.dir=serverB

      It somewhat works, but things that aren't as smooth as they should be:

      a) The resolution of jboss.server.base.dir isn't very smart. For example, to do the common thing and launch the script from within the bin dir you have to either use an absolute path to instance1/2 or do something kludgey like:

      ./standalone.sh -Djboss.server.base.dir=../serverB

      If the path is relative and resolving it doesn't result in a file that exists, an attempt should be made to resolve against jboss.home.dir.

      2) The launch script directly references the standalone/configuration/logging.properties and standalone/log/boot.log files. So, if those files aren't present the server doesn't boot properly, and both, e.g. serverA and serverB will use the standalone/log/boot.log as their boot log file (where logging goes until the boot process starts the logging subsystem.)

        Issue Links

          Activity

          Hide
          Brian Stansberry
          added a comment -

          AS7-2494 is the JIRA for fixing the logging configuration aspect.

          Show
          Brian Stansberry
          added a comment - AS7-2494 is the JIRA for fixing the logging configuration aspect.
          Hide
          Robert Reimann
          added a comment -

          The second issue...

          2) The launch script directly references the standalone/configuration/logging.properties and standalone/log/boot.log files. So, if those files aren't present the server doesn't boot properly, and both, e.g. serverA and serverB will use the standalone/log/boot.log as their boot log file (where logging goes until the boot process starts the logging subsystem.)

          ...is still present in 7.1.2.Final when using Mac OS X.

          Should i create a new Jira Issue on this or can someone reopen this one?

          Show
          Robert Reimann
          added a comment - The second issue... 2) The launch script directly references the standalone/configuration/logging.properties and standalone/log/boot.log files. So, if those files aren't present the server doesn't boot properly, and both, e.g. serverA and serverB will use the standalone/log/boot.log as their boot log file (where logging goes until the boot process starts the logging subsystem.) ...is still present in 7.1.2.Final when using Mac OS X. Should i create a new Jira Issue on this or can someone reopen this one?
          Hide
          jaikiran pai
          added a comment -

          The second issue...

          2) The launch script directly references the standalone/configuration/logging.properties and standalone/log/boot.log files. So, if those files aren't present the server doesn't boot properly, and both, e.g. serverA and serverB will use the standalone/log/boot.log as their boot log file (where logging goes until the boot process starts the logging subsystem.)

          ...is still present in 7.1.2.Final when using Mac OS X.

          Please create a separate JIRA for that one and add the relevant details to reproduce it.

          Show
          jaikiran pai
          added a comment - The second issue... 2) The launch script directly references the standalone/configuration/logging.properties and standalone/log/boot.log files. So, if those files aren't present the server doesn't boot properly, and both, e.g. serverA and serverB will use the standalone/log/boot.log as their boot log file (where logging goes until the boot process starts the logging subsystem.) ...is still present in 7.1.2.Final when using Mac OS X. Please create a separate JIRA for that one and add the relevant details to reproduce it.
          Hide
          Anurag Debnath
          added a comment -

          A user faced similar issue and I have a JIRA created with details to reproduce the issue.

          https://issues.jboss.org/browse/JBPAPP-9392

          Show
          Anurag Debnath
          added a comment - A user faced similar issue and I have a JIRA created with details to reproduce the issue. https://issues.jboss.org/browse/JBPAPP-9392

            People

            • Assignee:
              Brian Stansberry
              Reporter:
              Brian Stansberry
            • Votes:
              2 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: