Yes, the current builds of GlassFish v2 support session state fail over
in clustered environment.
I do not understand what you mean by transaction state failover, but I
will take a shot.
In-flight transactions at the time of a failure are aborted. If you
configure transaction log to be stored on a shared file system (or
database), then one of the healthy instances will recover transactions
automatically as soon as failure is detected. If the transaction log is
not reachable by the healthy instances, then the recovery will happen at
the time failed instance is restarted. This is supported in current
builds of GlassFish v2.
If automatic retry of transaction is important to you, there is an
option to configure idempotent URLs in the load balancer and have the
load balancer retry a request automatically in case of a failure. (BTW,
before someone points this out, this is exactly opposite of what
idempotent URLs are supposed to do, so I am not going to recommend doing
that).
For more on transaction recovery, see
http://docs.sun.com/app/docs/doc/819-3672/6n5sj2sm2?a=view
Hope this helps,
legolas wood wrote:
> Thanks Abhijit,
> Does current builds of Glassfish v2 support session/transaction state
> fail-over in clustered environment?
>
> Abhijit Kumar wrote:
>> If you do not need session state fail-over and are using http to
>> access your application then you might be able to use http load
>> balancer from GlassFish v2 along with two or more installations of
>> GlassFish v1 running your applications. If you need session state
>> failover and complete cluster management features then your best bet
>> is to move to GlassFish v2.
>>
>> Instructions for configuring load balancer is at
>> https://glassfish.dev.java.net/javaee5/build/GlassFish_LB_Cluster.html
>>
>> Alexis Moussine-Pouchkine wrote:
>>> no, glassfish v1 is the same as SJS App Server 9.0 PE.
>>> 9.1 is the same as GlassFish v2 (now in Beta 1).
>>> -Alexis
>>>
>>> legolas wood wrote:
>>>> Thank you for reply.
>>>> Can you please tell me whether *Sun Java System Application Server
>>>> 9.1* is the same with *glassfish-installer-v1_ur1-p01-b02.jar* .
>>>> I think i read somewhere that, Sun application server 9.1 is based
>>>> on Glassfish version 2.0
>>>> and our application does not works on glassfish version 2.0 (We do
>>>> not investigate what is incompatibility yet.)
>>>>
>>>>
>>>> Thanks
>>>>
>>>>
>>>> Pankaj Jairath wrote:
>>>>> Check these docs - http://docs.sun.com/app/docs/coll/1343.4.
>>>>> Specifically High Availability Administration Guide. In the
>>>>> existing HA mechanism, you can define cluster of server instances
>>>>> the membership of which can change dynamically (explicitly add
>>>>> instances, delete instances, failure). HA over a given protocol
>>>>> (for ex: HTTP, RMI-IIOP) would provide for failing over the
>>>>> request to another available / healthy instance in the defined
>>>>> cluster
>>>>>
>>>>> You can however use the self-management feature of GlassFish to
>>>>> automate the addition/start of another server instance in case of
>>>>> instance failures events
>>>>>
>>>>> regards
>>>>> Pankaj
>>>>>
>>>>> Sarah kho wrote:
>>>>>
>>>>>> Hi
>>>>>> Any comment?
>>>>>>
>>>>>> thanks
>>>>>>
>>>>>>
>>>>>> On 4/10/07, *Sarah kho* <sarah.kho_at_gmail.com
>>>>>> <mailto:sarah.kho_at_gmail.com>> wrote:
>>>>>>
>>>>>> have looked at glassfish web site and i find some information
>>>>>> about glassfish version 2 clustering and HA.
>>>>>> We have an application running on glassfish version 1 and we
>>>>>> need
>>>>>> to deploy a cluster for our customer.
>>>>>>
>>>>>> what i am looking to find is:
>>>>>> -some manual about clustering Glassfish version 1.0 to handle
>>>>>> high
>>>>>> loads (we need session replication and ...)
>>>>>> -some manuals and tips about setting up glassfish application
>>>>>> server in HA Mode, is there some hardware/software that can
>>>>>> detect one instance failure and start another machine? Does
>>>>>> glassfish /sun provide this hardware/software?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> 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
>