Hi guys I identified a performance issue when using JDBC persistence adapter.
When we do a switch from master to slave, having some pending messages in a destination, I see a bunch of SQL queries (largely more than the number of pending messages), dramatically degrading the performance (this Select doesn’t occur on regular behavior). I checked and it’s due to findNextMessage statement executed in doRecover of the adapter. Anyone already saw this behavior ? I’m checking how we can avoid/reduce or square the select query execution (avoiding performance degradation). Thanks Regards JB
