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.
'default' and
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 the AS
> boot, I believe it's OK to have it in "default".
>
> -Jaikiran
> 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 "default"?
>>
>> -Jaikiran
>>
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jboss-development
>
>
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development