Save yourself a whole lot of pain - in the long run. Download JDK 1.3.1 and
J2SDKEE 1.3 and you get servlet 2.3 and Tomcat 4.0 + a whole lot of other
neat stuff, like the deploytool. It's a little intimidating at first, but
once you work your way through a couple of servlet tutorials, you will love
not having to screw around with configuring Tomcat with a webserver. The
added benefit is this is the reference implementation by Sun and you have at
least a half-dozen major players out there with compatible server systems
(iPlanet, SilverStream, WebLogic....).
Further, Forte for Java 3.0 (prerelease) kicks ass now!
BTW: JWS was deprecated 1.5 years ago in favor of JServ/Tomcat.
Cheers!
Mark
----- Original Message -----
From: "Manish Bhatnagar" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 28, 2001 4:57 AM
Subject: Re: JWS Crashing with Extra memory usage by JREW - heap memory
problem.
> Hi!
> I agree with what you said. If I'm not wrong Sun has stopped any further
> development of JavaWebServer.
> We were using it some time back and, believe me, we had tough time making
it
> work. In my opinion Tomcat is
> far better than JWS apart from the fact that it is free. I found it faster
> than JWS. It doesn't crash anytime (at
> least not as frequently as JWS used to). I think these are more than
> sufficient reasons for switching to Tomcat.
> -mb-
>
> -----Original Message-----
> From: A mailing list for discussion about Sun Microsystem's Java Servlet
> API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of Tim
> Panton-Westpoint Ltd
> Sent: Thursday, June 28, 2001 2:13 PM
> To: [EMAIL PROTECTED]
> Subject: Re: JWS Crashing with Extra memory usage by JREW - heap memory
> problem.
>
>
> Some things to try:
> Check that the problem isn't in
> your servlets, run them in Optimizeit (I use JSDK 2.0 for this)
> and check for leaks.
>
> Which JDK/JRE are you using?
> It might be worth switching to something newer.
>
> If all else fails, go into taskmanager
> and set the processor affinity for
> the jrew.exe. This forces it to
> run on just one processor and
> so gets rid of many potential deadlocks.
>
> Whatever happens plan on dumping
> JWS - it is end of life.
>
> Tim.
>
> http://www.westpoint.ltd.uk/
> Internet reconnaissance services.
> http://www.westhawk.co.uk/
> Java programminq services
>
>
___________________________________________________________________________
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
>
>
___________________________________________________________________________
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
>
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
