Cannot see Lucee's console messages for debugging in JSR-223


Now that CommandBox uses JSR-223 to start Lucee, there is no way for me to access the console output of Lucee that shows the deployment of contexts, downloading of bundles, etc. I need to be able to turn this on for debugging and I used to be able to do it with the old CLI loader classes.

Micha pointed me at these settings, however I have tried many versions of trying to use these settings and they simply do not work:

I also tried the following JVM system props, but they also do nothing:

I've given up. If this works, please show me how to do it.




Michael Offner
December 3, 2018, 1:08 PM

one secure way around is to set

Brad Wood
February 26, 2019, 7:49 PM

What will it take to get this working. This is still a real pain when troubleshooting Lucee startups in CommandBox or JSR-223 in general. I've got someone whose CommandBox is trying to download OSGI bundles inside Lucee on startup and I have no way to be able to debug this for them. How can I redirect Lucee's output? Changing the system out stream is not a good solution for me since the JLine library in CommandBox needs to actually use the system out for console interactions.

Michael Offner
February 27, 2019, 7:07 AM

the goal need to be that Lucee never log to the console at all, i will try to give ithigher priority, but i cannot give you any time estimate. it is part of the upcoming sprint...

Brad Wood
February 27, 2019, 4:47 PM

Thanks for looking into it. It will be a great help in debugging to be able to get that output from JSR-223 redirected somewhere.

Michael Offner
March 14, 2019, 7:47 AM

removed all console log done by Lucee, now lucee logs to the "application" log instead IF AVAILABLE, if not it logs to the "global" log what does not follow the log pattern defined in the admin.



Michael Offner


Brad Wood




Fix versions



Affects versions