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.


Add a new idea Subscribe
Status Not under consideration
Workspace WebSphere Liberty
Created by Guest
Created on Jul 4, 2023

RELATED IDEAS

Clients have requested this capability. It would round out the filesystem consuming controls by giving stdout and stderr the same log filesystem space consumption as messages.log

Clients have requested this capability. It would round out the filesystem consuming controls by giving stdout and stderr the same log filesystem space consumption as messages.log

It should be possible to redirect Liberty server's stdout and stderr output streams to he filesystem.  stdout.log and stderr.log should be collected in the WLP_OUTPUT_DIR directory and space managed in the way as messages.log.  

One approach would be to create  posix named pipes or FIFOs called stdout..fifo and stderr.fifo.

Update server startup JCL to launch a daemon process to read the named pipes and write the data to stdout.log and stderr.log


 

Idea priority Medium
  • Guest
    Reply
    |     Aug 25, 2023

    Close, No Response (CNR) text example

    Thank you for the suggestion. We’ve not heard back from you in some time, and according to our policy (https://www.ibm.com/support/pages/node/6242260) for reviewing and addressing RFEs we have decided to close this request. If you would like to discuss this decision further, please contact Graham Charters <charters@uk.ibm.com>.


  • Guest
    Reply
    |     Jul 14, 2023

    We are not sure that it would be possible for us to roll the files written by JES. However looking at the support case it appears that the output being written to the console consists of:

    1. Liberty console

    2. JVM Verbose GC logging

    The Liberty console.log details are also in messages.log so you could disable this output by using the consoleLogLevel in the logging configuration in server.xml to OFF (or set com.ibm.ws.logging.console.log.level in bootstrap.properties or set the WLP_LOGGING_CONSOLE_LOGLEVEL environment variable). For more information about that, start here.

    The JVM can be configured to write the verbose GC log to a file using the -Xverbosegclog option, this option also supports rolling those log files. More information about that can be found here.

    If you do both of these there would be no output in the process output at which point there wouldn't be a need to roll those files. Would this solution work for you?

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.