Thanks - I've tried both the latest stable (which doesn't appear to contain a DataSource implementation) and the latest dev version (which does) of the postgres jdbc drivers. Both fail...
I'd kind of assumed that even a completely non-existant class would still result in an instantiated DataSource object, but that I wouldn't be able to retrieve any connections (duh !) from it - is this the behaviour I should expect, or is the behaviour I'm getting (viz a null pointer) what should be expected under those circumstances ? Currently my application will scale to about 3 users - fortunately it's a spare time project, so this doesn't actually matter in any real sense ;-) Dave. On Tuesday 26 Mar 2002 7:09 am, you wrote: > > I'm having some problems initialising a DataSource object for the > > purposes of connection pooling under tomcat. > > > > The database to which I'm trying to connect is Postgresql. The > > connections work fine with the standard java.sql.* approach. > > > Join the club. :-( > > > > Basically when I try to acquire a DataSource object, I get null. Nothing > > in my log files indicates the cause of the problem - or indeed that > > there is a problem at all (aside from my own log4j output). > > > > When using the standard java.sql stuff my jsp & servlets work perfectly > > in every respect, so I'm confident that the rest of my configuration is > > correct. Or correct enough, anyway. > > > Same here, same behaviour, PostgreSQL 7.2 > > > > Versions: > > tomcat: 4.0.3 > > jdk: 1.3.1 > > j2sdkee: 1.3 > > postgresql: 7.1.3 > > log4j: 1.2beta4 > > > One poster suggested it was the sign of Tyrex being unable to create a > DataSource object. PostgreSQL in it's JAR doesn't have a DataSource > implementation. Now there were some guys who say it is in the sources in > developers version. I'll dig there deeper, if anything comes up, I'll > e-mail. > Nix. -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
