Re: IgniteCheckedException: Failed to validate cache configuration. Cache store factory is not s erializable.

[rizal123]

Is there any solutions?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

IgniteCheckedException: Failed to validate cache configuration. Cache store factory is not s erializable.

[rizal123]

Dear Master Ignite,

i have exception "IgniteCheckedException: Failed to validate cache
configuration. Cache store factory is not s
erializable.".

*Here is my code:*

/**
 * 
 */
package com.sybase365.mobiliser.custom.btpn.brand.ignite.custom.config;

import java.io.Serializable;
import java.math.BigDecimal;
import java.sql.SQLException;
import java.sql.Types;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.HashMap;
import java.util.HashSet;
import java.util.LinkedHashMap;
import java.util.Properties;

import javax.cache.configuration.Factory;
import javax.sql.DataSource;

import org.apache.ignite.cache.CacheAtomicityMode;
import org.apache.ignite.cache.CacheMode;
import org.apache.ignite.cache.QueryEntity;
import org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStoreFactory;
import org.apache.ignite.cache.store.jdbc.JdbcType;
import org.apache.ignite.cache.store.jdbc.JdbcTypeField;
import org.apache.ignite.cache.store.jdbc.dialect.OracleDialect;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
import
org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;

import oracle.jdbc.pool.OracleDataSource;

/**
 * @author 17054072
 *
 */
public class ClientConfigurationFactory implements Serializable{

/**
 * 
 */
private static final long serialVersionUID = 4067320674189197181L;

private static final Properties props = new Properties();
/*static {

try {
InputStream in =
IgniteConfiguration.class.getClassLoader().getResourceAsStream("META-INF/spring/secret.properties");
props.load(in);
}
catch (Exception ignored) {
// No-op.
}
}*/

public static class DataSources {
  public static final OracleDataSource INSTANCE_dsOracle_Btpndev =
createdsOracle_Btpndev();

private static OracleDataSource createdsOracle_Btpndev() {
try {
OracleDataSource dsOracle_Btpndev = new OracleDataSource();

   
dsOracle_Btpndev.setURL("jdbc:oracle:thin:@10.1.92.63:1521:WOWDEV");
dsOracle_Btpndev.setUser("BTPN_BM_02");
dsOracle_Btpndev.setPassword("password");

   
/*dsOracle_Btpndev.setURL(props.getProperty("dsOracle_Btpndev.jdbc.url"));
   
dsOracle_Btpndev.setUser(props.getProperty("dsOracle_Btpndev.jdbc.username"));
   
dsOracle_Btpndev.setPassword(props.getProperty("dsOracle_Btpndev.jdbc.password"));*/

return dsOracle_Btpndev;
}
catch (SQLException ex) {
throw new Error(ex);
}
}
}

public static IgniteConfiguration createConfiguration() throws Exception
{
IgniteConfiguration cfg = new IgniteConfiguration();

cfg.setClientMode(true);
cfg.setIgniteInstanceName("BrandCluster");

TcpDiscoverySpi discovery = new TcpDiscoverySpi();

TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder();

ipFinder.setAddresses(Arrays.asList("10.1.92.137:47500")); 

discovery.setIpFinder(ipFinder);

cfg.setDiscoverySpi(discovery);

cfg.setCacheConfiguration(cacheSequenceCache());

return cfg;
}

public static CacheConfiguration cacheSequenceCache() throws Exception {
CacheConfiguration ccfg = new CacheConfiguration();

ccfg.setName("SequenceCache");
ccfg.setCacheMode(CacheMode.PARTITIONED);
ccfg.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);

CacheJdbcPojoStoreFactory cacheStoreFactory = new
CacheJdbcPojoStoreFactory();

cacheStoreFactory.setDataSourceFactory(new Factory() {
/**
 * 
 */
private static final long serialVersionUID = 
-8028910004810254541L;

/** {@inheritDoc} **/
public DataSource create() {
return DataSources.INSTANCE_dsOracle_Btpndev;
};
});

cacheStoreFactory.setDialect(new OracleDialect());

cacheStoreFactory.setTypes(jdbcTypeSequence(ccfg.getName()));

ccfg.setCacheStoreFactory(cacheStoreFactory);

ccfg.setReadThrough(true);
ccfg.setWriteThrough(true);
ccfg.setSqlSchema("PUBLIC");

ArrayList qryEntities = new ArrayList();

QueryEntity qryEntity = new QueryEntity();

qryEntity.setKeyType("java.lang.String");
qryEntity.setValueType("com.btpn.rizal.khaerul.model.Sequence");
qryEntity.setTableName("SEQUENCE");
qryEntity.setKeyFieldName("seqName");

HashSet keyFields = new HashSet();

keyFields.add("seqName");

qryEntity.setKeyFields(keyFields);

Re: C# client too slow to connect.

[Pavel Tupitsyn]

Hi,

Have you tried Thin Client mode?
https://apacheignite-net.readme.io/docs/thin-client

Pavel

On Tue, May 22, 2018 at 2:13 PM, F. D.  wrote:

> Hi Igor,
>
> it's almost the same. I'm considering startup + connection. I'm using
> Ignite 2.4.  The node excel is only client, and I have only a server node
> on an other machine in my organization, and I cannot see particular
> activity of cpu or network.
>
> Thanks,
>F.D.
>
> On Tue, May 22, 2018 at 11:00 AM Igor Sapego  wrote:
>
>> Hi,
>>
>> Try using "TcpDiscoveryStaticIpFinder" instead of
>> "TcpDiscoveryMulticastIpFinder".
>>
>> Does it take 1 min for connection only or for start up + connection?
>>
>> Best Regards,
>> Igor
>>
>> On Tue, May 22, 2018 at 11:45 AM, F. D.  wrote:
>>
>>> Hi,
>>>
>>> I'm trying to use Ignite to develop an internal system of data
>>> contribution. To do this, I'm launching Ignite inside Excel, and I'm using
>>> the C# binding.
>>>
>>> When try to connect it consumes a lot of time (~1 min.),  this is my
>>> simple app.config:
>>>
>>> 
>>> 
>>>
>>>   >> type="Apache.Ignite.Core.IgniteConfigurationSection,
>>> Apache.Ignite.Core"/>
>>>
>>>
>>>
>>>
>>>
>>>
>>>http://ignite.apache.org/schema/dotnet/
>>> IgniteConfigurationSection" localhost="10.200.30.100"
>>> peerAssemblyLoadingMode="CurrentAppDomain" gridName="IMIStreamer">
>>>   
>>>  
>>>   
>>>
>>>   
>>>
>>>   
>>>  
>>> 
>>>10.200.20.90:47500..47509
>>> 
>>>  
>>>   
>>>
>>>
>>>
>>>   
>>>
>>>
>>> 
>>>
>>> Is it possibile to reduce this time of connection?
>>> I've tried to use the thin client, but in this client there's no
>>> continuous query (and need it, because I want to be reactive when a cache
>>> change).
>>>
>>> Thanks in advance for your help,
>>>F.D.
>>>
>>>
>>

RE: Dependencies required to use ignite in embedded mode?

[Stanislav Lukyanov]

As you can see in the log, there is an exception
--
2018-05-23 00:41:58,863 ERROR [org.apache.ignite.logger.log4j.Log4JLogger]
Got exception while starting (will rollback startup routine).
class org.apache.ignite.IgniteException: Failed to load class names
properties file packaged with ignite binaries
[file=META-INF/classnames.properties,
ldr=com.suntecgroup.tbms.container.deploy.loader.RuntimeClassLoader@399c656d] 
--

ignite-core.jar contains a file META-INF/classnames.properties.
It looks like your custom class loader 
(com.suntecgroup.tbms.container.deploy.loader.RuntimeClassLoader)
fails to find this resource.
Check your class loader code and configuration, the issue should be there.

Stan

From: the_palakkaran
Sent: 22 мая 2018 г. 22:17
To: user@ignite.apache.org
Subject: RE: Dependencies required to use ignite in embedded mode?

@Stanislav

*This is my configuration:
*
IgniteConfiguration igniteConfig = new IgniteConfiguration();
DataStorageConfiguration dataStorageCfg = new
DataStorageConfiguration();
DataRegionConfiguration dataRegionCfg = new DataRegionConfiguration();
igniteConfig.setIgniteInstanceName("ignite");
igniteConfig.setPeerClassLoadingEnabled(true);
TcpDiscoverySpi spi = new TcpDiscoverySpi();
TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder();
String hosts[] = {"127.0.0.1"};
ipFinder.setAddresses(Arrays.asList(hosts));
spi.setIpFinder(ipFinder);
igniteConfig.setDiscoverySpi(spi);
dataRegionCfg.setName("CacheDataRegion");
dataRegionCfg.setInitialSize(2L * 1024 * 1024 * 1024);
dataRegionCfg.setMaxSize(10L*1024*1024*1024);
dataRegionCfg.setPersistenceEnabled(true);
dataStorageCfg.setDataRegionConfigurations(dataRegionCfg);
processingAttributesCacheConfig = new
CacheConfiguration<>("processingAttributesCache");
   
processingAttributesCacheConfig.setIndexedTypes(ProcessingAttributesKey.class, 
ProcessingAttributes.class);
processingAttributesCacheConfig.setReadThrough(true);
processingAttributesCacheConfig.setAtomicityMode(TRANSACTIONAL);
processingAttributesCacheConfig.setCacheMode(CacheMode.PARTITIONED);
ProcessingAttributesFactory processingAttributesFactory = new
ProcessingAttributesFactory();
igniteConfig.setDataStorageConfiguration(dataStorageCfg);
igniteConfig.setCacheConfiguration(processingAttributesCacheConfig);
IgniteLogger log = null;
try {
log = new Log4JLogger();
} catch (Exception e) {
}
igniteConfig.setGridLogger(log);  
ignite = Ignition.start(igniteConfig);
ignite.active(true);


*And here's the log :*

2018-05-23 00:41:58,638 INFO  [org.apache.ignite.logger.log4j.Log4JLogger] 

>>>__    
>>>   /  _/ ___/ |/ /  _/_  __/ __/  
>>>  _/ // (7 7// /  / / / _/
>>> /___/\___/_/|_/___/ /_/ /___/   
>>> 
>>> ver. 2.3.0#20171028-sha1:8add7fd5
>>> 2017 Copyright(C) Apache Software Foundation
>>> 
>>> Ignite documentation: http://ignite.apache.org

2018-05-23 00:41:58,638 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
Config URL: n/a
2018-05-23 00:41:58,638 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
Daemon mode: off
2018-05-23 00:41:58,639 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
OS: Linux 3.8.13-68.3.4.el6uek.x86_64 amd64
2018-05-23 00:41:58,639 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
OS user: hsbc
2018-05-23 00:41:58,639 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
PID: 36975
2018-05-23 00:41:58,639 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
Language runtime: Java Platform API Specification ver. 1.8
2018-05-23 00:41:58,640 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
VM information: Java(TM) SE Runtime Environment 1.8.0_51-b16 Oracle
Corporation Java HotSpot(TM) 64-Bit Server VM 25.51-b03
2018-05-23 00:41:58,640 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
VM total memory: 10.0GB
2018-05-23 00:41:58,640 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
Remote Management [restart: off, REST: on, JMX (remote: off)]
2018-05-23 00:41:58,672 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
IGNITE_HOME=/home/hsbc/HSBC_RCM_DEV_PC/Instance1
2018-05-23 00:41:58,672 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
VM arguments: [-Xms2G, -Xmx10G, -Xss1024k, -XX:PermSize=1500M,
-XX:MaxPermSize=1800M, -XX:NewSize=209715K, -XX:MaxNewSize=209715K,
-XX:SurvivorRatio=8, -XX:MaxTenuringThreshold=6, -XX:+UseParallelOldGC,
-XX:ParallelCMSThreads=2, -XX:ParallelGCThreads=6,
-XX:-UseAdaptiveSizePolicy, -XX:+CMSClassUnloadingEnabled,
-XX:+UseStringCache, -XX:+OptimizeStringConcat, -XX:+UseFastAccessorMethods,
-XX:+AggressiveOpts, -Djava.net.preferIPv4Stack=true,
-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl,
-Dcom.atomikos.icatch.no_file=true,
-Dcom.atomikos.icatch.service=com.atomikos.icatch.standalone.UserTransactionServiceFactory,

Re: Support for polymorphic SQL Queries

[ttlir]

Yes, all models are stored in the same cache.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Ignite equivalent of @GridUserResource

[Stanislav Lukyanov]

Well, with such a big leap between versions I’d say whatever works is good :)

Being nervous about the jar hell is always wise.
Going through the dependencies is probably the most straightforward option, 
unfortunately.
You could try to reduce the number of Ignite modules you’re using - optional 
ones are not picked up by default 
and ignite-core has almost no dependencies.
Or you could build your servers as regular Java applications, with a Main class 
instead of ignite.sh runner.
Then you’ll declare the Ignite modules you need as dependencies, and with some 
Maven kung-fu you should be able
to identify (and hopefully fix) conflicts at build-time.

Thanks,
Stan

From: chuston
Sent: 18 мая 2018 г. 4:04
To: user@ignite.apache.org
Subject: Re: Ignite equivalent of @GridUserResource

I'm also reviving a mothballed GridGain system that used a @GridUserResource
- moving from Java 6/GridGain 3 to Java 1.8 / Ignite 2.4.0+ 

To replace it, I'm doing the following: 
- Use a LifeCycleBean that populates the nodeLocalMap before startup. 
   - the objects placed in the nodeLocalMap are factories for accessing
other reference objects needed by the jobs (Company, Document, History
instances) 
- Copy the jar with the LifeCycleBean and all of it's dependencies into a
subdirectory of ${IGNITE_HOME}/lib 
   - Since the factories use web services, databases, etc - there are a lot
of dependencies 
- Side note: I also have a partitioned cache warming step so need the cache
key-value classes and loader dependencies too 

Two questions: 
1) Is there a better way to do it? 
2) I'm nervous that if I just do something like "mvn
dependency:copy-dependencies" that I will be putting jars into the lib
directory that contain classes used by ignite and inviting weird class cast
exceptions / class loader issues. I'm not at all excited by trying to sort
through which jars I depend on but are already present in the ignite
distribution / optional modules etc. Is there a magic reason not to worry
about this? Is there a better way to approach it? 

Thanks, 
-- Chris 



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Dependencies required to use ignite in embedded mode?

[the_palakkaran]

@Stanislav

*This is my configuration:
*
IgniteConfiguration igniteConfig = new IgniteConfiguration();
DataStorageConfiguration dataStorageCfg = new
DataStorageConfiguration();
DataRegionConfiguration dataRegionCfg = new DataRegionConfiguration();
igniteConfig.setIgniteInstanceName("ignite");
igniteConfig.setPeerClassLoadingEnabled(true);
TcpDiscoverySpi spi = new TcpDiscoverySpi();
TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder();
String hosts[] = {"127.0.0.1"};
ipFinder.setAddresses(Arrays.asList(hosts));
spi.setIpFinder(ipFinder);
igniteConfig.setDiscoverySpi(spi);
dataRegionCfg.setName("CacheDataRegion");
dataRegionCfg.setInitialSize(2L * 1024 * 1024 * 1024);
dataRegionCfg.setMaxSize(10L*1024*1024*1024);
dataRegionCfg.setPersistenceEnabled(true);
dataStorageCfg.setDataRegionConfigurations(dataRegionCfg);
processingAttributesCacheConfig = new
CacheConfiguration<>("processingAttributesCache");
   
processingAttributesCacheConfig.setIndexedTypes(ProcessingAttributesKey.class, 
ProcessingAttributes.class);
processingAttributesCacheConfig.setReadThrough(true);
processingAttributesCacheConfig.setAtomicityMode(TRANSACTIONAL);
processingAttributesCacheConfig.setCacheMode(CacheMode.PARTITIONED);
ProcessingAttributesFactory processingAttributesFactory = new
ProcessingAttributesFactory();
igniteConfig.setDataStorageConfiguration(dataStorageCfg);
igniteConfig.setCacheConfiguration(processingAttributesCacheConfig);
IgniteLogger log = null;
try {
log = new Log4JLogger();
} catch (Exception e) {
}
igniteConfig.setGridLogger(log);  
ignite = Ignition.start(igniteConfig);
ignite.active(true);


*And here's the log :*

2018-05-23 00:41:58,638 INFO  [org.apache.ignite.logger.log4j.Log4JLogger] 

>>>__    
>>>   /  _/ ___/ |/ /  _/_  __/ __/  
>>>  _/ // (7 7// /  / / / _/
>>> /___/\___/_/|_/___/ /_/ /___/   
>>> 
>>> ver. 2.3.0#20171028-sha1:8add7fd5
>>> 2017 Copyright(C) Apache Software Foundation
>>> 
>>> Ignite documentation: http://ignite.apache.org

2018-05-23 00:41:58,638 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
Config URL: n/a
2018-05-23 00:41:58,638 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
Daemon mode: off
2018-05-23 00:41:58,639 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
OS: Linux 3.8.13-68.3.4.el6uek.x86_64 amd64
2018-05-23 00:41:58,639 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
OS user: hsbc
2018-05-23 00:41:58,639 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
PID: 36975
2018-05-23 00:41:58,639 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
Language runtime: Java Platform API Specification ver. 1.8
2018-05-23 00:41:58,640 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
VM information: Java(TM) SE Runtime Environment 1.8.0_51-b16 Oracle
Corporation Java HotSpot(TM) 64-Bit Server VM 25.51-b03
2018-05-23 00:41:58,640 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
VM total memory: 10.0GB
2018-05-23 00:41:58,640 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
Remote Management [restart: off, REST: on, JMX (remote: off)]
2018-05-23 00:41:58,672 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
IGNITE_HOME=/home/hsbc/HSBC_RCM_DEV_PC/Instance1
2018-05-23 00:41:58,672 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
VM arguments: [-Xms2G, -Xmx10G, -Xss1024k, -XX:PermSize=1500M,
-XX:MaxPermSize=1800M, -XX:NewSize=209715K, -XX:MaxNewSize=209715K,
-XX:SurvivorRatio=8, -XX:MaxTenuringThreshold=6, -XX:+UseParallelOldGC,
-XX:ParallelCMSThreads=2, -XX:ParallelGCThreads=6,
-XX:-UseAdaptiveSizePolicy, -XX:+CMSClassUnloadingEnabled,
-XX:+UseStringCache, -XX:+OptimizeStringConcat, -XX:+UseFastAccessorMethods,
-XX:+AggressiveOpts, -Djava.net.preferIPv4Stack=true,
-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl,
-Dcom.atomikos.icatch.no_file=true,
-Dcom.atomikos.icatch.service=com.atomikos.icatch.standalone.UserTransactionServiceFactory,
-Djavax.net.ssl.trustStore=/home/Final_8AG_PC/Instance1/pot/web/ecp_sscert/pctruststore,
-Djavax.net.ssl.trustStorePassword=suntec,
-Doracle.jdbc.J2EE13Compliant=true, -Dbind.address=127.0.0.1, -Xdebug,
-Xrunjdwp:server=y,transport=dt_socket,address=8087,suspend=n]
2018-05-23 00:41:58,673 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
System cache's DataRegion size is configured to 40 MB. Use
DataStorageConfiguration.systemCacheMemorySize property to change the
setting.
2018-05-23 00:41:58,673 INFO  [org.apache.ignite.logger.log4j.Log4JLogger]
Configured caches [in 'sysMemPlc' dataRegion: ['ignite-sys-cache'], in
'CacheDataRegion' dataRegion: ['processingAttributesCache']
2018-05-23 00:41:58,673 WARN  [org.apache.ignite.logger.log4j.Log4JLogger]
Peer class loading is enabled (disable it in production for performance and
deployment consistency reasons)
2018-05-23 00:41:58,777 INFO  

RE: SQL TX: Reads should see own's previous writes

[Stanislav Lukyanov]

This fix is a part of the transactional SQL feature 
(https://issues.apache.org/jira/browse/IGNITE-4191) which is not fully 
implemented yet.
I believe it is pretty much impossible to pick this commit separately and apply 
to a previous Ignite version.

Stan

From: kotamrajuyashasvi
Sent: 22 мая 2018 г. 8:45
To: user@ignite.apache.org
Subject: SQL TX: Reads should see own's previous writes

Hi

I found the ticket: https://issues.apache.org/jira/browse/IGNITE-6938,
related to the feature of Reads should see own's previous writes with in the
same transaction, and its status says its resolved. I would like to know if
this feature can be applied like a patch. Or still it has some other
dependencies which are not yet implemented.

If this feature can be applied where can I find the code changes done for
that ?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: please explain this.....

[Denis Magda]

It doesn't collect any stats, check up the source of the page:
https://ignite.apache.org/latest

It's a plain text file that includes the recent version only. That's it, no
more than that.

--
Denis

On Tue, May 22, 2018 at 10:27 AM, Paul Anderson 
wrote:

> It should not be on by default... It serves no purpose other than data
> collection
>
> On Tue, 22 May 2018, 19:23 Ilya Kasnacheev, 
> wrote:
>
>> Hello Paul!
>>
>> You can just run Apache Ignite with IGNITE_UPDATE_NOTIFIER system
>> property or environment variable set to false.
>>
>> As in, -DIGNITE_UPDATE_NOTIFIER=false.
>>
>> This should completely prevent Apache Ignite from contacting this server.
>>
>> Regards,
>>
>> --
>> Ilya Kasnacheev
>>
>> 2018-05-22 16:19 GMT+03:00 Paul Anderson :
>>
>>> I'm sorry... contacting Microsoft identifying who's using what is
>>> unacceptable. Ignite is a significant piece of software, used by
>>> organisations and useless without a significant numbers of developers and a
>>> particular need. I is not Microsoft Office Home Edition, we are not
>>> consumers.
>>>
>>
>>

RE: Dependencies required to use ignite in embedded mode?

[Stanislav Lukyanov]

Hi,

Could you please start with -DIGNITE_QUIET=false and share the logs and the 
configuration?

In general, Ignite can start with just ignite-core.
A couple of modules that are also used very often are:
- ignite-indexing to use SqlQuery and SqlFieldQuery
- ignite-spring to use XML-based Ignite configs.

Thanks,
Stan

From: the_palakkaran
Sent: 22 мая 2018 г. 21:22
To: user@ignite.apache.org
Subject: Dependencies required to use ignite in embedded mode?

Hi,

Can someone help me with the dependencies needed for starting ignite in
embedded mode ? (Oracle DB).

I miss something so that my ignition does not start and hence cache is not
getting loaded, but no error thrown from Ignite.

Please help.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Dependencies required to use ignite in embedded mode?

[the_palakkaran]

Hi,

Can someone help me with the dependencies needed for starting ignite in
embedded mode ? (Oracle DB).

I miss something so that my ignition does not start and hence cache is not
getting loaded, but no error thrown from Ignite.

Please help.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: please explain this.....

[Paul Anderson]

It should not be on by default... It serves no purpose other than data
collection

On Tue, 22 May 2018, 19:23 Ilya Kasnacheev, 
wrote:

> Hello Paul!
>
> You can just run Apache Ignite with IGNITE_UPDATE_NOTIFIER system
> property or environment variable set to false.
>
> As in, -DIGNITE_UPDATE_NOTIFIER=false.
>
> This should completely prevent Apache Ignite from contacting this server.
>
> Regards,
>
> --
> Ilya Kasnacheev
>
> 2018-05-22 16:19 GMT+03:00 Paul Anderson :
>
>> I'm sorry... contacting Microsoft identifying who's using what is
>> unacceptable. Ignite is a significant piece of software, used by
>> organisations and useless without a significant numbers of developers and a
>> particular need. I is not Microsoft Office Home Edition, we are not
>> consumers.
>>
>
>

Re: please explain this.....

[Ilya Kasnacheev]

Hello Paul!

You can just run Apache Ignite with IGNITE_UPDATE_NOTIFIER system property
or environment variable set to false.

As in, -DIGNITE_UPDATE_NOTIFIER=false.

This should completely prevent Apache Ignite from contacting this server.

Regards,

-- 
Ilya Kasnacheev

2018-05-22 16:19 GMT+03:00 Paul Anderson :

> I'm sorry... contacting Microsoft identifying who's using what is
> unacceptable. Ignite is a significant piece of software, used by
> organisations and useless without a significant numbers of developers and a
> particular need. I is not Microsoft Office Home Edition, we are not
> consumers.
>

Re: Ignite 2.4.0 ( dump data from mysql)

[Ilya Kasnacheev]

Hello!

You can't use stand-alone distribution of Apache Ignite to run
WebConsole-generated projects, which are managed by Maven.

There should be a main class somewhere in new1, this is what you should be
running. Possibly with mvn clean install; mvn exec:java
-Dexec.mainClass=packaged.path.to.ServerNodeMain

They have different classpath. Stand-alone Apache Ignite has one classpath
but your WebConsole project has a different one.

Regards,

-- 
Ilya Kasnacheev

2018-05-21 12:20 GMT+03:00 anupam_4881 :

> Hello ,
>
> yes secret.properties is under src/main/resources/
> I am using xml ( not java )  to start & dump data. I copy complete  project
> named "new1" under config folder and start  as below. Kindly check and
> let me know what wrong i am doing.
> Will appreciate you help as i am struggling from last two week on same.
>
> [root@RND resources]# pwd
> /opt/apache-ignite-fabric-2.4.0-bin/config/*new1*/src/main/resources
> [root@RND resources]# ls
> META-INF * secret.properties*
> [root@RND resources]# cd /opt/apache-ignite-fabric-2.4.0-bin/bin/
> [root@RND bin]#  ./ignite.sh
> ../config/new1/src/main/resources/META-INF/*new1-server.xml*
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Client IgniteStreamer broken after cluster restart

[Ilya Kasnacheev]

Hello!

What an awesome perdu monocle have you found! I have created a ticket
against Apache Ignite JIRA:
https://issues.apache.org/jira/browse/IGNITE-8564

Regards,

-- 
Ilya Kasnacheev

2018-05-18 22:30 GMT+03:00 npordash :

> Sorry about that! Trying again.
>
> final BiFunction cfg = (name, client) 
> -> {
> final IgniteConfiguration c = new IgniteConfiguration();
> final TcpDiscoverySpi d = new TcpDiscoverySpi();
> d.setIpFinder(new TcpDiscoverySharedFsIpFinder());
> c.setDiscoverySpi(d);
> c.setIgniteInstanceName(name);
> c.setClientMode(client);
> c.setCacheConfiguration(new CacheConfiguration("test"));
> return c;
> };
>
> Ignite server = null;
> Ignite client = null;
> try {
>
> server = Ignition.start(cfg.apply("server", false));
> client = Ignition.start(cfg.apply("client", true));
>
> try (IgniteDataStreamer streamer = 
> client.dataStreamer("test")) {
> streamer.allowOverwrite(true);
> streamer.addData("k1", "v1");
> }
>
> TimeUnit.SECONDS.sleep(1);
> server.close();
> TimeUnit.SECONDS.sleep(1);
> server = Ignition.start(cfg.apply("server", false));
> TimeUnit.SECONDS.sleep(1);
>
> try (IgniteDataStreamer streamer = 
> client.dataStreamer("test")) {
> streamer.allowOverwrite(true);
> streamer.addData("k2", "v2");
> }
>
> } finally {
> if (client != null) {
> client.close();
> }
> if (server != null) {
> server.close();
> }
> }
>
>
> --
> Sent from the Apache Ignite Users mailing list archive
>  at Nabble.com.
>

Re: please explain this.....

[Paul Anderson]

I'm sorry... contacting Microsoft identifying who's using what is
unacceptable. Ignite is a significant piece of software, used by
organisations and useless without a significant numbers of developers and a
particular need. I is not Microsoft Office Home Edition, we are not
consumers.

Re: please explain this.....

[Evgenii Zhuravlev]

Everyone know which version they use, but not all know which version is
latest. Update checking is usual practice for software.

Evgenii

2018-05-22 16:08 GMT+03:00 Paul Anderson :

> It's stats collection, anyone using apache ignite knows very well which
> version they are using it should be off by default
>
> On Tue, May 22, 2018 at 2:54 PM, Evgenii Zhuravlev <
> e.zhuravlev...@gmail.com> wrote:
>
>> It's an update notifier, which checks apache.org for new versions of
>> Ignite.
>>
>> Evgenii
>>
>> 2018-05-22 15:22 GMT+03:00 Paul Anderson :
>>
>>> ... could someone tell my why Ignite on startup established a connection
>>> to a Microsoft IP address?
>>>
>>> (hosted apache.org server)
>>>
>>> java23892 root  118u IPv6 259029  0t0  TCP
>>> 192.168.43.15:44664->40.79.78.1:443 (ESTABLISHED)
>>>
>>> is this ignite itself of a dependant library?
>>>
>>
>>
>

Re: please explain this.....

[Paul Anderson]

It's stats collection, anyone using apache ignite knows very well which
version they are using it should be off by default

On Tue, May 22, 2018 at 2:54 PM, Evgenii Zhuravlev  wrote:

> It's an update notifier, which checks apache.org for new versions of
> Ignite.
>
> Evgenii
>
> 2018-05-22 15:22 GMT+03:00 Paul Anderson :
>
>> ... could someone tell my why Ignite on startup established a connection
>> to a Microsoft IP address?
>>
>> (hosted apache.org server)
>>
>> java23892 root  118u IPv6 259029  0t0  TCP
>> 192.168.43.15:44664->40.79.78.1:443 (ESTABLISHED)
>>
>> is this ignite itself of a dependant library?
>>
>
>

Re: please explain this.....

[Evgenii Zhuravlev]

It's an update notifier, which checks apache.org for new versions of Ignite.

Evgenii

2018-05-22 15:22 GMT+03:00 Paul Anderson :

> ... could someone tell my why Ignite on startup established a connection
> to a Microsoft IP address?
>
> (hosted apache.org server)
>
> java23892 root  118u IPv6 259029  0t0  TCP
> 192.168.43.15:44664->40.79.78.1:443 (ESTABLISHED)
>
> is this ignite itself of a dependant library?
>

Re: Turning off update checks...

[Evgenii Zhuravlev]

Set this environment/system property to “false”

ignite.update.notifier.enabled.by.default


2018-05-22 15:45 GMT+03:00 Paul Anderson :

>
>
>
>
> found the connection to microsoft.. dont want this to happen
>
> "upd-ver-checker" #86 daemon prio=5 os_prio=0 tid=0x7fee08c1f000
> nid=0x72e2 runnable [0x7fedcce04000]
>   java.lang.Thread.State: RUNNABLE
>at java.net.PlainSocketImpl.socketConnect(Native Method)
>at java.net.AbstractPlainSocketImpl.doConnect(
> AbstractPlainSocketImpl.java:350)
>- locked <0xebd3d160> (a java.net.SocksSocketImpl)
>at java.net.AbstractPlainSocketImpl.connectToAddress(
> AbstractPlainSocketImpl.java:206)
>at java.net.AbstractPlainSocketImpl.connect(
> AbstractPlainSocketImpl.java:188)
>at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
>at java.net.Socket.connect(Socket.java:589)
>at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:673)
>at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
>at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
>at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
>- locked <0xebd3cc28> (a 
> sun.net.www.protocol.https.HttpsClient)
>
>at sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:264)
>
>at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:367)
>
>at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnec
> tion.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191)
>at 
> sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156)
>
>at 
> sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050)
>
>at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnec
> tion.connect(AbstractDelegateHttpsURLConnection.java:177)
>at 
> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564)
>
>- locked <0xebd3a458> (a 
> sun.net.www.protocol.https.DelegateHttpsURLConnection)
>
>at 
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
>
>- locked <0xebd3a458> (a 
> sun.net.www.protocol.https.DelegateHttpsURLConnection)
>
>at sun.net.www.protocol.https.HttpsURLConnectionImpl.
> getInputStream(HttpsURLConnectionImpl.java:263)
>- locked <0xc094d5e8> (a 
> sun.net.www.protocol.https.HttpsURLConnectionImpl)
>
>at org.apache.ignite.internal.processors.cluster.
> HttpIgniteUpdatesChecker.getUpdates(HttpIgniteUpdatesChecker.java:65)
>at org.apache.ignite.internal.processors.cluster.
> GridUpdateNotifier$UpdateChecker.body(GridUpdateNotifier.java:268)
>at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>
>at org.apache.ignite.internal.processors.cluster.
> GridUpdateNotifier$1.run(GridUpdateNotifier.java:113)
>at java.lang.Thread.run(Thread.java:748)
>
>
>
>

Turning off update checks...

[Paul Anderson]

found the connection to microsoft.. dont want this to happen

"upd-ver-checker" #86 daemon prio=5 os_prio=0 tid=0x7fee08c1f000
nid=0x72e2 runnable [0x7fedcce04000]
  java.lang.Thread.State: RUNNABLE
   at java.net.PlainSocketImpl.socketConnect(Native Method)
   at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)

   - locked <0xebd3d160> (a java.net.SocksSocketImpl)
   at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)

   at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
   at java.net.Socket.connect(Socket.java:589)
   at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:673)
   at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
   at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
   at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
   - locked <0xebd3cc28> (a
sun.net.www.protocol.https.HttpsClient)
   at
sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:264)
   at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:367)
   at
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191)

   at
sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156)

   at
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050)

   at
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177)

   at
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564)

   - locked <0xebd3a458> (a
sun.net.www.protocol.https.DelegateHttpsURLConnection)
   at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)

   - locked <0xebd3a458> (a
sun.net.www.protocol.https.DelegateHttpsURLConnection)
   at
sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:263)

   - locked <0xc094d5e8> (a
sun.net.www.protocol.https.HttpsURLConnectionImpl)
   at
org.apache.ignite.internal.processors.cluster.HttpIgniteUpdatesChecker.getUpdates(HttpIgniteUpdatesChecker.java:65)

   at
org.apache.ignite.internal.processors.cluster.GridUpdateNotifier$UpdateChecker.body(GridUpdateNotifier.java:268)

   at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
   at
org.apache.ignite.internal.processors.cluster.GridUpdateNotifier$1.run(GridUpdateNotifier.java:113)

   at java.lang.Thread.run(Thread.java:748)

please explain this.....

[Paul Anderson]

... could someone tell my why Ignite on startup established a connection to
a Microsoft IP address?

(hosted apache.org server)

java23892 root  118u IPv6 259029  0t0  TCP
192.168.43.15:44664->40.79.78.1:443 (ESTABLISHED)

is this ignite itself of a dependant library?

Re: C# client too slow to connect.

[F. D.]

Hi Igor,

it's almost the same. I'm considering startup + connection. I'm using
Ignite 2.4.  The node excel is only client, and I have only a server node
on an other machine in my organization, and I cannot see particular
activity of cpu or network.

Thanks,
   F.D.

On Tue, May 22, 2018 at 11:00 AM Igor Sapego  wrote:

> Hi,
>
> Try using "TcpDiscoveryStaticIpFinder" instead of
> "TcpDiscoveryMulticastIpFinder".
>
> Does it take 1 min for connection only or for start up + connection?
>
> Best Regards,
> Igor
>
> On Tue, May 22, 2018 at 11:45 AM, F. D.  wrote:
>
>> Hi,
>>
>> I'm trying to use Ignite to develop an internal system of data
>> contribution. To do this, I'm launching Ignite inside Excel, and I'm using
>> the C# binding.
>>
>> When try to connect it consumes a lot of time (~1 min.),  this is my
>> simple app.config:
>>
>> 
>> 
>>
>>   > type="Apache.Ignite.Core.IgniteConfigurationSection, Apache.Ignite.Core"/>
>>
>>
>>
>>
>>
>>
>>http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection;
>> localhost="10.200.30.100" peerAssemblyLoadingMode="CurrentAppDomain"
>> gridName="IMIStreamer">
>>   
>>  
>>   
>>
>>   
>>
>>   
>>  
>> 
>>10.200.20.90:47500..47509
>> 
>>  
>>   
>>
>>
>>
>>   > sku=".NETFramework,Version=v4.5.2"/>
>>
>>
>> 
>>
>> Is it possibile to reduce this time of connection?
>> I've tried to use the thin client, but in this client there's no
>> continuous query (and need it, because I want to be reactive when a cache
>> change).
>>
>> Thanks in advance for your help,
>>F.D.
>>
>>
>

Re: Dose Iginte implement lock and latch in transaction，and where is the code ？

[Stanislav Lukyanov]

Let's keep the discussion in the newer thread:
http://apache-ignite-users.70518.x6.nabble.com/How-dose-ignite-implement-concurrent-control-in-transaction-tt21580.html

Thanks,
Stan



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Dose Iginte implement lock and latch in transaction，and where is the code ？

[Denis Mekhanikov]

Duplicate thread:
http://apache-ignite-users.70518.x6.nabble.com/How-dose-ignite-implement-concurrent-control-in-transaction-td21580.html

вт, 22 мая 2018 г. в 11:32, Igor Sapego :

> Re-sending to dev-list.
>
> Best Regards,
> Igor
>
> On Sat, May 19, 2018 at 6:02 PM, zhouxy1123  wrote:
>
> > Dose Iginte implement lock and latch in transaction，and where is the
> code ？
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
> >
>

Re: control.bat authentication support

[Alexey Kuznetsov]

Stan,

I think that we should add support for authentication in control.sh
One more tool will confuse Ignite users.

On Tue, May 22, 2018 at 3:53 AM, Stanislav Lukyanov 
wrote:

> Hi,
>
>
>
> Ignite doesn’t provide built-in support for authentication, so the
> built-in control.bat/sh also don’t have stubs for that.
>
> So yes, I guess you need to write your own tool.
>
>
>
> A tool like that would be pretty simple though – just start a client node,
> parse command line arguments and
>
> map them to the methods of the ignite.cluster().
>
>
>
> Stan
>
>
>
> *From: *Olexandr K 
> *Sent: *17 мая 2018 г. 17:09
> *To: *user@ignite.apache.org
> *Subject: *control.bat authentication support
>
>
>
> Hi guys,
>
>
>
> I configured Ignite user/password authentication by adding custom plugin.
>
> It works fine in server/client nodes and visor but I can't find any auth
> support in control.bat
>
> I checked it's source code and don't see any place where I can provide
> credentials.
>
>
>
> Should I write my own control tool or how can I solve this?
>
>
>
> BR, Oleksandr
>
>
>



-- 
Alexey Kuznetsov

Re: Cache not rebalanced after one node is restarted

[Vadym Vasiuk]

Has anyone some advice for this situation?
Thanks.

On Mon, May 21, 2018, 21:29 Vadym Vasiuk  wrote:

> HI All,
>
> I also noticed that if I bounce one of two nodes and data is then
> distributed as I described (one node has all the PRIMARY entries and second
> one has only BACKUP entries) - after I restart second node - data is again
> distributed normally.
> But what if I dont want to restart all nodes to make data distribution
> normal?
>
> Thanks.
>
>
> On Mon, May 21, 2018 at 2:49 PM, Vadym Vasiuk  wrote:
>
>> Hi Stanislav,
>>
>> Yes persistence is enabled and version is 2.4.
>>
>> Have tried to update topology after one node restart with below code from
>> client:
>>
>> Collection nodes = ignite.cluster().forServers.nodes();
>>
>> ignite.cluster().setBaselineTopology(nodes);
>>
>> And after that I still have all primary entries stored on one node and
>> backup entried on the one which I restarted.
>>
>> Maybe that method of topology update is incomplete?
>>
>> Thanks in advance for your reply.
>>
>> On Mon, May 21, 2018, 14:29 Stanislav Lukyanov 
>> wrote:
>>
>>> Hi,
>>>
>>>
>>>
>>> Do you have native persistence enabled?
>>>
>>> What is your Ignite version?
>>>
>>>
>>>
>>> If the Ignite version is 2.4+ and you have persistence, the problem is
>>> most likely with baseline topology.
>>>
>>> You need to make sure that the restarted node is in the baseline for the
>>> rebalance to happen, either by keeping its old consistentId or by updating
>>> the baseline.
>>>
>>>
>>>
>>> Check out the documentation here:
>>> https://apacheignite.readme.io/docs/baseline-topology
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Stan
>>>
>>>
>>>
>>> *From: *Вадим Васюк 
>>> *Sent: *20 мая 2018 г. 17:39
>>> *To: *user@ignite.apache.org
>>> *Subject: *Cache not rebalanced after one node is restarted
>>>
>>>
>>>
>>> Hi All,
>>>
>>>
>>>
>>> I have a 2 server nodes (with persistence enabled) and one client node
>>> started on my PC.
>>>
>>> From client I activate cluster and then create a simple cache with below
>>> configuration and add 10 entries to it:
>>>
>>>
>>>
>>> CacheConfiguration cfg = new CacheConfiguration<>();
>>> cfg.setName(*C*);
>>> cfg.setBackups(1);
>>> cfg.setRebalanceDelay(1000L);
>>> cfg.setCacheMode(CacheMode.*PARTITIONED*);
>>> cfg.setAtomicityMode(CacheAtomicityMode.*ATOMIC*);
>>> cfg.setRebalanceMode(CacheRebalanceMode.*SYNC*);
>>> IgniteCache cache = ignite.getOrCreateCache(cfg);
>>>
>>> IntStream.*range*(cache.size(CachePeekMode.*ALL*)+1, 
>>> cache.size(CachePeekMode.*ALL*)+1+10).forEach(i -> {
>>> cache.put(i, Utils.*getRandonString*(2));
>>> }
>>> );
>>>
>>> I have a simple computation task to check which entry went to which
>>> server and here is the output after I inserted data into the cache:
>>>
>>> server name: 544a56b3-1364-420e-bdbb-380a1460df72cache entries:
>>> 1,2,4,5,7,8backup entries: 3,6,9,10
>>>
>>> server name: eb630559-c6b4-46a4-a98b-3ba2abfefce9 cache entries:
>>> 3,6,9,10backup entries: 1,2,4,5,7,8
>>>
>>>
>>>
>>> As you can see all entries are saved and have backups on each other
>>> nodes.
>>>
>>>
>>>
>>> However after I restart one of these server nodes, I can see such data
>>> distribution:
>>>
>>> server name: eb630559-c6b4-46a4-a98b-3ba2abfefce9 cache entries:
>>> 1,2,3,4,5,6,7,8,9,10backup entries:
>>>
>>> server name: 544a56b3-1364-420e-bdbb-380a1460df72   cache entries:
>>>backup entries: 1,2,3,4,5,6,7,8,9,10
>>>
>>>
>>>
>>> As you can see data after one node restart is no longer distributed
>>> nicely.
>>>
>>> And from this moment I cannot make it redistribute.
>>>
>>>
>>>
>>> Could you please advice what I may be doing wrong?
>>>
>>>
>>>
>>> Thanks for your reply.
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Sincerely Yours
>>> Vadim Vasyuk
>>>
>>>
>>>
>>
>
>
> --
> Sincerely Yours
> Vadim Vasyuk
>

Re: AccessedExpirationPolicy with SQL

[Denis Mekhanikov]

Shaleen,

This is a known issue: https://issues.apache.org/jira/browse/IGNITE-7687
Judging by a comment in the ticket, it's not going to be fixed in the
nearest future.
Cache API works with TTL correctly, so if you strongly depend on the
expiration policy, you can move your access logic to cache API.

Denis


сб, 19 мая 2018 г. в 2:26, Shaleen Sharma :

> Is there any update on the below issue:
>
> Thanks
> Shaleen
>
>
>
> From: Shaleen Sharma
> Sent: Friday, 18 May, 5:00 pm
> Subject: Re: AccessedExpirationPolicy with SQL
> To: user@ignite.apache.org
>
>
>
> Update:
>
> I wrote a small test with TouchedExpiryPolicy as below, I am putting an
> Object of DocumentCacheDto in cache with TouchedExpiryPolicy set to 10
> secs. Thereafter I am accessing the same value after 8secs
> And even the cache entry is being touched by using get() the entry
> disappears after 10 secs. So why is TouchedExpiryPolicy is not renewing the
> expiry time of the cache entry..?
>
> private void test() {
>  documentCache.withExpiryPolicy(new TouchedExpiryPolicy(new
> Duration(MILLISECONDS, 1))).put(1L, new
> DocumentCacheDto().searchToken("111"));
>
>  try {
>  System.out.println(new Date() +", "+ documentCache.get(1L));
>  Thread.sleep(8000);
>  System.out.println(new Date() +", "+documentCache.get(1L));
>  Thread.sleep(8000);
>  System.out.println(new Date() +", "+ documentCache.get(1L));
>  Thread.sleep(8000);
>  System.out.println(new Date() +", "+documentCache.get(1L));
>  }catch(Exception e) {}
>}
>
> Output:
>
> Fri May 18 16:42:45 AEST 2018, DocumentCacheDto [searchToken=111,
> documentKey=0, document=null, expiryTime=null]
> Fri May 18 16:42:53 AEST 2018, DocumentCacheDto [searchToken=111,
> documentKey=0, document=null, expiryTime=null]
> Fri May 18 16:43:01 AEST 2018, null
> Fri May 18 16:43:09 AEST 2018, null
>
>
>
> *From:* Shaleen Sharma 
> *Sent:* Friday, 18 May 2018 3:37 PM
> *To:* user@ignite.apache.org
> *Subject:* AccessedExpirationPolicy with SQL
>
>
> Hi
>
> I am using AccessedExpiryPolicy in my cache setup. I am setting the data
> in cache using the usual ‘put ‘ method but I am retrieving the data using
> SqlFieldsQuery. In this setup the expiration policy only considers the time
> of data creation and hence the data gets expired after the time from the
> data creation completes. It doesn’t consider the data accessed and doesn’t
> renew the expiration time since the data was last accessed.
>  Do the ExpirationPolicies  not consider the data access using Ignite SQL
> or am I missing something ?
>
> Thanks
> Shaleen
>
>
>
>
>
>
>
>
>
>

Re: C# client too slow to connect.

[Igor Sapego]

Hi,

Try using "TcpDiscoveryStaticIpFinder" instead of
"TcpDiscoveryMulticastIpFinder".

Does it take 1 min for connection only or for start up + connection?

Best Regards,
Igor

On Tue, May 22, 2018 at 11:45 AM, F. D.  wrote:

> Hi,
>
> I'm trying to use Ignite to develop an internal system of data
> contribution. To do this, I'm launching Ignite inside Excel, and I'm using
> the C# binding.
>
> When try to connect it consumes a lot of time (~1 min.),  this is my
> simple app.config:
>
> 
> 
>
>type="Apache.Ignite.Core.IgniteConfigurationSection,
> Apache.Ignite.Core"/>
>
>
>
>
>
>
>http://ignite.apache.org/schema/dotnet/
> IgniteConfigurationSection" localhost="10.200.30.100"
> peerAssemblyLoadingMode="CurrentAppDomain" gridName="IMIStreamer">
>   
>  
>   
>
>   
>
>   
>  
> 
>10.200.20.90:47500..47509
> 
>  
>   
>
>
>
>   
>
>
> 
>
> Is it possibile to reduce this time of connection?
> I've tried to use the thin client, but in this client there's no
> continuous query (and need it, because I want to be reactive when a cache
> change).
>
> Thanks in advance for your help,
>F.D.
>
>

C# client too slow to connect.

[F. D.]

Hi,

I'm trying to use Ignite to develop an internal system of data
contribution. To do this, I'm launching Ignite inside Excel, and I'm using
the C# binding.

When try to connect it consumes a lot of time (~1 min.),  this is my simple
app.config:



   
  
   

   
   
   

   http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection;
localhost="10.200.30.100" peerAssemblyLoadingMode="CurrentAppDomain"
gridName="IMIStreamer">
  
 
  

  

  
 

   10.200.20.90:47500..47509

 
  
   

   
  
   



Is it possibile to reduce this time of connection?
I've tried to use the thin client, but in this client there's no continuous
query (and need it, because I want to be reactive when a cache change).

Thanks in advance for your help,
   F.D.

Re: control.bat authentication support

[Olexandr K]

Hi Stan,

Actually I see some support in CommandHandler.java which is called from
control.bat

At line 608 where configuration is created:

GridClientConfiguration cfg = new GridClientConfiguration();

we just need to add something like:

cfg.setSecurityCredentialsProvider(new SecurityCredentialsProvider() {
@Override
public SecurityCredentials credentials() throws
IgniteCheckedException {
return creds; //load them from control.bat command line
options or env variables
}
});

BR, Oleksandr

On Mon, May 21, 2018 at 11:53 PM, Stanislav Lukyanov  wrote:

> Hi,
>
>
>
> Ignite doesn’t provide built-in support for authentication, so the
> built-in control.bat/sh also don’t have stubs for that.
>
> So yes, I guess you need to write your own tool.
>
>
>
> A tool like that would be pretty simple though – just start a client node,
> parse command line arguments and
>
> map them to the methods of the ignite.cluster().
>
>
>
> Stan
>
>
>
> *From: *Olexandr K 
> *Sent: *17 мая 2018 г. 17:09
> *To: *user@ignite.apache.org
> *Subject: *control.bat authentication support
>
>
>
> Hi guys,
>
>
>
> I configured Ignite user/password authentication by adding custom plugin.
>
> It works fine in server/client nodes and visor but I can't find any auth
> support in control.bat
>
> I checked it's source code and don't see any place where I can provide
> credentials.
>
>
>
> Should I write my own control tool or how can I solve this?
>
>
>
> BR, Oleksandr
>
>
>

Re: Dose Iginte implement lock and latch in transaction，and where is the code ？

[Igor Sapego]

Re-sending to dev-list.

Best Regards,
Igor

On Sat, May 19, 2018 at 6:02 PM, zhouxy1123  wrote:

> Dose Iginte implement lock and latch in transaction，and where is the code ？
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Dose Iginte implement lock and latch in transaction，and where is the code ？

[Denis Mekhanikov]

Ignite performs implicit locking within transactions.
The moment, when it does so depends on its concurrency and isolation level.
Take a look at the documentation:
https://apacheignite.readme.io/docs/transactions

Here is an example of using transactions: CacheTransactionExample


You can also get explicit locks, but they cannot be used within
transactions: https://apacheignite.readme.io/docs/distributed-locks

Ignite also has distributed latches
. I don't recommend
using them within transactions, since it may make transactions too long.
It's better to start a transaction once you've finished waiting on a latch.

Denis

сб, 19 мая 2018 г. в 18:02, zhouxy1123 :

> Dose Iginte implement lock and latch in transaction，and where is the code ？
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Support for polymorphic SQL Queries

[Igor Sapego]

Hi,

Do you store all your models in the same cache?

Best Regards,
Igor

On Thu, May 17, 2018 at 8:57 PM, ttlir  wrote:

> I am using ignite to store different model classes which inherit from the
> same interface on a single ignite cache.  The problem that I am facing is
> with creating polymorphic queries.
> Let’s say I have a FinacialSecurity interface with different
> implementations
> Bond, CorporateBond, Swap, GovermentBond …. They all share currency. What I
> want to be able to do is to query all financial securities where currency =
> “USD”.  I wasn’t able to find an example where I could index currency and
> filter on it. Is there an easy way to create such queries? If so, is there
> an example that I can follow?
> Thanks,
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

SEVERE error while starting ignite in embedded mode

[the_palakkaran]

Hi,

When I am trying to start ignite in embedded mode, the below error is
thrown.

Can anyone help me understand what is wrong here?

May 22, 2018 12:57:08 PM org.apache.ignite.logger.java.JavaLogger error
SEVERE: Got exception while starting (will rollback startup routine).
class org.apache.ignite.IgniteException: Failed to load class names
properties file packaged with ignite binaries
[file=META-INF/classnames.properties,
ldr=com.container.deploy.loader.RuntimeClassLoader@308144a9]

at
org.apache.ignite.internal.MarshallerContextImpl.(MarshallerContextImpl.java:120)
at
org.apache.ignite.internal.GridKernalContextImpl.(GridKernalContextImpl.java:463)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:847)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1909)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1652)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1080)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:600)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:525)
at org.apache.ignite.Ignition.start(Ignition.java:322)
at
com.tpe.caching.config.IgniteConfig.igniteInstance(IgniteConfig.java:2724)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:166)
at
org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:586)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1094)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:989)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:504)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:475)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:304)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:228)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:300)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:195)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:703)
at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:760)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482)
at
com.tpe.caching.controller.IgniteController.loadCache(IgniteController.java:427)
at com.tpe.core.server.ServerManager.init(ServerManager.java:3663)
at
com.container.core.ServiceContainerCommandDespatcher.run(ServiceContainerCommandDespatcher.java:46)



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/