Closed jlhughes closed 6 years ago
Typo in server.xml HTTP/1.1 accidentally changed to HTTP/1.1. Users are not being loaded because of an S3 bucket issue that is believe to be caused by AppConfig.mode being ignored because of an possible bug parsing Enum properties.
connectionTimeout is currently set 90000.
The connectionTimeout parameter is not what is needed. It is 'our' client experiencing the timeout.
Our HTTPRequest client will wait for a long time - 3 minutes in localhost testing. While the same request from sandbox will be terminated at exactly 1 minute.
AWS configuration for Classic Load Balance Idle Timeou thttps://docs.aws.amazon.com/elasticloadbalancing/latest/classic/config-idle-timeout.html Set to 120s, testing...
RESOLVED: working. Will set to 180s in production.
In attempting to change service.xml connectionTimeout, tomcat will not restart. attempted:
All failing with NPE.