This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
For Digital Commerce, we are dockerizing all applications. Application life cycle ties to docker container life cycle. When the application fails to start, the container should also fail, so the orchestrator can notice the failure, then a new container will be deployed.
Currently, Liberty doesn't have an option to stop the server when there is an application failure during server start up. When there is an application failure during start up, the server continues to start, so the docker container is still running, orchestrator will not notice any issue because the container is still alive.
With this new feature, if there is an application failure during start up, Liberty server is stopped and then docker container will stop, The orchestrator notices this failure and will deploy a new container, this will avoid application downtime and improve the reliability and performance.
I opened PMR 21917,442,000 and tried to use the "set startTimeout" parameter, but it doesn't work. The response from WAS team is that "Liberty is not designed to stop a server when an application can't be started."
Idea priority | High |
RFE ID | 111022 |
RFE URL | |
RFE Product | WebSphere Application Server |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Thank you for this suggestion. We believe the recommended approach to addressing this requirement is to create readiness probe implementations and hook those to Kubernetes Readiness. The MicroProfile Health APIs make it easy to write Kubernetes probes. If you have any concerns about this suggestion/resolution, please contact Graham Charters <charters@uk.ibm.com>.