-
Notifications
You must be signed in to change notification settings - Fork 464
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WFCORE-6894 Extract interfaces from SuspendController appropriate for its consumers #6117
Conversation
3973ccb
to
6c8f8cb
Compare
Adding hold label while I experiment with ServerSuspendContoller API changes to better accommodate non-blocking server activity. |
… SuspendController directly to operation handlers, rather than referencing via MSC.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
…ntation. Reimplement SuspendController to better accommodate non-blocking server activity and simplify timeout behavior. Provide context to activity suspend/remove calls.
Replace GracefulShutdownService with static reference to CompletionStage of final suspend operation.
…create CompletionStage-based replacements.
@@ -314,7 +313,6 @@ protected void boot(final BootContext context) throws ConfigurationPersistenceEx | |||
} | |||
} | |||
context.getServiceTarget().addService(SUSPEND_CONTROLLER_CAPABILITY.getCapabilityServiceName(), suspendController) | |||
.addDependency(JBOSS_SERVER_NOTIFICATION_REGISTRY, NotificationHandlerRegistry.class, suspendController.getNotificationHandlerRegistry()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just in case anyone is also reviewing this. This effectively makes the SuspendController stop waiting for JBOSS_SERVER_NOTIFICATION_REGISTRY, but we are fine with it, since we think NotificationHandlerRegistry is an orphan relationship used in the past.
server/src/main/java/org/jboss/as/server/suspend/CountingRequestCountCallback.java
Outdated
Show resolved
Hide resolved
server/src/main/java/org/jboss/as/server/suspend/ServerActivity.java
Outdated
Show resolved
Hide resolved
server/src/main/java/org/jboss/as/server/suspend/ServerActivityCallback.java
Outdated
Show resolved
Hide resolved
server/src/main/java/org/jboss/as/server/suspend/SuspendController.java
Outdated
Show resolved
Hide resolved
server/src/main/java/org/jboss/as/server/suspend/SuspendController.java
Outdated
Show resolved
Hide resolved
request-controller/src/main/java/org/wildfly/extension/requestcontroller/RequestController.java
Outdated
Show resolved
Hide resolved
request-controller/src/main/java/org/wildfly/extension/requestcontroller/ControlPoint.java
Outdated
Show resolved
Hide resolved
default void suspendingServer(long timeout, TimeUnit unit) { | ||
if (timeout > 0) { | ||
ServerLogger.ROOT_LOGGER.suspendingServer(TimeUnit.MILLISECONDS.convert(timeout, unit)); | ||
} else if (timeout < 0) { | ||
ServerLogger.ROOT_LOGGER.suspendingServerWithNoTimeout(); | ||
} else { | ||
ServerLogger.ROOT_LOGGER.suspendingServer(); | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
Thanks @pferraro |
https://issues.redhat.com/browse/WFCORE-6894