rave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Geer <ch...@cxtsoftware.com>
Subject Re: Intermittent problems running a Rave extension project
Date Tue, 24 Jul 2012 17:46:23 GMT
On Tue, Jul 24, 2012 at 10:40 AM, Carlucci, Tony <acarlucci@mitre.org>wrote:

>
>
> >-----Original Message-----
> >From: Chris Geer [mailto:chris@cxtsoftware.com]
> >Sent: Tuesday, July 24, 2012 1:12 PM
> >To: dev@rave.apache.org
> >Subject: Re: Intermittent problems running a Rave extension project
> >
> >On Tue, Jul 24, 2012 at 10:04 AM, Carlucci, Tony <acarlucci@mitre.org
> >wrote:
> >
> >> Hi Rave Devs,
> >>
> >> We've got a Rave extension project setup on our servers using Apache 2.2
> >> and tcServer 2.0.4 (Tomcat 6) and we are getting intermittent 500
> errors.
> >> Here is a link to the email I sent to the Apache HTTPD users list that
> >> explains the problem:
> http://httpd.markmail.org/thread/yzbyf7xrn5jbqghm
> >>
> >> I was wondering if anyone has setup Rave or a Rave extension project
> >> running on Apache 2.2.x and tcServer / Tomcat 6, using mod_proxy_ajp as
> the
> >> connector?  We have seen this issue on different servers, and only with
> >> this particular application (other internal Java web apps running within
> >> the same instances), so I'm starting to think that something in either
> the
> >> Rave code base or our custom extension code is triggering the issue
> within
> >> the mod_proxy_ajp connection.   Any insight would be appreciated to
> help me
> >> isolate where the issue could be?
> >>
> >
> >Tony,
> >
> >We run a similar setup however we just use the http proxy, not the ajp
> >connector, without problems. When I first set ours up I thought I saw that
> >the HTTP module was recommended over AJP even with Tomcat but I don't know
> >where I saw that. Do you guys see big advantages to using AJP?
>
> Good to know Chris, thanks for the info.  I'll see if we can try using the
> HTTP connector instead of AJP and see if that makes a difference.  I'll
> talk with our sysadmins as to why we have historically used AJP instead of
> HTTP (there could be a legitimate reason like our SSO infrastructure).
>
> Do you have the same versions: Apache 2.2.x and Tomcat 6?
>

We are actually using Apache 2.4.x because we wanted to use form
authentication and session state at the Apache level. (never make it past
the proxy unless you are authenticated)

>
> >
> >
> >> Thanks, Tony
> >>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message