I have tried both Elastic Load Balancer and Apache HTTP load balancer, both of them with same effect. But apparently, as the instances are seeing each others, this settings works. One key factor is that the cluster is on Amazon AWS, and just because I am not sure that multicast is fully supported, I switched the cluster broadcast to TCP by using the GMS_DISCOVERY_LIST. I have also increased logging to maximum level but there's no trace of error or similar. All the articles and blog I have read reports to same same resolution steps which I have already applied. I have spent almost a week trying to understand what's going on with no luck. The web.xml contains the tag and the app is deployed with -availabilityenabled true and I have added to the glassfish-web.xml.įinally, the cookie is also set correctly and I am verifying the correctness of the cookie in the browser inspector.
ProcessCacheUpdate : instance1 's state is aliveandready]]
ProcessCacheUpdate : instance2 's state is aliveandready]] Instance 2 [timeMillis: 1Īlso from DAS log the overall situation seems fine: [[ This is the log that confirm that the instances are correctly seeing each others: In fact if the cluster contains only one node everything works fine.Īs soon as I add another node, despite the log message shows nothing wrong is happening, a new JSESSIONID is created on each request. At first I thought that the problem was related to JSF itself, but then as soon as I got deeper in the matter, I realized that the problem is likely in the cluster configuration. The app is a standard JSF app (with Primefaces). I am trying to configure a Glassfish cluster following the official HA guide.
0 kommentar(er)
