Chad,
May I know the problems you had with Tomcat. We have been using Tomcat
for a production site since September 2000 with no problems.
Thanks,
Jayesh
> -----Original Message-----
> From: Chad R. Larson [SMTP:clarson@eldocomp.com]
> Sent: Tuesday, November 13, 2001 1:41 PM
> To: nickf@ontko.com; Psql-Jdbc; pgsql-admin
> Subject: Re: [JDBC] [ADMIN] PostgreSQL->JDBC->Tomcat->Apache
> resource uses
>
> At 02:55 PM 11/13/01 -0500, Nick Fankhauser wrote:
> >And finally, if anyone else is running
> PostgreSQL->JDBC->Tomcat->Apache,
> >I'm curious about your hardware configuration & experiences with it.
> Any
> >mistakes that you can help me avoid?
>
> We're doing exactly the same thing, except substitute Macromedia's
> JRun for
> Tomcat. The Apache web server is running on its own box, for
> security's sake.
> I believe any machine exposed to the great unwashed Internet ought to
> be
> considered potentially compromised and hostile. It's in it's own
> firewalled DMZ.
>
> The web server is an Intel Pentium ATX motherboard in a 1U chassis
> running
> FreeBSD 4.3. The Apache was built to include mod_ssl to support
> secure
> connections. The JRun and PostgreSQL are running on a 4 CPU Sun E3500
>
> under Solaris 2.6.
>
> We had issues with Tomcat when we evaluated it, hence the JRun.
> Tomcat may
> be fixed by now, and we may revisit that issue when the JRun license
> is up
> for renewal. I also see no reason other than management skittishness
> that
> we couldn't run the backend on something like a 4 CPU 800MHz Xeon Dell
>
> server and FreeBSD. We've had fewer problems with the FreeBSD than
> with
> Solaris.
>
>
> -crl
> --
> Chad R. Larson (CRL22) chad@eldocomp.com
> Eldorado Computing, Inc. 602-604-3100
> 5353 North 16th Street, Suite 400
> Phoenix, Arizona 85016-3228
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to
> majordomo@postgresql.org)