Okay,

well, we haven't really done JSP/Tomcat on shared hosting before... We did allow it on our dedicated / colocated systems of course... But someone tell me, does it use a lot of resources?
Can it run safely on say, a 1.2 TBird (AMD) with 512 RAM?

VOTE! And explain why...

Originally posted by Eagle
Should I offer this to my clients or not (because it might use a lot of RAM / CPU)?
You may want to check the forum rules on this one...
Participants may not solicit the membership for feedback or suggestions on their product or services.

Originally posted by IntelligentHosting.com

You may want to check the forum rules on this one...


Thanks,
I took that part out :-)

How do you use Tomcat for shared hosting so that all the domains in server can run servlet or JSP from there own site.
If you have done it then please let me know.

I would like to know too :D

once you set up tomcat, you need to configure your both httpd.conf and server.xml to allow virtual hosting, also, make sure you restart tomcat server before reboot httpd server.

How it works is that, if httpd catches anything with extension of .jsp or anything under /servlet directory of the virtualhosting account, it sends directly to tomcat web server engine and thus everything gets parsed from there.

Your 512 MB ram and the 1.2 GHZ should handle them fine.

Vitual Hosting + Tomcat = :(

It's a pain!

We do it, but yes it is a PAIN.

Originally posted by Helicon
once you set up tomcat, you need to configure your both httpd.conf and server.xml to allow virtual hosting, also, make sure you restart tomcat server before reboot httpd server.

How it works is that, if httpd catches anything with extension of .jsp or anything under /servlet directory of the virtualhosting account, it sends directly to tomcat web server engine and thus everything gets parsed from there.

Your 512 MB ram and the 1.2 GHZ should handle them fine.



How to configure server.xml and httpd.conf for virtual hosting?
Our html files are in /home/httpd/html/ where we should upload the servlet or jsp files in which directory.

To answer your question would take 5 pages of documentation, jolly.

Have you installed tomcat on your server yet?

If you haven't, start with JDK 1.3 from http://java.sun.com,

then goto http://jakarta.apache.org/ for tomcat download and documentation.

Once you have tomcat installed, you are not done yet.

Go get mod_jk and install it.

If you can get all the above done, let me know, I'll help you configure the VH.

Why is it a pain

Originally posted by Helicon
To answer your question would take 5 pages of documentation, jolly.

Have you installed tomcat on your server yet?

If you haven't, start with JDK 1.3 from http://java.sun.com,

then goto http://jakarta.apache.org/ for tomcat download and documentation.

Once you have tomcat installed, you are not done yet.

Go get mod_jk and install it.

If you can get all the above done, let me know, I'll help you configure the VH.


I have installed JDK and uploaded tomcat on server. What should I do next. Could you please help me.

I have used TomCat for virtual hosting before - but it does use some system resources however. It scales really bad in fact.

I would any day recommend installing the Resin engine instead - it's fast, doesn't use as much memory, easier to configure and generally runs great!

The down side is that Resin costs money. But compare the (relatively) small price tag to the savings you make by not having to buy extra RAM and for the time saved in setting it up.

Uploaded tomcat is not enough, you need to follow the instruction and install the tomcat webserver.

See if you can actually start the server and goto http://yourdomain.com:8080, which is the default port of the tomcat webserver.

If that's done, then we can go ahead get mod_jk and start configuring VirtualHosting.

Hmm

but do you think it is worth installing Tomcat / JSP for your clients?
It is a nice system, so it should be able to run it...
Or does it use just TO MANY resources?

Tomcat web server itself doesnt take much resource.

However, there are way too many bad Java developers out there, one bad program can eat up your entire resource.

Well, that goes with any other scripting language such as Perl (especially mod_perl) or PHP.

But I think its a good feature to offer to your clients, most likely they wont be using it anyway other than Java developers.