RE: [enhydra] New enhydra releases

Hi,

"OutOfMemory" should be easy to resolve!

We've introduced (exposed) this (memory based) JVM configuration parameters
for the users.
They get configured trough enhydra configuration process ("configure" shell
script) and are the part of the "build.properties" parameters.

Properties are:

jvmxms=256
jvmxmx=512
jvmps=32
jvmmps=128

The faster way would be (if you have everything already configured) to edit
those values directly in corresponding configuration files!

Depending of you startup type:

1. Wrapper based startup
- Parameters are configured in "wrapper.conf" file placed in
"<multiserver>/conf" directory
...
wrapper.java.additional.4=-Xms256m
wrapper.java.additional.5=-Xmx512m
wrapper.java.additional.6=-XX:PermSize=32m
wrapper.java.additional.7=-XX:MaxPermSize=128m
...

2. Catalina shell based startup
- Parameters are configured in "catalina.sh" file placed in
"<multiserver>/bin" directory
...
# Additional Enhydra JVM memory setting
JAVA_OPTS="-Xms256m $JAVA_OPTS"
JAVA_OPTS="-Xmx512m $JAVA_OPTS"
JAVA_OPTS="-XX:PermSize=32m $JAVA_OPTS"
JAVA_OPTS="-XX:MaxPermSize=128m $JAVA_OPTS"
...


Please, play around with those parameter settings! 
This can be crucial for your production performance (not only for PermSize
problem in your development environment).

Regards,
  Slobodan Vujasinovic


-----Original Message-----
From: Petr Stehlik [mailto:pstehlik@xxxxxxxxxx] 
Sent: Tuesday, 18 December, 2007 11:25
To: enhydra@xxxxxxxxxxxxx
Subject: Re: [enhydra] New enhydra releases

Slobodan Vujasinovic wrote:
> Hi,

Slobodan,

> You are right, tomcat documentation, manager and host-manager are not 
> included in enhydra runtime distribution. This is bug in our build 
> procedure and it will be fixed in next enhydra release!

Very good.

> Also, you are right about "configureBase" shell script (it is not 
> upgraded to the latest directory changes introduced with Tomcat 6.0).

I see. BTW, I was hoping the Tomcat 6 will finally resolve the OutOfMemory
problem (PermGen space) that Enhydra is suffering from ever since (it's
actually a JDK bug, most probably) but it still happens after several
deploy/undeploys..

> This scenario can be useful if you are having multiple enhydra 
> instances running on the same physical machine but (of course) using 
> different connection and shutdown ports (easier maintenance and lower 
> hard disk requirements).
> 
> "configureBase" allows you create and configure such (CATALINA_BASE) 
> directories!

This sounds great. I'll try to remember such easy and clear explanation but
if you added it to the README.txt it would be even better (as I tend to
forget everything :-)

> Regarding "configure" shell script, it should be executed with "-jdk.dir"
> parameter!

The README.txt says:
======================
To configure the enhydra distribution:

cd to '<enhydra_root>/multiserver/enhydra' directory and type in the
following command:

configure    (Windows)

./configure  (Linux)
======================

So no mention of -jdk.dir...

Also, few lines below where you explain how to prepare the build.properties
file you say:

"jdk.dir - the path to your installation of the Java Development Kit
(obligational if environment variable JAVA_HOME isn't (properly) defined)"

So basically the -jdk.dir is not documented as a requirement for correct
configuration.

> In our next release, we'll also implement $JAVA_HOME environment 
> variable recognition.

Something as simple as the following patch would work:

--- multiserver/enhydra/configure.old   2007-10-26 18:37:38.000000000 +0200
+++ multiserver/enhydra/configure       2007-12-18 10:09:43.000000000 +0100
@@ -99,7 +99,6 @@
         then
                 JAVA_HOME=$(expr "x$param" : 'x[^=]*=\(.*\)')
                 export JAVA_HOME
-               jdk_DOT_dir=$JAVA_HOME
                 continue
         fi

@@ -315,6 +314,7 @@

  done

+jdk_DOT_dir=$JAVA_HOME

  export PATH=$JAVA_HOME/bin:$PATH


> Thank you very much for those problem reports!
> We'll resolve those issues for our next release.

Thanks for your great work on TAS/TDS.

Petr





--
You receive this message as a subscriber of the enhydra@xxxxxxxxxxxxx mailing 
list.
To unsubscribe: mailto:enhydra-unsubscribe@xxxxxxxxxxxxx
For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws