[
https://issues.jboss.org/browse/WFLY-8452?page=com.atlassian.jira.plugin....
]
Tomaz Cerar closed WFLY-8452.
-----------------------------
Assignee: Stuart Douglas (was: Jason Greene)
Resolution: Rejected
This is not a regression in any way, it is a graceful shutdown in action.
For your case, you should probably suspend server first and then shut it down.
{{:suspend(timeout=<some-timeout>)}}
this way server will just finish serving all in-flight requests but stop accepting new
ones.
after that you can shutdown the server.
you could also try with {{:shutdown(timeout=<some-timeout>)}}
but I don't know on top of my head if that would work in your scenario.
Management Interfaces stopping before server fully shutdown
-----------------------------------------------------------
Key: WFLY-8452
URL:
https://issues.jboss.org/browse/WFLY-8452
Project: WildFly
Issue Type: Bug
Components: CLI
Affects Versions: 10.1.0.Final
Reporter: John Farrelly
Assignee: Stuart Douglas
In our product, we use jboss-cli.sh to monitor if WildFly is running ({{jboss-cli.sh -c
--controller=${JBOSS_HOST}:${JBOSS_MANAGEMENT_PORT} "read-attribute
server-state"}}). We've been using this mechanism to determine if JBoss/WildFly
is running since JBoss 7.1.1.Final.
What we are seeing in WildFly 10.1.0.Final is that WildFly shuts down the native
interface before it has closed all other services. This means that some long-running
business logic thread in WildFly can stop it from shutting down, but the native interface
has already stopped, making it seem that WildFly has stopped.
I can see that other services (such as undertow) stay up until the long running business
logic thread has completed. This is a regression from JBoss AS 7.1.1, where the
management interfaces would not stop while long running business logic was still
executing.
Here's the management section of my standalone.xml:
{code:xml}
<management>
<security-realms>
<security-realm name="ManagementRealm">
<authentication>
<properties path="mgmt-users.properties"
relative-to="jboss.server.config.dir"/>
</authentication>
</security-realm>
<security-realm name="ApplicationRealm">
<authentication>
<properties path="application-users.properties"
relative-to="jboss.server.config.dir"/>
</authentication>
</security-realm>
</security-realms>
<management-interfaces>
<native-interface security-realm="ManagementRealm">
<socket-binding native="management-native"/>
</native-interface>
<http-interface security-realm="ManagementRealm">
<socket-binding http="management-http"/>
</http-interface>
</management-interfaces>
</management>
{code}
We use {{jboss-cli.sh}} to issue the shutdown command:
{code}
jboss-cli.sh -c --controller=${JBOSS_HOST}:${JBOSS_MANAGEMENT_PORT}
--command=":shutdown"
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)