ah, ok... I saw another thread that said:
"We have not started any work wrt cluster and session state replication in
the v3 workspace.
I believe though that you can front separate v3 instances with Apache mod_jk
with sticky loadbalancing but that would be without session state
availability.
We plan to get to it as soon as we are done with Sailfin v2."
guess that answers my question then, thanks!
On Sun, Dec 13, 2009 at 11:11 PM, CS Wong <lilwong_at_gmail.com> wrote:
> not having a centralized admin isn't a deal-breaker, but would this mean
> that session replication between nodes is not supported as of v3.0 as well?
> thanks!
>
>
> On Thu, Sep 3, 2009 at 9:18 PM, Alexis Moussine-Pouchkine <alexis.mp@
> sun.com> wrote:
>
>> v3.1 is when we'll have parity with the v2 clustering features.
>> v3 will only support lightweight clustering via mod_jk, no centralized
>> admin.
>> -Alexis
>>
>>
>> On Sep 3, 2009, at 14:32, glassfish_at_javadesktop.org wrote:
>>
>> Hi,
>>>
>>> I'm confused about one aspect of this presentation:
>>>
>>> http://mediacast.sun.com/users/am74686/media/GlassFishv3-EnRoutePourJavaEE6.pdf
>>>
>>> "V3.1 full clustering
>>> -> Likely 6 to 9 months after V3"
>>>
>>> What will be missing in the V3.0 clustering? Will it have less features
>>> than V2.1 clustering?
>>>
>>> Best regards,
>>>
>>> Matthias
>>> [Message sent by forum member 'matthiasfraass' (
>>> matthias.fraass_at_tricoder.net)]
>>>
>>> http://forums.java.net/jive/thread.jspa?messageID=362808
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>>
>