[INTPAK-117] Support configuring JAVA_OPTS Created: 11/Dec/17  Updated: 20/Mar/18  Resolved: 20/Mar/18

Status: Closed
Project: integration-packaging
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: High
Reporter: Daniel Farrell Assignee: Tim Rozet
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

From trozet, originally on puppet-opendaylight/139

Currently we use _JAVA_OPTIONS to set extra cmd line java arguments. This method doesn't seem to work well with multiple arguments, and if setting options that karaf.sh will also set by default, ODL wont start. karaf.sh checks for "JAVA_OPTS" environment variable to override default java options. We should modify the way we configure java options to use that variable, so that a user can be explicit and deterministic in getting the exact java options he/she wants.

 Comments   
Comment by Tim Rozet [ 26/Feb/18 ]

Not only do we need to fix the right options variable to use, we also need to not configure this as part of systemd.  We should instead configure it in karaf.  This provides better support to a deployment tool (like TripleO with containers) not using systemd, as well as users who are not using systemd and instead invoke karaf script itself.

Comment by Tim Rozet [ 20/Mar/18 ]
INTPAK-117 Fixes configuring Java Opts Migrates configuring Java Options to a more appropriate variable, "JAVA_OPTS" which is read by karaf as optional settings a user may provide. The change also includes moving the configuration by setting the variable in the karaf file itself, rather than in systemd. This allows support for non-systemd OSes and deployment tools. Change-Id: I2fd3c2a70e8d5f0f0645bc9e354a535d05526fd3 Signed-off-by: Tim Rozet <trozet@redhat.com>
Generated at Wed Feb 07 20:03:39 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.