Additional hippo instance on new port goes into infinite loop

Experience Manager (PaaS/OnPrem)
1

When we are trying to run an additional hippo instance on new port i.e. 8090, it goes into an infinite loop between /cms and /cms/?0
Our main instance is behind ELB and running on https while we are trying to run this additional instance on http, are we missing any configurations here?

2

see:
https://documentation.bloomreach.com/library/enterprise/installation-and-configuration/hippo-cms-loadbalancing-requirements.html

It boils down to the fact that you need sticky sessions for authoring instances.

3

Persistence, or sticky sessions should be configurable for most Loadbalancers. ELB also has this available: https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-sticky-sessions.html

The bigger problem I can see is that one listens on https, and the other on http, which will probably require some extra rules in your loadbalancer.

4

Thanks for the suggestions.
We tried putting a forward rule on ELB that forward from 80 to 8090 and configured ELB based sticky sessions but still we are facing the same issue.
http://:8090 works fine i.e. displays blank screen
while http://:8090/cms goes into an infinite loop between /cms and /cms/?0

Any pointers would be appreciated.