You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using waffle 1.8 with Tomcat 8 for Windows authentication in front of an OpenRDF Sesame 2.7.15 web app and found that every request that comes in leaks an OS Token handle (via using sysinternals handle.exe etc.). This is becoming a big problem on busy systems as the handle count goes in to the 100,000s over a week or so.
It looks like this could possibly come from the handle in the WindowsCredentialsHandleImpl initialized here into the serverCredential var. This is passed in, and held by, the WindowsSecurityContextImpl sc var, and this is disposed in every case, except when a successful negotiation completes, in which case it is returned to the caller here into the securityContext var.
It looks like the securityContext var needs to be disposed before returning from this method, perhaps in the finally block at the end.
The text was updated successfully, but these errors were encountered:
I'm using waffle 1.8 with Tomcat 8 for Windows authentication in front of an OpenRDF Sesame 2.7.15 web app and found that every request that comes in leaks an OS Token handle (via using sysinternals handle.exe etc.). This is becoming a big problem on busy systems as the handle count goes in to the 100,000s over a week or so.
It looks like this could possibly come from the handle in the WindowsCredentialsHandleImpl initialized here into the serverCredential var. This is passed in, and held by, the WindowsSecurityContextImpl sc var, and this is disposed in every case, except when a successful negotiation completes, in which case it is returned to the caller here into the securityContext var.
It looks like the securityContext var needs to be disposed before returning from this method, perhaps in the finally block at the end.
The text was updated successfully, but these errors were encountered: