You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by bintisepaha <bi...@tudor.com> on 2016/04/19 21:28:37 UTC
ignite logging not captured in log file (log4j)
Hi,
I am using log4j for clients connecting to the grid. sample log4j file below
(file name = RGP-log4j.properties). I set this file name in VM arguments for
both these args
-Dlog4j.configuration=file:RGP-log4j.properties
-Djava.util.logging.config.file=file:RGP-log4j.properties
log4j.rootCategory=DEBUG, file
log4j.appender.file=org.apache.log4j.RollingFileAppender
log4j.appender.file.File=C:/tmp/logs/RGP.log
log4j.appender.file.threshold=DEBUG
log4j.appender.file.layout=org.apache.log4j.EnhancedPatternLayout
log4j.appender.file.layout.ConversionPattern=[%d{dd MMM yyyy HH:mm:ss.SSS
z}] [%t] %-5p (%F:%L) %m%n
log4j.appender.file.MaxFileSize=250MB
log4j.appender.file.MaxBackupIndex=200
log4j.logger.org.springframework=INFO
log4j.logger.org.springframework.jms=INFO
log4j.logger.org.apache.activemq=INFO
log4j.logger.org.apache.commons=INFO
log4j.logger.com.tudor.datagrid=INFO
log4j.logger.org.apache.ignite=DEBUG
However, on console I see the logging like below, but I do not see the below
being logged to the file.
This error happen when the grid is down and a client tries to connect to it.
since it does not get logged on the client logs, only the exception stack
trace, its hard to say which all grid nodes it tried to connect to. Is there
anyway to enable the below logging to file. I am also worried that maybe
some ignite level logging does not make it to the file, and we may be
unaware of some exceptions/errors.
[13:44:27] / _/ ___/ |/ / _/_ __/ __/
[13:44:27] _/ // (7 7 // / / / / _/
[13:44:27] /___/\___/_/|_/___/ /_/ /___/
[13:44:27]
[13:44:27] ver. 1.5.0-final#20151229-sha1:f1f8cda2
[13:44:27] 2015 Copyright(C) Apache Software Foundation
[13:44:27]
[13:44:27] Ignite documentation: http://ignite.apache.org
[13:44:27]
[13:44:27] Quiet mode.
[13:44:27] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false
or "-v" to ignite.{sh|bat}
[13:44:27]
[13:44:27] OS: Windows 7 6.1 amd64
[13:44:27] VM information: Java(TM) SE Runtime Environment 1.7.0_45-b18
Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 24.45-b08
[13:44:27] Initial heap size is 95MB (should be no less than 512MB, use
-Xms512m -Xmx512m).
[13:44:29] Configured plugins:
[13:44:29] ^-- None
[13:44:29]
[13:44:30] Security status [authentication=off, tls/ssl=off]
[13:45:54] Failed to connect to any address from IP finder (will retry to
join topology every 2 secs): [grid-tp1-dev/10.22.50.95:47500,
grid-tp1-dev/10.22.50.95:47501, grid-tp1-dev/10.22.50.95:47502,
grid-tp1-dev/10.22.50.95:47503, grid-tp1-dev/10.22.50.95:47504,
grid-tp1-dev/10.22.50.95:47505, grid-tp1-dev/10.22.50.95:47506,
grid-tp1-dev/10.22.50.95:47507, grid-tp1-dev/10.22.50.95:47508,
grid-tp1-dev/10.22.50.95:47509, grid-tp2-dev/10.22.50.249:47500,
grid-tp2-dev/10.22.50.249:47501, grid-tp2-dev/10.22.50.249:47502,
grid-tp2-dev/10.22.50.249:47503, grid-tp2-dev/10.22.50.249:47504,
grid-tp2-dev/10.22.50.249:47505, grid-tp2-dev/10.22.50.249:47506,
grid-tp2-dev/10.22.50.249:47507, grid-tp2-dev/10.22.50.249:47508,
grid-tp2-dev/10.22.50.249:47509, grid-tp3-dev/10.22.50.250:47500,
grid-tp3-dev/10.22.50.250:47501, grid-tp3-dev/10.22.50.250:47502,
grid-tp3-dev/10.22.50.250:47503, grid-tp3-dev/10.22.50.250:47504,
grid-tp3-dev/10.22.50.250:47505, grid-tp3-dev/10.22.50.250:47506,
grid-tp3-dev/10.22.50.250:47507, grid-tp3-dev/10.22.50.250:47508,
grid-tp3-dev/10.22.50.250:47509, grid-tp4-dev/10.22.50.251:47500,
grid-tp4-dev/10.22.50.251:47501, grid-tp4-dev/10.22.50.251:47502,
grid-tp4-dev/10.22.50.251:47503, grid-tp4-dev/10.22.50.251:47504,
grid-tp4-dev/10.22.50.251:47505, grid-tp4-dev/10.22.50.251:47506,
grid-tp4-dev/10.22.50.251:47507, grid-tp4-dev/10.22.50.251:47508,
grid-tp4-dev/10.22.50.251:47509]
However, thi sis what is logged in the log file
[19 Apr 2016 13:45:54.345 EDT] [main] ERROR (ReconcilePositions.java:149)
class org.apache.ignite.IgniteException: Failed to start manager:
GridManagerAdapter [enabled=true,
name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
class org.apache.ignite.IgniteException: Failed to start manager:
GridManagerAdapter [enabled=true,
name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:882)
at org.apache.ignite.Ignition.start(Ignition.java:350)
at
com.tudor.datagridI.TradingDataAccessImpl.<init>(TradingDataAccessImpl.java:95)
at
com.tudor.datagridI.DataGridClient.getTradingDataAccess(DataGridClient.java:22)
at
com.tudor.reconcile.ReconcilePositions.<init>(ReconcilePositions.java:82)
at com.tudor.reconcile.ReconcilePositions.main(ReconcilePositions.java:119)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
manager: GridManagerAdapter [enabled=true,
name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1510)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:917)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1688)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1547)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1003)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:929)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:815)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:714)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:584)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:554)
at org.apache.ignite.Ignition.start(Ignition.java:347)
... 4 more
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
SPI: TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
reconCnt=5, maxAckTimeout=30000, forceSrvMode=false,
clientReconnectDisabled=false]
at
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:258)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:660)
at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1505)
... 14 more
Caused by: class org.apache.ignite.spi.IgniteSpiException: Join process
timed out.
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.tryJoin(ClientImpl.java:1512)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1327)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
Please let me know if I can provide more information.
Thanks,
Binti
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-logging-not-captured-in-log-file-log4j-tp4334.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: ignite logging not captured in log file (log4j)
Posted by vkulichenko <va...@gmail.com>.
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-logging-not-captured-in-log-file-log4j-tp4334p4525.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: ignite logging not captured in log file (log4j)
Posted by vkulichenko <va...@gmail.com>.
Can you clarify how exactly you're going to use rolling restart?
-Val
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-logging-not-captured-in-log-file-log4j-tp4334p4526.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: ignite logging not captured in log file (log4j)
Posted by bintisepaha <bi...@tudor.com>.
I will give it one more shot on our end with several clients connected to the
grid when we attempt to restart and let you know if we saw the same effect.
Does ignite support a rolling restart methodology?
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-logging-not-captured-in-log-file-log4j-tp4334p4515.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: ignite logging not captured in log file (log4j)
Posted by vkulichenko <va...@gmail.com>.
This sounds weird. Is it possible for you to create a small shareable GitHub
project that will reproduce the issue?
-Val
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-logging-not-captured-in-log-file-log4j-tp4334p4510.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: ignite logging not captured in log file (log4j)
Posted by bintisepaha <bi...@tudor.com>.
After enabling the dependency this is what I used. Does not seem to log
anything extra than my java code in the log file.
log4j.logger.org.apache.ignite=ERROR
log4j.logger.org.apache.activemq=INFO
log4j.logger.org.apache.commons=INFO
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-logging-not-captured-in-log-file-log4j-tp4334p4505.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: ignite logging not captured in log file (log4j)
Posted by vkulichenko <va...@gmail.com>.
If adding ignite-log4j module slows you down, then you're definitely
producing too much logs. Can you double check your settings?
-Vla
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-logging-not-captured-in-log-file-log4j-tp4334p4474.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: ignite logging not captured in log file (log4j)
Posted by bintisepaha <bi...@tudor.com>.
I had set it on ERROR level.
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-logging-not-captured-in-log-file-log4j-tp4334p4467.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: ignite logging not captured in log file (log4j)
Posted by vkulichenko <va...@gmail.com>.
Hi Binti,
Did you set DEBUG level of org.apache.ignite? If so, this will produce too
much output and will definitely slow you down. You should use DEBUG only if
it's needed, and preferably for several particular categories you need DEBUG
output for.
-Val
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-logging-not-captured-in-log-file-log4j-tp4334p4466.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: ignite logging not captured in log file (log4j)
Posted by bintisepaha <bi...@tudor.com>.
Val, adding the dependency worked. The clients also started logging at root
level. We will have to modify the client log4j files to only log Error
level. Thanks, but we saw another issue now. When we tried to bring up the
grid (server nodes - ERROR level) and if old clients were already connected,
it was very slow to bring up the grid. I had to undo the change in our UAT
environment and remove the logging dependency.
Have you noticed this issue before?
Is my understanding correct, that if the ignite-log4j dependency is found on
the classpath any node will start logging ignite logs?
Thanks,
Binti
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-logging-not-captured-in-log-file-log4j-tp4334p4460.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: ignite logging not captured in log file (log4j)
Posted by vkulichenko <va...@gmail.com>.
To use Log4J, you need to enable optional ignite-log4j module (if you're
using Maven, add ignite-log4j dependency). The Log4J logging will be enabled
automatically without any configuration changes and will use the Log4J
settings used in your application. How to properly configure Log4J, please
refer to its documentation.
-Val
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-logging-not-captured-in-log-file-log4j-tp4334p4429.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: ignite logging not captured in log file (log4j)
Posted by bintisepaha <bi...@tudor.com>.
I do not have ignite-log4j enabled. I tried doing what Kamal suggested, but
it expects a datatype of type IgniteLogger.
cfg.setGridLogger(new Log4JLogger());
Should I try this
cfg.setGridLogger(new JavaLogger());
How can I set it up in the XML configuration? Which log4j xml file should I
use? Sorry I am not very familiar with log4j settings.
Thanks,
Binti
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-logging-not-captured-in-log-file-log4j-tp4334p4423.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: ignite logging not captured in log file (log4j)
Posted by Kamal C <ka...@gmail.com>.
Binti,
Have you enabled log4j logger in Ignite Configuration ?
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setGridLogger(new Log4JLogger());
--Kamal
On Thu, Apr 21, 2016 at 12:38 AM, vkulichenko <valentin.kulichenko@gmail.com
> wrote:
> Binti,
>
> This doesn't depend on whether it's a client or server. Do you have
> ignite-log4j module enabled?
>
> -Val
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/ignite-logging-not-captured-in-log-file-log4j-tp4334p4388.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
Re: ignite logging not captured in log file (log4j)
Posted by vkulichenko <va...@gmail.com>.
Binti,
This doesn't depend on whether it's a client or server. Do you have
ignite-log4j module enabled?
-Val
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-logging-not-captured-in-log-file-log4j-tp4334p4388.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: ignite logging not captured in log file (log4j)
Posted by bintisepaha <bi...@tudor.com>.
Vladimir, was your ignite node a client node? mine is a client node where i
don't see the logging as i mentioned above. Could you please send a few
lines from your log when iginte is started, so that I can check on my end if
I see those?
Thanks,
Binti
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-logging-not-captured-in-log-file-log4j-tp4334p4377.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: ignite logging not captured in log file (log4j)
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Hi Binti,
This appears to be a problem with your log4j configuration. Please
double-check it on your side. I did the following:
1) Create a file with the same content as you provided.
2) Set it through system
property: -Dlog4j.configuration=file:/c:/logger/logger.cfg
3) Run Ignite node.
Result: thousands of debug/info statements from Ignite.
Vladimir.
On Tue, Apr 19, 2016 at 10:28 PM, bintisepaha <bi...@tudor.com>
wrote:
> Hi,
>
> I am using log4j for clients connecting to the grid. sample log4j file
> below
> (file name = RGP-log4j.properties). I set this file name in VM arguments
> for
> both these args
>
> -Dlog4j.configuration=file:RGP-log4j.properties
> -Djava.util.logging.config.file=file:RGP-log4j.properties
>
> log4j.rootCategory=DEBUG, file
> log4j.appender.file=org.apache.log4j.RollingFileAppender
> log4j.appender.file.File=C:/tmp/logs/RGP.log
> log4j.appender.file.threshold=DEBUG
> log4j.appender.file.layout=org.apache.log4j.EnhancedPatternLayout
> log4j.appender.file.layout.ConversionPattern=[%d{dd MMM yyyy HH:mm:ss.SSS
> z}] [%t] %-5p (%F:%L) %m%n
> log4j.appender.file.MaxFileSize=250MB
> log4j.appender.file.MaxBackupIndex=200
> log4j.logger.org.springframework=INFO
> log4j.logger.org.springframework.jms=INFO
> log4j.logger.org.apache.activemq=INFO
> log4j.logger.org.apache.commons=INFO
> log4j.logger.com.tudor.datagrid=INFO
> log4j.logger.org.apache.ignite=DEBUG
>
> However, on console I see the logging like below, but I do not see the
> below
> being logged to the file.
> This error happen when the grid is down and a client tries to connect to
> it.
> since it does not get logged on the client logs, only the exception stack
> trace, its hard to say which all grid nodes it tried to connect to. Is
> there
> anyway to enable the below logging to file. I am also worried that maybe
> some ignite level logging does not make it to the file, and we may be
> unaware of some exceptions/errors.
>
> [13:44:27] / _/ ___/ |/ / _/_ __/ __/
> [13:44:27] _/ // (7 7 // / / / / _/
> [13:44:27] /___/\___/_/|_/___/ /_/ /___/
> [13:44:27]
> [13:44:27] ver. 1.5.0-final#20151229-sha1:f1f8cda2
> [13:44:27] 2015 Copyright(C) Apache Software Foundation
> [13:44:27]
> [13:44:27] Ignite documentation: http://ignite.apache.org
> [13:44:27]
> [13:44:27] Quiet mode.
> [13:44:27] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false
> or "-v" to ignite.{sh|bat}
> [13:44:27]
> [13:44:27] OS: Windows 7 6.1 amd64
> [13:44:27] VM information: Java(TM) SE Runtime Environment 1.7.0_45-b18
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 24.45-b08
> [13:44:27] Initial heap size is 95MB (should be no less than 512MB, use
> -Xms512m -Xmx512m).
> [13:44:29] Configured plugins:
> [13:44:29] ^-- None
> [13:44:29]
> [13:44:30] Security status [authentication=off, tls/ssl=off]
> [13:45:54] Failed to connect to any address from IP finder (will retry to
> join topology every 2 secs): [grid-tp1-dev/10.22.50.95:47500,
> grid-tp1-dev/10.22.50.95:47501, grid-tp1-dev/10.22.50.95:47502,
> grid-tp1-dev/10.22.50.95:47503, grid-tp1-dev/10.22.50.95:47504,
> grid-tp1-dev/10.22.50.95:47505, grid-tp1-dev/10.22.50.95:47506,
> grid-tp1-dev/10.22.50.95:47507, grid-tp1-dev/10.22.50.95:47508,
> grid-tp1-dev/10.22.50.95:47509, grid-tp2-dev/10.22.50.249:47500,
> grid-tp2-dev/10.22.50.249:47501, grid-tp2-dev/10.22.50.249:47502,
> grid-tp2-dev/10.22.50.249:47503, grid-tp2-dev/10.22.50.249:47504,
> grid-tp2-dev/10.22.50.249:47505, grid-tp2-dev/10.22.50.249:47506,
> grid-tp2-dev/10.22.50.249:47507, grid-tp2-dev/10.22.50.249:47508,
> grid-tp2-dev/10.22.50.249:47509, grid-tp3-dev/10.22.50.250:47500,
> grid-tp3-dev/10.22.50.250:47501, grid-tp3-dev/10.22.50.250:47502,
> grid-tp3-dev/10.22.50.250:47503, grid-tp3-dev/10.22.50.250:47504,
> grid-tp3-dev/10.22.50.250:47505, grid-tp3-dev/10.22.50.250:47506,
> grid-tp3-dev/10.22.50.250:47507, grid-tp3-dev/10.22.50.250:47508,
> grid-tp3-dev/10.22.50.250:47509, grid-tp4-dev/10.22.50.251:47500,
> grid-tp4-dev/10.22.50.251:47501, grid-tp4-dev/10.22.50.251:47502,
> grid-tp4-dev/10.22.50.251:47503, grid-tp4-dev/10.22.50.251:47504,
> grid-tp4-dev/10.22.50.251:47505, grid-tp4-dev/10.22.50.251:47506,
> grid-tp4-dev/10.22.50.251:47507, grid-tp4-dev/10.22.50.251:47508,
> grid-tp4-dev/10.22.50.251:47509]
>
> However, thi sis what is logged in the log file
> [19 Apr 2016 13:45:54.345 EDT] [main] ERROR (ReconcilePositions.java:149)
> class org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> class org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
>
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:882)
> at org.apache.ignite.Ignition.start(Ignition.java:350)
> at
>
> com.tudor.datagridI.TradingDataAccessImpl.<init>(TradingDataAccessImpl.java:95)
> at
>
> com.tudor.datagridI.DataGridClient.getTradingDataAccess(DataGridClient.java:22)
> at
> com.tudor.reconcile.ReconcilePositions.<init>(ReconcilePositions.java:82)
> at
> com.tudor.reconcile.ReconcilePositions.main(ReconcilePositions.java:119)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
> manager: GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
>
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1510)
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:917)
> at
>
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1688)
> at
>
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1547)
> at
> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1003)
> at
>
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:929)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:815)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:714)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:584)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:554)
> at org.apache.ignite.Ignition.start(Ignition.java:347)
> ... 4 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
> SPI: TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
> reconCnt=5, maxAckTimeout=30000, forceSrvMode=false,
> clientReconnectDisabled=false]
> at
>
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:258)
> at
>
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:660)
> at
>
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1505)
> ... 14 more
> Caused by: class org.apache.ignite.spi.IgniteSpiException: Join process
> timed out.
> at
>
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.tryJoin(ClientImpl.java:1512)
> at
>
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1327)
> at
> org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
>
>
> Please let me know if I can provide more information.
>
> Thanks,
> Binti
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/ignite-logging-not-captured-in-log-file-log4j-tp4334.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>