Hi! We have an ensemble of three jetty-servers running jetty 9.3.8 on CentOS. There is a fairly high rate of communication between the servers. When we run the ensemble without SSL, everything works perfectly, but once SSL is activated, exactly one of the servers start to get a massive amount of connections in CLOSE_WAIT (more than 50 000). This, again, causes the Old Gen-part of the heap memory in the JVM to fill up, and the server becomes unable to communicate with exactly one of the other two, with Couldn't resolve address. However, the other machine can still communicate with the one that breaks down, and the 3rd machine can communicate with both.
Running forced garbage collection on the machine that breaks down makes no difference to the used memory in the Old Gen-part of the JVM heap memory, while on the other machines, GC pretty much completely cleans the memory. Also, the number of CLOSE_WAIT-connections in the machine that breaks down should be matched by FIN_WAIT2-connections in the other two, but there are only a few thousand of those. Does anyone know what may be the problem? Any help would be greatly appreciated. With regards, Johannes
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
