You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by rjdamore <rj...@gmail.com> on 2016/12/09 20:33:21 UTC
enabling log4j, read previous post, still have issues
Hi,
I've tried enabling log4j simply by including the ignite-log4j library.
However, it does not seem to have an effect. I've also read that to enable
Log4J module we should move the "optional/ignite-log4j" folder to the libs
directory before running "ignite.bat". My question is in order to avoid the
:
Can't load log handler "org.apache.ignite.logger.java.JavaLoggerFileHandler"
message,
should I include the igntie-log4j.jar file in the Ignite-Home directory
structure, or in my application structure? Also; where is this
optional/ignite-log4j folder? I have the binary distribution and the
source-built ignite installations, and I cannot locate this folder in either
of them. Is this a folder that I create myself?
Sorry if this is a naive question, but the actual error message for the log
handler is preventing us from using ignite in a distributed system. The log
is interrupting another applications ability to log to the same err.txt
file. I'm trying to get this message eliminated.
Thanks for any help.
The message i get is the same as :
http://apache-ignite-users.70518.x6.nabble.com/Can-t-load-log-handler-quot-org-apache-ignite-logger-java-JavaLoggerFileHandler-quot-td4490.html
However the solution in that thread is not working for me at all.
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/enabling-log4j-read-previous-post-still-have-issues-tp9466.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: enabling log4j, read previous post, still have issues
Posted by Andrey Gura <ag...@apache.org>.
Hi
please read `README.txt` file in `IGNITE_HOME/libs` directory of
Ignite. You should copy `IGNITE_HOME/libs/optional/ignite-log4j`
directory to `IGNITE_HOME/libs/` directory.
On Fri, Dec 9, 2016 at 11:33 PM, rjdamore <rj...@gmail.com> wrote:
> Hi,
> I've tried enabling log4j simply by including the ignite-log4j library.
> However, it does not seem to have an effect. I've also read that to enable
> Log4J module we should move the "optional/ignite-log4j" folder to the libs
> directory before running "ignite.bat". My question is in order to avoid the
> :
> Can't load log handler "org.apache.ignite.logger.java.JavaLoggerFileHandler"
> message,
>
> should I include the igntie-log4j.jar file in the Ignite-Home directory
> structure, or in my application structure? Also; where is this
> optional/ignite-log4j folder? I have the binary distribution and the
> source-built ignite installations, and I cannot locate this folder in either
> of them. Is this a folder that I create myself?
>
> Sorry if this is a naive question, but the actual error message for the log
> handler is preventing us from using ignite in a distributed system. The log
> is interrupting another applications ability to log to the same err.txt
> file. I'm trying to get this message eliminated.
> Thanks for any help.
>
> The message i get is the same as :
> http://apache-ignite-users.70518.x6.nabble.com/Can-t-load-log-handler-quot-org-apache-ignite-logger-java-JavaLoggerFileHandler-quot-td4490.html
>
> However the solution in that thread is not working for me at all.
>
>
>
>
> --
> View this message in context: http://apache-ignite-users.70518.x6.nabble.com/enabling-log4j-read-previous-post-still-have-issues-tp9466.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.