In my testing, I wasn't able to get early startup material from the IdP to show up in the Jetty log prior to context init without adding this to the startup:
I'm not sure under what conditions that's needed, but it seemed to be needed for me with 9.4, and I think we probably should add it to our logging module.
Environment
None
Activity
Show:
Scott Cantor March 11, 2021 at 7:58 PM
Added to the jetty artifact.
Scott Cantor March 11, 2021 at 7:52 PM
I don't think this hurts anything so I'm going to slap into the files in our artifact, but that's not really critical path to the release anyway.
Rod Widdowson November 17, 2020 at 4:50 PM
I tried adding
to my "command line " and it still does nothing.
Scott Cantor November 17, 2020 at 4:31 PM
Maybe it isn't even needed, but you can check....does the Windows install pick up any of the context initializer logging from the IdP's spring initializer? Mine does not (without this change).
Rod Widdowson November 17, 2020 at 4:22 PM
And to the windows installation (where it needs to go into the procrun configuration), not the module because of forking.
Note because of forking we cannot add this to the eclipse branch either (although in that case it works. Go figure.
In my testing, I wasn't able to get early startup material from the IdP to show up in the Jetty log prior to context init without adding this to the startup:
I'm not sure under what conditions that's needed, but it seemed to be needed for me with 9.4, and I think we probably should add it to our logging module.