[wildfly-dev] Allowing disabling of 'graceful startup'

Ingo Weiss ingo at redhat.com
Tue Jul 30 01:58:58 EDT 2019

Hi Brian, thanks for looking into this.

On 2019-07-29 12:17:36-0500, Brian Stansberry wrote:
> The Question
> Question is whether to
> a) have an overall config switch to disable graceful startup across the
> board (e.g. a new value for the --start-mode cmd line param passed to
> standalone.sh)
I think this the better solution based on your pros. Having this
limited to only HTTP(S) requests makes it very limiting and ends up
not being sufficient in some cases, as you described.

Do you think it would be possible to make this configurable per
subsystem as well?

For some subsystems, like Undertow and EJB, you may want to use as
soon as they become available to reach out other systems or even call
a servlet on another deployment that has already started, this a case
I've seen before, while others, like Messaging, you may want to wait
for other subsystem, like JCA, to come up first. Does it make sense?

> Best regards,
> Brian

Best regards
Ingo Weiss
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/wildfly-dev/attachments/20190730/16b42242/attachment.bin 

More information about the wildfly-dev mailing list