i found solution from
https://stackoverflow.com/questions/68768699/h2-database-dbexception-unsupported-connection-setting-multi-threaded
implementation ('com.h2database:h2') {
version {
strictly '1.4.197'
}
}
wkhapy...@gmail.com
From: wkhapy...@gmail.com
Date:
it is my code to run affinityCall
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setClientMode(true);
cfg.setPeerClassLoadingEnabled(true);
TcpDiscoveryMulticastIpFinder ipFinder = new TcpDiscoveryMulticastIpFinder();
ipFinder.setAddresses(Collections.singletonList("127.0.0.1:47500..4750
Hi,
I am looking at our configuration of the Ignite checkpointing system to
ensure we have it tuned correctly.
There is a checkpointing thread pool defined, which defaults to 4 threads
in size. I have not been able to find much of a discussion on when/how this
pool size should be changed to refle
If I move the deployment to the server side, the exact same code works in my
environment. Same if I deploy in XML rather than code.
Where are you getting the exception? If you’re seeing that on the client side,
something very weird is happening. The client shouldn’t have any need for the
implem
Example of timestamp data, difference is in "," after year.
Ignite 2.7.6 Java 8 ->"Sep 18, 2019 12:57:35 PM"
Ignite 2.13 Java 11 ->"Aug 31, 2022, 12:43:44 PM"
On Thu, Sep 1, 2022 at 9:03 AM Dren Butković
wrote:
> Hi,
>
> I have upgraded Ignite 2.7.6 on Java 8 to Ignite 2.13 on Jav
Hi,
I have upgraded Ignite 2.7.6 on Java 8 to Ignite 2.13 on Java 11.
In the REST API response the timestamp format has changed.
Locale and all other ENV variables on the host are equal.
Is there a possibility to define the format of the timestamp output in the
Ignite configuration?
Best regards
