JVM heap size adjustments

[Cantor, Scott]

On 1/12/16, 10:51 PM, "users on behalf of Paul Caskey" <users-bounces at shibboleth.net on behalf of pcaskey at internet2.edu> wrote:



>IMHO, it sure is a nice thing that the Windows version packages Jetty.  Turns an upgrade into a 30 second thing that any Windows sysadmin will be familiar with.

Production systems require changes and local adjustments and the embedded model cannot allow for that without losing control and preventing that kind of upgrade process from guaranteeing success. We can guarantee upgrades work but not if people are allowed to do things that are routinely necessary. If you don't need to do those things, it's more likely that you just don't know why you need to, but regardless you can always go ahead and go with that approach as far as it takes you. I'm not even against rolling it into a Linux installer because it's not much more work than maintaining the same example configs we have in the wiki anyway.

>Having to roll your own Jetty takes us back to where folks are afraid to upgrade their shibb systems and end up not doing it, which is worse, IMO.

Upgrading a container *is* a big deal. It isn't hard anymore but it's not a casual decision. It also isn't really connected to upgrading the IdP, and using a separate container makes upgrading one or the other easier and less risky.

Regressions are why people are afraid to upgrade software, and the only fix for that is not to have them or tolerate them, and to ship patches immediately if they're found.

I don't blame anybody for not tracking 2.x releases. It proved unreliable to upgrade, plain and simple.

-- Scott