Hi Wilfred,
I hope you have set persistence-type to "replicated" under
"web-containter-availability". This will enable in-memory replication
and session failover will work.
Thanks,
Kshitiz
wil2008 wrote:
> Hi Gopal
>
> Thank you for your suggestions!
>
> Yes I used the in-memory replication as the session persistence mechanism.
>
> I've also tried the "file" option. However the directory I named remains
> empty all the time.:-(
> (I named the directory through the Admin Console:
> Configurations -> (mycluster-config) -> Web Container -> Store Properties ->
> Directory)
>
> The "availability" at the levels of "Web Applications", "Availability
> Services" , "Web Container Availability" and "Heartbeat" for my cluster have
> all be set. There is <distributable/> in web.xml
> Anything else did I miss ?
>
> Is that I still have not activated any replication at all?:confused:
>
> I'm eager to learn if anyone did succeed in getting session failover with a
> similar setup?
>
> Thank you very much for any clue!
>
> Wilfred
>
>
> Gopal Jorapur wrote:
>
>> Hi Wilfred,
>>
>> Are you using in-memory as the session persistence mechanism?
>>
>> Please follow the links in this blog
>> http://blogs.sun.com/quality/entry/glassfish_for_enterprise
>>
>> You need to do little bit of configuration (make your application highly
>> available and deploy with --availability enabled flag)
>>
>> They are explained in the above blog
>>
>> Also, here is one blog (follow the later part which is common for apache
>> and other web servers)
>>
>> https://glassfish.dev.java.net/javaee5/build/GlassFish_LB_Cluster.html
>>
>> Thanks,
>> Gopal
>>
>> wil2008 wrote:
>>
>>> Hello
>>>
>>> I've read the 2 links referred to in this thread.
>>> Yet I still have problems getting failover to work when I load-balanced a
>>> Glassfish cluster with an Apache front-end. :(
>>> Glassfish v2 UR2
>>> Apache 2.2
>>> mod_jk 1.2.26
>>> AJPv13
>>>
>>> It seemed to me that when an instance went down, glassfish somehow did
>>> not
>>> have the data for the session with that instance, and thus in another
>>> instance it created a new session.
>>> I've double checked that the jvmRoute name in glassfish jvm option (for
>>> use
>>> with AJP) matched those in apache's workers.properties file, as done in
>>> this
>>> link
>>> http://blogs.sun.com/jluehe/entry/supporting_apache_loadbalancer_with_glassfish
>>>
>>> Did anyone try a similar setup and succeed?
>>>
>>> Thank you very much!
>>>
>>> Wilfred
>>>
>>>
>>> glassfish-2 wrote:
>>>
>>>
>>>> Hope this helps:
>>>>
>>>> https://glassfish.dev.java.net/javaee5/build/GlassFish_LB_Cluster.html
>>>> http://developers.sun.com/appserver/reference/techart/glassfishcluster/index.html
>>>> [Message sent by forum member 'janey' (janey)]
>>>>
>>>> http://forums.java.net/jive/thread.jspa?messageID=252393
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>