-
Notifications
You must be signed in to change notification settings - Fork 47
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
Liberty doc updates related to configurable quiesce timeout #6983
Comments
Update for the server stop command. https://openliberty.io/docs/latest/reference/command/server-stop.html On the same page: |
Similar to previous comment, the following page needs updated: |
The page that describes how to configure the application manager , needs to describe the new quiesceTimeout attribute on the applicationManager element. Attribute name: quieseTimeout |
Hi @jimblye - is there a target (or estimated) GA for this update? |
@dmuelle - Trying for GA 230012. |
@dmuelle I updated the pictures, texts and some of links above because we decided in the UFO review to move the location of the quiesceTimeout configuration from the Executor to the Application Manager component. |
configurable quiesce timeout #6983
Hi @jimblye Suggested corrections have been made. Draft links: Will update OL: https://docs-draft-openlibertyio.mqj6zf7jocq.us-south.codeengine.appdomain.cloud/docs/latest/reference/config/applicationManager.html - Need to clarify some information with @dmuelle on this. Will get back to you with the complete updates. Regards, |
Hi @jimblye The suggested corrections have been made. Draft links: The page that describes how to configure the application manager - (https://openliberty.io/docs/latest/reference/config/applicationManager.html) -> We do not own this document. So the quiesceTimeout attribute information will need to be made from the developer end. Regards, |
Existing documentation needs to be updated as a result of
new issue in OpenLiberty Make Quiesce timeout configurable - 25523
Any doc that describes the quiesce stage timeout probably needs an update.
The text was updated successfully, but these errors were encountered: