Hello!
Please check the IgniteConfiguration.setServiceConfiguration() method.
Regards,
--
Ilya Kasnacheev
чт, 21 мая 2020 г. в 15:55, marble.zh...@coinflex.com <
marble.zh...@coinflex.com>:
> thanks Ilya, lifecyclebean just verified works.
> Can you share the "configure Ignite to
thanks Ilya, lifecyclebean just verified works.
Can you share the "configure Ignite to automatically register service"
related links? thanks.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
You can configure Ignite to automatically register service on start-up or
call lifecycle listener:
https://apacheignite.readme.io/docs/ignite-life-cycle#lifecyclebean
Regards,
--
Ilya Kasnacheev
чт, 21 мая 2020 г. в 15:28, marble.zh...@coinflex.com <
marble.zh...@coinflex.com>:
>
Thanks a lot Ilya.
My confusion is, where to fire the task, does Ignite will help launch this
task when startup the ignite instance?
I have tried, but not found any logs output.
If ignite cannot help launch, only load the class into memory, then where to
fire/trigger this tasks? need a separate
Hello!
For example, method 'compute' has last argument as 'T arg' which is passed
to task.
Please see
https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/computegrid/ComputeTaskMapExample.java
for example.
Regards,
--
Ilya Kasnacheev
чт, 21 мая 2020
Can I understand the task deployment like this:
package jar to ./libs, Ignite only will load this class into instance, but
will not trigger that, task will only trigger by outside the ignite client
or jdbc or jmx?
In this case, outside programmer only need to know the taskName, and call
this
thanks a lot Alex.
I saw my jar from the java process. But cannot see the logs I print out from
the ignite console, I am not sure whether the task run or not run,
My META-INF/ignite.xml defined as below,
http://www.springframework.org/schema/beans;
Hi,
If you are using a regular downloaded version then:
When you put a jar into the libs dir it will be automatically located in
the classpath.
You can then do jinfo and find your jar. Use any class within
that jar inside your app and it should work.
you can do an experiment: