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 22:54:43 UTC
[jira] Created: (GERONIMODEVTOOLS-252) VM arguments are reverted to
default ones after starting the server
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
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.
[jira] Updated: (GERONIMODEVTOOLS-252) VM arguments are reverted to
default ones after starting the server
Posted by "Kan Ogawa (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kan Ogawa updated GERONIMODEVTOOLS-252:
---------------------------------------
Attachment: ServerVMArguments.jpg
> 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
> 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.
[jira] Updated: (GERONIMODEVTOOLS-252) VM arguments are reverted to
default ones after starting the server
Posted by "Piotr Szczepanik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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: 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
> 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.
[jira] Updated: (GERONIMODEVTOOLS-252) VM arguments are reverted to
default ones after starting the server
Posted by "Piotr Szczepanik (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (GERONIMODEVTOOLS-252) VM arguments are reverted
to default ones after starting the server
Posted by "Kan Ogawa (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546066 ]
Kan Ogawa commented on GERONIMODEVTOOLS-252:
--------------------------------------------
Hi Piotr,
Many application launcher configurations besides J2EE server may be put in Eclipse platform.
So I think that it is very convenient there is the "VM Arguments" field for Geronimo server in its overview page.
Anyhow, this issue is not bug. it should be closed.
If you want to discuss about this topic furthermore, I recommend that you use geronimo-user mailing list.
Thanks,
Kan Ogawa
> 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
> 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.
[jira] Commented: (GERONIMODEVTOOLS-252) VM arguments are reverted
to default ones after starting the server
Posted by "Kan Ogawa (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545657 ]
Kan Ogawa commented on GERONIMODEVTOOLS-252:
--------------------------------------------
Piotr,
Set VM arguments value to the "Server VM Arguments" field in Geronimo server overview page, and start the server.
( See my attached screen shot. )
> 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
> 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.
[jira] Closed: (GERONIMODEVTOOLS-252) VM arguments are reverted to
default ones after starting the server
Posted by "Tim McConnell (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (GERONIMODEVTOOLS-252) VM arguments are reverted to
default ones after starting the server
Posted by "Piotr Szczepanik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Piotr Szczepanik updated GERONIMODEVTOOLS-252:
----------------------------------------------
Hi Kan,
it's not a bug indeed, so we can close it.
Thanks,
Piotr Szczepanik
> 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
> 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.