[
https://issues.apache.org/jira/browse/GERONIMO-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Warner updated GERONIMO-3902:
-----------------------------------
Attachment: Geronimo-3902.patch
I modified the start-server,default.groovy script so that it checked to see if
any java opts were added on the command line. It's an all or nothing check so
this script won't set anything even if it's an unrelated java opt that's been
set. I had to make a change in StartServerCommand.groovy since the script was
processed after some default java opts were added to the list. This made the
check always fail. I moved the addition of those default java opts to until
after the script is processed to fix this. I haven't taken a look at the other
command scripts, but this same change might need to be made in them as well to
allow the same functionality in the rc.d scripts if we wanted that.
> start-server, default.groovy in etc/rc.d overrides -Xmx value when starting
> server using gshell
> -----------------------------------------------------------------------------------------------
>
> Key: GERONIMO-3902
> URL: https://issues.apache.org/jira/browse/GERONIMO-3902
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: startup/shutdown
> Affects Versions: 2.1, 2.1.1, 2.2
> Reporter: Jason Warner
> Assignee: Jason Warner
> Fix For: 2.1.1, 2.2
>
> Attachments: Geronimo-3902.patch
>
>
> The start-server, default.groovy file is included in etc/rc.d directory and
> contains a command to set the max heap size for geronimo when starting
> through gshell. This file overrides any max heap size values that are set
> via the command line causing issues when starting the server with non-default
> max heap values.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
