this configuration works for us. JRun doesn't handle some media types quite
rights (Shockwave files that load other Shockwave files could never find the
next file to load.....), Apache works just fine.
Joe Niski | Senior Software Engineer/Internet Architect
503.548.2176
CYBERSIGHT
strategy . marketing . design . technology
los angeles . portland . san francisco . toronto
> -----Original Message-----
> From: Benjamin Garfield [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 02, 2001 12:32 PM
> To: JRun-Talk
> Subject: Re: Apache & JRun
>
>
> Have you tried adding the following line to your
> local.properties file?
>
> default-app.use-webserver-root=true
>
> This is supposed to tell JRun to use the equivalent document
> mapping in the web server for all HTML and image
> content. If you use webapps, you will probably have to add
> an additional line for each webapp. For webapps, the
> webapp name would replace default-app.
>
> - Ben
>
> [EMAIL PROTECTED] wrote:
>
> > I also had this problem but with JRun and Netscape Server.
> If the app is
> > installed in the '/' virtual URL, Netscape will pass all
> requests for html,
> > images, etc to JRun, which results in a big performance hit
> for pages with
> > lots of elements.
> > So we have the same question. I'm sure there must be an
> option I can put in
> > the .properties file to fix this...anyone know?
> >
> > We also had to move our app to a '/app' directory so that
> /images and
> > /scripts would get served by netscape server.
> >
> > Even if you can't get this, you still get many of the
> benefits of having a
> > 'production quality' webserver in front of JRun. E.G:
> Ability to limit
> > maximum number of simultaneous connections, use standard
> webserver logging,
> > plus it will likely be generally better at handling heavy
> volumes and large
> > numbers of connections.
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, May 02, 2001 11:35 AM
> > To: JRun-Talk
> > Subject: Re: Apache & JRun
> >
> > Putting Apache in front of JRun should have the effect that
> all images and
> > static pages are handled by Apache, which scales much better and can
> > handle alot of users. JRun gets all requests in the
> (virtual) application
> > directory and should delegate them back to Apache.
> >
> > Apache answers HEAD request correctly to tell the client to GET the
> > page again when it has changed (but JRun should do this also), which
> > means that images/etc. will be cached on the client or proxy side.
> > JRun web server can be turned off when using Apache which should
> > save some CPU cycles. It's also a good thing to be able to configure
> > authentication in JRun (which means in one place) for all kind of
> > content and having it working for all kind of content.
> >
> > But here at Sysis we have problems when JRun is used together with
> > Apache. We had serious performance issues with just a few users on
> > a Dual 800 MHZ / 1 GB machine (Linux).
> >
> > In the default JRun & Apache configuration JRun seemed to be
> > handling all requests and not delegating static content
> back to Apache.
> > We verified this by calling "kill -quit" on the Java
> process several times.
> > The thread stack showed that most threads were spending their time
> > in the FileServlet which resulted in nearly 100% CPU usage.
> >
> > The only solution we found was to move the application
> directory from
> > "/" to "/xyz". Images were still referenced using
> "/images", which meant
> > that Apache handled these files directly and JRun had no chance to
> > get these request. We got a big performance boost from this.
> >
> > The performance problem was magnified because the browser never
> > seemed to cache the static content. This seems to be a problem with
> > JRun, because when Apache is used, caching on the client side worked
> > again.
> >
> > But we are not really happy with the solution because it
> means alot of
> > additional installation/setup effort, but at least it seems to work.
> >
> > So our question is how to configure JRun & Apache so that we get a
> > system that performs well. Is it the right solution to
> create separate
> > virtual directories for static and dynamic content or is there a
> > simpler solution?
> >
> >
> >
> > "eric cheng"
> >
> > <eric.cheng@smart-p To: JRun-Talk
> > <[EMAIL PROTECTED]>
> > layer.com> cc:
> >
> > Subject:
> Apache & JRun
> >
> > 30.04.01 11:48
> >
> > Please respond to
> >
> > jrun-talk
> >
> >
> >
> >
> >
> > Hi, everybody
> >
> > I got a serious concept-wise question
> >
> > According to the guide of JRun, JRun actually can run as a
> standalone
> > server
> > which means it can serve the purpose as the apache. It can
> deliver html. Am
> > I correct
> >
> > However, we are able to configure it as with external web
> server by using
> > the connector. What will be the benefit of this?
> >
> > This is the most important question that really confused me.
> > Even after I configured the apache and JRun, how do I know
> that the html
> > file is served by the apache instead of the JRun? How can I
> make sure that
> > JRun is only doing its own job - serving those jsp and
> servlet instead of
> > html and other stuff which is supposed to be done by apache.
> >
> > If I configured properly, does it mean that the jsp file
> which I put under
> > the documentdirectory of apache will be responsed by JRun?
> >
> > Looking forward to your valuable feedback
> >
> > Best Regards,
> > Gigi2
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
