geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jack Cai (JIRA)" <>
Subject [jira] Commented: (GERONIMO-5040) PermGenSpace Problems and shut-down issues when using the "Apache Commons Daemon" under Windows
Date Mon, 25 Jan 2010 14:23:34 GMT


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

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

> PermGenSpace Problems and shut-down issues when using the "Apache Commons Daemon" under
> -----------------------------------------------------------------------------------------------
>                 Key: GERONIMO-5040
>                 URL:
>             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
> 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.

View raw message