Can you mock out the web service calls to confirm that it is CXF eating up your DBCP pool and nothing something else?
Glen Am Montag, den 03.03.2008, 13:19 -0800 schrieb Michael McCaskill: > I'm coming from Spring-Webservices. I like that CXF supports contract-last > since I'm in a prototype, rapid development phase for my work project. But > I've noticed that weird things happen when using CXF with Spring > Transactions. > > It appears that after so many web service calls, the DBCP pool is exhausted > and connections aren't returned. This wasn't happening with > Spring-Webservices. I've tried the 2.1-incubator-SNAPSHOT as well. It needs > to be said that I am filtering out the Spring-2.0.6 dependencies and opting > for 2.5. I'm using Spring's @Transactional annotation, JAXB, > JaxWsProxyFactoryBean on client, jaxws:endpoint on server, Hibernate 3.1 and > Oracle 9.2.0.8.
