Re: Tomcat vs JServ
I use the rule - "Nothing extra". If you do not use JSP, then JServe could be better choice as "Best Free Product 1999". Dmitry R., [EMAIL PROTECTED] Chief Architect, MetricStream.COM Santa Clara, CA -Original Message- From:Eric Mosley [EMAIL PROTECTED] Sent:Thu, 19 Apr 2001 10:59:22 +0100 To: [EMAIL PROTECTED] Subject: Tomcat vs JServ Hi, I'm trying to evaluate whether to use Tomcat or JServ. The system will be freeBSD and I know that Tomcat has some "issues" with that - but I'm willing to take the chance. However, if speed and memory are issues which would be best for basic servlet functionality? Surely it would be JServ as it has been in bug fixing mode for so long it will have matured and is quite fast anyway? Any insights appreciated, Eric ___ Visit http://www.visto.com/info, your free web-based communications center. Visto.com. Life on the Dot.
RE: Tomcat vs JServ
At 02:16 PM 4/19/2001 -0500, you wrote: >Actually, you *can* use mod_jserv with Tomcat (3.2.1, at least) -- >that's how I have it set up (although it's only semi-intentional :-). Apache 3.2.x (whatever) actually ships with that mod in the distribution. Apparently when the binaries were being packaged together that was the only mod available at the time. Even the docs say something like "well, to get this running now we give mod_jrun, but when mod_jk is available you'll want to use that..." or words like that.
Re: Tomcat vs JServ
On Thu, 19 Apr 2001, Joe Laffey wrote: > On Thu, 19 Apr 2001, Tim O'Neil wrote: > > > JServ is dead code. Don't use it. Tomcat is that same code's > > successor. > > I hardly think that code being dead should put it into a "Don't use > it" category. JServ is stable as hell and that means a lot. Sure, it > only support JSDK 2.0, but you can do a lot with that. Most of my > clients still use Jdk 1.1.x, and these are Fortune 500 companies! [ ... ] OK, I think we've beaten this horse enough :-). Sure, if you've got something up and running with JServ, and it's working fine, and you're not planning any major work on it, there's no reason to upgrade (and I don't think anyone was saying otherwise, certainly not me :-). But if you're just getting started with Servlets/JSP, and you're trying to decide between JServ and Tomcat, I'd say the choice is clear, and you go with the up-to-date, active technology of Tomcat. I'd even say that if you have something currently running with JServ, if you plan to do more than the tiniest amount of work on it, then you'd be better off switching over to Tomcat. Things that are multiple versions of the spec behind, and are using technology/implementations that are not being actively worked on, can be a problem to maintain. And maintenance is often more important than performance. (And even if Tomcat lags behind JServ in performance currently, that will change.) Milt Epstein Research Programmer Software/Systems Development Group Computing and Communications Services Office (CCSO) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED]
RE: Tomcat vs JServ
On Thu, 19 Apr 2001, Chris Ward wrote: > > JServ is dead code. Don't use it. Tomcat is that same code's > > successor. > > Also, you'll need "mod_jk" to glue Tomcat to Apache. I only mention > it because I spent two days finding this out! Most of that time was > spent hunting for mod_jserv. D'oh! [ ... ] Actually, you *can* use mod_jserv with Tomcat (3.2.1, at least) -- that's how I have it set up (although it's only semi-intentional :-). I don't know exactly, but I believe some versions of Tomcat allow either mod_jserv or mod_jk, some only mod_jk, and some (4.0, I think) only allow a different one, mod_webapp. Milt Epstein Research Programmer Software/Systems Development Group Computing and Communications Services Office (CCSO) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED]
Re: Tomcat vs JServ
BUT, if one is using neither JServ nor Tomcat, one should use Tomcat. It is unwise to build an infrastructure around dead code. Sincerely yours; Mark Mynsted VHA Management Information Systems Client Services [EMAIL PROTECTED] (972) 830 - 0592, Internal x1592 >>> [EMAIL PROTECTED] 4/19/2001 11:58:22 AM >>> On Thu, 19 Apr 2001, Tim O'Neil wrote: > > > JServ is dead code. Don't use it. Tomcat is > that same code's successor. > I hardly think that code being dead should put it into a "Don't use it" category. JServ is stable as hell and that means a lot. Sure, it only support JSDK 2.0, but you can do a lot with that. Most of my clients still use Jdk 1.1.x, and these are Fortune 500 companies! Don't knock tried and tested software. Also, the beauty of Open Source is that if you find a bug you can fix it yourself. I do this all the time (and submit the patch). Joe Laffey LAFFEY Computer Imaging St. Louis, MO -- Need to do multi-file string replacement in Un*x, but don't want to mess with sed? Try rpl. It's a free text replacement utility with source. http://www.laffeycomputer.com/rpl.html -- Check it out!
Re: Tomcat vs JServ
I disagree. Using that code closes the door to a number of options that would be available to you using Tomcat, and absolutely closes the door on anything in the future. As for being more stable, I would also disagree with you but I don't have any specific cases to prove it. In any case, I do feel that using it would be a mistake. And labeling yourself as a maintainer of a particular line of source is another can of worms. At 11:58 AM 4/19/2001 -0500, you wrote: >On Thu, 19 Apr 2001, Tim O'Neil wrote: > > > > > > > JServ is dead code. Don't use it. Tomcat is > > that same code's successor. > > > >I hardly think that code being dead should put it into a "Don't use it" >category. JServ is stable as hell and that means a lot. Sure, it only >support JSDK 2.0, but you can do a lot with that. Most of my clients still >use Jdk 1.1.x, and these are Fortune 500 companies! > >Don't knock tried and tested software. Also, the beauty of Open Source is >that if you find a bug you can fix it yourself. I do this all the time >(and submit the patch). > >Joe Laffey >LAFFEY Computer Imaging >St. Louis, MO >-- >Need to do multi-file string replacement in Un*x, but don't want to mess >with sed? Try rpl. It's a free text replacement utility with source. >http://www.laffeycomputer.com/rpl.html -- Check it out! >
Re: Tomcat vs JServ
Sounds like you haven't setup your mount points for mod_jk in Apache so it doesn't know to forward the request to Tomcat. This is covered in the docs. > From: "Arnaud Dostes - NTI" <[EMAIL PROTECTED]> > Organization: NTI > Reply-To: [EMAIL PROTECTED] > Date: Thu, 19 Apr 2001 18:56:28 +0200 > To: <[EMAIL PROTECTED]> > Subject: Re: Tomcat vs JServ > > Did you succeed in gluing tomcat to apache ? > I get 404 errors when running servlets and running a jsp file displays the > code > > thanks.
Re: Tomcat vs JServ
Did you succeed in gluing tomcat to apache ? I get 404 errors when running servlets and running a jsp file displays the code thanks. - Original Message - From: "Chris Ward" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, April 19, 2001 6:32 PM Subject: RE: Tomcat vs JServ > JServ is dead code. Don't use it. Tomcat is > that same code's successor. Also, you'll need "mod_jk" to glue Tomcat to Apache. I only mention it because I spent two days finding this out! Most of that time was spent hunting for mod_jserv. D'oh! Look at http://jakarta.apache.org/tomcat/jakarta-tomcat/src/doc/mod_jk-howto.htm l for specifics. Chris
Re: Tomcat vs JServ
On Thu, 19 Apr 2001, Tim O'Neil wrote: > > > JServ is dead code. Don't use it. Tomcat is > that same code's successor. > I hardly think that code being dead should put it into a "Don't use it" category. JServ is stable as hell and that means a lot. Sure, it only support JSDK 2.0, but you can do a lot with that. Most of my clients still use Jdk 1.1.x, and these are Fortune 500 companies! Don't knock tried and tested software. Also, the beauty of Open Source is that if you find a bug you can fix it yourself. I do this all the time (and submit the patch). Joe Laffey LAFFEY Computer Imaging St. Louis, MO -- Need to do multi-file string replacement in Un*x, but don't want to mess with sed? Try rpl. It's a free text replacement utility with source. http://www.laffeycomputer.com/rpl.html -- Check it out!
RE: Tomcat vs JServ
> JServ is dead code. Don't use it. Tomcat is > that same code's successor. Also, you'll need "mod_jk" to glue Tomcat to Apache. I only mention it because I spent two days finding this out! Most of that time was spent hunting for mod_jserv. D'oh! Look at http://jakarta.apache.org/tomcat/jakarta-tomcat/src/doc/mod_jk-howto.htm l for specifics. Chris
Re: Tomcat vs JServ
At 10:59 AM 4/19/2001 +0100, you wrote: >I'm trying to evaluate whether to use Tomcat or JServ. The system will be >freeBSD and I know that Tomcat has some "issues" with that - but I'm >willing to take the chance. > >However, if speed and memory are issues which would be best for basic >servlet functionality? > >Surely it would be JServ as it has been in bug fixing mode for so long it >will have matured and is quite fast anyway? > >Any insights appreciated, JServ is dead code. Don't use it. Tomcat is that same code's successor.
Re: Tomcat vs JServ
I guess it comes down to if it aint broke, don't fix it. If your happy with the old 2.0 spec, and the fact your unlikely to get much support if things do go wrong, I guess there isn't much reason to change. At the end of the day, tomcat is more uptodate than JServ, and using mod_jk is easier to integrate with Apache. sam - Original Message - From: "Eric Mosley" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, April 19, 2001 2:54 PM Subject: RE: Tomcat vs JServ > > I have a jServ box that has run with no problems of any kind for over a > > year and a half. To me that says a lot of jServ. Does the latest release > > of Tomcat finally support the automatic starting up of Tomcat (not > > manual)? What about speed? In some casual tests my jServ system runs > > faster than Tomcat. Has anyone done any real benchmarks? > > Actually this is the essence of what I was enquiring about! I also have an > old JServ machine which has been running for two years with zero problems. > The crucial issue (for me anyway) is which is faster and less memory > intensive for basic servlets (where you would be happy with 2.0 servlet > functionality)... > > Anybody!? >
RE: Tomcat vs JServ
> I have a jServ box that has run with no problems of any kind for over a > year and a half. To me that says a lot of jServ. Does the latest release > of Tomcat finally support the automatic starting up of Tomcat (not > manual)? What about speed? In some casual tests my jServ system runs > faster than Tomcat. Has anyone done any real benchmarks? Actually this is the essence of what I was enquiring about! I also have an old JServ machine which has been running for two years with zero problems. The crucial issue (for me anyway) is which is faster and less memory intensive for basic servlets (where you would be happy with 2.0 servlet functionality)... Anybody!?
RE: Tomcat vs JServ
On Thu, 19 Apr 2001, [iso-8859-1] Benoît Jacquemont wrote: > You shouldn't use JServ anymore. Tomcat comes in replacement of JServ. And > actually, JServ is kind of dead because, as Milt Epstein said, there won't > be any other development on JServ. So no more enhancement will be made to > the engine. I have a jServ box that has run with no problems of any kind for over a year and a half. To me that says a lot of jServ. Does the latest release of Tomcat finally support the automatic starting up of Tomcat (not manual)? What about speed? In some casual tests my jServ system runs faster than Tomcat. Has anyone done any real benchmarks? Joe Laffey LAFFEY Computer Imaging St. Louis, MO -- Need to do multi-file string replacement in Un*x, but don't want to mess with sed? Try rpl. It's a free text replacement utility with source. http://www.laffeycomputer.com/rpl.html -- Check it out!
RE: Tomcat vs JServ
You shouldn't use JServ anymore. Tomcat comes in replacement of JServ. And actually, JServ is kind of dead because, as Milt Epstein said, there won't be any other development on JServ. So no more enhancement will be made to the engine. There is no point to compare Tomcat and JServ. Tomcat and JServ are not competitors, Tomcat is just the replacement for JServ. If you want to use the servlet/JSP engine from the Apache Project, use Tomcat. Benoît >Hi, >I'm trying to evaluate whether to use Tomcat or JServ. The system will be freeBSD and I know that Tomcat has some "issues" >with that - but I'm willing to take the chance. >However, if speed and memory are issues which would be best for basic servlet functionality? >Surely it would be JServ as it has been in bug fixing mode for so long it will have matured and is quite fast anyway? >Any insights appreciated, >Eric
Re: Tomcat vs JServ
I'm not sure which "issues" you mean I think that fact that JServ has been in bug fixing for a while now is more down to the fact that no more development is being done with it. Tomcat supports the latest standards and works fine with Apache via mod_jk. And its being actively developed. I for one would be eager to see more empahasis being placed on using mod_jk and apache rather than JServ. sam - Original Message - From: Eric Mosley To: [EMAIL PROTECTED] Sent: Thursday, April 19, 2001 10:59 AM Subject: Tomcat vs JServ Hi, I'm trying to evaluate whether to use Tomcat or JServ. The system will be freeBSD and I know that Tomcat has some "issues" with that - but I'm willing to take the chance. However, if speed and memory are issues which would be best for basic servlet functionality? Surely it would be JServ as it has been in bug fixing mode for so long it will have matured and is quite fast anyway? Any insights appreciated, Eric
Re: Tomcat vs JServ
On Thu, 19 Apr 2001, Simone Pensa wrote: > Hi, > the main difference is that Tomcat implements Servlet version 2.2 > and higher, while JServ refers to Servlet specification version 2.0. [ ... ] And that's a *big* difference. Further, there is no more active development on JServ, while there is with Tomcat (it is the servlet reference implementation, after all). So Tomcat will keep up with new versions of the spec (2.3 is almost ready to go, and Tomcat 4.0 is tracking it; Tomcat 3.X implements the 2.2 spec), while JServ is stuck on 2.0. >From those considerations alone it seems to me that Tomcat should be the way to go. Especially for anyone starting out with servlets. The 2.2 spec introduced some relatively significant changes from earlier versions of the spec. > > Eric Mosley wrote: > > > > Hi, > > > > I'm trying to evaluate whether to use Tomcat or JServ. The system > > will be freeBSD and I know that Tomcat has some "issues" with that > > - but I'm willing to take the chance. > > > > However, if speed and memory are issues which would be best for > > basic servlet functionality? > > > > Surely it would be JServ as it has been in bug fixing mode for so > > long it will have matured and is quite fast anyway? > > > > Any insights appreciated, > > > Milt Epstein Research Programmer Software/Systems Development Group Computing and Communications Services Office (CCSO) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED]
Re: Tomcat vs JServ
Hi, the main difference is that Tomcat implements Servlet version 2.2 and higher, while JServ refers to Servlet specification version 2.0. I don't know issues related to perfomance and memory. Simone > Eric Mosley wrote: > > Hi, > > I'm trying to evaluate whether to use Tomcat or JServ. The system will be > freeBSD and I know that Tomcat has some "issues" with that - but I'm willing > to take the chance. > > However, if speed and memory are issues which would be best for basic servlet > functionality? > > Surely it would be JServ as it has been in bug fixing mode for so long it will > have matured and is quite fast anyway? > > Any insights appreciated, > > Eric > > -- Simone Pensa Siemens Information and Communication Networks SpA Communication on Air - Research Programs Palazzo Laboratori CL3C 20010 Settimo Milanese Milano, Italy phone : +39 02 2733 7810 fax : +39 02 2733 7989 mailto: [EMAIL PROTECTED]
