CMS/Runner Log Level in 11.5

[Former Member]

Forum,

Does anyone know of a way to programmatically set the Log Level using BLS?

At the beginning of a TRX set the Log Level to DEBUG and when the TRX completes reset it back to ERROR?

Thanks

Roger

[jcgood25]

Roger,

You might want to consider running something like this URL:

/Lighthammer/Runner?Transaction=Folder/File&Input1=XXX&Input2=YYY&LogType=TRACEDEBUG

/Lighthammer/Runner?Transaction=Folder/File&Input1=XXX&Input2=YYY&&LogType=DEBUG

This will do a test run of the TRX similar to the F5 / F6 in the BLS editor, but you can capture the results in the browser window (obviously the primary cms log is still controlled by the system settings).

You could 'borrow' the syntax from the Log Configuration jsp page, but I would discourage that. The INFO log level may be what you need to troubleshoot the issue(s).

Regards,

Jeremy

[Former Member]

Jeremy,

I understand what you are telling me but that method won't help my issue.

The application that provides web services to BLS has problems from time to time and these problems almost always occur early in the morning on random days. By the time I come into work the problem no longer exists. The Runner log captures the error, but of course no details as DEBUG would. The TRX has three web service calls and it would be nice if I could identify the culprit.

I really don't want to turn on DEBUG for Runner or General when I go home and capture everything until I come in the next morning in hopes of catching something, but I may have to.

Thanks for your insight!

Roger

[jcgood25]

The morning 'hangover' you are describing sounds more like it might be due to IIS going to sleep, or the application pool restarting itself and creating a disconnect with ServletExec.

Based upon the cms logs, does it appear as though MII reinitializes on the random days?

You would likely see the startup sequence including a chunk starting with:

SYSTEM InitializationEngine - Beginning Illuminator Initialization on XXXXXXXX

and end with:

SYSTEM InitializationEngine - Illuminator system started up successfully

The first touch would seemingly wake things up and most users might dismiss this or just refresh a page (perhaps just wait unusually long for the login page).

[Former Member]

Jeremy,

Nothing in the CMS log like you indicate. What I do see are numerous "JCO_ERROR_SERVER_STARTUP" and of course my problem error of "Error Invoking Web Service Action: Null"

Roger