Uploaded image for project: 'OpenIDM'
  1. OpenIDM
  2. OPENIDM-1989

2 different boot.properties files are loaded

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Not a defect
    • OpenIDM 3.0.0
    • OpenIDM 3.0.0
    • documentation, Installation
    • None
    • OpenIDM version "3.0.0-SNAPSHOT" (revision: 3476) jenkins-OpenIDM-3249 null

    Description

      When following the migration instructions to upgrade from 2.1 to 3.0, a couple of boot.properties files are present in the end:

      • one in the project location (which is my OpenIDM 2.1 installation directory actually, that is /opt/OpenIDM)
      • one in the OpenIDM 3.0 conf/boot directory (/opt/openidm-3.0/conf/boot in my case)

      The messages I see on the console when running the startup script with the "-p" option are as follows:

      nohup ./startup.sh -p /project_dir 2>/dev/null >./logs/nohup.out&

      Executing ./startup.sh...

      Using OPENIDM_HOME: /opt/OpenIDM
      Using OPENIDM_OPTS: -Xmx1024m -Xms1024m
      Using LOGGING_CONFIG: -Djava.util.logging.config.file=/opt/OpenIDM/conf/logging.properties
      Using boot properties at /opt/openidm-3.0/conf/boot/boot.properties
      -> OpenIDM version "3.0.0-SNAPSHOT" (revision: 3476) jenkins-OpenIDM-3249 null

      Using OPENIDM_HOME: /opt/OpenIDM
      Using OPENIDM_OPTS: -Xmx1024m -Denvironment=Dev
      Using LOGGING_CONFIG: -Djava.util.logging.config.file=/opt/OpenIDM/conf/logging.properties
      Using boot properties at /opt/openidm-3.0/conf/boot/boot.properties
      Using boot properties at /opt/OpenIDM/conf/boot/boot.properties

      So, it seems like the migration instructions misses something about the boot.properties file.

      Attachments

        Activity

          People

            Lana Lana Frost
            cgrosjean Cyril Grosjean
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: