We do and I’m sensitive to that 100% but there is no reason ACCP should break upgrades afaik. The algorithms it implements are identical and for the ones it doesn’t the JRE implementation is used — ACCP is the higher priority implementation. Do we have any examples of it breaking anything? Or that it’s problematic?
We recently did a 4.1 upgrade that was mixed JRE / ACCP and it worked fine. It’s how we figured out ACCP was missing because 4.1 was noticeably slower (graph in JIRA) and the JRE crypto library dominated the flamegraph (can try to dig up a screenshot maybe). Jordan On Wed, Jul 26, 2023 at 08:35 Mick Semb Wever <m...@apache.org> wrote: > > > Can you say more about the shape of your concern? >> > > > Integration testing where some nodes are running JCE and others accp, and > various configurations that are and are not accp compatible/native. > > I'm not referring to (re-) unit testing accp or jce themselves, or matrix > testing over them, but our commitment to always-on upgrades against all > possible configurations that integrate. We've history with config changes > breaking upgrades, for as simple as they are. >
