« Return to Thread: (no subject)
Agree with you
De : Deneux,
Christophe [mailto:christophe.deneux@...]
Envoyé : lundi 12 janvier
2009 12:45
À : petals-dev@...;
petals-users@...; petals-dev@...
Objet : [petals-dev]
RE : PEtALS startup script - Xmx option
Please use an
default external env var to set extra options(ex: PETALS_OPTS)
And replace -Xmx with this env var:
java ... ${PETALS_OPTS}
So it is easy to set the env var in our user profile, and not modify
startup script.
_______________________________________________________________________________
Christophe
DENEUX / Capgemini Sud / Méditerranée
Integration Architect / OW2 PEtALS Comitter
Tel: + 33 4 93 95 55 92 / www.capgemini.com
Porte de
l'Arénas - Entrée B / 455 Promenade des Anglais / 06200 Nice / FRANCE
Join the Collaborative Business Experience
_______________________________________________________________________________
Please consider
the environment and do not print this email unless absolutely necessary.
Capgemini encourages environmental awareness.
De:
Date: lun. 12/01/2009 11:56
À: petals-users@...; petals-dev@...
Objet : [petals-dev] PEtALS
startup script - Xmx option
Hi,
The current PEtALS startup scripts set a maximal memory size to 1024M
PEtALS, in standard basic mode, use around 25M.
As some (virtual) machines don't have 1024M of memory,
I want to remove this option. The default value is 64M, which is already
enough.
If someone needs a higher value, it is always possible to set it in the
script.
Does anybody opposed to that?
« Return to Thread: (no subject)
| Free embeddable forum powered by Nabble | Forum Help |