Rudder

François ARMAND wrote:

The problem here is that if only one of the two is down, we have to restart Jetty for both.

And typically, if it's Rudder webapp that is down, and that Jetty restart in the middle of an inventory processing, then we are doomed (the inventory will be partially processed).

This is a manifestation of #1721.

Perhaps we should have two jetty, with only one application for each of them.

This also seems related to #1974.

Retargeting from 2.6 to general ideas - the 2.6 roadmap has not been decided on yet.

We went in the opposite direction in rudder 6.0. We merged both since their functionnal perimeter was more and more linked, to the point it didn't make any sense to have too app.
If we had to split now, it would perhaps be around policy generation, which is a totally orthogonal process that policy definition and compliance aggregation.