On Sun, Jan 07, 2001 at 07:43:42PM -0500, Scott M. Stirling wrote:
> Throwing Apache in the front end is bound to decrease performance,
> versus using Orion's HTTP server. It's certainly the easiest (and a
> good portable one -- better than ipchains) solution, but I didn't
> mention because it defeats the purpose of using Orion as the web server
> for performance.
If you configure Apache as a Proxy Http-Server for orion running on an
unpriviliged (>1024) port should not really decrease performance.
Have a look for the mod_rewrite and mod_proxy Documentation on your
favourite www.apache.org mirror.
> The real problem expressed by the original email is that regular
> restarts of the server are necessary. All Java app servers suffer from
> this in one place or another. Eventually, they'll all have to be able
> to dynamically reload configuration settings, and any class or
> component. Orion is all ready well on the way toward that goal with
> dynamic reload of ears, EJB jars, servlets, etc.
Restarting of the orion appserver are possible via ormi (see admin.jar),
the apache webserver IMHO should not be needed to restart.
Happy hacking,
-billy.
--
Philipp Meier o-matic GmbH
Gesch�ftsf�hrer Pfarrer-Wei�-Weg 16-18
Tel.: +49-(0)700-66284236 89077 Ulm
PGP signature
