Hi,
I have the following settings which works fine in ignite 2.0.0; however,
when I upgraded to 2.3.0, the ignite hangs during start. I am using a single
node setup in a laptop, no cluster.
IgniteConfiguration igniteConfig = new
IgniteConfiguration();
igniteConfig.setGridLogger(new Slf4jLogger(log));
// igniteConfig.setGridName(GRID_NAME);
igniteConfig.setIgniteInstanceName(GRID_NAME);
igniteConfig.setPeerClassLoadingEnabled(false);
// For a stand-alone single node cluster
igniteConfig.setDiscoverySpi(new
TcpDiscoverySpi().setIpFinder(new
TcpDiscoveryVmIpFinder(true)));
List<CacheConfiguration<?, ?>> cacheConfigs = new
ArrayList<CacheConfiguration<?, ?>>();
addCacheConfigForCommon(cacheConfigs);
addCacheConfigForAuth(cacheConfigs);
addCacheConfigForUpstreamParty(cacheConfigs);
addCacheConfigForBFSParty(cacheConfigs);
addCacheConfigForBFSLoan(cacheConfigs);
igniteConfig.setCacheConfiguration(cacheConfigs.toArray(new
CacheConfiguration[cacheConfigs.size()]));
In the log (console log in eclipse) following is printed
**********************Ignite starting....
2017-11-05 10:39:02.035 INFO 3392 --- [ main]
trationDelegate$BeanPostProcessorChecker : Bean 'igniteConfig' of type
[org.apache.ignite.configuration.IgniteConfiguration] is not eligible for
getting processed by all BeanPostProcessors (for example: not eligible for
auto-proxying)
[10:39:02] __________ ________________
[10:39:02] / _/ ___/ |/ / _/_ __/ __/
[10:39:02] _/ // (7 7 // / / / / _/
[10:39:02] /___/\___/_/|_/___/ /_/ /___/
[10:39:02]
[10:39:02] ver. 2.3.0#20171028-sha1:8add7fd5
[10:39:02] 2017 Copyright(C) Apache Software Foundation
[10:39:02]
[10:39:02] Ignite documentation: http://ignite.apache.org
[10:39:02]
[10:39:02] Quiet mode.
[10:39:02] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false
or "-v" to ignite.{sh|bat}
[10:39:02]
[10:39:02] OS: Windows 8.1 6.3 amd64
[10:39:02] VM information: Java(TM) SE Runtime Environment 1.8.0_92-b14
Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.92-b14
[10:39:02] Configured plugins:
[10:39:02] ^-- None
[10:39:02]
[10:39:06] Message queue limit is set to 0 which may lead to potential OOMEs
when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to
message queues growth on sender and receiver sides.
[10:39:06] Security status [authentication=off, tls/ssl=off]
2017-11-05 10:39:07.213 ERROR 3392 --- [ main]
: Failed to resolve default logging config file:
config/java.util.logging.properties
Console logging handler is not configured.
Thanks
Sumanta
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/