Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (nike.apache.org: domain of kevan.miller@gmail.com
 designates 209.85.213.54 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1257)
Subject: Re: Regarding GERONIMO-6317 Profiling clustering modules to save
 build time
From: Kevan Miller <kevan.miller@gmail.com>
In-Reply-To: <4F7F01E4.4040507@cait.org>
Date: Fri, 6 Apr 2012 11:11:03 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <59355147-A454-4481-B1AD-896B0789EFDE@gmail.com>
References: <4F7DA321.1090009@cait.org>
 <A880121E-D7C8-4D8A-9F75-1BCBB84A74CF@gmail.com> <4F7F01E4.4040507@cait.org>
To: dev@geronimo.apache.org


On Apr 6, 2012, at 10:47 AM, Russell E Glaue wrote:

>=20
> On 04/05/2012 02:49 PM, Kevan Miller wrote:
>>=20
>> On Apr 5, 2012, at 9:50 AM, Russell E Glaue wrote:
>>=20
>>> "Clustering features are not available in the current 3.0-beta =
branch, so add some profiles to not build it, thus save the build time."
>>>=20
>>> Is commit 1309635 related to this?
>>>=20
>>>=20
>>> Is someone able to explain why WADI Clustering and Plugin Farming =
are not available in the 3.0-beta branch? Is it broken?
>>=20
>> Hi Russell,
>> The WADI project seems to be largely dormant. Without anyone willing =
to bring the function forward, I don't think anyone has looked at trying =
to get it to work on a 3.0 base.
>>=20
>> Is WADI important to you?
>>=20
>> --kevan
>>=20
>=20
> I'm wanting to get Geronimo up in my employer's web farms, and finally =
getting multiple instance support was a huge step forward for me. But =
now removing support for clustering is a step backward. We had been =
planning on its use.
>=20
> Some mechanism is important to anyone who wants web user sessions to =
have persistence among multiple clustered/loadbalanced Geronimo servers. =
And we have had (used to anyway) lots of conversations on the importance =
of Geronimo clustering capabilities and how to do it.
> https://cwiki.apache.org/GMOxDEV/clustering-initial-discussion.html
>=20
> Yes.., we can use other 3rd party like Terracotta, but that does not =
make Geronimo enterprise-ready out-of-the-box. And the terracotta plugin =
is probably not updated for 3.0.
> =
https://cwiki.apache.org/GMOxDEV/clustering-geronimo-with-open-terracotta.=
html
>=20
> If we remove WADI support, will we replace it with some other =
mechanism to share web user sessions among Geronimo instances? Or will =
we tell users to rely on tomcat's and jetty's native session replication =
and management? This alternative will not be a clean configuration, =
since the changes would have manually to go into tomcat and jetty server =
config files - not deployed as plans.

OK. So, for session replication, most people that I know of use Tomcat =
native clustering =
(https://cwiki.apache.org/GMOxDOC30/tomcat-native-clustering.html). Does =
that not work for you? If we can go into specific issues, that would be =
great...

Great conversation to be having. Thanks!

--kevan=