Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: tomcat-user@jakarta.apache.org
Message-Id: <sadeae83.037@vhamail12.corp.vha.com>
Date: Thu, 19 Apr 2001 09:22:46 -0500
From: "Mark Mynsted" <MMYNSTED@vha.com>
To: <tomcat-user@jakarta.apache.org>,<jeff@kilbride.com>
Subject: Re: Tomcat vs. other app servers
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

>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...)

Here is a question:  Do you work for Allaire?

Sincerely yours;

Mark Mynsted


VHA Management Information Systems Client Services
mmynsted@vha.com
(972) 830 - 0592, Internal x1592

>>> jeff@kilbride.com 4/19/2001 12:05:37 AM >>>
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" <scott.tatum@wcom.com>
To: <tomcat-user@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=20
> Senior Applications Developer, Special Projects
> WorldCom | http://www.wcom.com/=20
>
> 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 <%=3D 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=20
> > > Senior Applications Developer, Special Projects
> > > WorldCom | http://www.wcom.com/=20
> > >
> > > 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?
> > >
> > >
> > >
>
>
>