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 (https://ideas.ibm.com).


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 (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.


Status Needs more information
Workspace WebSphere Liberty
Created by Guest
Created on Aug 28, 2026

Allow option to log Context Not Found errors

When a problem/corruption occurs in one instance of a cluster, it is a challenge to identify which Liberty JVM has the problem.

In a Case I opened with IBM, I had cluster of 50+ CICS regions with the same Liberty JVM & application running in the region. We identified that one (or more) of the instances were corrupt and when the client would load balance to that instance, they would get a HTTP 404 Context Not Found webpage. First, this webpage identifies itself using the WAS branding, not the more modern Liberty nomenclature. However, this error doesn't identify which instance had the problem nor is it logged to messages.log . Through the Case, we were informed that is not an option and to open an Idea for it.

In the meantime, to resolve Production impact, we had to, one-by-one, switch the JVM to an alternate port to target that one directly until we found a single instance was corruption and required a cache flush and application reinstall. This was far more involved than it should have been.

Idea priority Medium
  • Admin
    Jahnvi Bedia
    Sep 2, 2026

    Hi, thank you for opening an idea with us.

    We believe the information you are looking for can be obtained through HTTP access logging, which provides visibility into incoming requests, including the request details and HTTP response status. This should help you identify and track specific 404 responses without needing to bypass the proxy or make changes to the ports.

    We have a document that provides more information on configuring and using access logging: https://openliberty.io/docs/latest/access-logging.html

    Please let us know if you have any questions while setting this up or if you find that the information provided by the access logs does not address your specific use case. We would be happy to discuss further.