Heads up: pax-jdbc-release 1.0.1 and redesign of trackers in pax-jdbc-config

pax-jdbc 1.0.1 release I would like to do a pax-jdbc 1.0.1 release today or tomorrow. We fixed a bug in the hikari pooling and a user asked for the fixed version. There is also an open issue with the aries pooling. If possible we should fix this for 1.0.1 but there is a workaround.

Re: Heads up: pax-jdbc-release 1.0.1 and redesign of trackers in pax-jdbc-config

Not sure that we want the same xa credential as the datasource one every time. In order to fix it on the user side, we've got to specify in the config user= password= AND pool.username= pool.password= Using the same credential could be problematic with multiple XA resource (or maybe I don't

Re: Heads up: pax-jdbc-release 1.0.1 and redesign of trackers in pax-jdbc-config

Can you explain this in more detail? I would not expect any problems with multiple connections using the same credentials. Christian On 10.02.2017 14:04, Charlie Mordant wrote: Not sure that we want the same xa credential as the datasource one every time. In order to fix it on the user side,

Re: Heads up: pax-jdbc-release 1.0.1 and redesign of trackers in pax-jdbc-config

Sorry, I thought that the XA credentials were given to create UserTransaction (not managed connection). So there's not any issue except my foolishness ;-). 2017-02-10 14:07 GMT+01:00 Christian Schneider : > Can you explain this in more detail? I would not expect any