Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

[Neelesh]

java 1.7.0_67 definitely has this issue with ignite 1.9, 2.0 and 2.1. We do
not see this issue with java 8

On Tue, Aug 8, 2017 at 6:56 AM, Evgenii Zhuravlev 
wrote:

> I tried your code with java 1.7.0_80-b15 and everything works fine.
>
> Also, check that you use right config file - you provided a file with name
> ignite-config.xml.xml, but in the code, you use ignite-config-login.xml.
>
> Evgenii
>
> 2017-08-08 16:44 GMT+03:00 Evgenii Zhuravlev :
>
>> Yes, It's possible to check the last update of java 1.7
>>
>> Evgenii
>>
>> 2017-08-08 16:42 GMT+03:00 Ankit Singhai :
>>
>>> Even disabling TLS/SSL doesn't have any effect. Moving to Java 1.8 is
>>> not an
>>> option as we have other dependencies which are incompatible with 1.8.
>>>
>>> Any other suggestion?
>>>
>>> Regards,
>>> Ankit Singhai
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context: http://apache-ignite-users.705
>>> 18.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-Gene
>>> ral-error-java-lang-IllegalMonitorStateException-Attemptet-t
>>> p15684p16054.html
>>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>>
>>
>>
>

Re: Setting jobcontext attributes for jobs submitted via run/call

[Neelesh]

Val, that works like a charm. Thanks! The API documentation for the
annotation JobContextResource says it can be used only into ComputeJobs. It
wasn't very clear it could be used inside an IgniteRunnable as well. Thanks!
-neelesh

On Fri, Feb 26, 2016 at 4:30 PM, vkulichenko <valentin.kuliche...@gmail.com>
wrote:

> Hi Neelesh,
>
> You can inject job context into the closure using annotation:
>
> public class MyGridJob implements IgniteRunnable {
> @JobContextResource
> private ComputeJobContext jobCtx;
>
> ...
> }
>
> Let me know if it works for you.
>
> -Val
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Setting-jobcontext-attributes-for-jobs-submitted-via-run-call-tp3209p3213.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Setting jobcontext attributes for jobs submitted via run/call

[Neelesh]

Hi all,
Im trying to use jobcontext attributes to control the behavior of my custom
CollisionSpi implementation.

Is it possible to set job context attributes for jobs submitted thu
IgniteCompute#run() / IgniteCompute#call() and other compute methods? Or Do
I have to use custom computetask/computejob for this?

Any help appreciated

Thanks!

-Neelesh

IGNITE-1144

[Neelesh]

We are planning to try out ignite at our org and are using it for some
pilot projects. Since we are a SaaS company, we need better control over
job scheduling/load balancing. IgniteQueue looked very promising for most
cases, but I stumbled in to
https://issues.apache.org/jira/browse/IGNITE-1144. Anyone knows if this
will be on the radar soon?

I was also comparing Geode to Ignite, and I love Ignite's documentation,
programming model and hadoop/spark support! Thank you for building a great
product!

Thanks!