You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Piotr Szczepanik (JIRA)" <ji...@apache.org> on 2007/11/26 23:19:43 UTC

[jira] Updated: (GERONIMODEVTOOLS-252) VM arguments are reverted to default ones after starting the server

     [ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Piotr Szczepanik updated GERONIMODEVTOOLS-252:
----------------------------------------------

    Environment: Ubuntu Linux 7.10 (i386), Eclipse 3.3.1, Java 1.6.0_03-b05

> VM arguments are reverted to default ones after starting the server
> -------------------------------------------------------------------
>
>                 Key: GERONIMODEVTOOLS-252
>                 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-252
>             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: Critical
>
> 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.