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 Future consideration
Created by Guest
Created on Dec 6, 2022

Observed a negative value for %D and a dash(-) for %{R}W in the NCSA access log

In the customer's WASv8.5.5.20 system, they have observed a negative value for %D and a dash(-) for %{R}W in the NCSA access log.

Referring the WAS code, it just subtract System.currentTimeMillis from the previous System.currentTimeMillis. We were focusing on the condition where the OS clock goes back in time to past and seeking the way to prevent the backword time adjustment from both Java and OS perspectives. The likely cause is NTP, but it's still not clear. In the discussion from Java perspective, Java dev team pointed out the necessisity of use of System.nanoTime() instead of System.currentTimeMillis.

Idea priority Medium