OO 10.70 - general.log keeps on rolling non-stop showing some JDBC connections stuff???

Hi!

There is no running flows in central but I can see this data continuously rolling in my general.log? Is there an issue or a flow that is continuously running or might be an endless loop somewhere? Please help me check... thanks in advance:

2018-04-19 11:41:07,510 [scoreOrchestratorScheduler-2] (StatisticalLoggingSessionEventListener.java:275) INFO  - Session Metrics {
    222863 nanoseconds spent acquiring 1 JDBC connections;
    0 nanoseconds spent releasing 0 JDBC connections;
    0 nanoseconds spent preparing 0 JDBC statements;
    0 nanoseconds spent executing 0 JDBC statements;
    0 nanoseconds spent executing 0 JDBC batches;
    0 nanoseconds spent performing 0 L2C puts;
    0 nanoseconds spent performing 0 L2C hits;
    0 nanoseconds spent performing 0 L2C misses;
    0 nanoseconds spent executing 0 flushes (flushing a total of 0 entities and 0 collections);
    0 nanoseconds spent executing 0 partial-flushes (flushing a total of 0 entities and 0 collections)
}
2018-04-19 11:41:07,529 [WorkerFillBufferThread] (StatisticalLoggingSessionEventListener.java:275) INFO  - Session Metrics {
    183712 nanoseconds spent acquiring 1 JDBC connections;
    0 nanoseconds spent releasing 0 JDBC connections;
    0 nanoseconds spent preparing 0 JDBC statements;
    0 nanoseconds spent executing 0 JDBC statements;
    0 nanoseconds spent executing 0 JDBC batches;
    0 nanoseconds spent performing 0 L2C puts;
    0 nanoseconds spent performing 0 L2C hits;
    0 nanoseconds spent performing 0 L2C misses;
    0 nanoseconds spent executing 0 flushes (flushing a total of 0 entities and 0 collections);
    0 nanoseconds spent executing 0 partial-flushes (flushing a total of 0 entities and 0 collections)
}

Regards,

Don

  • Verified Answer

    Hi Don,

    This usually happens because the general log (at least) is set with log level debug. In this mode all of the transactions that OO uses get logged in the general.log. If you need to get more log info than the standard, but not also get these logs switch the log level to INFO. 

    Hope this helps,

    Vlad

  • Hmmmmnnnn! I checked my log4j.properties and my log.level was set to INFO already... now I'm wonding where is this coming from?  By the way I have 2 centrals, general log for the 1st is OK, the 2nd continuously rolling with this JDBC thing...

    log.file.path=${oo.home}/var/logs
    #loglevel can be any of DEBUG INFO WARN ERROR FATAL
    #log.level=WARN
    log.level=INFO
    execution.log.level=INFO
    reverse.log.level=WARN
    deployment.log.level=INFO
    #date.pattern="'.'yyyy-MM-dd"
    def.file.max.size=10MB
    def.files.backup.count=10
    msg.layout=%d [%t] (%F:%L) %-5p - %m%n

  • I changed my log.level = WARN and that JDBC thing was gone... thanks Vlad