threads/85112: Resource temporarily unavailable reading from
sockets with Java/libpthread/jdbc
Daniel Eischen
deischen at freebsd.org
Fri Aug 19 18:05:53 GMT 2005
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 at spatula.net>
> To: bug-followup at 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
More information about the freebsd-threads
mailing list