It seems WebSession's removeAttribute does not support HttpSessionBindingListener

When a session expires or is invalidated, or an attribute gets removed, HttpSessionBindingListener's valueUnbound callback function should be fired. However, it seems that WebSession's removeAttribute does not support HttpSessionBindingListener. class WebSession implements HttpSession, Externaliz

Re: Process write key

Hi Evgenii, Huge thanks for the clarification! Indeed I modified the code and built it before, and somehow it crept back in my current working environment! My fault. Best regards, Yuci -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Process-write-key-tp13006

Process write key

Hi, Our Ignite (version 1.7) log file size goes up sharply, from the level of KB to 10GB. And eventually the cluster suffers. It is filled up with messages like below: [17:25:37,054][INFO ][grid-nio-worker-0-#42%null%][TcpCommunicationSpi] Process write key... [17:25:37,054][INFO ][grid-n

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

Hi Val, Thanks for the explanation for not allowing re-connection of server nodes. Regarding the RESTART_JVM policy, this policy does not work for our web application. The reason is that in our web application Ignite is started by the servlet context listener org.apache.ignite.startup.servlet.Se

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

A follow-up question about recovery. Node ves-hx-40 was frozen for about a minute due to VM backup, and was considered failed by the cluster. Then ves-hx-40 woke up after the VM backup, and found itself being disconnected from topoloyg (see below the logs). It then stopped itself. [23:34:03,752]

Re: How to pass variable to the configuration file

Hi AG, That looks good. Now I can set my properties file ${MY_APP_HOME}/conf/apache-ignite.properties accordingly for the production cluster and failover cluser: * Production nodeIpAddresses=10.22.3.30,10.22.3.31,10.22.3.32,10.22.3.33 * Failover nodeIpAddresses=10.22.4.30,10.22.4.31,10.22.4.32,1

Re: Is it possible to create a near cache without any copy on servers nodes?

Hi Alexey, Thank you. So my understanding of client nodes was wrong. The correct understanding should be: if I start a node as client node, and a cache created by the client node is set to Local Mode, then the server nodes would never see the local cache of the client node. Is it right? Thank y

Re: Is it possible to create a near cache without any copy on servers nodes?

Hi Andrew, I have looked at Local Mode cache. But the thing is that Local Mode cache is located on server nodes. Suppose I have two server nodes, node A and B, and one client node, node C. Node C has a near cache, and server node A and B are of Local Mode cache. And then client node C puts an

How caches in Local Mode works?

Suppose I have two server nodes in the cluster, both nodes have all caches in Local Mode. Node A has cached an entry (key1, value1). Now node B would like to check if an entry keyed by key1 has been cached. Would node B be able to see that entry cached at node A or not? (If not, node B could cac

Is it possible to create a near cache without any copy on servers nodes?

According to the documentation http://apacheignite.gridgain.org/docs/near-caches, a Near cache can be created on a client node, so as to front a partitioned cache on server nodes. Now what I would like to achive is to just create a near cache on the client node, without any copy or any partitioned

How to pass variable to the configuration file

Suppose I have the following configuration file for standalone Ignite server nodes: 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.spr

Re: Failed to wait for initial partition map exchange

Hi Vladislav, We have the same issue, "Failed to wait for initial partition map exchange", when stopping or restarting one of the nodes in our cluster. In other words, when stopping or restarting just one of the nodes, the whole cluster screws up, i.e., the whole cluster stops working. Just had a

Failed to process message: Creating partition which does not belong to local node

Hi, Our app is getting the following error messages. Wonder what is all about. Should I go check the key.hashCode() implementations, but the log does not point out which key it's talking about. What would the indication of this message be: something seriously wrong with the cluster? Many thanks,

About extra data node?

Hi, Currently we have four web app servers, which are session-clustered via Ignite. I've also added a fifth server as a data note, which is of the same capacity of the other four servers, CPU/memory wise. This node is not a web app server, but just part of the cluster as an extra server node. It

BinaryObjectException: Binary type has different field types

Hi, We are using Ignite Web Session Clustering and we've got five web servers running in the cluster. In the new version of our web application, we changed a field type in the session class (see as below) from String to Enum. And then we deployed the new version one server after another. Consequ

Re: How to stop ignite node gracefully

In addition to "kill -9", you can also use ignitevisorcmd.sh, and then use the open command to connect Visor console to the grid. Now you can just type "kill" to use the kill command in an interactive way, to stop/restart an Ignite node, gracefully I suppose. -- View this message in context: ht

Re: Is Apache Tomcat 8 supported for Web Session Clustering yet?

Hi Yakov, I have not vigorously tested it, but so far it has been working perfectly fine in Tomcat 8. Cheers, Yuci -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Is-Apache-Tomcat-8-supported-for-Web-Session-Clustering-yet-tp7824p8049.html Sent from the Apache

Is Apache Tomcat 8 supported for Web Session Clustering yet?

According to the Web Session Clustering documentation: https://apacheignite.readme.io/docs/web-session-clustering, Tomcat 8 seems still not supported yet. Or Tomcat 8 is supported but the documentation needs to be updated? Cheers, Yuci -- View this message in context: http://apache-ignite-use

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

Hi vdpyatkov, Thanks for the advice. I've just looked at the documentation (http://apacheignite.gridgain.org/docs/cluster-config), there are actually four timeouts to set for TcpDiscoverySpi: 1. setNetworkTimeout(long) 2. setSocketTimeout(long) 3. setAckTimeout(long) 4. setJoinTimeout(long) Wond

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

The root cause of the problem just found is that the VMs are frozen sometimes. Our service team takes backup of the VMs once per day. During the backup, the VMs that our application servers are running on would be frozen for a few seconds usually, but sometimes more than 40 seconds! When I say a V

Re: failureDetectionTimeout NotWritablePropertyException

Hi Val, I've just upgraded Spring from version 3.1.2.RELEASE to 3.2.17, and the problem of setting failureDetectionTimeout is now gone. (I'm not upgrading to 4.1.0.RELEASE, to keep other modules in my application happy.) Thanks for your help. Yuci -- View this message in context: http://apac

Re: failureDetectionTimeout NotWritablePropertyException

I just thought of the same thing, the version of Spring :-) But thanks very much for the explanation. I'm currently using Spring version 3.1.2.RELEASE. I'll try a newer version of Spring today, and hope it won't break any existing functionalities of the application. -- View this message in con

Re: failureDetectionTimeout NotWritablePropertyException

It does not help. If I add the following method to IgniteConfiguration.java public IgniteConfiguration setFailureTimeout(long failureDetectionTimeout) { this.failureDetectionTimeout = failureDetectionTimeout; return this; } And change the configuration to: It works. B

failureDetectionTimeout NotWritablePropertyException

Wonder if anyone understands why I get the following error? All I want to do is set the failureDetectionTimeout property: Aug 25, 2016 2:52:31 PM org.apache.catalina.core.StandardContext listenerStart SEVERE: Exception sending context initialized event to listener instance of class org.apache.igni

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

OK, I'll upload all the logs when they are ready. By the way, I've just upgraded to Ignite 1.7.0, but it does not help. The problem persists. Just in case if useful, please find below my Ignite configuration: http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2

Re: Cannot get cache through the REST API

Hi Alexey, As I wrote in another thread, you would be able to see the CPU and heap activities there captured in JVisualVM: http://apache-ignite-users.70518.x6.nabble.com/Puzzled-about-JVM-configuration-td7091.html The cause of it is the JVM configuration: -XX:NewSize=128m -XX:MaxNewSize=128m

Who is going to take care of the off-heap memory?

If I understand correctly, JVM GC takes care of the on-heap memory. My question is, who is going to take care of the off-heap memory? I guess the answer is Ignite :-) But something I'm not so sure is, can I just make all caches off-heap, and my JVM GC will work with minimal memory, so that my app

Combined off heap size?

According to page http://apacheignite.gridgain.org/docs/off-heap-memory, I can set the off heap size using the offHeapMaxMemory. If I understand correctly, this is for a single cache. Considering the following configuration, I've got three caches, namely session-cache, data-cache and penalty-cache

Puzzled about JVM configuration

I'm a bit puzzled about the basic JVM configuration (which is said has proven to provide fairly smooth throughput without large spikes) on the Ignite JVM and System Tuning page (https://apacheignite.readme.io/docs/jvm-and-system-tuning): -XX:NewSize=128m -XX:MaxNewSize=128m -XX:MaxTenuringThresh

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

Another question is: What is the reason that Ignite shall stop the node in the case of big GC pause or temporary network issue? (By the way, I'm not saying big GC pause or temporary network issue is the case for this topic though.) -- View this message in context: http://apache-ignite-users.705

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

Happened again, the Ignite node on ves-hx-40 went down. The other node ves-hx-41 has been running fine, and the network should not be of any issue. (1) Ignite logs on ves-hx-40: [01:03:11,571][INFO ][grid-timeout-worker-#33%null%][IgniteKernal] Metrics for local node (to disable set 'metricsLog

Re: Cannot get cache through the REST API

Hi Val, As for the REST API, I don't have a particular favouritism towards it. I started to look at it because the Ignite Web Console agent uses it to collect statistics. It looks to me that the Ignite Web Console monitoring places too much overhead to the application, the CPU and memory wise acco

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

Ever since the web application has not be usable. Whenever I try to open a web page, I get the following error message in my application log file: 2016-08-10 15:39:43,052 ERROR root/error 495 - Failed to update web session: null java.lang.IllegalStateException: Grid is in invalid state to perform

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

Happened again. (1) Ignite logs: [08:14:01,990][INFO ][grid-timeout-worker-#33%null%][IgniteKernal] Metrics for local node (to disable set 'metricsLogFrequency' to 0) ^-- Node [id=7faa417f, name=null, uptime=14:52:13:438] ^-- H/N/C [hosts=2, nodes=2, CPUs=4] ^-- CPU [cur=16.5%,

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

Happened again. (1) Ignite logs: [08:14:01,990][INFO ][grid-timeout-worker-#33%null%][IgniteKernal] Metrics for local node (to disable set 'metricsLogFrequency' to 0) ^-- Node [id=7faa417f, name=null, uptime=14:52:13:438] ^-- H/N/C [hosts=2, nodes=2, CPUs=4] ^-- CPU [cur=16.5%,

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

Happened again. (1) Ignite logs: [08:14:01,990][INFO ][grid-timeout-worker-#33%null%][IgniteKernal] Metrics for local node (to disable set 'metricsLogFrequency' to 0) ^-- Node [id=7faa417f, name=null, uptime=14:52:13:438] ^-- H/N/C [hosts=2, nodes=2, CPUs=4] ^-- CPU [cur=16.5%, avg=1

Re: Cannot get cache through the REST API

Hi Val, Our application has got a number of caches, one of which is for web session clustering. The reason I'm trying to get cached entries via the REST API, is that I would like to find/purge/etc what is cached during the time of the troubleshooting/debugging/etc. It is not essential in our busi

Re: Cannot get cache through the REST API

Hi Saikat, Thanks for your kind input. But there is no luck yet. I guess that in order to runs sql fields query over cache, you need to make fields visible for sql queries first. But in my case, the session objects are not annotated with @QuerySqlField Furthermore, I got the following error messa

Re: Cannot get cache through the REST API

Hi Val, Thanks for the reply. But I found all cache related APIs (e.g., commands getall, get) require a key parameter. The issue is how I would be able to find out the keys in the first place? Is there any API that can list all the keys of a particular cache? By the way, I guess session IDs may b

Cannot get cache through the REST API

I want to see the list of entries cached, so I'm trying the following REST API. But it does not return anything. http://ves-hx-40.ebi.ac.uk:8080/ignite?cmd=getorcreate&cacheName=session-cache The response: { "error": "", "response": null, "sessionToken": "", "

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

Here is what looked like for the other node: By the way, there were no HTTP traffic

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

Thanks for your reply. Indeed the CPU and memory was a bit intense during the period of time when I ran the Apache Ignite Web Console Agent, so as to use the Apache Ignite Web Console to monitoring my Ignite nodes. But it seemed under control (notes: figures below are provided by JavaMelody):

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

Thanks for your reply. Indeed the CPU and memory was a bit intense during the period of time when I ran the Apache Ignite Web Console Agent, so as to use the Apache Ignite Web Console to monitoring my Ignite nodes. But it seemed under control (notes: figures below are provided by JavaMelody):

Local node seems to be disconnected from topology (failure detection timeout is reached)

Hello, One of my Ignite nodes was stopped and the logs were appended as below. It seems that grid-timeout-worker checks the health of the cluster every minute. But then in my case, before the due time 23:34:19, at 23:34:03 it reported "Local node seems to be disconnected from topology (failure det