+1 for the release Regards JB
Le 26 sept. 2018 à 03:46, à 03:46, Grzegorz Grzybek <[email protected]> a écrit: >Hello > >https://ops4j1.jira.com/browse/PAXJDBC-133 is fixed now. I'd like to >cut a >release of pax-jdbc 1.3.1 this week - there are no more unresolved >PAXJDBC >issues. Anything more before I start the release? > >regards >Grzegorz Grzybek > >śr., 26 wrz 2018 o 09:13 françois papon <[email protected]> >napisał(a): > >> Thanks Grzegorz ! >> >> *François Papon* >> >> >> Le mer. 26 sept. 2018 à 11:02, Grzegorz Grzybek ><[email protected]> a >> écrit : >> >>> Hello >>> >>> Thanks for reporting - I've created >>> https://ops4j1.jira.com/browse/PAXJDBC-133 issue and I'm working on >it - >>> I think I'll release 1.3.1 this week. >>> >>> best regards >>> Grzegorz Grzybek >>> >>> wt., 25 wrz 2018 o 11:51 Matej Ferencak <[email protected]> >>> napisał(a): >>> >>>> 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. >>>> >>> -- >>> -- >>> ------------------ >>> 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. >>> >> -- >> -- >> ------------------ >> 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. >> > >-- >-- >------------------ >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. -- -- ------------------ 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.
