Hi:
One smalll addendum. Since junkeira seemed to want to have a 2 machine
cluster, then what Shreedhar refers to as "port-hopping" will not work
and you
must use an intervening loadbalancer. "port-hopping" only will work
when you
use a single host and only change the port part of your url. This takes
advantage
of the way browsers handle cookies. If the JSESSIONID cookie in particular
for your session on the first instances is not sent as part of the
request to the second
instance then (by definition) a new session must and will be created.
hope this helps
Shreedhar Ganapathy wrote:
> Hi
> The method you are following whereby you call each instance on its own
> listener port would require you to move to the url of the other
> instance in order to see session availability. i.e
>
> http://<node1HostName>:<node1Port>/clusterjsp/
>
> to
>
> http://<node2HostName>:<node2Port>/clusterjsp/
>
>
> This is what we call instance or port hopping which is useful for
> testing replication at the GlassFish level but this is not what you'd
> want to do for your production deployment.
>
> If you would like to be able to access a url without having to change
> the underlying instance host and port, you have to front it with a
> load balancer/proxy.
>
> That is the recommended way to deploy to production in a highly
> available environment at the basic level.
>
> Beyond this, to adequately provide redundancy to prevent single points
> of failure in the production deployed setup, it is recommended to use
> a Hardware LB in front of a Web Server cluster, which in turn, uses
> the LB plugin to load balance to a GlassFish cluster. Additionally,
> at the NIC card level, you would want to have multple network
> interfaces to provide redundancy at that level as well.
>
> Here are two good resources for starters:
> https://glassfish.dev.java.net/javaee5/build/GlassFish_LB_Cluster.html
> http://docs.sun.com/app/docs/doc/819-3679 (official high availability
> document)
>
> hth
> Shreedhar
>
>
> glassfish_at_javadesktop.org wrote:
>
>> hi all,
>>
>> I followed the typical process described in many blogs:
>> http://blog.augmentedfragments.com/2007/11/project-part-2-glassfish-cluster.html
>>
>>
>> and so I have two machines with the configuration:
>> cluster
>> node1
>> instance1
>>
>> node2
>> instance2
>>
>> then I connect to the node1 by the url:
>> http://<node1HostName>:<node1Port>/clusterjsp/
>>
>> How to ensure the following situation:
>> - stop the node 1 instance, the instance1
>> - the browser accessing through the link without changing
>> does not notice anything, the node2 start to answer
>>
>> I have set the cluster "availability" box as enable.
>> I already did the changes </distributable> in the clusterjsp example.
>> I still lose the connection, is there anything that I'm missing?
>> (is possible to access the other machine by changing the link,
>> but it creates a new session,but it should be transparent)
>> thanks in advance
>> [Message sent by forum member 'junkeira' (junkeira)]
>>
>> http://forums.java.net/jive/thread.jspa?messageID=271237
>>
>> ---------------------------------------------------------------------
>> 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
>