Hi Matthew
I didn't get any joy on this despite exhausting all avenues of support. We tried it but the behaviour was wild and caused issues like hanging the JVM so we scrapped it. Support couldn't help us find root cause. We ended up writing the logs to the WAS System Out and just use filtering to review log activity specific to our handlers. Not ideal but we decided we didn't really need things to be separate like with log4j.
Regards, Kenny
------------------------------
Kenny Dick
------------------------------
Original Message:
Sent: Tue July 08, 2025 08:07 PM
From: Matthew Clay
Subject: JUL Logging for FileNet Custom Event Action Handler
Kenny did you ever get a resolution to this?
------------------------------
Matthew Clay
Original Message:
Sent: Wed August 02, 2023 03:29 AM
From: Kenny Dick
Subject: JUL Logging for FileNet Custom Event Action Handler
Hey Everyone
I'm looking to connect with anyone who has successfully converted their custom event action code module to use the new JUL logging capability which replaced Log4j. During development, we're seeing some issues with formatting and multiple lock files per iteration of the event fired so could so with the some help from someone who has it working.
Thanks in advance, Kenny
------------------------------
Kenny Dick
------------------------------