| From | Sent On | Attachments |
|---|---|---|
| Comerford, Sean | Dec 10, 2009 12:23 pm | |
| John Clingan | Dec 10, 2009 12:47 pm | |
| Comerford, Sean | Dec 10, 2009 12:54 pm | |
| Dominik Dorn | Dec 10, 2009 1:03 pm | |
| Alexis Moussine-Pouchkine | Dec 10, 2009 1:29 pm | |
| Jan Luehe | Dec 10, 2009 1:34 pm | |
| Eduardo Pelegri-Llopart | Dec 10, 2009 2:12 pm |
| Subject: | Re: V3 clustering support? | |
|---|---|---|
| From: | Alexis Moussine-Pouchkine (alex...@sun.com) | |
| Date: | Dec 10, 2009 1:29:14 pm | |
| List: | net.java.dev.glassfish.users | |
Terracotta supports GlassFish v2.x. I see no technical reason for v3 to be an issue but you should ask TC. cheers, -Alexis
On Dec 10, 2009, at 22:04, Dominik Dorn wrote:
Terracotta integration would really rock. Afaik, they also have integrations for JMS + Tomcat etc. already.
On Thu, Dec 10, 2009 at 9:47 PM, John Clingan <John...@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





