Setting a startup timeout

[April Monoceros]

I'm running into an issue where a large deployment will timeout after 7.5 minutes (450 seconds) on startup.

Presumably this is a setting _somewhere_, but all my searching has led me nowhere. Does anyone have any idea on what the magic words are to adjust the startup timeout?

Ideally, yes, we'd have Wildfly start faster than 450 seconds, but at this point the server does tend to start okay, just really close to or just over that timeout. It'd be nice to not have to worry about it, when it goes long but still starts up.

And with the "just over", when I start it as a Windows service, it fails to start, but when I start it using the command line, the command times out, but things start up in the background anyway.

Thanks for any help, and my apologies if that's not enough info or I'm barking up the wrong tree.

[James Perkins]

I'm not sure if there is specific documentation, but the property you want is jboss.as.management.blocking.timeout. In CLI you can set it like:
/system-property=jboss.as.management.blocking.timeout:add(value=600)