mod_cluster will use the AJP connector if it is defined, though it does
not require it (i.e. it can use the HTTP connector). That said, I
completely disagree with the notion that we shouldn't include support
for httpd proxying in a development profile. This is not an uncommon
setup for a development environment. As mod_cluster is now our
recommended httpd proxying/load balancing technology, IMO, it is quite
appropriate to include it in the "default" profile.
On Thu, 2010-09-23 at 11:52 -0400, Bill Burke wrote:
mod-cluster has replaced the old AJP connector? I'm advocating
anything from 'default' that doesn't make sense for development.
On 9/23/10 11:46 AM, Paul Ferraro wrote:
> mod_cluster.sar provides AS support for the mod_cluster httpd module.
> The "default" profile has always included support for the mod_jk and
> mod_proxy httpd modules via the AJP connector in jbossweb.sar's
> server.xml and the supporting JvmRouteValue. Are you advocating for the
> removal of these from "default" as well?
> On Wed, 2010-09-22 at 11:39 -0400, Bill Burke wrote:
>> As I've stated before, we should move away from 'all' vs.
>> instead focus on 'production' and 'development' profiles. IMO,
>> mod-cluster, or any clustering, should not be in the 'development'
>> profile no matter how fast or slow it is. In my experiments, gutting
>> non-development and legacy components had a significant impact 5-10% on
>> boot time.
>> On 9/22/10 5:14 AM, Jaikiran Pai wrote:
>>> Had a chat with Remy about this and it looks intentional to have it in
>>> "default". Since this doesn't add any noticeable time during
>>> boot, I believe it's OK to have it in "default".
>>> On Wednesday 22 September 2010 02:11 PM, Jaikiran Pai wrote:
>>>> In AS trunk, I see that we are deploying mod_cluster.sar in the
>>>> "default" JBoss AS config. Do we need that for
>>>> jboss-development mailing list
>>> jboss-development mailing list
> jboss-development mailing list