Hi,
I have a situation where our application is running in the clustered
environment
described below (this is provided by the person managing this environment):
ECC_RG is a network name that is specified in a cluster resource.
The IP 172.23.146.172 is the IP that is specified inside this group
for ECC_RG.
The way ECC_RG is set up is as follows:
The 2 nodes are 172.23.146.169 and 172.23.146.170 (losan169,
losan170)
The IP of the MCS cluster is 172.23.146.171 - This is specified in
the cluster resource group in the cluster admin.
The Resource group that is in control of the ECC part that is
installed on the cluster is ECC_RG.
In this group is a resource that defines the IP address
172.23.146.172 and also another resource that defines the network name as
ECC_RG.
So ECC_RG is not in the DNS anywhere or a WINS name. It is just
defined in the cluster group that controls the ECC install.
All of these IP's are in the hosts.txt file on both of the nodes.
When I access the application specifying the resource name ECC_RG
(http://ecc_rg:8080/login), my session is terminated
after every request. For example, say I succesfully login. If I make another
request, the session is determined to be null
and I must log back in. However, if I access the application specifying any
other resource identifier for the hosts in the
cluster, including the IP for ECC_RG (172.23.146.172 ), everything works
fine. So if instead I type http://172.23.146.172:8080/login,
I can make all the requests I want.
In looking at this with ProxyTrace, it seems that in both cases a cookie is
set on the client, but only when ecc_rg
is NOT specified in the URL, is the session cookie being passed in the
requests.
Can anyone give me a clue as to why this might be happening?
Many Thanks,
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
