Hi,

I'm using latest Hibernate 2.X in my web application development. I'm noticing every now and then weird errors in my log file



What does this mean, and what can I do to fix it?

Thanks, Jason

I get that, too, and have not clue what it's about... :-/ So I will be interested in the answer as well!

For me, this doesn't seem to be in response to any event... it just pops up all of a sudden when nothing else seems to be going on.

Do you also see one like this?:

java.sql.SQLException: Unable to connect to any hosts due to exception: java.net.SocketException: Address already in use
at com.mysql.jdbc.Connection.createNewIO(Connection.java:1719)
at com.mysql.jdbc.Connection.<init>(Connection.java:432)
at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:400)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:140)
at com.mchange.v2.c3p0.impl.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:138)
at com.mchange.v2.c3p0.impl.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:235)
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1.acquireResource(C3P0PooledConnectionPool.java:65)
at com.mchange.v2.resourcepool.BasicResourcePool.assimilateResource(BasicResourcePool.java:721)
at com.mchange.v2.resourcepool.BasicResourcePool.acquireUntil(BasicResourcePool.java:502)
at com.mchange.v2.resourcepool.BasicResourcePool.access$000(BasicResourcePool.java:34)
at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:903)
at com.mchange.v2.async.CarefulRunnableQueue$TaskThread.run(CarefulRunnableQueue.java:145)

—ml—

> c3p0-TRAVIS: An idle resource is broken and must be purged.
> c3p0-TRAVIS: java.sql.SQLException: Connection is invalid
>         at
> com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1.refurbishResource(C3P0PooledConnectionPool.java:141)
>        at
> com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1.refurbishIdleResource(C3P0PooledConnectionPool.java:105)
>        at
> com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask.run(BasicResourcePool.java:1105)
>        at
> com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:148)

Hi. This message simply means that c3p0 was configured to periodically test idle Connections, and during such a test, it found that one was broken, and removed it from the pool. It is nothing to worry about -- if it never happened, there'd be no need for Connection testing at all.

It says "c3p0-TRAVIS" only for the embarrassing reason that sometimes when I work with users to track down a problem, I add their names to log messages I think will be relevant to the issue, so that they can easily grep for the relevant info. Apparently several messages still annotated with Travis' name slipped into a public release... Embarrassing for me, but nothing to worry about.

(The message gives very little information about how the Connection actually failed... I'll try to make it a bit more informative.)

Anyway, more recent versions of c3p0 leave Travis' name out of it... the next prerelease of c3p0 (0.9.0-pre4) will include more about the observed Connection failure in the message.

smiles,
Steve (c3p0 guy)

Great-- nothing nothing like getting a questioned answered from the source developer! Thanks for the info-- nothing bad seems to happen with the DB so it didn't seem like anything fatal.

Thanks, Jason