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
Created by Guest
Created on Jul 6, 2022

The fix for PI67363 to be made available on the WAS 8.5 platform.

Issue as per APAR : The following error is seen in logs during startup of Application Server 9.0 after fresh install SystemErr R ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console Although the error is safe to be ignored, fixed have been added to the 9.0 codestream to prevent it from displaying. Customer has requested this be implemented on the 8.5 codestream
Idea priority Low
  • Guest
    Jul 7, 2022

    There is no need to backport PI67363 to 8.5.5 because log4j was removed via PH42762 as a response to a security vulnerabilty in log4j. If this APAR were installed, or the 8.5.5 install were upgraded to (the most recent service release of WebSphere) there is no more log4j so this problem would not occur.