Ok, good... I thought that was the plan I heard (clustering eventually but
not in 1st release) but just wanted to confirm.
Both forwards and backwards compability between v2 and v3 node agents would
be nice but not sure how important until I see exactly what sort of
clustering a V3 DAS will support I guess.
On 12/10/09 3:47 PM, "John Clingan" <John.Clingan_at_Sun.COM> wrote:
>
> On Dec 10, 2009, at 12:24 PM, Comerford, Sean wrote:
>
>> What is the plan around clustering in V3?
>>
>
> It is in the plans. Working on the v3.next roadmap. Stay tuned.
>
>> It seems to have been completely dropped in the initial release.
>>
>
> It was not planned for the initial release, but we are working on it for an
> update release. Note, this is the same approach we took with Java EE 5. First
> release is Java EE compatible but single instance. Update release adds HA and
> centralized admin. mod_jk provides service availability for GlassFish v3.
>
>> Will a V2 DAS be able to manage a V3 instance at some point?
>>
>
> No, although moving forward that is an interesting requirement. We'll likely
> change the remote administration API (JMX/RMI to http-based), so it would take
> extra effort from v2 to v3, but v3 and beyond ... Hmmmm ...
>
>> Will there be a V3 DAS?
>>
>
> Yep, that's the plan.
>
>
>> Or is clustering more or less a dead feature at this point?
>>
>
> Nope, I've addressed that above.
--
Sean Comerford, Software Engineer
ESPN.com Site Architecture Group
Office: 860.766.6454 Cell: 860.329.5842