Access Console output for debugging JSR-223 starts


#1

This post is a conversation I started with Micha in Slack but it stalled out. Moving here to Discourse with the hopes of getting some input on it.


Is there any way to get access to the console output when Lucee is starting up via JSR-223? I used to be able to do this in CommandBox 3 with the cli loader, but with JSR-223 I don’t know how to debug the actual Lucee startup. I want to see the debugging messages that Lucee itself outputs, not arbitrary messages of my own making. The expansion of the server/web contexts, downlaoding of bundles, etc
This sort of stuff:

WEB CONTEXT (53e8d78557fa27dce7957fcec0dfa25f)
-------------------------------------------------------------------
- config:D:\.Command Box\server\C3D9460AC18B18AC462BBBF1E02425C8-cfconfig\lucee-5.2.8.0-SNAPSHOT\WEB-INF\lucee-web (custom setting)
- webroot:C:\Users\Brad.development\Documents\GitHub\cfconfig
- hash:53e8d78557fa27dce7957fcec0dfa25f
- label:53e8d78557fa27dce7957fcec0dfa25f
===================================================================
[INFO ] 2018-05-21 23:08:34.36 fixed LFI
[INFO ] 2018-05-21 23:08:34.37 fixed salt
[INFO ] 2018-05-21 23:08:34.37 fixed S3
[INFO ] 2018-05-21 23:08:34.37 fixed PSQ
[INFO ] 2018-05-21 23:08:34.37 fixed logging
[INFO ] 2018-05-21 23:08:34.37 fixed Extension
[INFO ] 2018-05-21 23:08:34.38 fixed component mappings
[INFO ] 2018-05-21 23:08:34.38 fixed to big felix.log
[INFO ] 2018-05-21 23:08:34.38 deploy web context
[INFO ] 2018-05-21 23:08:34.39 loaded config
[INFO ] 2018-05-21 23:08:34.41 loaded constants
[INFO ] 2018-05-21 23:08:34.47 loaded loggers
[INFO ] 2018-05-21 23:08:34.47 loaded temp dir
[INFO ] 2018-05-21 23:08:34.48 loaded id
[INFO ] 2018-05-21 23:08:34.49 loaded version
[INFO ] 2018-05-21 23:08:34.49 loaded security
[INFO ] 2018-05-21 23:08:34.49 loaded lib

Micha replied with this link:

And my replies were as follows:

Ahh, interesting. I’ve never noticed that setting.
Of course, what to do is there is no XML file to start with because Lucee hasn’t created the contexts!
Do these system properties also take the same values?

lucee.system.out
lucee.system.err

I’ve seen those but had no idea what I would pass into them.
But seeing the XML file now makes me think the system properties maybe can take the same values.

I set these two java properties before loading Lucee via JSR-223

lucee.system.out=default
lucee.system.err=default

but nothing happened.
I have also set the following XML in my lucee-server.xml and still no output:

<system out="default" err="default"/>

I’m going to need more direction from you on how to use this.


#2

@isapir or @micstriit can either of you please help finish this conversation by explaining how to use the settings Micha pointed out in the Slack conversation above?


#3

Unrelated to your question but what Slack channels are you on? I have never used Slack and seen there is cfml.slack.com but is there lucee specific channels?


#4

I’m on a ton of Slack channels :slight_smile: There is a #lucee channel that is pretty active on the CFML Slack team. You should really join it. The conversation above, however, happened on an internal LAS member slack team.


#5

Ahh ok thanks. I asked for an invite to the CFML slack channel, just waiting on them to accept it.


#6

The invites for the CFML Slack are automated. You should have gotten an E-mail right away. Check your spam folder.