<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jul 31, 2019 at 8:40 AM Ingo Weiss <<a href="mailto:ingo@redhat.com">ingo@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2019-07-30 17:40:52-0500, Brian Stansberry wrote:<br>
> On Tue, Jul 30, 2019 at 12:59 AM Ingo Weiss <<a href="mailto:ingo@redhat.com" target="_blank">ingo@redhat.com</a>> wrote:<br>
> <br>
> > Hi Brian, thanks for looking into this.<br>
> ><br>
> > On 2019-07-29 12:17:36-0500, Brian Stansberry wrote:<br>
> > > The Question<br>
> > ><br>
> > > Question is whether to<br>
> > ><br>
> > > a) have an overall config switch to disable graceful startup across the<br>
> > > board (e.g. a new value for the --start-mode cmd line param passed to<br>
> > > standalone.sh)<br>
> ><br>
> > I think this the better solution based on your pros. Having this<br>
> > limited to only HTTP(S) requests makes it very limiting and ends up<br>
> > not being sufficient in some cases, as you described.<br>
> ><br>
> > Do you think it would be possible to make this configurable per<br>
> > subsystem as well?<br>
> ><br>
> > For some subsystems, like Undertow and EJB, you may want to use as<br>
> > soon as they become available to reach out other systems or even call<br>
> > a servlet on another deployment that has already started, this a case<br>
> > I've seen before, while others, like Messaging, you may want to wait<br>
> > for other subsystem, like JCA, to come up first. Does it make sense?<br>
> ><br>
> <br>
> If I understand you correctly, instead of my a) a global flag, or my b) an<br>
> undertow flag, there would be several b)s. One to tell undertow to let<br>
> requests through, one to tell EJB to let requests through,, one to tell<br>
> messaging to let requests through (although that one's theoretical as<br>
> messaging doesn't have graceful startup/shutdown anyway.) Probably one for<br>
> every subsystem that does anything related to graceful. The user then<br>
> toggles the ones they want for their app. They'd have to know which they<br>
> want.<br>
<br>
That's what I was thinking.<br>
<br>
> That would be a quite big increase in scope.<br>
<br>
Yeah, it was an increase in scope indeed, but I think it might end up<br>
being a better fit for users.<br>
<br>
It could surely be a multiple-phase approach. We start with a, see how<br>
it goes, then move to b * no_of_possible_subsystems.<br></blockquote><div><br></div><div class="gmail_default" style="font-family:"trebuchet ms",sans-serif">That's true; a global switch doesn't preclude something more fine-grained in the future.</div><div class="gmail_default" style="font-family:"trebuchet ms",sans-serif"></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> Not sure it's worth it, but it's something to think about while I'm on PTO.<br>
> :)<br>
<br>
Enjoy and don't think about this. That's bad for you :)<br></blockquote><div><br></div><div class="gmail_default" style="font-family:"trebuchet ms",sans-serif">Thanks. Probably won't think too much. :) But this is a not small or trivial thing, nor something huge like dealing with javax.* being renamed to jakarta.* so it's the kind of thing I sometimes find relaxing to think about when I'm chilling out.</div><div class="gmail_default" style="font-family:"trebuchet ms",sans-serif"></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
-- <br>
Ingo Weiss<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Brian Stansberry<div>Manager, Senior Principal Software Engineer</div><div>Red Hat</div></div></div></div>