You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Johannes Weberhofer (JIRA)" <ji...@apache.org> on 2010/01/21 16:13:59 UTC
[jira] Created: (GERONIMO-5040) PermGenSpace Problems and shut-down
issues when using the "Apache Commons Daemon" under Windows
PermGenSpace Problems and shut-down issues when using the "Apache Commons Daemon" under Windows
-----------------------------------------------------------------------------------------------
Key: GERONIMO-5040
URL: https://issues.apache.org/jira/browse/GERONIMO-5040
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components: Plugins
Affects Versions: 2.2, 2.1.4
Reporter: Johannes Weberhofer
Geronimo should - in my optinion - be started in "Java"-Mode. In Java (and the currently used exe-Mode) it is necessary to add all important options directly into the "startup"-"arguments" fields before the "-jar" line, which should be noticed in the Wiki. The issue is related to DAEMON-119.
At the "shutdown" page, it is necessary to explicitly select the "Java"-Mode and set a timeout (30 seconds or so); otherwise the geronimo server will simply be killed without any chance to terminate gracefully.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5040) PermGenSpace Problems and
shut-down issues when using the "Apache Commons Daemon" under Windows
Posted by "Johannes Weberhofer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851644#action_12851644 ]
Johannes Weberhofer commented on GERONIMO-5040:
-----------------------------------------------
In the meantime commons-daemon-1.0.2 was released fixing DAEMON-112 and several other bugs
> PermGenSpace Problems and shut-down issues when using the "Apache Commons Daemon" under Windows
> -----------------------------------------------------------------------------------------------
>
> Key: GERONIMO-5040
> URL: https://issues.apache.org/jira/browse/GERONIMO-5040
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Plugins
> Affects Versions: 2.1.4, 2.2
> Reporter: Johannes Weberhofer
> Attachments: GERONIMO-5040-service_pr.bat.diff
>
>
> Geronimo should - in my optinion - be started in "Java"-Mode. In Java (and the currently used exe-Mode) it is necessary to add all important options directly into the "startup"-"arguments" fields before the "-jar" line, which should be noticed in the Wiki. The issue is related to DAEMON-119.
> At the "shutdown" page, it is necessary to explicitly select the "Java"-Mode and set a timeout (30 seconds or so); otherwise the geronimo server will simply be killed without any chance to terminate gracefully.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5040) PermGenSpace Problems and
shut-down issues when using the "Apache Commons Daemon" under Windows
Posted by "Jack Cai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830825#action_12830825 ]
Jack Cai commented on GERONIMO-5040:
------------------------------------
See http://www.mail-archive.com/dev@commons.apache.org/msg13327.html
> PermGenSpace Problems and shut-down issues when using the "Apache Commons Daemon" under Windows
> -----------------------------------------------------------------------------------------------
>
> Key: GERONIMO-5040
> URL: https://issues.apache.org/jira/browse/GERONIMO-5040
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Plugins
> Affects Versions: 2.1.4, 2.2
> Reporter: Johannes Weberhofer
> Attachments: GERONIMO-5040-service_pr.bat.diff
>
>
> Geronimo should - in my optinion - be started in "Java"-Mode. In Java (and the currently used exe-Mode) it is necessary to add all important options directly into the "startup"-"arguments" fields before the "-jar" line, which should be noticed in the Wiki. The issue is related to DAEMON-119.
> At the "shutdown" page, it is necessary to explicitly select the "Java"-Mode and set a timeout (30 seconds or so); otherwise the geronimo server will simply be killed without any chance to terminate gracefully.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5040) PermGenSpace Problems and
shut-down issues when using the "Apache Commons Daemon" under Windows
Posted by "Johannes Weberhofer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804553#action_12804553 ]
Johannes Weberhofer commented on GERONIMO-5040:
-----------------------------------------------
I had the impression, there is no much movement on Apache Commons Daemon. Do you think, they will release a new version?
> PermGenSpace Problems and shut-down issues when using the "Apache Commons Daemon" under Windows
> -----------------------------------------------------------------------------------------------
>
> Key: GERONIMO-5040
> URL: https://issues.apache.org/jira/browse/GERONIMO-5040
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Plugins
> Affects Versions: 2.1.4, 2.2
> Reporter: Johannes Weberhofer
> Attachments: GERONIMO-5040-service_pr.bat.diff
>
>
> Geronimo should - in my optinion - be started in "Java"-Mode. In Java (and the currently used exe-Mode) it is necessary to add all important options directly into the "startup"-"arguments" fields before the "-jar" line, which should be noticed in the Wiki. The issue is related to DAEMON-119.
> At the "shutdown" page, it is necessary to explicitly select the "Java"-Mode and set a timeout (30 seconds or so); otherwise the geronimo server will simply be killed without any chance to terminate gracefully.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5040) PermGenSpace Problems and
shut-down issues when using the "Apache Commons Daemon" under Windows
Posted by "Jack Cai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804545#action_12804545 ]
Jack Cai commented on GERONIMO-5040:
------------------------------------
If I rememer correctly, the reason that I didn't use the java mode is because there is a defect in Apache Commons Daemon to detect the java.exe location in some cases. See https://issues.apache.org/jira/browse/DAEMON-112.
So to minimize the code difference between the geronimo version and the commons version, I falled back to use the exe mode, which should work. You can add the parameters to set the permgenspace if you want.
For the missing timeout setting, I didn't find that geronimo is killed before it stops gracefully. Maybe there are two few apps on my server.
Anyway, we are expecting that Apache Commons Daemon would do a new release which shall include all the pending patches. So hopefully after that we can update the batch file to use the Java mode.
> PermGenSpace Problems and shut-down issues when using the "Apache Commons Daemon" under Windows
> -----------------------------------------------------------------------------------------------
>
> Key: GERONIMO-5040
> URL: https://issues.apache.org/jira/browse/GERONIMO-5040
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Plugins
> Affects Versions: 2.1.4, 2.2
> Reporter: Johannes Weberhofer
> Attachments: GERONIMO-5040-service_pr.bat.diff
>
>
> Geronimo should - in my optinion - be started in "Java"-Mode. In Java (and the currently used exe-Mode) it is necessary to add all important options directly into the "startup"-"arguments" fields before the "-jar" line, which should be noticed in the Wiki. The issue is related to DAEMON-119.
> At the "shutdown" page, it is necessary to explicitly select the "Java"-Mode and set a timeout (30 seconds or so); otherwise the geronimo server will simply be killed without any chance to terminate gracefully.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5040) PermGenSpace Problems and shut-down
issues when using the "Apache Commons Daemon" under Windows
Posted by "Johannes Weberhofer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Johannes Weberhofer updated GERONIMO-5040:
------------------------------------------
Attachment: GERONIMO-5040-service_pr.bat.diff
> PermGenSpace Problems and shut-down issues when using the "Apache Commons Daemon" under Windows
> -----------------------------------------------------------------------------------------------
>
> Key: GERONIMO-5040
> URL: https://issues.apache.org/jira/browse/GERONIMO-5040
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Plugins
> Affects Versions: 2.1.4, 2.2
> Reporter: Johannes Weberhofer
> Attachments: GERONIMO-5040-service_pr.bat.diff
>
>
> Geronimo should - in my optinion - be started in "Java"-Mode. In Java (and the currently used exe-Mode) it is necessary to add all important options directly into the "startup"-"arguments" fields before the "-jar" line, which should be noticed in the Wiki. The issue is related to DAEMON-119.
> At the "shutdown" page, it is necessary to explicitly select the "Java"-Mode and set a timeout (30 seconds or so); otherwise the geronimo server will simply be killed without any chance to terminate gracefully.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.