[wildfly-dev] MORE_JAVA_OPTS in standalone.sh

[Darran Lofthouse]

One issue with that however is how you would cope with duplicate or 
conflicting options within the OPTS, all it could take is one conflict a 
script can not resolve and you are back to just defining the whole string.

Regards,
Darran Lofthouse.


On 18/03/15 12:42, Arun Gupta wrote:
> I'd like to not override the default JAVA_OPTS used by WildFly,
> instead add my own value to it. I think that's where MORE_JAVA_OPTS or
> EXTRA_JAVA_OPTS could be useful.
>
> Copy/pasting the existing JAVA_OPTS and including my own does not feel right :)
>
> Arun
>
> On Tue, Mar 17, 2015 at 10:22 PM, Jaikiran Pai <jai.forums2013 at gmail.com> wrote:
>> Hi Arun,
>>
>> The WildFly startup scripts allow you to *override* the JAVA_OPTS by setting
>> an environment variable of that same name. See the standalone.conf (for *nix
>> OS) file for details. From what I see, there's no option to append to the
>> default JAVA_OPTS, by setting an environment variable. This could be worked
>> around (in a bit brittle manner) by setting the overriding environment
>> variable value to contain the default JAVA_OPTS (copied over from
>> standalone.conf) plus the other custom/specific ones that the caller wants
>> to pass.
>>
>> -Jaikiran
>>
>> On Wednesday 18 March 2015 10:27 AM, Arun Gupta wrote:
>>>
>>> Can standalone.sh script be extended such that it takes an additional
>>> environment variable that is then added to JAVA_OPTS during startup?
>>>
>>> This can be used for passing additional Java options from WildFly
>>> Docker image. Cursory look at the script does not reveal anything like
>>> that exist.
>>>
>>> Arun
>>>
>>>
>>
>
>
>