From owner-freebsd-java@FreeBSD.ORG Wed Feb 7 16:01:33 2007 Return-Path: X-Original-To: freebsd-java@freebsd.org Delivered-To: freebsd-java@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DCAA916A41A for ; Wed, 7 Feb 2007 16:01:32 +0000 (UTC) (envelope-from jan.grant@bristol.ac.uk) Received: from dirg.bris.ac.uk (dirg.bris.ac.uk [137.222.10.102]) by mx1.freebsd.org (Postfix) with ESMTP id A56BF13C4A6 for ; Wed, 7 Feb 2007 16:01:32 +0000 (UTC) (envelope-from jan.grant@bristol.ac.uk) Received: from mail.ilrt.bris.ac.uk ([137.222.16.62]) by dirg.bris.ac.uk with esmtp (Exim 4.66) (envelope-from ) id 1HEoyK-0007RY-GF; Wed, 07 Feb 2007 15:44:39 +0000 Received: from cse-jg.cse.bris.ac.uk ([137.222.12.37]:53261) by mail.ilrt.bris.ac.uk with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1HEoxl-0001RK-UP; Wed, 07 Feb 2007 15:44:01 +0000 Date: Wed, 7 Feb 2007 15:44:01 +0000 (GMT) From: Jan Grant X-X-Sender: cmjg@tribble.ilrt.bris.ac.uk To: freebsd-java@freebsd.org Message-ID: <20070207153528.H25702@tribble.ilrt.bris.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-ILRT-MailScanner: Found to be clean X-ILRT-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=0.109, required 5, autolearn=disabled, ALL_TRUSTED -1.44, AWL 1.47, TW_KR 0.08) X-ILRT-MailScanner-From: jan.grant@bristol.ac.uk X-Spam-Status: No X-Spam-Score: -1.4 X-Spam-Level: - Subject: krb5 bug: Do any of the freebsd java folk (Greg?) have an upstream contact? X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Feb 2007 16:01:33 -0000 I'm trying to raise a bug with Sun about the sun.security.krb5 implementation. Unfortunately this is somewhat hampered by my suffering from RSI at the moment. The problem is a straightforward resource leak, as you can see if you look at this: http://java.sun.com/j2se/jrl_download.html in particular, at jdk_sec-1_5_0-src-scsl.zip You'll see that sun.security.krb5.internal.UDPClient has no close() method; and the UDPClient-using code path in sun.security.krb5.KrbKdcReq (which has a few other close-to-the-coalface errors) consequently leaks FDs (unlike the TCP path, which has a try/finally that closes the socket properly). We're seeing a krb5 client application (the Yale CAS SSO) keel over in no time due to FD exhaustion. A trivial fix (the non-whitespace part of the diff is 8 lines) sorts this out. Prepping a test case is somewhat difficult when this email represents most of the typing I'm going to get done today :-( Cheers, jan -- jan grant, ISYS, University of Bristol. http://www.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ Goth is the new black.