We are load testing JD Edwards in AWS, once again getting a lot of 504 errors. We are using the AWS provided ELB to load balance JD Edwards between AZ’s. 10 users are giving us a pile of 504’s.
I searched back and remember that we had the same problem for another client in AWS, another search revealed that I needed to make the following changes in weblogic for both nodes.
We need to make a change to keep alive and the connection timeout for JD Edwards to avoid this. Note that this was slightly different, as we are doing https at the current site.
Duration
The amount of time this server waits before closing an inactive HTTP connection.
Number of seconds to maintain HTTP keep-alive before timing out the request.
MBean Attribute:WebServerMBean.KeepAliveSecs
Minimum value: 5
Maximum value: 3600
Secure value: 30
HTTPS Duration
The amount of time this server waits before closing an inactive HTTPS connection.
Number of seconds to maintain HTTPS keep-alive before timing out the request.
MBean Attribute:WebServerMBean.HttpsKeepAliveSecs
Minimum value: 30
Maximum value: 360
Secure value: 60
Connect Timeout
The amount of time that this server should wait to establish an outbound socket connection before timing out. A value of 0 disables server connect timeout.
MBean Attribute:ServerMBean.ConnectTimeout
Minimum value: 0
Maximum value: 240
After making the above changes and bouncing the instance we did not get a single 504!
No comments:
Post a Comment