concurrentlinkedhashmap dependency non-optional when declared as global JNDI Resource about vibur-dbcp HOT 10 CLOSED

@dcalde, can you please confirm that statementCacheMaxSize was set to 0 when this happened? Also, which version of Vibur did you use?

from vibur-dbcp.

Yes, statementCacheMaxSize is not set at all, it uses the ViburDBCPConfig default of 0

from vibur-dbcp.

@dcalde, are you able to provide us with any more information in order to replicate this issue, any configuration samples, the concrete Tomcat version in which this problem, as well as the concrete Vibur DBCP version which you're using?

In latest (5.0) version of Vibur DBCP all reference to com.googlecode.concurrentlinkedhashmap.* are isolated in StatementCache.java and the StatementyCache itself is not instantiated when statementCacheMaxSize is zero. For this reason, the problem which you're encountering is very strange, and that's why I'm asking for more details.

from vibur-dbcp.

This happened on my local dev machine. Windows 7 Pro, JDK 1.8.0_60, Tomcat 8.0.27, running inside Intellij IDEA 14.1.5. JmxRemoteLifecycleListener not enabled.

Simply adding concurrentlinkedhashmap-lru-1.4.2.jar to tomcat/lib fixed it.

from vibur-dbcp.

Thanks for this info.

But are you using an of-maven-central Vibur DBCP version, like for example version 5.0 or version 4.0, or your own patched version of Vibur DBCP? If you're using a patched version, can you please send me the diff by email so that I can evaluate whether the diff has anything to do with the problem?

from vibur-dbcp.

I was using a patched version (1.0) but it was leaking connections (probably due to my changes... you might remember our discussion from ~1.5 years ago regarding testing connections on create) which is why we updated to the 5.0. Since updating to 5.0 and applying the changes as per the other JNDI bug, the pool is now working as expected.
Daniel

from vibur-dbcp.

No worries, thanks Daniel.

I will close this issue as invalid and I'll fix the other JNDI issue.

Please let me know if you encounter any other issues.

from vibur-dbcp.

I don't think it is invalid, but I am happy to re-test once the other JNDI bug is resolved, so I replicate the issue with a non-patched version.

from vibur-dbcp.

The other JNDI related issue #5 was just fixed on master.

As to this current issue #4, I guess my wording that the issue is invalid wasn't precise enough. I was trying to say that I'm not expecting #4 to be present in Vibur DBCP 5.0 or in the current master version. If possible, can you please retest the scenario in which you got the current issue #4 with version 5.0 or with build from master, and let me know whether the issue is present in any of those?

If yes, I'll dig it further.

from vibur-dbcp.

@dcalde, my current opinion is that this issue here (#4) is not present in Vibur DBCP 5.0, and I would like to close it. I don't have sufficient resources to release bug fixing releases for older Vibur DBCP versions, and the solution for anyone who is experiencing this issue (#4) will be to migrate to version 5.0.

from vibur-dbcp.