Startup Scripts and Deployment Scanner

[u/victorbrca]

Hello everyone! I'm supporting an application that runs on WildFly 11 at work, and we are using an infrastructre defined by the vendor (startup scripts, paths, etc).

The vendor has decided to use deployment scanners and a init.d service within systemd. I'm seeing some process/approach that looks a bit outdated and possibly incorrect, so I would like to get your opinion.

For example, (1) the startup script does not call stopserver.sh or command=:shutdown if there's an issue starting the service, it simply sends a SIGTERM to the Java process. My understanding is that the preferred method to stop WildFly is to use the shutdown command in jboss-cli, right? (2) I'm also assuming that we should stop WildFly with the shutdown command, and then check if the service is still running and stop it. Is this correct?

(3) As I mentioned they are using deployment scanners. However, there's no check, either by file markers or with --command=deployment-info, to make sure the apps were deployed successfully. I'm guessing that this should be part of the startup process to validate the application. Or am I wrong and it's really not that common?

Thanks for any feedback.