You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Arun Kumar Jain (JIRA)" <ji...@apache.org> on 2017/11/13 09:24:00 UTC
[jira] [Commented] (IGNITE-1026) Existing queue can't be acquired
on client
[ https://issues.apache.org/jira/browse/IGNITE-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249288#comment-16249288 ]
Arun Kumar Jain commented on IGNITE-1026:
-----------------------------------------
Hi [~vkulichenko],
I get the same behaviour with ignite 2.3. Maybe this is a regression? Or was it not fixed due to some reasons?
> Existing queue can't be acquired on client
> ------------------------------------------
>
> Key: IGNITE-1026
> URL: https://issues.apache.org/jira/browse/IGNITE-1026
> Project: Ignite
> Issue Type: Bug
> Components: data structures
> Affects Versions: sprint-4
> Reporter: Valentin Kulichenko
> Assignee: Valentin Kulichenko
> Priority: Blocker
> Fix For: sprint-7
>
>
> Server code:
> {code}
> Ignite ignite = Ignition.start();
> ignite.queue("queue", 1000, new CollectionConfiguration());
> {code}
> Client code:
> {code}
> Ignition.setClientMode(true);
> Ignite ignite = Ignition.start();
> IgniteQueue q = ignite.queue("queue", 0, null);
> {code}
> Start server, then client. The second will fail with NPE:
> {code}
> at org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.getCollection(DataStructuresProcessor.java:911)
> at org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.queue(DataStructuresProcessor.java:777)
> at org.apache.ignite.internal.IgniteKernal.queue(IgniteKernal.java:2768)
> at Client.main(Client.java:30)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)