You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by fatality <fa...@gmail.com> on 2017/05/16 20:29:07 UTC
Is it restricted by ignite to put elements into queue in closures
Hi
I have posted below question a while ago and still not received any response
yet. Could you please tell me what can be accessed or can not be from
closures that we send with remotelisteners.
http://apache-ignite-users.70518.x6.nabble.com/Closures-stuck-in-2-0-when-try-to-add-an-element-into-the-queue-td12587.html#a12609
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Is-it-restricted-by-ignite-to-put-elements-into-queue-in-closures-tp12934.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Is it restricted by ignite to put elements into queue in
closures
Posted by afedotov <al...@gmail.com>.
Well, actually the question was answered on stackoverflow
<http://stackoverflow.com/questions/43891757/closures-stuck-in-2-0-when-try-to-add-an-element-into-the-queue>
with the following:
It's not allowed to invoke ignite.queue and ignite.affinity methods in
EventListener, because it may lead to deadlock.
All cache operations, including EventListeners are executed in system pool,
so it's not recommended to invoke inside EventListener operations, that
uses system pool too.
You could read more here at "Closures Execution and Thread Pools":
https://apacheignite.readme.io/docs/async-support#section-listeners-and-chaining-futures
And here
https://apacheignite.readme.io/docs/thread-pools#section-system-pool
Kind regards,
Alex.
On Tue, May 16, 2017 at 11:29 PM, fatality [via Apache Ignite Users] <
ml+s70518n12934h88@n6.nabble.com> wrote:
> Hi
>
> I have posted below question a while ago and still not received any
> response yet. Could you please tell me what can be accessed or can not be
> from closures that we send with remotelisteners.
>
> http://apache-ignite-users.70518.x6.nabble.com/Closures-
> stuck-in-2-0-when-try-to-add-an-element-into-the-queue-td12587.html#a12609
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Is-it-
> restricted-by-ignite-to-put-elements-into-queue-in-closures-tp12934.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1h65@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1&code=YWxleGFuZGVyLmZlZG90b2ZmQGdtYWlsLmNvbXwxfC0xMzYxNTU0NTg=>
> .
> NAML
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Is-it-restricted-by-ignite-to-put-elements-into-queue-in-closures-tp12934p12935.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.