embed-server vs wildfly

[Sizum]

 I've encountered that when running a command in embed-server, our applications are reloaded when the main server is running. Is it possible to run commands in embed without affecting the main server? Please help

[Brian Stansberry]

In general, no. You can't have two server processes that share the same jboss.server.base.dir (e.g. $WILDFLY_HOME/standalone by default.) And an embedded server inside a CLI process is effectively a server process.

Now, specifically why what you are doing is causing the non-embedded server process to reload applications, I don't know. Perhaps other users who've done similar things will have an idea why. All sorts of bad things can happen when two processes share the same writable dirs, so we haven't particularly thought through all the various possibilities.

When you say 'applications are reloaded' do you mean the server as a whole reloads? Or just deployments are redeployed?  How are they deployed? Via the deployment scanner?

[Sizum]

I did the testing. When WildFly is running and applications are running on it, the directories contain application content in the ../tmp/deployment*** and .../temp directories When we disable an application, these directories are emptied because the application is no longer running. But when WildFly is running, the application is running on it and any command occurs in embed, then the server starts and stops in the logs, after executing, for example, deploy -l, and the temp directory becomes empty. The application stops functioning. If you output the stdout log, it will contain entries about the application stopping.

четверг, 1 сентября 2022 г. в 22:31:27 UTC+5, brian.st...@redhat.com: