You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Henrik Ross <hr...@ESECLENDING.com> on 2001/04/18 23:40:58 UTC
Tomcat vs. other app servers
What are peoples opinions on Tomcat vs. other app servers?
Performance, scalability, security, reliability?
Can Tomcat function in a real production business environment?
Re: Tomcat vs. other app servers
Posted by Scott Tatum <sc...@wcom.com>.
Everything remained the same except swapping JRun with Tomcat.
Sun Enterprise 250 (1 gig RAM)
Solaris 2.7
Apache 1.3.14
Tomcat 3.2.1 (mod_jk)
I liked the nice web interface for JRun setup/admin, but IMO Tomcat has it beat
just about everwhere else.
-Scott
--
Scott Tatum | scott.tatum@wcom.com
Senior Applications Developer, Special Projects
WorldCom | http://www.wcom.com/
Jeff Kilbride wrote:
> Hi Scott,
>
> That's great to hear. May I ask what environment you were running JRun under
> and is it the same environment you're now using Tomcat under?
>
> Thanks,
> --jeff
>
> ----- Original Message -----
> From: "Scott Tatum" <sc...@wcom.com>
> To: <to...@jakarta.apache.org>
> Sent: Wednesday, April 18, 2001 2:52 PM
> Subject: Re: Tomcat vs. other app servers
>
> > Before using Tomcat, our group had spent several k's on JRun 3.0
> > application server. We have several Intranet applications that receive
> > thousands of hits per day. Under JRun we were experiencing daily
> > lockups. After Service Pack 2 for JRun 3 did not fix the problem, I
> > tested out Tomcat 3.2.1.
> >
> > We eventually transitioned all of our jsp/servlet applications from JRun
> > to Tomcat, and have not had a single lockup since. The Tomcat server
> > also serves pages faster IMO. JRun does not support servlet reloading
> > either.
> > >From my experience, Tomcat has high degrees of performance, scalability,
> > and especially reliability. The only issue I don't know much about is
> > security. It is not as much of a concern to us as all of our
> > applications are Intranet-only.
> >
> > Tomcat has been rock-solid for us and we hope to use it for all our
> > future Intranet applications, and are looking forward to a production
> > release of Tomcat 4.
> >
> > -Scott
> >
> > --
> > Scott Tatum | scott.tatum@wcom.com
> > Senior Applications Developer, Special Projects
> > WorldCom | http://www.wcom.com/
> >
> > Henrik Ross wrote:
> >
> > > What are peoples opinions on Tomcat vs. other app servers?
> > >
> > > Performance, scalability, security, reliability?
> > >
> > > Can Tomcat function in a real production business environment?
> >
> >
> >
> >
Re: Tomcat vs. other app servers
Posted by Jeff Kilbride <je...@kilbride.com>.
Hi Scott,
That's great to hear. May I ask what environment you were running JRun under
and is it the same environment you're now using Tomcat under?
Thanks,
--jeff
----- Original Message -----
From: "Scott Tatum" <sc...@wcom.com>
To: <to...@jakarta.apache.org>
Sent: Wednesday, April 18, 2001 2:52 PM
Subject: Re: Tomcat vs. other app servers
> Before using Tomcat, our group had spent several k's on JRun 3.0
> application server. We have several Intranet applications that receive
> thousands of hits per day. Under JRun we were experiencing daily
> lockups. After Service Pack 2 for JRun 3 did not fix the problem, I
> tested out Tomcat 3.2.1.
>
> We eventually transitioned all of our jsp/servlet applications from JRun
> to Tomcat, and have not had a single lockup since. The Tomcat server
> also serves pages faster IMO. JRun does not support servlet reloading
> either.
> >From my experience, Tomcat has high degrees of performance, scalability,
> and especially reliability. The only issue I don't know much about is
> security. It is not as much of a concern to us as all of our
> applications are Intranet-only.
>
> Tomcat has been rock-solid for us and we hope to use it for all our
> future Intranet applications, and are looking forward to a production
> release of Tomcat 4.
>
> -Scott
>
> --
> Scott Tatum | scott.tatum@wcom.com
> Senior Applications Developer, Special Projects
> WorldCom | http://www.wcom.com/
>
> Henrik Ross wrote:
>
> > What are peoples opinions on Tomcat vs. other app servers?
> >
> > Performance, scalability, security, reliability?
> >
> > Can Tomcat function in a real production business environment?
>
>
>
>
JSPs with extra path info?
Posted by David Wall <dw...@myEastside.com>.
I'm trying to get Tomcat 3.2.2b2 to handle a URL of the format:
http://www.myeastside.com/app/GA.jsp/Test+word.doc?m=1&a=2
The idea is that I expect this to run my JSP called /app/GA.jsp. It should
have some extra path string of "Test+word.doc" and two parameters that I can
retrieve named "m" and "a".
But when I run it, tomcat's JspEngine keeps bringing up my notfound page.
I run Tomcat with Apache 1.3.19 and mod_jk.so using the AJP13 connector. I
have mounts like:
JkMount /app/*.jsp ajp13
JkMount /app/servlet/* ajp13
and I even added this just in case...
JkMount /app/*.jsp/* ajp13
I believe it's getting through Apache to TC okay since the jasper log shows:
2001-04-18 05:12:08 - JspEngine --> /notFound.jsp
2001-04-18 05:12:08 - ServletPath: /notFound.jsp
2001-04-18 05:12:08 - PathInfo: null
And it is bringing up my not found page. The GA.jsp file is present in the
right area though, right along with my other jsps.
Thanks,
David
Re: Tomcat vs. other app servers
Posted by Jeff Kilbride <je...@kilbride.com>.
Excellent!
You are proclaimed Java Trivia King for the day...
--jeff
----- Original Message -----
From: "Milt Epstein" <me...@uiuc.edu>
To: <to...@jakarta.apache.org>
Sent: Thursday, April 19, 2001 3:49 AM
Subject: Re: Tomcat vs. other app servers
> On Wed, 18 Apr 2001, Jeff Kilbride wrote:
>
> > It wouldn't surprise me if JRun ran better in a Windows
> > environment. After all, that's what it was originally designed
> > for. The JRun 1.x series was a lifesaver for me in late 1997 when we
> > ported all of our Perl code to Java. That was before we moved to
> > Linux from NT and before there were any in-process solutions for
> > Perl on NT. Fortunately, back then, you could actually get the JRun
> > developers on the phone to answer questions if you ran into
> > problems. Times have changed!
> >
> > Trivia question -- what was the name of the company that developed
> > JRun and was eventually bought out by Allaire?
> > Super Trivia -- who was the CEO and lead developer? (who must've
> > made a bunch of cash in the buyout...)
> [ ... ]
>
> Live Software. Paul Colton.
>
> What do I win? :-).
>
> Milt Epstein
> Research Programmer
> Software/Systems Development Group
> Computing and Communications Services Office (CCSO)
> University of Illinois at Urbana-Champaign (UIUC)
> mepstein@uiuc.edu
>
AllowedAddresses
Posted by LM <lu...@ubu.es>.
When I use Jserv, I can choose:
_________________________________________________________
# Syntax: security.allowedAddresses=[IP address],[IP Address]... (Comma
separated list of IP addresses)
security.allowedAddresses=127.0.0.1,192.168.0.15
__________________________________________________________
in the jserv.properties file
Can I make the same with Tomcat 3.2.1 ?
Thanks in advance
Luis M.
Re: Tomcat vs. other app servers
Posted by Milt Epstein <me...@uiuc.edu>.
On Wed, 18 Apr 2001, Jeff Kilbride wrote:
> It wouldn't surprise me if JRun ran better in a Windows
> environment. After all, that's what it was originally designed
> for. The JRun 1.x series was a lifesaver for me in late 1997 when we
> ported all of our Perl code to Java. That was before we moved to
> Linux from NT and before there were any in-process solutions for
> Perl on NT. Fortunately, back then, you could actually get the JRun
> developers on the phone to answer questions if you ran into
> problems. Times have changed!
>
> Trivia question -- what was the name of the company that developed
> JRun and was eventually bought out by Allaire?
> Super Trivia -- who was the CEO and lead developer? (who must've
> made a bunch of cash in the buyout...)
[ ... ]
Live Software. Paul Colton.
What do I win? :-).
Milt Epstein
Research Programmer
Software/Systems Development Group
Computing and Communications Services Office (CCSO)
University of Illinois at Urbana-Champaign (UIUC)
mepstein@uiuc.edu
Re: Tomcat vs. other app servers
Posted by Jeff Kilbride <je...@kilbride.com>.
It wouldn't surprise me if JRun ran better in a Windows environment. After
all, that's what it was originally designed for. The JRun 1.x series was a
lifesaver for me in late 1997 when we ported all of our Perl code to Java.
That was before we moved to Linux from NT and before there were any
in-process solutions for Perl on NT. Fortunately, back then, you could
actually get the JRun developers on the phone to answer questions if you ran
into problems. Times have changed!
Trivia question -- what was the name of the company that developed JRun and
was eventually bought out by Allaire?
Super Trivia -- who was the CEO and lead developer? (who must've made a
bunch of cash in the buyout...)
;o)
--jeff
----- Original Message -----
From: "Scott Tatum" <sc...@wcom.com>
To: <to...@jakarta.apache.org>
Sent: Wednesday, April 18, 2001 8:14 PM
Subject: Re: Tomcat vs. other app servers
> My apologies for inadvertantly FUDding JRun. We have run JRun 2.3 with
much better
> success. I don't know if it is just me, but JRun products seem to like NT
> environments better. The setups that we have had with JRun/NT have all
worked
> great. Our problems have only manifested when connected to Apache under
Solaris.
>
> My problem was specifically with JRun 3.0+Apache. We would experience
daily
> lockups, where all requests would eventually timeout. The normal
stop/start of JRun
> wouldn't work, the java process had to be kill -9'd (sending TERM had no
effect).
> Once you did that, the error_log would spam nondescript errors. Not
wanting to sign
> a support contract <g> I posted several times to Allaire's JRun forums
about the
> issue. I got a few "I'm having the exact same problem" replies, but never
did find
> a solution.
>
> Eventually I figured out I could hang it on demand by changing a jsp file,
saving
> it, then loading the page in the browser within a second or two of saving.
It would
> reduce to kill -9 status every time. Around then I decided to try Tomcat
just to
> see how it did. Once I saw how good it was I never looked back. :)
>
> If you are a current JRun user, don't be alarmed by my words - my case
seemed to be
> a pretty isolated one. But if you are looking for a fast, stable servlet
container,
> then run don't walk to Tomcat! Once you lose a few hairs and learn out how
to
> configure it, it will be your best friend.
>
> -Scott
> (p.s. This is not to discount other servlet containers. I hear resin is
fast and
> stable, and it does have a pretty attractive licensing setup)
>
> --
> Scott Tatum | scott.tatum@wcom.com
> Senior Applications Developer, Special Projects
> WorldCom | http://www.wcom.com/
>
> Jeff Turner wrote:
>
> > We have found JRun 3.0 to be a fine product (as was it's 2.3
predecessor), and
> > use it in many production environments. One should be careful to avoid
> > unsubstantiated claims on this forum, lest it amount to FUD.
> >
> > That said, most of our developers use Tomcat for development. It is
> > spec-compliant, doesn't crash, has excellent support (this list:) and
3.3/4.0
> > eliminates much classpath pain. By contrast, JRun *extends* the spec,
accepting
> > invalid syntax (like <%= foo; %>) which means JSP authors must
constantly be on
> > guard to avoid portability problems. JRun does not have a tomcat-users
> > equivalent, thus has effectively no user community. Unless you're a fan
of
> > phone-based support, that doesn't leave one much recourse when help is
needed.
> >
> > http://www.theserverside.com is probably the best forum for JSP/servlet
> > container comparisons.
> >
> > --Jeff
> >
> > On Wed, Apr 18, 2001 at 04:52:31PM -0500, Scott Tatum wrote:
> > > Before using Tomcat, our group had spent several k's on JRun 3.0
> > > application server. We have several Intranet applications that receive
> > > thousands of hits per day. Under JRun we were experiencing daily
> > > lockups. After Service Pack 2 for JRun 3 did not fix the problem, I
> > > tested out Tomcat 3.2.1.
> > >
> > > We eventually transitioned all of our jsp/servlet applications from
JRun
> > > to Tomcat, and have not had a single lockup since. The Tomcat server
> > > also serves pages faster IMO. JRun does not support servlet reloading
> > > either.
> > > >From my experience, Tomcat has high degrees of performance,
scalability,
> > > and especially reliability. The only issue I don't know much about is
> > > security. It is not as much of a concern to us as all of our
> > > applications are Intranet-only.
> > >
> > > Tomcat has been rock-solid for us and we hope to use it for all our
> > > future Intranet applications, and are looking forward to a production
> > > release of Tomcat 4.
> > >
> > > -Scott
> > >
> > > --
> > > Scott Tatum | scott.tatum@wcom.com
> > > Senior Applications Developer, Special Projects
> > > WorldCom | http://www.wcom.com/
> > >
> > > Henrik Ross wrote:
> > >
> > > > What are peoples opinions on Tomcat vs. other app servers?
> > > >
> > > > Performance, scalability, security, reliability?
> > > >
> > > > Can Tomcat function in a real production business environment?
> > >
> > >
> > >
>
>
>
Re: Tomcat vs. other app servers
Posted by Scott Tatum <sc...@wcom.com>.
My apologies for inadvertantly FUDding JRun. We have run JRun 2.3 with much better
success. I don't know if it is just me, but JRun products seem to like NT
environments better. The setups that we have had with JRun/NT have all worked
great. Our problems have only manifested when connected to Apache under Solaris.
My problem was specifically with JRun 3.0+Apache. We would experience daily
lockups, where all requests would eventually timeout. The normal stop/start of JRun
wouldn't work, the java process had to be kill -9'd (sending TERM had no effect).
Once you did that, the error_log would spam nondescript errors. Not wanting to sign
a support contract <g> I posted several times to Allaire's JRun forums about the
issue. I got a few "I'm having the exact same problem" replies, but never did find
a solution.
Eventually I figured out I could hang it on demand by changing a jsp file, saving
it, then loading the page in the browser within a second or two of saving. It would
reduce to kill -9 status every time. Around then I decided to try Tomcat just to
see how it did. Once I saw how good it was I never looked back. :)
If you are a current JRun user, don't be alarmed by my words - my case seemed to be
a pretty isolated one. But if you are looking for a fast, stable servlet container,
then run don't walk to Tomcat! Once you lose a few hairs and learn out how to
configure it, it will be your best friend.
-Scott
(p.s. This is not to discount other servlet containers. I hear resin is fast and
stable, and it does have a pretty attractive licensing setup)
--
Scott Tatum | scott.tatum@wcom.com
Senior Applications Developer, Special Projects
WorldCom | http://www.wcom.com/
Jeff Turner wrote:
> We have found JRun 3.0 to be a fine product (as was it's 2.3 predecessor), and
> use it in many production environments. One should be careful to avoid
> unsubstantiated claims on this forum, lest it amount to FUD.
>
> That said, most of our developers use Tomcat for development. It is
> spec-compliant, doesn't crash, has excellent support (this list:) and 3.3/4.0
> eliminates much classpath pain. By contrast, JRun *extends* the spec, accepting
> invalid syntax (like <%= foo; %>) which means JSP authors must constantly be on
> guard to avoid portability problems. JRun does not have a tomcat-users
> equivalent, thus has effectively no user community. Unless you're a fan of
> phone-based support, that doesn't leave one much recourse when help is needed.
>
> http://www.theserverside.com is probably the best forum for JSP/servlet
> container comparisons.
>
> --Jeff
>
> On Wed, Apr 18, 2001 at 04:52:31PM -0500, Scott Tatum wrote:
> > Before using Tomcat, our group had spent several k's on JRun 3.0
> > application server. We have several Intranet applications that receive
> > thousands of hits per day. Under JRun we were experiencing daily
> > lockups. After Service Pack 2 for JRun 3 did not fix the problem, I
> > tested out Tomcat 3.2.1.
> >
> > We eventually transitioned all of our jsp/servlet applications from JRun
> > to Tomcat, and have not had a single lockup since. The Tomcat server
> > also serves pages faster IMO. JRun does not support servlet reloading
> > either.
> > >From my experience, Tomcat has high degrees of performance, scalability,
> > and especially reliability. The only issue I don't know much about is
> > security. It is not as much of a concern to us as all of our
> > applications are Intranet-only.
> >
> > Tomcat has been rock-solid for us and we hope to use it for all our
> > future Intranet applications, and are looking forward to a production
> > release of Tomcat 4.
> >
> > -Scott
> >
> > --
> > Scott Tatum | scott.tatum@wcom.com
> > Senior Applications Developer, Special Projects
> > WorldCom | http://www.wcom.com/
> >
> > Henrik Ross wrote:
> >
> > > What are peoples opinions on Tomcat vs. other app servers?
> > >
> > > Performance, scalability, security, reliability?
> > >
> > > Can Tomcat function in a real production business environment?
> >
> >
> >
Re: Tomcat vs. other app servers
Posted by Milt Epstein <me...@uiuc.edu>.
On Thu, 19 Apr 2001, Jeff Turner wrote:
> We have found JRun 3.0 to be a fine product (as was it's 2.3
> predecessor), and use it in many production environments. One should
> be careful to avoid unsubstantiated claims on this forum, lest it
> amount to FUD.
>
> That said, most of our developers use Tomcat for development. It is
> spec-compliant, doesn't crash, has excellent support (this list:)
> and 3.3/4.0 eliminates much classpath pain. By contrast, JRun
> *extends* the spec, accepting invalid syntax (like <%= foo; %>)
> which means JSP authors must constantly be on guard to avoid
> portability problems. JRun does not have a tomcat-users equivalent,
> thus has effectively no user community. Unless you're a fan of
> phone-based support, that doesn't leave one much recourse when help
> is needed.
[ ... ]
JRun does/did have a JRun-talk mailing list. There was participation
by Allaire/JRun people, but it was a little strange, they seemed to
disclaim it as a support forum (it was a support forum when it started
out, before Allaire took over JRun). Anyway, it wasn't as useful as
this list. They also have some online/web-based fora, but I never
used those.
I had used JRun (2.2), along with Netscape Enterprise Server, before
switching to Tomcat/Apache some time back. It worked fine for us.
> On Wed, Apr 18, 2001 at 04:52:31PM -0500, Scott Tatum wrote:
> > Before using Tomcat, our group had spent several k's on JRun 3.0
> > application server. We have several Intranet applications that receive
> > thousands of hits per day. Under JRun we were experiencing daily
> > lockups. After Service Pack 2 for JRun 3 did not fix the problem, I
> > tested out Tomcat 3.2.1.
> >
> > We eventually transitioned all of our jsp/servlet applications from JRun
> > to Tomcat, and have not had a single lockup since. The Tomcat server
> > also serves pages faster IMO. JRun does not support servlet reloading
> > either.
> > >From my experience, Tomcat has high degrees of performance, scalability,
> > and especially reliability. The only issue I don't know much about is
> > security. It is not as much of a concern to us as all of our
> > applications are Intranet-only.
> >
> > Tomcat has been rock-solid for us and we hope to use it for all our
> > future Intranet applications, and are looking forward to a production
> > release of Tomcat 4.
> >
> > -Scott
> >
> > --
> > Scott Tatum | scott.tatum@wcom.com
> > Senior Applications Developer, Special Projects
> > WorldCom | http://www.wcom.com/
> >
> > Henrik Ross wrote:
> >
> > > What are peoples opinions on Tomcat vs. other app servers?
> > >
> > > Performance, scalability, security, reliability?
> > >
> > > Can Tomcat function in a real production business environment?
> >
> >
> >
>
Milt Epstein
Research Programmer
Software/Systems Development Group
Computing and Communications Services Office (CCSO)
University of Illinois at Urbana-Champaign (UIUC)
mepstein@uiuc.edu
Re: Tomcat vs. other app servers
Posted by Jeff Turner <je...@socialchange.net.au>.
We have found JRun 3.0 to be a fine product (as was it's 2.3 predecessor), and
use it in many production environments. One should be careful to avoid
unsubstantiated claims on this forum, lest it amount to FUD.
That said, most of our developers use Tomcat for development. It is
spec-compliant, doesn't crash, has excellent support (this list:) and 3.3/4.0
eliminates much classpath pain. By contrast, JRun *extends* the spec, accepting
invalid syntax (like <%= foo; %>) which means JSP authors must constantly be on
guard to avoid portability problems. JRun does not have a tomcat-users
equivalent, thus has effectively no user community. Unless you're a fan of
phone-based support, that doesn't leave one much recourse when help is needed.
http://www.theserverside.com is probably the best forum for JSP/servlet
container comparisons.
--Jeff
On Wed, Apr 18, 2001 at 04:52:31PM -0500, Scott Tatum wrote:
> Before using Tomcat, our group had spent several k's on JRun 3.0
> application server. We have several Intranet applications that receive
> thousands of hits per day. Under JRun we were experiencing daily
> lockups. After Service Pack 2 for JRun 3 did not fix the problem, I
> tested out Tomcat 3.2.1.
>
> We eventually transitioned all of our jsp/servlet applications from JRun
> to Tomcat, and have not had a single lockup since. The Tomcat server
> also serves pages faster IMO. JRun does not support servlet reloading
> either.
> >From my experience, Tomcat has high degrees of performance, scalability,
> and especially reliability. The only issue I don't know much about is
> security. It is not as much of a concern to us as all of our
> applications are Intranet-only.
>
> Tomcat has been rock-solid for us and we hope to use it for all our
> future Intranet applications, and are looking forward to a production
> release of Tomcat 4.
>
> -Scott
>
> --
> Scott Tatum | scott.tatum@wcom.com
> Senior Applications Developer, Special Projects
> WorldCom | http://www.wcom.com/
>
> Henrik Ross wrote:
>
> > What are peoples opinions on Tomcat vs. other app servers?
> >
> > Performance, scalability, security, reliability?
> >
> > Can Tomcat function in a real production business environment?
>
>
>
Re: Tomcat vs. other app servers
Posted by Scott Tatum <sc...@wcom.com>.
Before using Tomcat, our group had spent several k's on JRun 3.0
application server. We have several Intranet applications that receive
thousands of hits per day. Under JRun we were experiencing daily
lockups. After Service Pack 2 for JRun 3 did not fix the problem, I
tested out Tomcat 3.2.1.
We eventually transitioned all of our jsp/servlet applications from JRun
to Tomcat, and have not had a single lockup since. The Tomcat server
also serves pages faster IMO. JRun does not support servlet reloading
either.
>From my experience, Tomcat has high degrees of performance, scalability,
and especially reliability. The only issue I don't know much about is
security. It is not as much of a concern to us as all of our
applications are Intranet-only.
Tomcat has been rock-solid for us and we hope to use it for all our
future Intranet applications, and are looking forward to a production
release of Tomcat 4.
-Scott
--
Scott Tatum | scott.tatum@wcom.com
Senior Applications Developer, Special Projects
WorldCom | http://www.wcom.com/
Henrik Ross wrote:
> What are peoples opinions on Tomcat vs. other app servers?
>
> Performance, scalability, security, reliability?
>
> Can Tomcat function in a real production business environment?