I'm using xapool (org.enhydra.jdbc.pool.StandardXAPoolDataSource) with Spring and JPA and I'm getting connection timed out errors. I found the "checkLevelObject" setting, but it doesn't seem to have helped. Should that have fixed it? Are there other setting that I could use to test the connections and have them replaced without impacting the application?
Asked
Active
Viewed 586 times
0
-
Which settings did you use for the checkObjectLevel? – ewernli Dec 15 '09 at 07:23
-
– HappyEngineer Dec 15 '09 at 18:51
1 Answers
1
I found out that xapool is a dead project. It is at 1.6beta and hasn't been updated since Dec 2006. I switched my pool to C3P0 and everything works properly now.
HappyEngineer
- 4,017
- 9
- 46
- 60
-
BTW, I had problems with c3p0 as well. It didn't do transactions properly. See http://stackoverflow.com/questions/1977366/spring-transactional-cpool-which-one-do-i-use/2002505#2002505 for full instructions on how I did it. – HappyEngineer Jan 04 '10 at 22:04