You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Franck Routier <Fr...@hospvd.ch> on 2001/09/13 14:56:41 UTC
New xml parser on startup in Tomcat ?
Hi,
I'm still fighting with the same problem :
Tomcat, just out of the box, won't start and gives me a OutOfMemoryError on
startup, then dies.
Apparently, it does this while reading it's conf file.
The problem occurs with versions 3.3-b2 and 4.0-rc1.
The interresting point is that version 3.2.3, bundled with jboss 2.4.0 WORKS,
but the same version (3.2.3) bundled with jboss 2.4.1 doesn't (same error).
I read this in jboss forum, on another subject, but I thing it might be
related :
"The problem is that in Tomcat 3.x you have to put your parsers in the
classpath before everything else becouse they are no relying on system
properties to decide which parser to use. There is an explanation on how to
to this is tomcat´s archives. In Tomcat 4.x the parser loaded by Tomcat for
it´s own use does not conflict on the parser used by applications. The
problem is solved in last version of JBOSS by using system properties to
define which parser to use. I´ll look for the archives and post them later "
Sadly I'm not skilled enough to tell if this is really related...
Any idea why Tomcat won't start on my machine, except when launched with
jboss 2.4.0...
I use jdk 1.3-ppc from Blackdown on Debian Gnu-Linux-ppc.
Thanks,
Franck
Re: Tomcat + gcj + LinuxPPC ?
Posted by Anthony Green <gr...@redhat.com>.
Franck wrote:
> 1) Is there a quickstart howto or any kind of documentation somewhere to
> get me on the track ?
No, not yet. There is a mailing list for questions (CC'd -
rhug-rhats@sources.redhat.com, it's also archived on the web). I'll try to
put something together in the next couple of days.
> 2) Would gcj-3.0 1:3.0.2-0pre010908 be new enough ? (there is a .deb for it
> that would make it easier for me) ?
Unfortunately not. This is bleeding edge stuff, and requires the very latest
CVS sources for GCC (what will eventually become 3.1). Follow these
instructions for building...
http://gcc.gnu.org/java/build-snapshot.html
We're fixing runtime and compiler bugs as they are discovered, but I'm very
happy with what's working today.
AG
Tomcat + gcj + LinuxPPC ?
Posted by Franck Routier <Fr...@hospvd.ch>.
At 01:38 20.09.2001 -0700, Anthony Green wrote:
>Franck wrote:
>
> > Any idea on how to make it start quicker ?
>
>Yes, help me test and debug Tomcat built with gcj on LinuxPPC. Tomcat is
>precompiled to native code (like C/C++). Servlets are compiled to shared
>libraries. When I finish hacking GnuJavaCompiler for jasper, JSP pages will
>also be compiled to shared libraries and loaded.
>
>Gcj is known to work well on PowerPC Linux systems. Tomcat starts in just a
>couple of seconds on my x86 box. I would expect the same on PowerPC Linux.
>You'll need the very latest GCC development sources which includes important
>fixes for gcj and libgcj (the runtime library).
>
>See http://sources.redhat.com/rhug
>
>AG
Hey, why not ...?
Just two questions :
1) Is there a quickstart howto or any kind of documentation somewhere to
get me on the track ?
2) Would gcj-3.0 1:3.0.2-0pre010908 be new enough ? (there is a .deb for it
that would make it easier for me) ?
Thanks,
Franck
-------
Franck Routier
SHC - Support FIH9
Re: New xml parser on startup in Tomcat ?
Posted by Jonathan Eric Miller <je...@uchicago.edu>.
The reason it's slow is because it's creating a SecureRandom object (used
for creating session IDs and for SSL) and that is true for all platforms.
There's a way to speed it up, but, it is supposed to decrease security.
Jon
----- Original Message -----
From: "Anthony Green" <gr...@redhat.com>
To: <to...@jakarta.apache.org>; <Fr...@hospvd.ch>
Sent: Thursday, September 20, 2001 3:38 AM
Subject: Re: New xml parser on startup in Tomcat ?
> Franck wrote:
> > It works perfectly, although Tomcat is veeeeeeeeeery long to start
(almost
> > as long as netbeans !)
> > The point is that there is no JIT implementation for Linux PPC :-(
> > But still, it's long, even after I commented out the Tomcat-Apache in
> > server.xml...
> >
> > Any idea on how to make it start quicker ?
>
> Yes, help me test and debug Tomcat built with gcj on LinuxPPC. Tomcat is
> precompiled to native code (like C/C++). Servlets are compiled to shared
> libraries. When I finish hacking GnuJavaCompiler for jasper, JSP pages
will
> also be compiled to shared libraries and loaded.
>
> Gcj is known to work well on PowerPC Linux systems. Tomcat starts in just
a
> couple of seconds on my x86 box. I would expect the same on PowerPC
Linux.
> You'll need the very latest GCC development sources which includes
important
> fixes for gcj and libgcj (the runtime library).
>
> See http://sources.redhat.com/rhug
>
> AG
>
>
Re: New xml parser on startup in Tomcat ?
Posted by Anthony Green <gr...@redhat.com>.
Franck wrote:
> It works perfectly, although Tomcat is veeeeeeeeeery long to start (almost
> as long as netbeans !)
> The point is that there is no JIT implementation for Linux PPC :-(
> But still, it's long, even after I commented out the Tomcat-Apache in
> server.xml...
>
> Any idea on how to make it start quicker ?
Yes, help me test and debug Tomcat built with gcj on LinuxPPC. Tomcat is
precompiled to native code (like C/C++). Servlets are compiled to shared
libraries. When I finish hacking GnuJavaCompiler for jasper, JSP pages will
also be compiled to shared libraries and loaded.
Gcj is known to work well on PowerPC Linux systems. Tomcat starts in just a
couple of seconds on my x86 box. I would expect the same on PowerPC Linux.
You'll need the very latest GCC development sources which includes important
fixes for gcj and libgcj (the runtime library).
See http://sources.redhat.com/rhug
AG
Re: New xml parser on startup in Tomcat ?
Posted by Franck Routier <Fr...@hospvd.ch>.
Thanks, it was it !
the command for Blackdown JVM is (Linux) :
export CATALINA_OPTS="-mx=128m" (nice machine, but not that big :-)
$CATALINA_HOME/bin/catalina.sh start
It works perfectly, although Tomcat is veeeeeeeeeery long to start (almost
as long as netbeans !)
The point is that there is no JIT implementation for Linux PPC :-(
But still, it's long, even after I commented out the Tomcat-Apache in
server.xml...
Any idea on how to make it start quicker ?
Franck
At 09:06 13.09.2001 -0700, you wrote:
>"OutOfMemoryError" means that your JVM is not providing enough heap space
>to run Tomcat. If I remember correctly, the Blackdown JVM has a *very*
>small default heap size, while the heap size on the Sun and IBM JVMs is
>much larger.
>
>What you need to do is consult the documentation from Blackdown and figure
>out how to increase the heap size to at least 64 megabytes. You can then
>configure Tomcat startup to use this by setting the environment variable
>TOMCAT_OPTS (for Tomcat 3.x) or CATALINA_OPTS (for Tomcat 4.0). Here's
>what you would do on the *Sun* JDK to increase heap size to 512 megabytes
>(assuming a nice big machine):
>
> Unix:
>
> export CATALINA_OPTS="-DXmx=512m"
> $CATALINA_HOME/bin/catalina.sh start
>
> Windows:
>
> set CATALINA_OPTS="-DXmx=512m"
> %CATALINA_HOME%\bin\catalina start
>
>but you will need to figure out the right setting for Blackdown.
>
>Craig McClanahan
>
>
>On Thu, 13 Sep 2001, Franck Routier wrote:
>
> > Date: Thu, 13 Sep 2001 14:56:41 +0200
> > From: Franck Routier <Fr...@hospvd.ch>
> > Reply-To: tomcat-user@jakarta.apache.org
> > To: tomcat-user@jakarta.apache.org
> > Subject: New xml parser on startup in Tomcat ?
> >
> > Hi,
> >
> > I'm still fighting with the same problem :
> >
> > Tomcat, just out of the box, won't start and gives me a OutOfMemoryError on
> > startup, then dies.
> > Apparently, it does this while reading it's conf file.
> > The problem occurs with versions 3.3-b2 and 4.0-rc1.
> >
> > The interresting point is that version 3.2.3, bundled with jboss 2.4.0
> WORKS,
> > but the same version (3.2.3) bundled with jboss 2.4.1 doesn't (same error).
> >
> > I read this in jboss forum, on another subject, but I thing it might be
> > related :
> >
> > "The problem is that in Tomcat 3.x you have to put your parsers in the
> > classpath before everything else becouse they are no relying on system
> > properties to decide which parser to use. There is an explanation on how to
> > to this is tomcat´s archives. In Tomcat 4.x the parser loaded by Tomcat for
> > it´s own use does not conflict on the parser used by applications. The
> > problem is solved in last version of JBOSS by using system properties to
> > define which parser to use. I´ll look for the archives and post them
> later "
> >
> > Sadly I'm not skilled enough to tell if this is really related...
> >
> > Any idea why Tomcat won't start on my machine, except when launched with
> > jboss 2.4.0...
> >
> > I use jdk 1.3-ppc from Blackdown on Debian Gnu-Linux-ppc.
> >
> > Thanks,
> >
> > Franck
> >
> >
-------
Franck Routier
SHC - Support FIH9
Re: New xml parser on startup in Tomcat ?
Posted by "Craig R. McClanahan" <cr...@apache.org>.
"OutOfMemoryError" means that your JVM is not providing enough heap space
to run Tomcat. If I remember correctly, the Blackdown JVM has a *very*
small default heap size, while the heap size on the Sun and IBM JVMs is
much larger.
What you need to do is consult the documentation from Blackdown and figure
out how to increase the heap size to at least 64 megabytes. You can then
configure Tomcat startup to use this by setting the environment variable
TOMCAT_OPTS (for Tomcat 3.x) or CATALINA_OPTS (for Tomcat 4.0). Here's
what you would do on the *Sun* JDK to increase heap size to 512 megabytes
(assuming a nice big machine):
Unix:
export CATALINA_OPTS="-DXmx=512m"
$CATALINA_HOME/bin/catalina.sh start
Windows:
set CATALINA_OPTS="-DXmx=512m"
%CATALINA_HOME%\bin\catalina start
but you will need to figure out the right setting for Blackdown.
Craig McClanahan
On Thu, 13 Sep 2001, Franck Routier wrote:
> Date: Thu, 13 Sep 2001 14:56:41 +0200
> From: Franck Routier <Fr...@hospvd.ch>
> Reply-To: tomcat-user@jakarta.apache.org
> To: tomcat-user@jakarta.apache.org
> Subject: New xml parser on startup in Tomcat ?
>
> Hi,
>
> I'm still fighting with the same problem :
>
> Tomcat, just out of the box, won't start and gives me a OutOfMemoryError on
> startup, then dies.
> Apparently, it does this while reading it's conf file.
> The problem occurs with versions 3.3-b2 and 4.0-rc1.
>
> The interresting point is that version 3.2.3, bundled with jboss 2.4.0 WORKS,
> but the same version (3.2.3) bundled with jboss 2.4.1 doesn't (same error).
>
> I read this in jboss forum, on another subject, but I thing it might be
> related :
>
> "The problem is that in Tomcat 3.x you have to put your parsers in the
> classpath before everything else becouse they are no relying on system
> properties to decide which parser to use. There is an explanation on how to
> to this is tomcat´s archives. In Tomcat 4.x the parser loaded by Tomcat for
> it´s own use does not conflict on the parser used by applications. The
> problem is solved in last version of JBOSS by using system properties to
> define which parser to use. I´ll look for the archives and post them later "
>
> Sadly I'm not skilled enough to tell if this is really related...
>
> Any idea why Tomcat won't start on my machine, except when launched with
> jboss 2.4.0...
>
> I use jdk 1.3-ppc from Blackdown on Debian Gnu-Linux-ppc.
>
> Thanks,
>
> Franck
>
>