Hi,
.
Can anyone provide a clarification of how jetty is being used by Ignite
2.8.1 and whether there is another way to avoid its vulnerabilities when
using Ignite besides upgrading to a newer Ignite version?
To be more specific, if I don't enable REST API (by not moving
ignite-rest-http from libs/
Hi all Igniters,
I am trying to minimize Ignite's memory consumption on my server.
Some background:
My server has 16GB RAM, and is supposed to run applications other than
Ignite.
I use Ignite to store a cache. I use the TRANSACTIONAL_SNAPSHOT mode and I
don't use persistence (configuration file a
Hi,
I couldn't find an answer anywhere else, hopefully you can help me.
I have the following class:
class Pair {
friend struct ignite::binary::BinaryType;
public:
Pair() {
_len = 0;
_buff = nullptr;
}
Pair(char* buff, int len) {
_len = len;
_buff = new char[len];
for (int i = 0; i < len; i++) {
Hi,
I am using C++ Ignite Thin Client (2.8.1 version) to store values in cache
on an Ignite local node.
On Ignite log, I get many of the following error messages:
[09:41:13,542][WARNING][grid-nio-worker-client-listener-3-#33][ClientListenerProcessor]
Client disconnected abruptly due to network co
