I think you will find that you can leave the password out now, and
updating to the latest driver may improve the first problem too
Dave
-----Original Message-----
From: pgsql-jdbc-owner@postgresql.org
[mailto:pgsql-jdbc-owner@postgresql.org] On Behalf Of tsmets@brutele.be
Sent: Wednesday, March 06, 2002 10:51 AM
To: Doug Fields; pgsql jdbc
Subject: Re: [JDBC] Pooled Connections (was Connections with Tomcat
3.2.4 and PostgreSQL 7.1.3)
JBoss docs mentions that the 7.x driver jdbc7.0-1.2.jar is causing
troubles
with:
<quote>
Extreme Java "long" values will cause SQLExceptions and may corrupt the
driver so that further actions will fail. </quote>
A bit further they mention :
<quote>
You must include a User name and password. They can be bogus if your
PostgreSQL in to trust the machine you are coming from, but you cannot
leave them out. </quote>
Rgds,
THomas,
--
Thomas SMETS
rue J. Wytsmanstraat 62
1050 Bruxelles
yahoo-id: smetsthomas
----- Original Message -----
From: "Doug Fields" <dfields-postgres@pexicom.com>
To: <Dave@micro-automation.net>
Cc: "'Justin Clift'" <justin@postgresql.org>; <tsmets@brutele.be>;
"'pgsql jdbc'" <pgsql-jdbc@postgresql.org>; <hyellina@iprimus.com.au>
Sent: 06 March, 2002 4:27 PM
Subject: Re: [JDBC] Pooled Connections (was Connections with Tomcat
3.2.4 and PostgreSQL 7.1.3)
> At 07:30 AM 3/6/2002, Dave Cramer wrote:
> >Pooled connections aren't rocket science. There are quite a few
> >freely available, poolman for one.
>
> For what it's worth, I never got Poolman 2.0.4 to work with the JDBC
> 7.2 drivers; occasionally and for no reason it would give me spurious
> errors
on
> perfectly good SQL. I posted about it a week or two ago on this list.
> I received no replies, and furthermore got no replies from the
> author(s) and found little information about it on the net.
>
> I now use Protomatter (protomatter.sourceforge.net) and have had very
> good success with it. It's a more simple implementation, hence,
> probably faster and/or more bug free, and the author has been very
> talkative and has implemented some enhancements/repairs that I have
> suggested/provided.
>
> Also to back up what Dave said - you never know when and/or even if
> the GC is going to collect your connections, so always close them in a
> finally block. The beauty of GC is that it's non-deterministic and
> allows you to
be
> sloppy. The horror of GC is that it's non-deterministic and allows you
> to be sloppy.
>
> Cheers,
>
> Doug
>
>
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly
