Unsubscribe

[ANKIT SINGHAI]

-- 
Regards,
Ankit Singhai

Re: Certificate upgrade in Ignite Cluster

[ANKIT SINGHAI]

Hi,
I meant tls/ssl=on.

On Fri, May 10, 2019, 12:23 Nikolay Izhikov  wrote:

> Hello, Ankit.
>
> Please, clarify, what do you mean by "secure mode"?
>
> В Чт, 09/05/2019 в 05:33 -0700, Ankit Singhai пишет:
> > Hello,
> > We are running Ignite Cluster with 3 servers and 10 client nodes in
> secure
> > mode. Now as the certificate is going to expire, how can we configure the
> > new certificate without taking any down time?
> >
> > Thanks,
> > Ankit Singhai
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Certificate upgrade in Ignite Cluster

[Ankit Singhai]

Hello,
We are running Ignite Cluster with 3 servers and 10 client nodes in secure
mode. Now as the certificate is going to expire, how can we configure the
new certificate without taking any down time?

Thanks,
Ankit Singhai



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

What is update check & how to disable it?

[Ankit Singhai]

Hello,
On Ignite version:-

>>> ver. 2.6.0#20180710-sha1:669feacc
>>> 2018 Copyright(C) Apache Software Foundation

In Apache Ignite logs every hour the below statement is logged:-
"INFO  [ignite-update-notifier-timer] cluster.GridUpdateNotifier" 
What is this statement is trying to convey / do? and How to stop this ?

Somewhere in forum we found below solution but it isn't working:-
Setting system property -Dignite.update.notifier.enabled.by.default=false 


Regards,
Ankit Singhai



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

Do we require to set MaxDirectMemorySize JVM parameter?

[Ankit Singhai]

Hi All,
Do we require to set MaxDirectMemorySize JVM parameter on IgniteServer to
make use of OFFHEAP?

For an example to make use of 8 GB off heap should I add MaxDirectMemorySize
if yes then how much?
  
  

  
  
  
  
  

  


Regards,
Ankit




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

Cache Mode = LOCAL throwing exception while initialisation

[Ankit Singhai]

Hi,
I am trying to create an Ignite cache with cacheMode="LOCAL" and on
initialisation it is throwing NPE.

localCache XML
http://www.springframework.org/schema/beans";
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
   xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd";>





























Ignite Config XML

http://www.springframework.org/schema/beans";
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
   xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd";>






















127.0.0.1:47500..47509















































For server instance memory configuration is un-commented & for client it is
commented.

Failed to process custom exchange task:
ClientCacheChangeDummyDiscoveryMessage
[reqId=d470058b-dd64-4f27-b0c8-bade7fdec9be, cachesToClose=null,
startCaches=[sampleCacheLocalIgnite]]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.CacheGroupContext.(CacheGroupContext.java:190)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCacheGroup(GridCacheProcessor.java:1918)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1860)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processClientCacheStartRequests(CacheAffinitySharedManager.java:431)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processClientCachesChanges(CacheAffinitySharedManager.java:603)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCustomExchangeTask(GridCacheProcessor.java:410)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.processCustomTask(GridCachePartitionExchangeManager.java:1789)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1878)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)

Any I/Ps what I am missing here?

Regards,
Ankit Singhai




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

Re: Failed to create string representation of binary object.

[Ankit Singhai]

Hi Alex,
Below is the POJO:-

import java.io.Externalizable;
import java.io.IOException;
import java.io.ObjectInput;
import java.io.ObjectOutput;
import java.util.Date;

public class UserRegistrationInfoResponse implements Externalizable {
private static final long serialVersionUID = 1L;
private Date registrationDate;
private String affiliateInformation;
private Date rmpConversionDate;

public UserRegistrationInfoResponse() { 
super();
}

public Date getRegistrationDate() {
return registrationDate;
}

public void setRegistrationDate(Date registrationDate) {
this.registrationDate = registrationDate;
}

public Date getRmpConversionDate() {
return rmpConversionDate;
}

public void setRmpConversionDate(Date rmpConversionDate) {
this.rmpConversionDate = rmpConversionDate;
}

public String getAffiliateInformation() {
return affiliateInformation;
}

public void setAffiliateInformation(String affiliateInformation) {
this.affiliateInformation = affiliateInformation;
}

@Override
public String toString() {
return "UserRegistrationInfo [affiliateInformation="
+ affiliateInformation + ", registrationDate="
+ registrationDate + ", rmpConversionDate=" + rmpConversionDate
+ "]";
}

@Override
public void readExternal(ObjectInput in) throws IOException,
ClassNotFoundException {
registrationDate = (Date) in.readObject();
affiliateInformation = (String) in.readObject();
rmpConversionDate = (Date) in.readObject();

}

@Override
public void writeExternal(ObjectOutput out) throws IOException {
out.writeObject(registrationDate);
out.writeObject(affiliateInformation);
out.writeObject(rmpConversionDate);

}

}

Thanks,
Ankit Singhai



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

Failed to create string representation of binary object.

[Ankit Singhai]

org.apache.ignite.internal.marshaller.optimized.OptimizedMarshaller.unmarshal0(OptimizedMarshaller.java:235)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:94)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryUtils.doReadOptimized(BinaryUtils.java:1734)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:1943)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:1768)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.unmarshalField(BinaryReaderExImpl.java:338)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryObjectImpl.field(BinaryObjectImpl.java:625)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:225)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:186)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryObjectImpl.toString(BinaryObjectImpl.java:853)
~[ignite-core-2.1.0.jar:2.1.0]
at java.lang.String.valueOf(String.java:2849) ~[?:1.7.0_80]
at
org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:884)
~[ignite-core-2.1.0.jar:2.1.0]
... 29 more
Caused by: java.io.IOException: java.lang.reflect.InvocationTargetException
at
org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readSerializable(OptimizedObjectInputStream.java:575)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.read(OptimizedClassDescriptor.java:927)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:324)
~[ignite-core-2.1.0.jar:2.1.0]
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:364)
~[?:1.7.0_80]
at
org.apache.ignite.internal.marshaller.optimized.OptimizedMarshaller.unmarshal0(OptimizedMarshaller.java:227)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:94)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryUtils.doReadOptimized(BinaryUtils.java:1734)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:1943)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:1768)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.unmarshalField(BinaryReaderExImpl.java:338)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryObjectImpl.field(BinaryObjectImpl.java:625)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:225)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:186)
~[ignite-core-2.1.0.jar:2.1.0]

Class is available in classpath and also under marshaller folder

Regards,
Ankit Singhai



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

Failed to create string representation of binary object after few days of run.

[Ankit Singhai]

org.apache.ignite.internal.marshaller.optimized.OptimizedMarshaller.unmarshal0(OptimizedMarshaller.java:230)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:94)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryUtils.doReadOptimized(BinaryUtils.java:1734)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:1943)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:1768)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.unmarshalField(BinaryReaderExImpl.java:338)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryObjectImpl.field(BinaryObjectImpl.java:625)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:225)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryObjectExImpl.appendValue(BinaryObjectExImpl.java:280)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryObjectExImpl.appendValue(BinaryObjectExImpl.java:328)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:229)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryObjectExImpl.toString(BinaryObjectExImpl.java:186)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.binary.BinaryObjectImpl.toString(BinaryObjectImpl.java:853)
~[ignite-core-2.1.0.jar:2.1.0]
at java.lang.String.valueOf(String.java:2849) ~[?:1.7.0_80]
at java.lang.StringBuilder.append(StringBuilder.java:128)
~[?:1.7.0_80]
at
java.util.AbstractCollection.toString(AbstractCollection.java:458)
~[?:1.7.0_80]
at java.lang.String.valueOf(String.java:2849) ~[?:1.7.0_80]
at
org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
~[ignite-core-2.1.0.jar:2.1.0]
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:884)
~[ignite-core-2.1.0.jar:2.1.0]
... 29 more
Caused by: java.lang.ClassNotFoundException:
com.partygaming.services.mds.userprofile.api.UserRegistrationInfoResponse
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
~[?:1.7.0_80]
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
~[?:1.7.0_80]
at java.security.AccessController.doPrivileged(Native Method)
~[?:1.7.0_80]


Whatever class mentioned is available in /work/marshaller folder.

Regards,
Ankit Singhai





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

Re: REST API Secret key not working

[Ankit Singhai]

It's working thanks please someone correct the documentation

setSecretKey(String)
Defines secret key used for client authentication. When provided, client
request must contain HTTP header X-Signature with the string "[1]:[2]",
where [1] is timestamp in milliseconds and [2] is the Base64 encoded SHA1
hash of the secret key.

https://apacheignite.readme.io/v2.0/docs/rest-api




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

REST API Secret key not working

[Ankit Singhai]

Hi All,
I am trying to use secret key for REST API.

Snippet of Ignite Config XML







REST request via POSTMAN

OkHttpClient client = new OkHttpClient();

Request request = new Request.Builder()
  .url("http://127.0.0.1:6060/ignite?cmd=version";)
  .get()
  .addHeader("x-signature",
"\"1507726963290:qUqP5cyxm6YcTAhz05Hph5gvu9M=\"")
  .addHeader("cache-control", "no-cache")
  .addHeader("postman-token", "2cd42700-f138-94c0-38e5-fa8b9727cdf5")
  .build();

Response response = client.newCall(request).execute();

I am getting Response code :- 401 i.e un-authorized

Used openssl to get Base64 SHA1 of test => echo -n "test" | openssl sha1
-binary | base64

Thanks
Ankit Singhai



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

Re: REST API should be exposed on https

[Ankit Singhai]

Any inputs ?



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

REST API should be exposed on https

[Ankit Singhai]

Hi All,
We would like to make use of REST API feature in our production environment.
How can be enable it over https? please help out me with any document /
sample.

Thanks,
Ankit Singhai



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

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

[Ankit Singhai]

Thanks using latest Java 7 resolves the issue.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p16078.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

[Ankit Singhai]

Thanks using latest Java 7 resolves the issue.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p16077.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

[Ankit Singhai]

Even disabling TLS/SSL doesn't have any effect. Moving to Java 1.8 is not an
option as we have other dependencies which are incompatible with 1.8.

Any other suggestion?

Regards,
Ankit Singhai




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p16054.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

[Ankit Singhai]

PFA log. No luck even by setting the flag for IPV4 = true.
ignite-de5180fb.zip

  



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p16050.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

[Ankit Singhai]

Hi,
SSL is configured in java code and I didn't try to replicate it w/o SSL. I
will add the property -Djava.net.preferIPv4Stack=true and post the results.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p16048.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

[Ankit Singhai]

Hi Folks,
Did anyone facing this issue? Can you please look into it?

Regards,
Ankit Singhai



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p16023.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

[Ankit Singhai]

Hi Alex,
Did you get an chance to look at it ?

Regards,
Ankit Singhai



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p15984.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

[Ankit Singhai]

Please check folks

On 31-Jul-2017 13:33, "Ankit Singhai [via Apache Ignite Users]" <
ml+s70518n1581...@n6.nabble.com> wrote:

> Hi Alex / Folks,
> PFA zip containing:-
> 1. Server log
> 2. Grid Config
> 3. Java class to initialise all caches
> 4. Cache CoException_In_Ignite.zip
> <http://apache-ignite-users.70518.x6.nabble.com/file/n15810/Exception_In_Ignite.zip>nfig
>
> 5. Few POJOs
>
> Please try to replicate at your end and we are stuck at this issue.
>
> Regards,
> Ankit Singhai
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Caused-by-
> org-h2-jdbc-JdbcSQLException-General-error-java-lang-
> IllegalMonitorStateException-Attemptet-tp15684p15810.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1&code=YW5raXQyODRAZ21haWwuY29tfDF8LTEzOTEzMzU5OTQ=>
> .
> NAML
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p15860.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

[Ankit Singhai]

Hi Alex / Folks,
PFA zip containing:-
1. Server log
2. Grid Config
3. Java class to initialise all caches 
4. Cache Co Exception_In_Ignite.zip
<http://apache-ignite-users.70518.x6.nabble.com/file/n15810/Exception_In_Ignite.zip>
 
nfig
5. Few POJOs

Please try to replicate at your end and we are stuck at this issue.

Regards,
Ankit Singhai 



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p15810.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

[Ankit Singhai]

Hi Alex,
Did you get an chance to look at this? 
Now I am getting this error for both searchable and non-searchable caches.

Thanks,
Ankit Singhai



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p15808.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

[Ankit Singhai]

Hi Alex,
Today I tried the same use-case with Apache Ignite 2.1.0. I am getting the
same error, attaching the log.
Waiting for your analysis. ignite-c8506efe.zip
<http://apache-ignite-users.70518.x6.nabble.com/file/n15758/ignite-c8506efe.zip>
  

Regards,
Ankit Singhai



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p15758.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

[Ankit Singhai]

Hi Alex,
Yes it is reproducible every time.
Linux Version:-
Linux 3.10.0-514.26.1.el7.x86_64 #1 SMP Wed Jun 28 20:34:34 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux

Java Version:-
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)

I have already posted grid & cache config xmls. POJO is also available
please use that.

Regards,
Ankit Singhai



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p15716.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

[Ankit Singhai]

Hi Folks,
Any help on the above issue.

Regards,
Ankit Singhai



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p15714.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

[Ankit Singhai]

Hi All,
I am trying to create an searchable cache where in Linux environment I am
getting the below exception everytime but not getting it in my Windows
laptop.

org.apache.ignite.IgniteCheckedException: Failed to register query type:
QueryTypeDescriptorImpl [space=loginServiceTokenCacheIgnite,
name=TokenSessionDetails, tblName=null, fields={globalSessionId=class
java.lang.String, serviceSessionId=class java.lang.String, serviceId=class
java.lang.String, bindingKey=class java.lang.String, tokenScope=class
java.lang.Object}, idxs={}, fullTextIdx=null, keyCls=class java.lang.String,
valCls=class java.lang.Object, keyTypeName=java.lang.String,
valTypeName=com.pg.loginservice.tokenmanagement.data.TokenSessionDetails,
valTextIdx=false, typeId=0, affKey=null, keyFieldName=null,
valFieldName=null, obsolete=false]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:1866)
~[ignite-indexing-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.registerCache0(GridQueryProcessor.java:1306)
~[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:756)
~[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:817)
~[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1265)
~[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1943)
~[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1833)
~[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:379)
~[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:688)
~[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:529)
[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1806)
[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
[ignite-core-2.0.0.jar:2.0.0]
at java.lang.Thread.run(Thread.java:744) [?:1.7.0_45]
Caused by: org.h2.jdbc.JdbcSQLException: General error:
"java.lang.IllegalMonitorStateException: Attempted to release write lock
while not holding it [lock=7f4c31441960, state=0002280d"; SQL
statement:
CREATE TABLE "loginServiceTokenCacheIgnite".TokenSessionDetails (_key
VARCHAR INVISIBLE NOT NULL,_val OTHER INVISIBLE,_ver OTHER
INVISIBLE,globalSessionId VARCHAR,serviceSessionId VARCHAR,serviceId
VARCHAR,bindingKey VARCHAR,tokenScope OTHER) engine
"org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$H2TableEngine"
[5-195]
at
org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
~[h2-1.4.195.jar:1.4.195]
at org.h2.message.DbException.get(DbException.java:168)
~[h2-1.4.195.jar:1.4.195]
at org.h2.message.DbException.convert(DbException.java:295)
~[h2-1.4.195.jar:1.4.195]
at org.h2.command.Command.executeUpdate(Command.java:268)
~[h2-1.4.195.jar:1.4.195]
at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement.java:193)
~[h2-1.4.195.jar:1.4.195]
at org.h2.jdbc.JdbcStatement.execute(JdbcStatement.java:165)
~[h2-1.4.195.jar:1.4.195]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$H2TableEngine.createTable(IgniteH2Indexing.java:3975)
~[ignite-indexing-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createTable(IgniteH2Indexing.java:2006)
~[ignite-indexing-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:1859)
~[ignite-indexing-2.0.0.jar:2.0.0]
... 12 more
Caused by: java.lang.IllegalMonitorStateException: Attempted to release
write lock while not holding it [lock=7f4c31441960,
state=0002280d
at
org.apache.ignite.internal.util.OffheapReadWriteLock.writeUnlock(OffheapReadWriteLock.java:259)
~[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.writeUnlock(PageMemoryNoStoreImpl.java:495)
~[ignite-core-2.0.0.jar:2.0.0]
at
org.apache.ignite.internal.processors.cache.database.tree.util.PageHandler.writeUnlock(PageHandler.java:379)
~[ignite-core-2.0.0.jar:2

Re: Ignite Cluster going OOM

[Ankit Singhai]

Hi Andrew,
Please let us know when Ignite 2.1.0 would be available & do you think we
can try with Ignite 2.0?

Thanks
Ankit Singhai




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cluster-going-OOM-tp15175p15683.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Cluster going OOM

[Ankit Singhai]

Thanks Andrew. Will wait few days for new release and after that would update
you on the test results.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cluster-going-OOM-tp15175p15223.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Cluster going OOM

[Ankit Singhai]

ignite-d662243f.gz
 
 

It is server log file.

Note:- 20 Caches are created but only 4 is being used.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cluster-going-OOM-tp15175p15188.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Cluster going OOM

[Ankit Singhai]

Load is 16K transactions / min it includes creation, updation, accessing &
deleting it also.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cluster-going-OOM-tp15175p15187.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Cluster going OOM

[Ankit Singhai]

Hi Andrew,
Below is the grid config







10.179.29.135:47500..47509
10.179.29.136:47500..47509
10.179.29.137:47500..47509













 










I have not tried with less number of clients & increasing the number of
servers. Please suggestion in this regard.

Use case:- All the caches are storing session related data (such as login
session and sso token management) which is created once, updating is not
that frequent but accessing is 50 / 60 times.  




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cluster-going-OOM-tp15175p15186.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Ignite Cluster going OOM

[Ankit Singhai]

Hi Guys,
I am using Ignite 1.8.0 with 3 servers and 30 clients. Where in each server
has 4 GB of java heap. Server is going OOM very soon and heap dump shows the
below as top consumer.

Class Name  
 
| Shallow Heap | Retained Heap | Percentage
--
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl
@ 0x705dd8970|   72 |   767,921,176 | 17.96%
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl
@ 0x700f38708|   72 |   749,744,568 | 17.53%
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl
@ 0x702763d90|   72 |   723,323,712 | 16.91%
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl
@ 0x702575918|   72 |   375,394,760 |  8.78%
--



I have 4 caches and they are configured to use OFFHEAP_TIERED

Cache 1




Cache2




Cache3





Cache4




Please help me out.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cluster-going-OOM-tp15175.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Cache Console

[Ankit Singhai]

You can use visor command utility. It is available @
ignite_install/bin/ignite visor.sh and your configuration xml should be @
ignite_install/config folder.

On 19 Jul 2017 20:17, "Ajay [via Apache Ignite Users]" <
ml+s70518n15125...@n6.nabble.com> wrote:

> Hi,
>
> Can we see the cache resides in ignite cluster with any console or tool
> etc.
> ?
>
> Thanks,
> Ajay.
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Ignite-Cache-Console-tp15125.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cache-Console-tp15125p15129.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: With same load Ignite is not able to respond after enabling SSL

[Ankit Singhai]

igniteClient.gz
  
server1.gz
  
server2.gz
  
server3.gz
  



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/With-same-load-Ignite-is-not-able-to-respond-after-enabling-SSL-tp12146p12149.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite client deployed on Tomcat is not able to make secure connection with standalone Ignite Server

[Ankit Singhai]

Hi Val,
It was resolved there was certificate error.

Thanks



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-client-deployed-on-Tomcat-is-not-able-to-make-secure-connection-with-standalone-Ignite-Server-tp11928p12147.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

With same load Ignite is not able to respond after enabling SSL

[Ankit Singhai]

Hi All,
We have 3 servers and 10 clients in topology, wherein all use-cases are on
Ignite Cache. Load is round 40K cache operations / min i.e. Create, Read,
Update and Delete but after enabling SSL we are getting below exceptions
(which was working earlier with out SSL).


[07:25:15] (err) Failed to execute compound future reducer:
GridNearGetFuture [tx=null, ver=GridCacheVersion [topVer=104236831,
time=1492773516157, order=1492771941620, nodeOrder=23],
innerFuts=[[node=292ba740-8376-4ecc-a836-31e222be7c9e, loc=false,
done=true]], super=GridCompoundIdentityFuture [super=GridCompoundFuture
[rdc=Map reducer: {}, initFlag=0, lsnrCalls=0, done=false, cancelled=false,
err=null, futs=[trueclass org.apache.ignite.IgniteCheckedException:
Failed to send message (node may have left the grid or TCP connection cannot
be established due to firewall issues) [node=TcpDiscoveryNode
[id=292ba740-8376-4ecc-a836-31e222be7c9e, addrs=[10.179.29.136],
sockAddrs=[in1s5xraai002.ivycomptech.co.in/10.179.29.136:47500],
discPort=47500, order=1, intOrder=1, lastExchangeTime=1492771286410,
loc=false, ver=1.8.0#20161205-sha1:9ca40dbe, isClient=false],
topic=TOPIC_CACHE, msg=GridNearGetRequest
[futId=a382d109b51-0e611836-1099-4aef-8fc5-4db1230b4a99,
miniId=b382d109b51-0e611836-1099-4aef-8fc5-4db1230b4a99,
ver=GridCacheVersion [topVer=104236831, time=1492773516157,
order=1492771941620, nodeOrder=23], keyMap=null, reload=false,
readThrough=true, skipVals=false, topVer=AffinityTopologyVersion [topVer=25,
minorTopVer=4], subjId=ccc10d0d-3e3f-41e0-8d24-0ab2272cc8f9, taskNameHash=0,
accessTtl=8640], policy=2]
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1153)
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1217)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:910)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.map(GridNearGetFuture.java:384)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.init(GridNearGetFuture.java:162)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearCacheAdapter.loadAsync(GridNearCacheAdapter.java:272)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearAtomicCache.getAllAsync(GridNearAtomicCache.java:417)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.getAsync(GridCacheAdapter.java:1737)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4800)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4783)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1395)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:1118)
at
com.pg.partner.loginservice.cache.PartnerTokenCacheManager.getPartnerToken(PartnerTokenCacheManager.java:62)
at
com.pg.partner.loginservice.impl.PartnerLoginServiceImpl.generatePartnerToken(PartnerLoginServiceImpl.java:185)
at sun.reflect.GeneratedMethodAccessor67.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.partygaming.serviceregistry.SRRemoteInvocation.invoke(SRRemoteInvocation.java:189)
at
com.partygaming.serviceregistry.resolver.AbstractServiceResolver.executeOnService(AbstractServiceResolver.java:1259)
at
com.partygaming.serviceregistry.exportimport.RemoteServiceRegistryImpl.execute(RemoteServiceRegistryImpl.java:17)
at sun.reflect.GeneratedMethodAccessor66.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322)
at sun.rmi.transport.Transport$1.run(Transport.java:177)
at sun.rmi.transport.Transport$1.run(Transport.java:174)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:173)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:556)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:811)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:670)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed to send
message to remote node: TcpDiscoveryNode
[id=292ba740-8376-4e

Ignite client deployed on Tomcat is not able to make secure connection with standalone Ignite Server

[Ankit Singhai]

Hi All,
In my environment I have Ignite Server(s) running as Standalone program(s)
configured to use SSL. 
My standalone programs are able to connect securely to Server's. However one
of my client which is deployed is not able to connect to server.

What additional changes I have to do in Tomcat config files to enable TLS
between this client and server?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-client-deployed-on-Tomcat-is-not-able-to-make-secure-connection-with-standalone-Ignite-Server-tp11928.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: IgniteDataStreamer with Continuous Query

[ANKIT SINGHAI]

Can someone please have a look at below query?

Thanks

On Dec 29, 2016 2:13 PM, "Ankit Singhai"  wrote:

> Hi,
> In my test case scenario I am pumping data into cache via data streamer
> which has Created expiration policy of 60 seconds to have sliding window of
> 60 seconds, after the initial bursts I am making my thread to sleep then
> again pump data, but for the 2nd bursts I am not getting any events (local
> or remote) only the data I receive is after initial search. Can somebody
> point out what I am doing wrong here?
>
> Ignite Configuration
>  class="org.apache.ignite.configuration.IgniteConfiguration">
> 
> 
>
> 
>
>
>
>
>
>
>
> 
>  class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
> 
>
>
>
>  class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.
> TcpDiscoveryVmIpFinder">
> 
> 
>
> 127.0.0.1:47500..47509
> 
> 
> 
> 
> 
>
> 
> 
> 
>
> 
> 
>  id="lifeCycleBeanImpl"/>
> 
> 
>
> 
>  class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
> 
> 
> 
> 
> 
>
> Cache Configuration
>  class="org.apache.ignite.configuration.CacheConfiguration"
> scope="singleton">
> 
>
>
> 
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>
> 
>  class="org.apache.ignite.cache.eviction.fifo.FifoEvictionPolicy">
>
> 
> 
> 
>
>
> 
>
>
> 
>
>
> 
>
>
> 
> 
>
> Ignite Data Streamer Code via StreamTransformer
>
> CacheConfiguration ipCacheConfiguration =
> (CacheConfiguration)applicationContext.getBean("ipCache");
> ipCacheConfiguration.setIndexedTypes(String.class, Integer.class);
>
> ipCacheConfiguration.setExpiryPolicyFactory(FactoryBuilder.factoryOf(new
> CreatedExpiryPolicy(new Duration(SECONDS, 60;
>
> IgniteCache ipCache =
> ignite.getOrCreateCache(ipCacheConfiguration);
>
> Random RAND = new Random();
>
> try (IgniteDataStreamer igniteDataStreamer =
> ignite.dataStreamer(ipCache.getName())){
> igniteDataStreamer.allowOverwrite(true);
>
> igniteDataStreamer.receiver(new
> StreamTransformer() {
> @Override
> public Object process(MutableEntry
> mutableEntry, Object... objects) throws EntryProcessorException {
> Integer val = mutableEntry.getValue();
>
> // Increment count by 1.
> mutableEntry.setValue(val == null ? (int) 1L : val +
> 1);
>
> return null;
> }
> });
>
> int range = 1000;
> for(int i = 1 ; i <= 10 ; i++) {
> igniteDataStreamer.addData(""+RAND.nextInt(range), 1);
> }
>
> try {
> Thread.sleep(7);
> } catch (InterruptedException e) {
> e.printStackTrace();
> }
>
> System.out.println("After Sleeping");
> for(int i = 1 ; i <= 10 ; i++) {
> igniteDataStreamer.addData(""+RAND.nextInt(range), 1);
> }
> }
>
> Continuous Query Code (running on an different JVM)
> CacheConfiguration ipCacheConfiguration =
> (CacheConfiguration)applicationContext.getBean("ipCache");
> ipCacheConfiguration.setIndexedTypes(String.class, Integer.class);
>
> ipCacheConfiguration.setExpiryPolicyFactory(FactoryBuilder.factoryOf(new
> CreatedExpiryPolicy(new Duration(SECONDS, 60;
>
> IgniteCache ipCache =
> ignite.getOrCreateCache(ipCacheConfiguration);
>
> ContinuousQuery continuousQuery = new
> ContinuousQuery<>();
> continuousQuery.setInitialQuery(new ScanQuery(new
> IgniteBiPredicate() {
> @Override
> public boolean apply(String integer, Integer integer2) {
> return integer2 >

Re: IgniteDataStreamer with Continuous Query

[Ankit Singhai]

Hi,
In my test case scenario I am pumping data into cache via data streamer
which has Created expiration policy of 60 seconds to have sliding window of
60 seconds, after the initial bursts I am making my thread to sleep then
again pump data, but for the 2nd bursts I am not getting any events (local
or remote) only the data I receive is after initial search. Can somebody
point out what I am doing wrong here?

Ignite Configuration






















127.0.0.1:47500..47509
























Cache Configuration












































Ignite Data Streamer Code via StreamTransformer

CacheConfiguration ipCacheConfiguration =
(CacheConfiguration)applicationContext.getBean("ipCache");
ipCacheConfiguration.setIndexedTypes(String.class, Integer.class);
   
ipCacheConfiguration.setExpiryPolicyFactory(FactoryBuilder.factoryOf(new
CreatedExpiryPolicy(new Duration(SECONDS, 60;

IgniteCache ipCache =
ignite.getOrCreateCache(ipCacheConfiguration);

Random RAND = new Random();

try (IgniteDataStreamer igniteDataStreamer =
ignite.dataStreamer(ipCache.getName())){
igniteDataStreamer.allowOverwrite(true);

igniteDataStreamer.receiver(new
StreamTransformer() {
@Override
public Object process(MutableEntry
mutableEntry, Object... objects) throws EntryProcessorException {
Integer val = mutableEntry.getValue();

// Increment count by 1.
mutableEntry.setValue(val == null ? (int) 1L : val + 1);

return null;
}
});

int range = 1000;
for(int i = 1 ; i <= 10 ; i++) {
igniteDataStreamer.addData(""+RAND.nextInt(range), 1);
}

try {
Thread.sleep(7);
} catch (InterruptedException e) {
e.printStackTrace();
}

System.out.println("After Sleeping");
for(int i = 1 ; i <= 10 ; i++) {
igniteDataStreamer.addData(""+RAND.nextInt(range), 1);
}
}

Continuous Query Code (running on an different JVM)
CacheConfiguration ipCacheConfiguration =
(CacheConfiguration)applicationContext.getBean("ipCache");
ipCacheConfiguration.setIndexedTypes(String.class, Integer.class);
   
ipCacheConfiguration.setExpiryPolicyFactory(FactoryBuilder.factoryOf(new
CreatedExpiryPolicy(new Duration(SECONDS, 60;

IgniteCache ipCache =
ignite.getOrCreateCache(ipCacheConfiguration);

ContinuousQuery continuousQuery = new
ContinuousQuery<>();
continuousQuery.setInitialQuery(new ScanQuery(new
IgniteBiPredicate() {
@Override
public boolean apply(String integer, Integer integer2) {
return integer2 > 100;
}
}));

continuousQuery.setLocalListener(new
CacheEntryUpdatedListener() {
@Override
public void onUpdated(Iterable> iterable) throws CacheEntryListenerException {
for (CacheEntryEvent events : iterable) {
System.out.println(" Inside local listener :: " +
events);
}
}
});

continuousQuery.setRemoteFilterFactory(new
Factory>() {
@Override
public CacheEntryEventFilter create() {
return new CacheEntryEventFilter() {
@Override
public boolean evaluate(CacheEntryEvent cacheEntryEvent) throws
CacheEntryListenerException {
System.out.println("Remote Listener");
return cacheEntryEvent.getValue() > 100;
}
};
}
});

try (QueryCursor> cur =
ipCache.query(continuousQuery)){
for(Cache.Entry c : cur) {
System.out.println(c);
}
}

Thanks



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/IgniteDataStreamer-with-Continuous-Query-tp9779p9795.html
Sent from the Apache Ignite Us

Re: IgniteDataStreamer with Continuous Query

[ANKIT SINGHAI]

Thanks

On Dec 28, 2016 7:12 PM, "dkarachentsev"  wrote:

> Hi Ankit,
>
> Yes, you can use ContinuousQuery with DataStreamer. Code samples you may
> found here [1] and [2].
>
> [1]
> https://github.com/apache/ignite/blob/master/examples/
> src/main/java/org/apache/ignite/examples/streaming/
> StreamTransformerExample.java
>
> [2]
> https://github.com/apache/ignite/blob/master/examples/
> src/main/java/org/apache/ignite/examples/datagrid/
> CacheContinuousQueryExample.java
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/IgniteDataStreamer-with-Continuous-Query-tp9779p9781.
> html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: How to query data from List

[ANKIT SINGHAI]

Thanks Val

On Dec 28, 2016 9:33 PM, "vkulichenko" 
wrote:

> Yes, this is possible. See this thread:
> http://apache-ignite-users.70518.x6.nabble.com/Does-
> Ignite-support-query-and-index-the-embedded-object-column-td9663.html
>
> -Val
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/How-to-query-data-from-List-tp9766p9785.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

IgniteDataStreamer with Continuous Query

[Ankit Singhai]

Hi All,
Can we have DataStreamerer pushing data via StreamTransformer to an cache
and an ContinousQuery executing on cache to raise the event when the
condition meets?

Any sample would do lot of help.

Thanks
Ankit Singhai



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/IgniteDataStreamer-with-Continuous-Query-tp9779.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: How to query data from List

[ANKIT SINGHAI]

Suppose I have an cache entry string, POJO and this POJO contains another
POJO can we query on inner POJO?

On Dec 28, 2016 8:32 AM, "vkulichenko" 
wrote:

Hi Kumar,

You can't query collections this way. You should store each Person as a
separate entry to achieve this.

-Val



--
View this message in context: http://apache-ignite-users.
70518.x6.nabble.com/How-to-query-data-from-List-tp9766p9767.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

WARNING: Failed to load 'igniteshmem' library from classpath. Will try to load it from IGNITE_HOME. WARNING: Failed to start shared memory communication server.

[Ankit Singhai]

ELEASE.jar 
[ppoker@in1tdevvir131 igniteCorePartnerService]$ pwd 
/home/pg/pg-services/igniteCorePartnerService 

Any pointers what I am missing here? 

Thanks & Regards, 
Ankit Singhai



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/WARNING-Failed-to-load-igniteshmem-library-from-classpath-Will-try-to-load-it-from-IGNITE-HOME-WARNI-tp9715.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.