How to revert to a Logback configuration when running applications as a Windows service
Article ID: KB0076155
Updated On:
| Products | Versions |
|---|---|
| TIBCO Streaming | 7 |
Description
After configuring an application to run as a Windows service, log files are no longer generated.
Issue/Introduction
How to revert to a Logback configuration when running applications as a Windows service
Resolution
Instructions for StreamBase 7
When running in the context of a Windows service, StreamBase Server's Log4j logging is configured by default to write to the Windows Event Log. If you were previously using a Logback configuration (rather than Log4j), you should perform the following steps to revert to Logback:- In the Windows service's environment, set the following variables..
STREAMBASE_USE_CUSTOM_LOGGING=true
SB_CLIENT_CLASSPATH=/full/path/to/sbclient.jar (This restores the reference to logback.)
- Your service will still need to find the logback.xml file, as usual, by having it listed in the sbd.sbconf as so:
<java-vm>
<sysproperty name="logback.configurationFile" value="/path/to/logback.xml"/>
</java-vm>
<sysproperty name="logback.configurationFile" value="/path/to/logback.xml"/>
</java-vm>
These modifications will undo the automatic switch to Log4j when running your applications in background mode.
Note that Logback does not have NT Event Log capability, so it will not be able to trigger NT Event Notification (which Log4j does using the default configuration).
Instructions for TIBCO Streaming 10
TIBCO Streaming 10 always uses Logback exclusively and does not use Log4J. However you may need to add to your logging configuration the Windows Event Logger appender, as described in the Help documentation here: TIBCO Streaming > Installation Guide > Configuring Windows as a Service, "Windows Event Logging Appender"
Feedback
Yes
No
Powered by
