8:01 a.m.
Maybe the original intention was not to have the configuration done in
the server at all, so a new .conf file will not accomplish that.
If that is the case I'd propose a WILDFLY_EXTRA_JAVA_OPTS to prevent
mixing up with any generic JAVA_OPTS that may be set (or our nice test
for a stray JAVA_OPTS would be moot).
Fernando
On 2015-03-18 8:55 AM, Fernando Nasser wrote:
On 2015-03-18 8:48 AM, Fernando Nasser wrote:
> On 2015-03-18 8:42 AM, 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 :)
> JAVA_OPTS="${JAVA_OPTS} <your new args>"
Ah, I understand now, you don't want to modify your standalone.conf file.
Maybe we could source a custom .conf file so some additional changes
could be made w/o touching the shipped one.
So after
if [ -r "$RUN_CONF" ]; then
. "$RUN_CONF"
fi
we'd also source some other file CUSTOM_CONF to get any changes.
Fernando
>
>
>> Arun
>>
>> On Tue, Mar 17, 2015 at 10:22 PM, Jaikiran Pai <jai.forums2013(a)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
>>>>
>>>>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev