[
https://issues.apache.org/jira/browse/IGNITE-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14611914#comment-14611914
]
Gianfranco Murador commented on IGNITE-788:
-------------------------------------------
Hello Artem ,
I will make the changes later this week. As already said, I can ensure, with
the current implementation,
that the lines will be of the same format. In the file patch-ignite-788.zip (
see in the jira) there are examples of log file producted with the new module.
The contents of the log file can become the same respect to log4j, but there
must be a default log file (default.log),because there are initial calls with a
thread context not setted. I set the thread context when the nodeid is setted.
Let me know if, for you, this solution is good.
For thread context I mean this:
https://logging.apache.org/log4j/2.x/manual/thread-context.html
> add support for log4j2 into org.apache.ignite.logger.log4j package
> (Log4J2Logger)
> ---------------------------------------------------------------------------------
>
> Key: IGNITE-788
> URL: https://issues.apache.org/jira/browse/IGNITE-788
> Project: Ignite
> Issue Type: New Feature
> Components: general, newbie
> Affects Versions: sprint-3
> Reporter: Yakov Zhdanov
> Assignee: Gianfranco Murador
> Labels: newbie
> Fix For: sprint-7
>
> Attachments: ignite-788-review.patch,
> ignite-sprint-5_ignite-788.patch, ignite-sprint-5_ignite-788.patch,
> patch-ingnite-788.zip
>
>
> This should be a new module. See {{ignite-log4j}} module for reference
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
