Martin Marcher wrote:
Thought I'd just mention that the default Tomcat 5.5 install with Debian Etch is setup to use 128MB, and this can be changed in the init.d script (tomcat5.5):Chris i just mistakenly posted that to your address and got an answer from bluebottle.com could you at least not blacklist me in case we have to get in touch by some incident in the future so we won't wonder why mail isn't arriving. oh and I f***** hate those verification tools... ---------- Forwarded message ---------- From: Martin Marcher <martin@marcher.name> Date: 21.09.2007 19:13 Subject: Re: Basic Tomcatt5.5 Admin question To: Nyizsnyik Ferenc <nyizsa@bluebottle.com> 2007/9/21, Nyizsnyik Ferenc <nyizsa@bluebottle.com>:On Fri, 21 Sep 2007 07:42:59 -0700 Dancing Fingers <bcl122@netscape.net> wrote:Hi guys, I finally got Tomcat5.5 going on Etch AMD and I start studying the JSP developers guide but I get stuck in the beginning. The book says to create a new directory under ROOT but I don't have permission in my default account. The last install I did a chgrp / user/share/tomcat5.5-webapps/ROOT www-data but I screwed the package up so bad that I re-installed the system. Could anyone tell me how the is typically done?when learning tomcat/jboss just download the tarball unpack it to some dir and use startup.sh (tomcat) or run.sh (jboss) to run it. both can be a ressource hog and i think tomcat is by default configured to use 256MB Ram for doing nothing, nada, zip, null, zero.
# Set java.awt.headless=true if CATALINA_OPTS is not set so the # Xalan XSL transformer can work without X11 display on JDK 1.4+# It also looks like the default heap size of 64M is not enough for most cases
# se the maximum heap size is set to 128M
if [ -z "$CATALINA_OPTS" ]; then
CATALINA_OPTS="-Djava.awt.headless=true -Xmx128M"
fi
you then also have the opportunity to do fast testing of libraries that require certain tomcat versions but will otherwise ease up your life or simply deploy your playground to a tomcat6 just to see how it behaves (or even jboss for that matter) i think to learn the jsp side this is the better approach (the same is true for eclipse imho, which if you do serious development in J2EE will end up anyway having multiple times on disk even in the same version because 2 plugins just won't play together and you don't have the time to fix it but rather work, so you download eclipse 3.2 the 3rd time set up a worskpace and configure your plugins for the project using $PLUGIN there.... (hope someone can still follow what I mean) martin -- http://noneisyours.marcher.name http://feeds.feedburner.com/NoneIsYours