Using SLF4J logging front end and alternative back-end loggers

This does not apply to TIBCO Streaming 10.x or later which does not use the SLF4J logger.

If you are use SLF4J in your code and logging isn't working as expected, be aware that StreamBase bundles SLF4J with the product. If you force the SLF4J jar files to load before the StreamBase client jar (sbclient.jar), your logging may start working as expected, but StreamBase platform logging may be compromised.

By default StreamBase uses SLF4J with Logback logging. See the following section of our documentation on configuring StreamBase to use a different back end: Using StreamBase Logging

If you see console logging errors like this:
It means that some other SLF4J implementation besides the one in sbclient.jar was found on the classpath.

You may either configure StreamBase to NOT supply SLF4J (see the above documentation link), or you may remove the alternative implementation from your classpath configuration.

Using SLF4J logging