Yes, I have used JNI.
What's the problem??

-----Original Message-----
From: Manish Bhatnagar [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 01, 2002 6:35 PM
To: Tomcat Users List
Subject: RE: Jetty .vs. tomcat


By any chance are you using JNI in your webapp?

-----Original Message-----
From: Steve Wong [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 01, 2002 3:10 PM
To: Tomcat Users List
Subject: RE: Jetty .vs. tomcat


Hi mingfai,

        I am trying other application servers because I have some
problems using tomcat in a production environment.

        The environment is Solaris 8, JRE1.2.2, tomcat3.3,
Apache1.3.23 with mod_ssl and mod_jk.
        What I discovered is that when I use apache benchmark
tool(ab) to generate many requests on apache, the java heap
allocated
in tomcat continuously increases.  Up to a point that there
is OutOfMemoryError.
        If I generate the requests on tomcat instead, there is no
problem.
        I am using the OptimizeIt to see the above result.

        And What I can find in cvs log of mod_jk is that there was
a memory leak bug in May last year.  But this bug is said to
be fixed.
        If I use Apache1.3.23 without mod_ssl, I find that the java
heap remains stable.  However, I discovered that the
allocated memory
of the java process of tomcat continuously increases.
Because I am afraid that there will be OutOfMemeryError in
the production
environment.  So, I restart the tomcat process regularly.

        Have you discovered the same things for your web
application??

Thx. and Regards.
Steve.

-----Original Message-----
From: Ming Fai [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 01, 2002 4:05 PM
To: Tomcat Users List
Subject: RE: Jetty .vs. tomcat


hi Steve,

I'm a Tomcat user. from what I read on the web, I believe
Jetty does
outperform Tomcat significantly in static pages and also
outperform Tomcat
to a unknown degree in dynamic pages. so, why i still choose
Tomcat?

My main consideration is in scalability. Multiple instance
of Tomcat can be
run and load balanced with Apache and mod_jk. I believe it
can achieve a
very high scalability in handling simultanceous requests.
Other
considerations are: good integration with other Apache and
commercial
products, better support (i personally think the 'support'
from Apache group
is better than other open src groups), full implementation
of JCP
specification etc.

And Tomcat should not be used together with Apache if there
is heavy loading
of static pages.

Other than Tomcat and Jetty, Resin is also quite famous. And
there are other
commercial choice like WebLogic, JRun and Orion.  You should
make decision
base on your need.

In my opinion, if your site is small in scale, and requires
a very good
response time, then Jetty or Resin are your choice.
Otherwise, Tomcat is a
good choice in general and it is a proven product. It
occupies about 50% of
the servlet engine market as of mid 2001.
(http://www.devx.com/judgingjava/articles/sixyears/printable
/sixyearsp2.asp#
fig7)

Any comment are welcome!

Regards,
mingfai






> -----Original Message-----
> From: Steve Wong [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 01, 2002 3:17 PM
> To: [EMAIL PROTECTED]
> Subject: Jetty .vs. tomcat
>
>
>
>       How will you compare jetty with tomcat?
>       Which one will you choose for a production environment?
Why?
>       Any Performance figures about these 2 servlet containers?
>
> Thx. and Regards.
> Steve.
>
> --
> To unsubscribe:
<mailto:[EMAIL PROTECTED]>
> For additional commands:
<mailto:[EMAIL PROTECTED]>
> Troubles with the list:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe:
<mailto:[EMAIL PROTECTED]>
For additional commands:
<mailto:[EMAIL PROTECTED]>
Troubles with the list:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe:
<mailto:[EMAIL PROTECTED]>
For additional commands:
<mailto:[EMAIL PROTECTED]>
Troubles with the list:
<mailto:[EMAIL PROTECTED]>



--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Reply via email to