Your method of jar replacement would have worked better if you were
doing a point upgrade paying attention to the third number, keeping the
first two the same. For example, upgrading from 5.5.16 to 5.5.25 is a
reasonably safe upgrade without significant breaking changes. At worst,
such an upg
Just wanted to say thanks very much for all the very helpful replies on
this.
I now have several avenues to pursue and I assume now that the problem was
my upgrade method, and not a bug in 5.5.25.
There is a general issue this brings up--not really a question anymore, just
a point to ponder (for
