Lately I’ve been having some issues with our web app and I was wondering if anyone could help or point me to the right direction.
In the first 2 cases I have monitored and the JSESSIONID cookie is correctly set and returned with all subsequent requests (always the same).
But there is something that troubles me regarding the JSESSIONID. When having multiple PAS on the same server, the JSESSIONID is post fixed with the PAS name, like: JSESSIONID=SomeUniqueKey.PasName. In our configuration, we have 2 Appservers (let's say PrimaryAppSrv and SecondaryAppSrv), where only the last one is configured to host the webApp containing the REST services in question here. So I would have expected the JSESSIONID to be in form of "SomeUniqueKey.SecondaryAppSrv", and it's like this in our development environment, but in production and on the server causing the errors you see in the attached log file (Application.2017-11-25.log) is like this: "SomeUniqueKey.PrimaryAppSrv", where the postfix is of the other AppServer. Is this a normal thing?
I have added also the log file (see Application.2017-11-25.log), where starting with "14:00:00" you will see some relevant (I hope) errors. What I did was, go to the login page, enter a valid username (mfa) and password -> success. Then I simply requested another service and I got back tons of errors. The CP did reach my ABL logic, but it was not containing any valid information (USER-ID, ROLES).
Some more information about our setup:
I have attached some configuration files and one of the logs.