Resolution:
Abstract:  
========
Debug log entries seen in log file when log level is set at INFO.        
  
Description:
============
When log level is set to INFO sometimes DEBUG level log entries will be found in TIBCO Business Events. Some examples of DEBUG entries from a INFO level log are listed below:

2013 Dec 11 16:31:31:630 GMT -8 Debug [main] - [com.tibco.security.TIBCOSecurity] system property set to j2se
2013 Dec 11 16:31:31:630 GMT -8 Debug [main] - [com.tibco.security.TIBCOSecurity] getVendor()=j2se
2013 Dec 11 16:31:31:813 GMT -8 Debug [main] - [com.tibco.security.TIBCOSecurity] getVendor()=j2se
2013 Dec 11 16:31:31:816 GMT -8 Debug [main] - [com.tibco.security.impl.np.CryptoVendor] Initialized crypto vendor j2se
  
Environment:
===========
ANY TIBCO BUSINESS EVENTS ENVIRONMENT
  
Symptoms:
========
You will see log entries with DEBUG role in TIBCO Business Events log file when actual log level is set to INFO.  

Cause:
=====

The “Send To terminal” is enabled and the “include output” check box is selected in the  Cluster Deployment Descriptor (CDD) file in the LogConfig. The DEBUG entries are actually STDOUT messages which are routed to the TIBCO Business Events logs when the “Send To terminal” and “include output” are enabled.  

Resolution:
==========
If you do not want the DEBUG messages in the engine logs when set at the INFO level then disable “send to terminal” in your logConfig in your Cluster Deployment Descriptor (CDD).
  
References:
==========
SR_ID: 1-FLW9WA

Debug log entries seen in log file when log level is set at INFO.