Petals ESB Container

Externalize Java options

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 4.1.0
  • Fix Version/s: 4.2.0
  • Component/s: Launcher
  • Security Level: Public
  • Description:

    The startup script contains the definition of JVM options to use with Petals. To avoid to introduce defect when updating the startup script, Java options should be externalized in an environment file.

  • Environment:
    -

Activity

Hide
Christophe DENEUX added a comment - Thu, 6 Jun 2013 - 09:25:53 +0200 - edited

Caution, on Debian-based systems several Petals container can run concurrently, so the environement configuration should be done per container.

Show
Christophe DENEUX added a comment - Thu, 6 Jun 2013 - 09:25:53 +0200 - edited Caution, on Debian-based systems several Petals container can run concurrently, so the environement configuration should be done per container.
Hide
Christophe DENEUX added a comment - Thu, 6 Jun 2013 - 16:22:44 +0200

Fixed in trunk.

For the ZIP archive, a new configuration file has been introduced to set JAVA options: $PETALS_HOME/conf/env.sh
For the Debian packages:

  • a new default configuration file has been introduced to set the default JAVA options: /etc/petals-esb/default-env.sh
  • this new default configuration can be replaced by a dedicated configuration set in the container configuration using the property 'petals.environment.config.file'. This property accepts a relative file as value only for container configuration provided with a local URL (file://...). Otherwise an absolute file is required.
Show
Christophe DENEUX added a comment - Thu, 6 Jun 2013 - 16:22:44 +0200 Fixed in trunk. For the ZIP archive, a new configuration file has been introduced to set JAVA options: $PETALS_HOME/conf/env.sh For the Debian packages:
  • a new default configuration file has been introduced to set the default JAVA options: /etc/petals-esb/default-env.sh
  • this new default configuration can be replaced by a dedicated configuration set in the container configuration using the property 'petals.environment.config.file'. This property accepts a relative file as value only for container configuration provided with a local URL (file://...). Otherwise an absolute file is required.

People

Dates

  • Created:
    Thu, 6 Jun 2013 - 09:24:23 +0200
    Updated:
    Thu, 6 Jun 2013 - 16:22:44 +0200
    Resolved:
    Thu, 6 Jun 2013 - 16:22:44 +0200