Re: Strange annoying messages in Ignite 2.11 logs for one of Ignite nodes

Hi all, I'd like to add that this is accompanied by the following messages: ``` ignite_1| [17:07:27,540][WARNING][grid-nio-worker-tcp-comm-0-#103%TcpCommunicationSpi%][TcpCommunicationSpi] Failed to shutdown socket: null ignite_1| java.nio.channels.ClosedChannelException

Re: Ignite client node hangs while IgniteAtomicLong is created

get them hanging? > > Can you throw together a reproducer project? > > Regards, > -- > Ilya Kasnacheev > > > вт, 4 авг. 2020 г. в 12:51, Ilya Roublev > iroublev@ > : > >> We are developing Jira cloud app using Apache Ignite both as data storage >>

Re: Ignite client node hangs while IgniteAtomicLong is created

Hello, Ilya,Attached are two thread dumps, the second is taken 13 minutes after thefirst one: threaddump.txt , threaddump2.txt .The hanging

Re: Ignite client node hangs while IgniteAtomicLong is created

Hello, Ilya, Attached are two thread dumps, the second is taken 13 minutes after the first one: threaddump.txt , threaddump2.txt . The

Ignite client node hangs while IgniteAtomicLong is created

We are developing Jira cloud app using Apache Ignite both as data storage and as job scheduler. This is done via a standard Ignite client node. But we need to use Atlassian Connect Spring Boot to be able to communicate with Jira. In short, all is done exactly as in our article Boosting Jira Cloud

Re: Prevent automatic Ignite server node start for Spring Boot

ilya.kasnacheev wrote > It seems that somebody (like spring boot) have started > > org.apache.ignite.cache.CacheManager > > > How to prevent it I am unaware, you should probably consult with Spring > Boot docs. Thank you very much! It seems that spring.cache.type: simple put in

Prevent automatic Ignite server node start for Spring Boot

I have the following problem. I'm developing a Spring Boot application, this application uses Ignite, but via creation of some client nodes (when it is necessary). The following is the part of pom.xml for the project: The problem is when the application is started, I get the following log: But