next »

[Benjamin G.]

Hi,

We're trying to implement an intensive webservices server (1 client consuming the webservice in batch mode (price calculation)).
We are facing with a socket problem because after the response has sent the socket stay in "TIME_WAIT" status
We suspect that's the socket between the client and apache :

10.10.1.88.80        10.10.1.88.45288     49152      0 49152      0 TIME_WAIT
10.10.1.88.80        10.10.1.88.45290     49152      0 49152      0 TIME_WAIT
10.10.1.88.80        10.10.1.88.45292     49152      0 49152      0 TIME_WAIT
10.10.1.88.80        10.10.1.88.45294     49152      0 49152      0 TIME_WAIT
10.10.1.88.80        10.10.1.88.45296     49152      0 49152      0 TIME_WAIT
10.10.1.88.80        10.10.1.88.45298     49152      0 49152      0 TIME_WAIT
10.10.1.88.80        10.10.1.88.45300     49152      0 49152      0 TIME_WAIT
10.10.1.88.80        10.10.1.88.45302     49152      0 49152      0 TIME_WAIT
10.10.1.88.80        10.10.1.88.45304     49152      0 49152      0 TIME_WAIT
10.10.1.88.80        10.10.1.88.45306     49152      0 49152      0 TIME_WAIT

We've reduce the tcp_time_wait_interval to 5 seconds but we suspect that is issue still a overall performance problem

If anyone have a good advice on this our some experience ...

(Server is on Solaris Sparc 10 with apache 2.4 and genero 3.10.07 + fastcgidispatch)


Thanks