Re: the pain of choice
On Mon, Apr 19, 2004 at 11:32:38PM +0200, C. Kukulies wrote: Can someone give me an advice which way to go WRT to using a tomcat/apache combo on a Unix (not Linux) system? There are so many options, jk, jk2, tomcat 3-4-5, apache 1.3, apache2. worker.properties worker2.properties, jk2.properties in tomcat/conf, mod_jk.conf in etc/apache, mod_jk, mod_jk2. Then I see constructs in brackets [] in worker.properties and without these. What is workers.host=jsp-hostname? Is it an IP host? Or is it some placeholder which must be in workers.list? Thanks to all. After a short excursion into trying to build the connector-current from CVS (someone noted that the standard src tar ball doesn't include all sources necessary to do the ant build) build also fell over on this even with a checked out tree of jakarta-tomcat-connectors. But, ok, this is in flux but it would be nice if that would be buildable also sooner or later. (I'm using jdk1.4.2, FWIW). I managed now to get a working combo of apache-1.3_29 and tomcat-5.0.19 with the mod_jk connector working. Crucial for my servlet mapping was to create an appropriate web.xml file in the deply directory under webapps/servelts/WEB-INF. -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: the pain of choice
On Mon, Apr 19, 2004 at 05:53:19PM -0400, Parsons Technical Services wrote: I don't know if you will get much response with this request. What you may wish to do is define your requirements for your application and environment. Then set back and take in all the opinions on which way is best. Here are a few questions to start with: What JDK are you developing against? -- 1.4.2 But not crucial What is you platform? -- What do you mean by that? Servlet API 2.1 What is your OS? -- FreeBSD Is this for production or development? -- Production How many users?-- 2 How many deployers?-- 1 How many apps? -- 1 How big are the apps? -- very small How much static? -- ?please explain Do you want or need Apache?-- need cgi-scripting (Virtual hosting?) -- absolutely not necessary -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: the pain of choice
At this point it looks like tomcat 5 will handle your needs. Look at this for cgi: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/cgi-howto.html What JDK are you developing against? -- 1.4.2 But not crucial What is you platform? -- What do you mean by that? By platform I mean the hardware you are running on. Servlet API 2.1 What is your OS? -- FreeBSD Is this for production or development? -- Production How many users?-- 2 How many deployers?-- 1 How many apps? -- 1 How big are the apps? -- very small How much static? -- ?please explain CGI, servlets, jsp etc are all dynamic. HTML, HTM, etc are static. If you have a large amount of static pages some people will use Apache to serve it and Tomcat for the dynamic. Although as Tomcat evolves it is no longer a neccesity as it was in the past. Do you want or need Apache?-- need cgi-scripting See above. (Virtual hosting?) -- absolutely not necessary Nothing here stands out that would suggest that you need anything other than Tomcat 5 running alone. But to qualify, I have not done any cgi and only did a quick take on the documentation. Read it carefully before proceeding. You may also want to start a new thread and ask the list about any limitations or concerns that are not addressed in the docs. Doug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: the pain of choice
Parsons Technical Services wrote:
At this point it looks like tomcat 5 will handle your needs
Look at this for cgi:
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/cgi-howto.html
Although it could be done like this, if you have some Apache experience,
I'd recommend Apache in front of Tomcat 5.0.19.
The simplest way to deploy Tomcat from this scenario is to ProxyPass it
from Apache. I doubt from your requirements that configuring a connector
is necessary.
For ProxyPass documentation, see:
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/proxy-howto.html
basically it comes down to this:
1. make sure the following module is uncommented in httpd.conf:
LoadModule proxy_module {path-to-modules}/mod_proxy.so
AddModule mod_proxy.c
2. add the following to httpd.conf
ProxyPass /myapp http://localhost:8080/myapp
ProxyPassReverse /myapp http://localhost:8080/myapp
(I'm using 8080 as the Tomcat port, since that is the default for Tomcat).
Good luck.
Michiel
What JDK are you developing against? -- 1.4.2 But not crucial
What is you platform? -- What do you mean by that?
What is your OS? -- FreeBSD
Is this for production or development? -- Production
How many users?-- 2
How many deployers?-- 1
How many apps? -- 1
How big are the apps? -- very small
How much static? -- ?please explain
CGI, servlets, jsp etc are all dynamic. HTML, HTM, etc are static. If you
have a large amount of static pages some people will use Apache to serve it
and Tomcat for the dynamic. Although as Tomcat evolves it is no longer a
neccesity as it was in the past.
Do you want or need Apache?-- need cgi-scripting
See above.
(Virtual hosting?) -- absolutely not necessary
Nothing here stands out that would suggest that you need anything other than
Tomcat 5 running alone. But to qualify, I have not done any cgi and only did
a quick take on the documentation. Read it carefully before proceeding. You
may also want to start a new thread and ask the list about any limitations
or concerns that are not addressed in the docs.
--
Michiel Toneman Software Engineer Bibit Global Payment Services
Regulierenring 10 3981 LB Bunnik [EMAIL PROTECTED]
Tel. +31-30-6595168 Fax +31-30-6564464 http://www.bibit.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: the pain of choice
Jk vs jk2. JK is dead STOP USING IT. JK2 all the way!! (sorry, jk2 is the prefered way to link apache2 to tomcat[45]) I would suggest using tomcat 4 for now if you are going immediately into a production environment where you have to abide by a server level agreement. Otherwise use tomcat 5. Tomcat 5 is listed as stable but seems a bit shakey right now with the bugs that keep popping up. There is no reason that I know of not to use Apache2. You will be using worker2.properties. Since I know nothing about JK I can't comment on the rest. -Original Message- From: C. Kukulies [mailto:[EMAIL PROTECTED] Sent: Monday, April 19, 2004 5:33 PM To: [EMAIL PROTECTED] Subject: the pain of choice Can someone give me an advice which way to go WRT to using a tomcat/apache combo on a Unix (not Linux) system? There are so many options, jk, jk2, tomcat 3-4-5, apache 1.3, apache2. worker.properties worker2.properties, jk2.properties in tomcat/conf, mod_jk.conf in etc/apache, mod_jk, mod_jk2. Then I see constructs in brackets [] in worker.properties and without these. What is workers.host=jsp-hostname? Is it an IP host? Or is it some placeholder which must be in workers.list? -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: the pain of choice
The reason I must keep using apache 1.3 is because I have been unable to get remoteUser() from apache2. I have used identicle settings for mod_jk with both apache 1.3 and 2.x. With apache 1.3 I can get remoteUser() with apache 2.x I cannot. I need remoteUser() for my web applications to work. Lloyd On Tue, 2004-04-20 at 09:32, Angus Mezick wrote: Jk vs jk2. JK is dead STOP USING IT. JK2 all the way!! (sorry, jk2 is the prefered way to link apache2 to tomcat[45]) I would suggest using tomcat 4 for now if you are going immediately into a production environment where you have to abide by a server level agreement. Otherwise use tomcat 5. Tomcat 5 is listed as stable but seems a bit shakey right now with the bugs that keep popping up. There is no reason that I know of not to use Apache2. You will be using worker2.properties. Since I know nothing about JK I can't comment on the rest. -Original Message- From: C. Kukulies [mailto:[EMAIL PROTECTED] Sent: Monday, April 19, 2004 5:33 PM To: [EMAIL PROTECTED] Subject: the pain of choice Can someone give me an advice which way to go WRT to using a tomcat/apache combo on a Unix (not Linux) system? There are so many options, jk, jk2, tomcat 3-4-5, apache 1.3, apache2. worker.properties worker2.properties, jk2.properties in tomcat/conf, mod_jk.conf in etc/apache, mod_jk, mod_jk2. Then I see constructs in brackets [] in worker.properties and without these. What is workers.host=jsp-hostname? Is it an IP host? Or is it some placeholder which must be in workers.list? -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: the pain of choice
Great, let's use JK2 My experience: rant-mode tar -xvzf jakarta-tomcat-connectors-jk2-src-current.tar.gz cd jakarta-tomcat-connectors-jk2-2.0.4-src/ less README.txt - gibberish, doesn't help me much less RELEASE-NOTES.txt -- Tomcat Connectors Version @VERSION@ Release Notes This version matches the version included with tomcat-5.0.2, and supports tomcat 3.3, 4.0, 4.1, 5.0. Bugs and issues will be tracked with tomcat5 - this file will list only issues related with older versions. -- 5.0.2??? my confidence is growing. ls doc/* doc/install_tomcat33.html doc/install_tomcat40.html doc/install_tomcat41.html Hmmm, I want to install it for tomcat 5.0.19. Ok, I'll read the most current (install_tomcat41.html). Try it, it's quite amusing... Not helpful. ant Buildfile: build.xml build: BUILD FAILED file:/data/michiel/jakarta-tomcat-connectors-jk2-2.0.4-src/build.xml:45: Basedir /data/michiel/jakarta-tomcat-connectors-jk2-2.0.4-src/util does not exist Total time: 1 second -- Ok, it can't find it's own files Great cd jk See if this works. ant -- Buildfile: build.xml detect: [echo] jakarta-tomcat-connectors prepare: BUILD FAILED file:/data/michiel/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/build.xml:142: Warning: Could not find file /data/michiel/jakarta-tomcat-connectors-jk2-2.0.4-src/coyote/build/lib/tomcat-coyote.jar to copy. Total time: 1 second -- lets read the README.txt blablabla Tomcat 4.1. No mention of Tomcat 5.x This feels like abandoned alpha software all the way, there is NO WAY I'm putting this on a production machine. /rant-mode Summary: if you package and distribute software like this, how on earth do you expect your users to build, let alone use it? Cheers, Michiel P.S. Compare this to the Tomcat release on UNIX: tar xvzf jakarta-tomcat-xxx.tgz cd jakarta-tomcat-xxx bin/startup.sh it works Angus Mezick wrote: Jk vs jk2. JK is dead STOP USING IT. JK2 all the way!! (sorry, jk2 is the prefered way to link apache2 to tomcat[45]) I would suggest using tomcat 4 for now if you are going immediately into a production environment where you have to abide by a server level agreement. Otherwise use tomcat 5. Tomcat 5 is listed as stable but seems a bit shakey right now with the bugs that keep popping up. There is no reason that I know of not to use Apache2. You will be using worker2.properties. Since I know nothing about JK I can't comment on the rest. -Original Message- From: C. Kukulies [mailto:[EMAIL PROTECTED] Sent: Monday, April 19, 2004 5:33 PM To: [EMAIL PROTECTED] Subject: the pain of choice Can someone give me an advice which way to go WRT to using a tomcat/apache combo on a Unix (not Linux) system? There are so many options, jk, jk2, tomcat 3-4-5, apache 1.3, apache2. worker.properties worker2.properties, jk2.properties in tomcat/conf, mod_jk.conf in etc/apache, mod_jk, mod_jk2. Then I see constructs in brackets [] in worker.properties and without these. What is workers.host=jsp-hostname? Is it an IP host? Or is it some placeholder which must be in workers.list? -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Michiel Toneman Software Engineer Bibit Global Payment Services Regulierenring 10 3981 LB Bunnik [EMAIL PROTECTED] Tel. +31-30-6595168 Fax +31-30-6564464 http://www.bibit.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: the pain of choice
Sad but true. Why DON'T the ant build files work? Did someone get lazy? Is JK2 part of a source tree that we're only getting a portion of when we download the source tarball? Great, let's use JK2 My experience: rant-mode tar -xvzf jakarta-tomcat-connectors-jk2-src-current.tar.gz cd jakarta-tomcat-connectors-jk2-2.0.4-src/ less README.txt - gibberish, doesn't help me much less RELEASE-NOTES.txt -- Tomcat Connectors Version @VERSION@ Release Notes This version matches the version included with tomcat-5.0.2, and supports tomcat 3.3, 4.0, 4.1, 5.0. Bugs and issues will be tracked with tomcat5 - this file will list only issues related with older versions. -- 5.0.2??? my confidence is growing. ls doc/* doc/install_tomcat33.html doc/install_tomcat40.html doc/install_tomcat41.html Hmmm, I want to install it for tomcat 5.0.19. Ok, I'll read the most current (install_tomcat41.html). Try it, it's quite amusing... Not helpful. ant Buildfile: build.xml build: BUILD FAILED file:/data/michiel/jakarta-tomcat-connectors-jk2-2.0.4-src/build.xml:45: Basedir /data/michiel/jakarta-tomcat-connectors-jk2-2.0.4-src/util does not exist Total time: 1 second -- Ok, it can't find it's own files Great cd jk See if this works. ant -- Buildfile: build.xml detect: [echo] jakarta-tomcat-connectors prepare: BUILD FAILED file:/data/michiel/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/build.xml:142: Warning: Could not find file /data/michiel/jakarta-tomcat-connectors-jk2-2.0.4-src/coyote/build/lib/tomcat-coyote.jar to copy. Total time: 1 second -- lets read the README.txt blablabla Tomcat 4.1. No mention of Tomcat 5.x This feels like abandoned alpha software all the way, there is NO WAY I'm putting this on a production machine. /rant-mode Summary: if you package and distribute software like this, how on earth do you expect your users to build, let alone use it? Cheers, Michiel P.S. Compare this to the Tomcat release on UNIX: tar xvzf jakarta-tomcat-xxx.tgz cd jakarta-tomcat-xxx bin/startup.sh it works Angus Mezick wrote: Jk vs jk2. JK is dead STOP USING IT. JK2 all the way!! (sorry, jk2 is the prefered way to link apache2 to tomcat[45]) I would suggest using tomcat 4 for now if you are going immediately into a production environment where you have to abide by a server level agreement. Otherwise use tomcat 5. Tomcat 5 is listed as stable but seems a bit shakey right now with the bugs that keep popping up. There is no reason that I know of not to use Apache2. You will be using worker2.properties. Since I know nothing about JK I can't comment on the rest. -Original Message- From: C. Kukulies [mailto:[EMAIL PROTECTED] Sent: Monday, April 19, 2004 5:33 PM To: [EMAIL PROTECTED] Subject: the pain of choice Can someone give me an advice which way to go WRT to using a tomcat/apache combo on a Unix (not Linux) system? There are so many options, jk, jk2, tomcat 3-4-5, apache 1.3, apache2. worker.properties worker2.properties, jk2.properties in tomcat/conf, mod_jk.conf in etc/apache, mod_jk, mod_jk2. Then I see constructs in brackets [] in worker.properties and without these. What is workers.host=jsp-hostname? Is it an IP host? Or is it some placeholder which must be in workers.list? -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Michiel Toneman Software Engineer Bibit Global Payment Services Regulierenring 10 3981 LB Bunnik [EMAIL PROTECTED] Tel. +31-30-6595168 Fax +31-30-6564464 http://www.bibit.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: the pain of choice
Hi Michiel ! Cut the developers some slack, man ! Writing the software is difficult enough, if you need to do a buildfile, test it and document it, it can seem like a monstrous commitment. If you want instructions on getting it built, I just updated my Tomcat 5 document to cover jk2.0.4. The new release is, BTW, a lot less buggy than jk2.0.2, the previous release. Now, *that* one, you had to jump through hoops to get it installed, including editing the Makefile. Michiel Toneman wrote: Great, let's use JK2 My experience: snip -- A complex system that works is invariably found to have evolved from a simple system that works. ++ | Pascal Chong | | email: [EMAIL PROTECTED] | || | Please visit my site at : http://cymulacrum.net| | If you're using my documentation, please read the Terms and| | and Conditions at http://cymulacrum.net/terms.html | ++ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: the pain of choice
*shrug* I use win2k and it is EASY to use jk2 on that. Kinda bad that the unix/linux install is worse than the windows one. Sigh. --Angus -Original Message- From: Michiel Toneman [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 10:44 AM To: Tomcat Users List Subject: Re: the pain of choice Great, let's use JK2 My experience: rant-mode tar -xvzf jakarta-tomcat-connectors-jk2-src-current.tar.gz cd jakarta-tomcat-connectors-jk2-2.0.4-src/ less README.txt - gibberish, doesn't help me much less RELEASE-NOTES.txt -- Tomcat Connectors Version @VERSION@ Release Notes This version matches the version included with tomcat-5.0.2, and supports tomcat 3.3, 4.0, 4.1, 5.0. Bugs and issues will be tracked with tomcat5 - this file will list only issues related with older versions. -- 5.0.2??? my confidence is growing. ls doc/* doc/install_tomcat33.html doc/install_tomcat40.html doc/install_tomcat41.html Hmmm, I want to install it for tomcat 5.0.19. Ok, I'll read the most current (install_tomcat41.html). Try it, it's quite amusing... Not helpful. ant Buildfile: build.xml build: BUILD FAILED file:/data/michiel/jakarta-tomcat-connectors-jk2-2.0.4-src/bui ld.xml:45: Basedir /data/michiel/jakarta-tomcat-connectors-jk2-2.0.4-src/util does not exist Total time: 1 second -- Ok, it can't find it's own files Great cd jk See if this works. ant -- Buildfile: build.xml detect: [echo] jakarta-tomcat-connectors prepare: BUILD FAILED file:/data/michiel/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/ build.xml:142: Warning: Could not find file /data/michiel/jakarta-tomcat-connectors-jk2-2.0.4-src/coyote/b uild/lib/tomcat-coyote.jar to copy. Total time: 1 second -- lets read the README.txt blablabla Tomcat 4.1. No mention of Tomcat 5.x This feels like abandoned alpha software all the way, there is NO WAY I'm putting this on a production machine. /rant-mode Summary: if you package and distribute software like this, how on earth do you expect your users to build, let alone use it? Cheers, Michiel P.S. Compare this to the Tomcat release on UNIX: tar xvzf jakarta-tomcat-xxx.tgz cd jakarta-tomcat-xxx bin/startup.sh it works Angus Mezick wrote: Jk vs jk2. JK is dead STOP USING IT. JK2 all the way!! (sorry, jk2 is the prefered way to link apache2 to tomcat[45]) I would suggest using tomcat 4 for now if you are going immediately into a production environment where you have to abide by a server level agreement. Otherwise use tomcat 5. Tomcat 5 is listed as stable but seems a bit shakey right now with the bugs that keep popping up. There is no reason that I know of not to use Apache2. You will be using worker2.properties. Since I know nothing about JK I can't comment on the rest. -Original Message- From: C. Kukulies [mailto:[EMAIL PROTECTED] Sent: Monday, April 19, 2004 5:33 PM To: [EMAIL PROTECTED] Subject: the pain of choice Can someone give me an advice which way to go WRT to using a tomcat/apache combo on a Unix (not Linux) system? There are so many options, jk, jk2, tomcat 3-4-5, apache 1.3, apache2. worker.properties worker2.properties, jk2.properties in tomcat/conf, mod_jk.conf in etc/apache, mod_jk, mod_jk2. Then I see constructs in brackets [] in worker.properties and without these. What is workers.host=jsp-hostname? Is it an IP host? Or is it some placeholder which must be in workers.list? -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Michiel Toneman Software Engineer Bibit Global Payment Services Regulierenring 10 3981 LB Bunnik [EMAIL PROTECTED] Tel. +31-30-6595168 Fax +31-30-6564464 http://www.bibit.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED
Re: the pain of choice
Strange you saying that if everyday I see so many problems and bugs in jk2... A question : jk2 can use the same mod_jk.config used by jk? question 2 : I've asked before but here it goes : - How can I make tomcat generate the mod_jk.conf withou those virtualhost tag? this makes apache ignore everything that goes inside this. DO I have to configureapache to be aware of this virtualhost config? Or i have to configure some property at the respective listeners of server.xml to do this Thanks Emerson Angus Mezick wrote: Jk vs jk2. JK is dead STOP USING IT. JK2 all the way!! (sorry, jk2 is the prefered way to link apache2 to tomcat[45]) I would suggest using tomcat 4 for now if you are going immediately into a production environment where you have to abide by a server level agreement. Otherwise use tomcat 5. Tomcat 5 is listed as stable but seems a bit shakey right now with the bugs that keep popping up. There is no reason that I know of not to use Apache2. You will be using worker2.properties. Since I know nothing about JK I can't comment on the rest. -Original Message- From: C. Kukulies [mailto:[EMAIL PROTECTED] Sent: Monday, April 19, 2004 5:33 PM To: [EMAIL PROTECTED] Subject: the pain of choice Can someone give me an advice which way to go WRT to using a tomcat/apache combo on a Unix (not Linux) system? There are so many options, jk, jk2, tomcat 3-4-5, apache 1.3, apache2. worker.properties worker2.properties, jk2.properties in tomcat/conf, mod_jk.conf in etc/apache, mod_jk, mod_jk2. Then I see constructs in brackets [] in worker.properties and without these. What is workers.host=jsp-hostname? Is it an IP host? Or is it some placeholder which must be in workers.list? -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Emerson Cargnin Analista de Sistemas Setor de Desenvolvimento de Sistemas - TRE-SC tel : (048) - 251-3700 - Ramal 3181 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: the pain of choice
once I got jk2 build to work... I remember having to create dirs and copy files by hand... []s Emerson to Greg Adams wrote: Sad but true. Why DON'T the ant build files work? Did someone get lazy? Is JK2 part of a source tree that we're only getting a portion of when we download the source tarball? Great, let's use JK2 My experience: rant-mode tar -xvzf jakarta-tomcat-connectors-jk2-src-current.tar.gz cd jakarta-tomcat-connectors-jk2-2.0.4-src/ less README.txt - gibberish, doesn't help me much less RELEASE-NOTES.txt -- Tomcat Connectors Version @VERSION@ Release Notes This version matches the version included with tomcat-5.0.2, and supports tomcat 3.3, 4.0, 4.1, 5.0. Bugs and issues will be tracked with tomcat5 - this file will list only issues related with older versions. -- 5.0.2??? my confidence is growing. ls doc/* doc/install_tomcat33.html doc/install_tomcat40.html doc/install_tomcat41.html Hmmm, I want to install it for tomcat 5.0.19. Ok, I'll read the most current (install_tomcat41.html). Try it, it's quite amusing... Not helpful. ant Buildfile: build.xml build: BUILD FAILED file:/data/michiel/jakarta-tomcat-connectors-jk2-2.0.4-src/build.xml:45: Basedir /data/michiel/jakarta-tomcat-connectors-jk2-2.0.4-src/util does not exist Total time: 1 second -- Ok, it can't find it's own files Great cd jk See if this works. ant -- Buildfile: build.xml detect: [echo] jakarta-tomcat-connectors prepare: BUILD FAILED file:/data/michiel/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/build.xml:142: Warning: Could not find file /data/michiel/jakarta-tomcat-connectors-jk2-2.0.4-src/coyote/build/lib/tomcat-coyote.jar to copy. Total time: 1 second -- lets read the README.txt blablabla Tomcat 4.1. No mention of Tomcat 5.x This feels like abandoned alpha software all the way, there is NO WAY I'm putting this on a production machine. /rant-mode Summary: if you package and distribute software like this, how on earth do you expect your users to build, let alone use it? Cheers, Michiel P.S. Compare this to the Tomcat release on UNIX: tar xvzf jakarta-tomcat-xxx.tgz cd jakarta-tomcat-xxx bin/startup.sh it works Angus Mezick wrote: Jk vs jk2. JK is dead STOP USING IT. JK2 all the way!! (sorry, jk2 is the prefered way to link apache2 to tomcat[45]) I would suggest using tomcat 4 for now if you are going immediately into a production environment where you have to abide by a server level agreement. Otherwise use tomcat 5. Tomcat 5 is listed as stable but seems a bit shakey right now with the bugs that keep popping up. There is no reason that I know of not to use Apache2. You will be using worker2.properties. Since I know nothing about JK I can't comment on the rest. -Original Message- From: C. Kukulies [mailto:[EMAIL PROTECTED] Sent: Monday, April 19, 2004 5:33 PM To: [EMAIL PROTECTED] Subject: the pain of choice Can someone give me an advice which way to go WRT to using a tomcat/apache combo on a Unix (not Linux) system? There are so many options, jk, jk2, tomcat 3-4-5, apache 1.3, apache2. worker.properties worker2.properties, jk2.properties in tomcat/conf, mod_jk.conf in etc/apache, mod_jk, mod_jk2. Then I see constructs in brackets [] in worker.properties and without these. What is workers.host=jsp-hostname? Is it an IP host? Or is it some placeholder which must be in workers.list? -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Michiel Toneman Software Engineer Bibit Global Payment Services Regulierenring 10 3981 LB Bunnik [EMAIL PROTECTED] Tel. +31-30-6595168 Fax +31-30-6564464 http://www.bibit.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Emerson Cargnin Analista de Sistemas Setor de Desenvolvimento de Sistemas - TRE-SC tel : (048) - 251-3700 - Ramal 3181 - To unsubscribe, e-mail: [EMAIL PROTECTED
Re: the pain of choice
Chris, I hope you got enough information to help you decide. It seems this thread has taken on a life of its own and pushed the boundaries of being on topic for the thread. Anyway, if you have any further questions or if anyone can see any pitfalls please advise. If you still need Apache for some reason and decide to go with JK2, then research it well and ensure you are using current how-to's and files. It can be difficult. I tried it once on an earlier version and was unsuccessful due to missing files. I did not need it at the time and did not have the time to work with it further but there are many who have it up and running. Let us know you decision and why. It will help us to know what kinds of questions to ask of users in the future. Doug www.parsonstechnical.com At this point it looks like tomcat 5 will handle your needs. Look at this for cgi: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/cgi-howto.html What JDK are you developing against? -- 1.4.2 But not crucial What is you platform? -- What do you mean by that? By platform I mean the hardware you are running on. Servlet API 2.1 What is your OS? -- FreeBSD Is this for production or development? -- Production How many users?-- 2 How many deployers?-- 1 How many apps? -- 1 How big are the apps? -- very small How much static? -- ?please explain CGI, servlets, jsp etc are all dynamic. HTML, HTM, etc are static. If you have a large amount of static pages some people will use Apache to serve it and Tomcat for the dynamic. Although as Tomcat evolves it is no longer a neccesity as it was in the past. Do you want or need Apache?-- need cgi-scripting See above. (Virtual hosting?) -- absolutely not necessary Nothing here stands out that would suggest that you need anything other than Tomcat 5 running alone. But to qualify, I have not done any cgi and only did a quick take on the documentation. Read it carefully before proceeding. You may also want to start a new thread and ask the list about any limitations or concerns that are not addressed in the docs. Doug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
the pain of choice
Can someone give me an advice which way to go WRT to using a tomcat/apache combo on a Unix (not Linux) system? There are so many options, jk, jk2, tomcat 3-4-5, apache 1.3, apache2. worker.properties worker2.properties, jk2.properties in tomcat/conf, mod_jk.conf in etc/apache, mod_jk, mod_jk2. Then I see constructs in brackets [] in worker.properties and without these. What is workers.host=jsp-hostname? Is it an IP host? Or is it some placeholder which must be in workers.list? -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: the pain of choice
I don't know if you will get much response with this request. What you may wish to do is define your requirements for your application and environment. Then set back and take in all the opinions on which way is best. Here are a few questions to start with: What JDK are you developing against? What is you platform? What is your OS? Is this for production or development? How many users? How many deployers? How many apps? How big are the apps? How much static? Do you want or need Apache? (Virtual hosting?) Doug www.parsonstechnical.com - Original Message - From: C. Kukulies [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, April 19, 2004 5:32 PM Subject: the pain of choice Can someone give me an advice which way to go WRT to using a tomcat/apache combo on a Unix (not Linux) system? There are so many options, jk, jk2, tomcat 3-4-5, apache 1.3, apache2. worker.properties worker2.properties, jk2.properties in tomcat/conf, mod_jk.conf in etc/apache, mod_jk, mod_jk2. Then I see constructs in brackets [] in worker.properties and without these. What is workers.host=jsp-hostname? Is it an IP host? Or is it some placeholder which must be in workers.list? -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
