From owner-freebsd-java Tue Sep 4 17: 4:37 2001 Delivered-To: freebsd-java@freebsd.org Received: from daedalus.cs.brandeis.edu (daedalus.cs.brandeis.edu [129.64.3.179]) by hub.freebsd.org (Postfix) with ESMTP id C8FA337B401 for ; Tue, 4 Sep 2001 17:04:33 -0700 (PDT) Received: from localhost (meshko@localhost) by daedalus.cs.brandeis.edu (8.9.3/8.9.3) with ESMTP id UAA30153; Tue, 4 Sep 2001 20:04:01 -0400 Date: Tue, 4 Sep 2001 20:04:01 -0400 (EDT) From: Mikhail Kruk To: Bill Huey Cc: Fuyuhiko Maruyama , Subject: Re: (j2sdk1.3.1) AWT improvement In-Reply-To: <20010904163119.A13798@gnuppy> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > On Tue, Sep 04, 2001 at 07:22:06PM -0400, Mikhail Kruk wrote: > > It definitely works better! Thanks! > > Is there a patch for the connect (56) problem? > > Look in this file: > > ../src/solaris/hpi/green_threads/src/iomgr.c > > Find the connect() definition and make that the block with ioctl() > is used over the second connect() attempt. That's all. ;-) Yeah, yeah, I couldn't figure out how to fix it from the discussion :( Thanks for explaining :) So now I've tried the application I wanted to try and bottom line is that Swing works flawlessly now, network works too (including SSL) and performance is almost acceptable (can't wait to test is with JIT ;) on my PII-300. Also I've been running a small network server on 1.3.1 for the last 10 days or so and had no problems with it. It hasn't been under a lot of load yet, but it saw 10-15 simultaneous users and survived. So many thanks to everyone who worked on the port! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message