JVM heap size adjustments
Cantor, Scott
cantor.2 at osu.edu
Wed Jan 13 00:18:21 EST 2016
On 1/12/16, 11:54 PM, "users on behalf of Paul Caskey" <users-bounces at shibboleth.net on behalf of pcaskey at internet2.edu> wrote:
>Not really arguing your point, but separate upgrades being less risky isn’t always true.
>
>Particularly when upgrading from Jetty 9.2 to 9.3 with IdP 3.1. :) Never saw that on Windows because of the packaged Jetty.
But 3.1 didn't require 9.3. That's really the point. They're separate.
You also didn't see a problem because we didn't upgrade Jetty. Tying them together doesn't make upgrading either one much easier, it just makes upgrading Jetty less frequent because the tying increases risk and requires us to be more conservative. But people can be just as conservative without us forcing it.
Part of the the risk I meant was coupling them instead of strictly relying only on the servlet spec as a contract and maintaining total separation so that if the container upgrade works in its own right, you don't break the IdP, and vice versa. That separation reduces the risk of that kind of bug.
-- Scott
>
More information about the users
mailing list