From owner-freebsd-threads@FreeBSD.ORG Fri Aug 19 18:05:53 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 393D716A41F for ; Fri, 19 Aug 2005 18:05:53 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0BAE43D49 for ; Fri, 19 Aug 2005 18:05:52 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.4/8.13.4/NETPLEX) with ESMTP id j7JI5nrH022193; Fri, 19 Aug 2005 14:05:49 -0400 (EDT) Date: Fri, 19 Aug 2005 14:05:49 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Nick Johnson In-Reply-To: <200508191500.j7JF0fV0008876@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-threads@freebsd.org Subject: Re: threads/85112: Resource temporarily unavailable reading from sockets with Java/libpthread/jdbc X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Aug 2005 18:05:53 -0000 On Fri, 19 Aug 2005, Nick Johnson wrote: > The following reply was made to PR threads/85112; it has been noted by GNATS. > > From: Nick Johnson > To: bug-followup@FreeBSD.org > Cc: > Subject: Re: threads/85112: Resource temporarily unavailable reading from > sockets with Java/libpthread/jdbc > Date: Fri, 19 Aug 2005 07:52:40 -0700 (PDT) > > The problem is happening during a socket read, not during connect (see the > stack trace). Whatever. Unless you can produce a C program to show the problem, you should report this to -java. There is no magic in connect(), read(), write(), open(), socket(), whatever in libpthread. > The connect is definitely working; it causes postgres to spawn processes > to handle the requests... but a database connection is far more than just > a connect. There are credentials to exchange, database names to give, > etc. -- DE