[Coefficient-users] Re: Coefficient

[Thomas F. <tfo...@us...>]

On Thu, 2005-01-27 at 17:00 +0200, Thomas Fogwill wrote:
> So, not exactly the same version as you, but close enough, I'd think. I
> will, however, try with the mysql-connector-java-3.0.16-ga-bin.jar
> driver. My guess is that this is where the problem lies.

mmm... still couldn't replicate your problem (I tried with 3.0.16).

Anyway, let's try something else. I've created a new hibernateUtil.jar
here: http://icomdmz1.csir.co.za/~tfogwill/files/hibernateUtil.jar

In this one, I commented out line 816; that's the line where the
connection is explicitly closed. i.e.
815:        if (conn != null) {
816:            //conn.close();
817:        } 

This is not necessarily a good idea. I don't know why he did it, but I'm
sure Dylan had a good reason for explicitly closing the connection here.
Nonetheless, let's try it like this for now, to see if it solves the
problem for you.

Failing that, I could always give you a sql dump of my initialised
database. That should get you up and running, as the whole db init
process won't need to happen. I'd prefer actually solving the problem,
though; and for that to happen, it's better to have it breaking on your
system (as I can't replicate your problem on mine).

> it seems that the mysql driver "remembers" that you closed the
> connection, probably by creating a new Throwable() and holding a
> reference to it internally).

Indeed, it does exactly that. On line 1123 of Connection.java, in method
close(), this is done to remember when and where the connection was
explicitly closed:
    this.explicitCloseLocation = new Throwable();
this.explicitCloseLocation is then obviously thrown later.



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.