This content has been marked as final. Show 3 replies
It seems that you might need to tune few parameters from weblogic side as show below and then try to test and see if you get any improvements
Console Path: Servers > Configuration (tab) > Tuning (sub-tab)
Tune the above parameter value
The number of backlogged, new TCP connection requests that should be allowed for this server's regular and SSL ports. Setting the backlog to 0 may prevent this server from accepting any incoming connection on some operating systems.
Console Path: Servers > Protocols (tab) > HTTP (sub-tab)
Tune the above two parameters values
The amount of time this server waits between receiving chunks of data in an HTTP POST data before it times out. This is used to prevent denial-of-service attacks that attempt to overload the server with POST data.
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.
Topic: Tune the Chunk Parameters
However the values for this parameters are totally dependent end to end environments
Hope above information helps you.
I would also recommend that you troubleshoot further if your problem is really regarding a HTTP request (socket) backlog.
On top of these above suggestions, can you please generate a few netstat snapshots during your load test (netstat or netstat -an) from your application server. This will allow you to track down any growing Socket backlog. Look for any excessive pool of sockets attached to your WL server socket. You will also be able to compare such snapshot before and after any tuning performed.
Also, take a look and see if you have this Exception in the logs: Too many open files. If you do, this indicates that you reached your maximum capacity of File Descriptors / sockets for your load testing environment.