[jboss-jira] [JBoss JIRA] (DROOLS-991) File KnowledgeRuntimeLogger does not produce file until close() operation is closed

[Anton Giertli (JIRA)]

     [ https://issues.jboss.org/browse/DROOLS-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anton Giertli updated DROOLS-991:
---------------------------------
    Description: 
When you use file logger, like this:
        KieServices.Factory.get().getLoggers().newFileLogger(session, fileName)


The actual file does not get created until you call close() method.

While this may be beneficial in many use cases(probably the reasoning behind this is performance aspect), when debugging a rule execution, where rule are getting stuck - i.e. the whole JVM becomes unresponsive, then the actual log file will never be created.

Therefore, it would be nice to have this configurable, i.e.

1) Create log file when the close() method is called - better performance - this could be the default behavior.

2) Create log file immediately, and update it whenever there is something new to be logged - worse performance, but there will be some log available even if the rule execution will get stuck - this could be the configurable behavior

  was:
When you use file logger, like this:
        KieServices.Factory.get().getLoggers().newFileLogger(session, fileName)


The actual file does not get created until you call close() method.

While this may be beneficial in many use cases(probably the reasoning behind this is performance aspect), when debugging a rule execution, where rule are getting stuck - i.e. the whole JVM becomes unresponsive, then the actual log file will never be created.

Therefore, it would be nice to have this configurable, i.e.

1) Create log file when the close() method is called - better performance

2) Create log file immediately, and update it whenever there is something new to be logged - worse performance, but there will be some log available even if the rule execution will get stuck



> File KnowledgeRuntimeLogger does not produce file until close() operation is closed
> -----------------------------------------------------------------------------------
>
>                 Key: DROOLS-991
>                 URL: https://issues.jboss.org/browse/DROOLS-991
>             Project: Drools
>          Issue Type: Enhancement
>            Reporter: Anton Giertli
>            Assignee: Mario Fusco
>
> When you use file logger, like this:
>         KieServices.Factory.get().getLoggers().newFileLogger(session, fileName)
> The actual file does not get created until you call close() method.
> While this may be beneficial in many use cases(probably the reasoning behind this is performance aspect), when debugging a rule execution, where rule are getting stuck - i.e. the whole JVM becomes unresponsive, then the actual log file will never be created.
> Therefore, it would be nice to have this configurable, i.e.
> 1) Create log file when the close() method is called - better performance - this could be the default behavior.
> 2) Create log file immediately, and update it whenever there is something new to be logged - worse performance, but there will be some log available even if the rule execution will get stuck - this could be the configurable behavior



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)