Date: Fri, 19 Aug 2005 14:05:49 -0400 (EDT) From: Daniel Eischen <deischen@freebsd.org> To: Nick Johnson <freebsd@spatula.net> Cc: freebsd-threads@freebsd.org Subject: Re: threads/85112: Resource temporarily unavailable reading from sockets with Java/libpthread/jdbc Message-ID: <Pine.GSO.4.43.0508191404400.12955-100000@sea.ntplx.net> In-Reply-To: <200508191500.j7JF0fV0008876@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <freebsd@spatula.net> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.43.0508191404400.12955-100000>