ARA on AWS using ELB

[RazDamaschin603129]

Hello,

We recently moved our ARA to AWS. In a nutshell, we have 2 linux machine running ECC behind an ELB, 2 Windows Machines running ARA behind an ELB and 1 Windows machine running the AE.

The issue we are having is that when having 2 instances of ARA running in the same time, when logged in as admin into a client that has access to Release Automation, we cannot see the "Release Automation" Tab on the left side when creating or editing a user, so we cannot give them rights to ARA on that client. The moment we take any of the 2 instances out of service, the tab will appear.

Does anyone have experience with creating a similar setup in AWS and willing to share the experience?

Thank you,
--Raz

[Michael Pirson]

Hey Raz,

I would look at the following article:

https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-sticky-sessions.html

EDIT: I found this piece in the documentation:

Requirements for Load Balancers

• To run with AWI, your load balancer must support sticky sessions. Like many Java webapps, AWI uses the JSESSIONID session cookie. You can configure your load balancer to use this cookie, or add its own, to route requests of the same session to the same server. 
• If you run AWI with websockets enabled, your load balancer must support them.

• Please use the same path on your load balancer and the servlet containers.

  Example:

  If your servers are located on http://backend1/awi and http://backend2/awi, and your load balancer is located on the host publicawihost, configure your load balancer to serve AWIon http(s)://publicawihost/awi.

https://docs.automic.com/documentation/webhelp/english/ARA/12.1/DOCU/12.1/ARA%20Guides/Default.htm#Installation_Manual/AWI/ConfiguringAWI.htm?Highlight=sticky%20sessions

*Every time I've seen this issue it has been due to the sticky sessions configuration.

[Aarusha_9652]

This post was removed [at your discretion: there was no link to the initial question]               

[RazDamaschin603129]

Michael_Pirson
Thank you for your insight. I tried that path, however, the issue persists. The load balancing does work for the AWI, both instances are serving properly there.

The problem is with the ARA load balancing. When the second ARA instance is in the pool, the Release Automation perspective does work, but when I edit or create a new user I cannot see the 'Release Automation' tab on the left side of the screen, so I can't give users access to that. I do have cookie stickiness turned on in the ELB and I tried both 'Enable load balancer generated cookie stickiness' as well as 'Enable application generated cookie stickiness'

com.uc4.bond.api.errorhandling.BondApiException: Error in asynchronous call.

[Michael Pirson]

Hey Raz,

That seems like it would be the correct approach to this.

I would probably engage support at this point. With proper debugging enabled they should be able to track a specific user session throughout the entire app. I don't have access to an ARA system anymore or id run a test debug for you.

I would assume its DEBUG for the logback.xml and log4net but they should be able to provide instruction if you want to continue to troubleshoot on your own.

Good luck!