Stop the old application server, which also ensures that the database is not used in any way anymore.
Consider a graceful shutdown of the application server. The motivation for this is described in the earlier chapter Stop creation of new jobs in the internal job system. This can be achieved with the CLI command “suspend” or “shutdown” in combination with a timeout parameter, where you make the server wait for all active requests to complete before shutting down.
See the vendor’s application server documentation for details:
-
Red Hat Portal – Starting and Stopping JBoss EAP – “Suspend Servers” [JBoss Suspend]
-
Mastertheboss – “How to shutdown WildFly gracefully” [WildFly Suspend]
In contrast, a simple shutdown is done like this:
# ./jboss-cli.sh --connect controller=remote+https://127.0.0.1:10048 command=:shutdown
{
"outcome" => "success",
"result" => undefined
}