Spring Data and XML configuration
Hi, I have seen the SpringDataExample from the ignite/example github repo. We configure the caches through the SpringAppCfg. I want to use Spring Data but initialise the caches through the XML file. Do you have a sample for this? Thank you in advance Think before you print. This e-mail, and any files and attachments transmitted with it, is confidential. It is intended for the sole use of the named recipients(s) only. If you have received this message in error, please immediately notify us by replying to this message and then permanently delete it. Any views and opinions expressed are those of the individual author/sender and are not necessarily shared or endorsed by INTRASOFT International SA or any associated or related company. This e-mail transmission is not binding for the purposes of forming a contract and does not form a contractual obligation of any type.
Re: Can client node use IgniteQueue?
I have also tried version 2.3 with the same issue. Hi, I am still experiencing this issue with ignite version 2.2.0 Can you please confirm which version has this been fixed in? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Can client node use IgniteQueue?
Hi, I am still experiencing this issue with ignite version 2.2.0 Can you please confirm which version has this been fixed in? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Ignite 2.3.0 hangs in startup
Hi All, Evgenii, Can you please help me here? We are kind of clue-less on this one and as a result not able to upgrade to 2.3.0. Can you please let me know how to enable verbose logging in embedded mode (i.e. running from within Spring Boot application)? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Spring Data and XML configuration
Hi, just replace code-based configuration inside
SpringAppCfg#igniteInstance() with single line XML file-based
initialisation:
@Bean
public Ignite igniteInstance() {
return Ignition.start("ignite-config.xml");
}
Re: Ignite 2.3.0 hangs in startup
Hi Evgenii, I have now the following set-up IgniteConfiguration igniteConfig = new IgniteConfiguration(); igniteConfig.setGridLogger(new Slf4jLogger(log)); where log is my Slf4j logger. However, the server still hangs at startup giving the same message. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Ignite 2.3.0 hangs in startup
Hi Evgenii, I checked further, I am using logback with Slf4j (default setting in spring boot). Can this be an issue? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Ignite 2.3.0 hangs in startup
For using slf4j, you need to have a configure file, as it showed in the message, default it's config/java.util.logging.properties, so, you can add this file to this path or try to configure slf4j: https://www.slf4j.org/docs.html Ignite slf4 logger constructor also have another constructor - new Slf4jLogger(Logger logger). Evgenii -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Error serialising arrays using Ignite 2.2 C# client
I’m using the Ignite 2.2 C# client to make ComputeTask calls. I have a type in an argument to one of those calls that is a two dimensional array of floats, like this: [Serializable] Public float[,] = new float[32, 32]; When this field is present in a structure being serialized (either in the argument, or in the response), I get the following error (when the field is in the result): Call completed successfully, but result serialization failed […, serializationErrMsg=Expression of type 'System.Single[,]' cannot be used for parameter of type 'System.Single[]'] This is odd as the serializer seems to be getting one dimensional and two dimensional arrays confused. If I change the element being serialized to a single dimensional array (as below), then the serialization is fine. [Serializable] Public float[] = new float[1024]; Are multi-dimensional arrays expected to be supported? Note: This is a rectangular array, not a jagged array (which would be possible if the definition was float[][]), which I expect would give the serialiser more trouble. Thanks, Raymond.
