geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim McConnell (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMODEVTOOLS-252) VM arguments are reverted to default ones after starting the server
Date Wed, 28 Nov 2007 18:11:43 GMT

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

Tim McConnell closed GERONIMODEVTOOLS-252.
------------------------------------------

       Resolution: Invalid
    Fix Version/s: 2.0.2

Closing per Kan and Piotr

> 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: Minor
>             Fix For: 2.0.2
>
>         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.


Mime
View raw message