|
I have an application which works perfectly until I added in the connection pool. all I did was adding
properties.setProperty("hibernate.c3p0.max_size", "1");
properties.setProperty("hibernate.c3p0.min_size", "0");
properties.setProperty("hibernate.c3p0.timeout", "10000");
properties.setProperty("hibernate.c3p0.max_statements", "100");
properties.setProperty("hibernate.c3p0.idle_test_period", "300");
properties.setProperty("hibernate.c3p0.acquire_increment", "2");
to the Configuration properties. and session.save(object) stops working.
there is no error thrown. the insert statement was never issued as made evident by spy.log. and the thread remains a live. but the call never returns.
another funny thing.
the configuration with connection pool does work as long as no subclassing (with <union-subclass> was used. the combination of subclassing and connection pool causes this failure. this rings any bells?
|
Login
FAQ
Search
