Proxool: Proxy JDBC Connection Pool

Sameet Nasnodkar wrote:

>I just started using Proxool today and The error I get is from the jdbc
>driver of Postgresql saying 'The user property is missing. It is
>mandatory.'
>
>This means that proxool is not sending the user name correctly. Here is
>the code and the properies for the wht I am trying
>
>// Code is below
>PropertyConfigurator.configure("jdbc.properties");
>c = DriverManager.getConnection("proxool.miaf-connection");
>
>// jdbc.properties is below
>jdbc-0.proxool.alias=miaf-connection
>jdbc-0.proxool.driver-url=jdbc:postgresql://localhost:5432/lportal
>jdbc-0.proxool.driver-class=org.postgresql.Driver
>jdbc-0.user=snasnod1
>jdbc-0.password=
>jdbc-0.proxool.maximum-connection-count=20
>#jdbc-0.proxool.house-keeping-test-sql=select CURRENT_DATE
>  
>

Your usage seems to be correct, but I'm confident that Proxool treats 
the user property correctly. We have a unit test to specifically test this.

>Also, since it does not throw any exception during the
>PropertyConfigurator.configure, I am assuming that it has found the
>jdbc.properties file.
>  
>

Maybe it is finding the wrong copy of the file?

How about debug output? Have you configured logging? It should give you 
information about the pool as it is being registered.

-
Bill

HibernateSession.close() will close the connection and return it to the
pool.
The real JDBC connection isn't actually closed at that moment but only =
the
proxied one given to Hibernate by the pool.

If your pool isn't configured to validate the connection on borrow, then =
you
may give a closed/dirty connection to Hibernate and therefore receiving =
an
exception the first time Hibernate wants to do something with it.

In most cases, the problem you experience is caused by a wrong Hibernate
session handling. Make sure you don't reuse the same session across =
multiple
calls, make sure your session is actually (and properly) closed, turn on
Hibernate and Proxool debugging and you will probably find the answer to
your problem.

(BTW: pretty sure you don't get this exception the first time your timer
fires but the second time well... This is a good indication of bad =
Hibernate
session handling :(

-bertrand


-----Original Message-----
From: proxool-user-admin@...
[mailto:proxool-user-admin@...] On Behalf Of Per =
Thomas
Jahr
Sent: mardi 26 octobre 2004 10:31
To: proxool-user@...
Subject: [Proxool-user] Connection remains active when closing session =
in
Hibernate


Hi,

This is maybe a Hibernate question. But I will try my question here
first:

I have an application that uses Proxool 8.3 and Hibernate 2.1.6. In this
application I have a timer thread that runs every 10 minutes. This =
thread
does a query against a database. This is a not a complex query and it
returns within milliseconds.

The problem is that I get a SqlException and "connection closed" when =
the
timer fires. This is because the housekeeper kills the connection. The
connection has reached the maximum-active-time so the housekeeper kills =
it.

So, the question is: shouldn't Hibernate's session.close() return the
connection to the Hibernate pool?=20

Instead it seems like the connection remains active even after
session.close(). As I understand it the status of the connection should =
be
available (and not active) after session.close().

Thanks
--=20
Per Thomas Jahr



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal =
Use
IT products in your business? Tell us what you think of them. Give us =
Your
Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Proxool-user mailing list
Proxool-user@...
https://lists.sourceforge.net/lists/listinfo/proxool-user

The problem seems to be that when calling HibernateSession.close() the
connection is not returned to the pool again. The Proxool servlet only
shows active connections (red bar) and no available connections (green
bar). 

I use this template (from the Hibernate doc). Isn't this correct?

session = sessionFactory.openSession();
tx = session.beginTransaction();
....
tx.commit();
session.close() (in finally) 

But the connection is not returned to the pool. When I run a debugger I
can see that HibernateSession.close() is begin called. But the Proxool
servlet still only shows active connections.

All 62 places where I do a openSession there is also a session.close(). 
I will try with the property test-before-use.

Thanks
-- 
Per Thomas Jahr