geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Piotr Szczepanik (JIRA)" <>
Subject [jira] Updated: (GERONIMODEVTOOLS-252) VM arguments are reverted to default ones after starting the server
Date Tue, 27 Nov 2007 18:19:43 GMT


Piotr Szczepanik updated GERONIMODEVTOOLS-252:

    Priority: Minor  (was: Critical)

I am sorry,
I have overlooked that option in the server settings. Thanks for help.

On the other hand I keep wondering whether putting this kind of configuration in the server
configuration is the right choice when it comes to usability?
1. Many other servers have it in the Launch configuration and...
2. it is actually a launch setting - not the server's one.

What do you think? But of course it's not a critical issue anymore.

> VM arguments are reverted to default ones after starting the server
> -------------------------------------------------------------------
>                 Key: GERONIMODEVTOOLS-252
>                 URL:
>             Project: Geronimo-Devtools
>          Issue Type: Bug
>          Components: eclipse-plugin
>    Affects Versions: 2.0.0
>         Environment: Ubuntu Linux 7.10 (i386), Eclipse 3.3.1, Java 1.6.0_03-b05
>            Reporter: Piotr Szczepanik
>            Priority: Minor
>         Attachments: ServerVMArguments.jpg
> If you change VM arguments in the "Run Dialog" for Apache Geronimo (ie. adding "-XX:MaxPermSize=128m"
which is needed on my platform) they are reverted back to default value after you successfully
the server.
> What is worse they are not applied to the server that has just started.
> Steps to reproduce:
> 1. Change VM arguments
> 2. Start the server
> 3. Wait for the start of the server
> 4. Check the VM arguments
> 5. They are reverted back to default one

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message