Skip to Main Content
Cloud Platform

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 (

Shape the future of IBM!

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:

Search existing ideas

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 your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace WebSphere Liberty
Created by Guest
Created on Mar 16, 2020

LIBERTY and configuration validation when starting

Liberty read configuration from server.xml
But if it exists bad configuration it will start without any fatal errors. (ignore the xml that liberty does not understand)
It is a kind of “best effort” starting that I do not want.
I prefer that It does not start and said “bad configuration with …”.
If not it will not have the behavior that we expect to be.

may be we can add a switch to have a strict validation of the xml configuration when starting ?

Can we see the effective “in memory” configuration ?

** If you declare Two registries it will federate both. So there is implicit configuration inside the runtime I‘d like to see this somewhere.

** if you read multiples files (include xml, configuration dropins…) , I want to see the “in memory result configuration tree”
I‘d like to see the server.xml with all the configuration that is currently in memory.

Idea priority Low
RFE ID 141043
RFE Product WebSphere Application Server
  • Admin
    Graham Charters
    Nov 5, 2021

    Thank you for the suggestion. The requirement does have merit, we would need specific examples where onError=FAIL is not working. Please raise support tickets for specific examples and we will consider updates for each. If you would like to discuss this decision further, please contact Graham Charters <>.

  • Guest
    Mar 16, 2021

    Part 2 of this request is a duplicate of

    Part 1, it is possible to set onError=FAILin to catch some of these cases, but not all.