Hi,
We noticed a problem since PAX JDBC 1.3.0.
When using pax-jdbc-config bundle, there is a
ConcurrentModificationException thrown during its deactivation.
This for instance leads to failed feature deployments in case the bundle
has to be restarted.
We are using Karaf 4.2.1, which recently switched to pax-jdbc 1.3.0.
Earlier Karaf versions which included 1.2.1 did not have this problem.
The actual issue was introduced with git
revision 02e93e6dd45057d026bf7cefd4ccbe724531fab4
Take a look
at
pax-jdbc-config/src/main/java/org/ops4j/pax/jdbc/config/impl/DataSourceConfigManager.java
@Override
public void deleted(String pid) {
ServiceTracker<?, ?> tracker = trackers.remove(pid);
if (tracker != null) {
tracker.close();
}
}
synchronized void destroy() {
for (String pid : trackers.keySet()) {
deleted(pid);
}
}
The newly introduced destroy() method has a loop which causes an exception
in case there are more than one data sources configured (which is needed to
replicate the issue).
Regards,
Matej.
--
--
------------------
OPS4J - http://www.ops4j.org - [email protected]
---
You received this message because you are subscribed to the Google Groups
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
