nbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig.
>> Diese Nachricht dient lediglich dem Austausch von Informationen und
>> entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten
>> Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den
>> I
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Date: Mon, 17 A
Susan Teague Rector:
> I've searched around on the net and have found differing opinions about
> where to actually place the java_opts env var for tomcat.
> Should this variable be in /tomcat/bin/catalina.sh? When I set it in
> this file and then print out all env vars, it looks like it is not s
Something will eventually call bin/startup.sh (or bin/catalina.sh).
Changing bin/startup.sh (or bin/catalina.sh) is typically a bad idea.
Whatever is calling that should export JAVA_OPTS first.
For example:
export JAVA_OPTS='-Xmx256m'
- or -
export JAVA_OPTS='-Xmx256m -Djava.awt.headless=true'
Susan Teague Rector wrote:
> Hello all,
> I've searched around on the net and have found differing opinions about
> where to actually place the java_opts env var for tomcat.
> Should this variable be in /tomcat/bin/catalina.sh? When I set it in
> this file and then print out all env vars, it looks
Hello all,
I've searched around on the net and have found differing opinions about
where to actually place the java_opts env var for tomcat.
Should this variable be in /tomcat/bin/catalina.sh? When I set it in
this file and then print out all env vars, it looks like it is not set.
How do I set