Logging to stdout mostly stops after some period (1-2 days?)

[bbockelm]

I have a test issuer which is run at trace-level logging and is logging to stdout. This is preferred for me as the stdout is forwarded to kubectl logs.

However, after some amount of time (unclear if it is time-based or size-based; perhaps after some log rotation is triggered?), the flow to stdout stops. This is the only message:

OA4MP command line client state stored on Mon Jun 12 20:04:24 UTC 2023

Is it possible to keep the logs flowing?

[jjg-123]

This seems to describe the problem: https://stackoverflow.com/questions/6314285/java-util-logging-stops-working-after-a-while

TL;DR -- The logger itself may get garbage collected after being unused for a period of time. Solution is to ensure a gratuitous strong reference to it.

[bbockelm]

@jjg-123 - was this ever resolved?

[bbockelm]

Just as a FYI -- after upgrading to 5.4.1, I still see logs stop working after about a day.

[jbasney]

fixed in https://github.com/ncsa/oa4mp/releases/tag/v5.4.2 ?