[jira] [Commented] (IGNITE-264) Queue failover tests fail in transactional cache

[Alexey Goncharuk (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726947#comment-14726947
 ] 

Alexey Goncharuk commented on IGNITE-264:
-

Found another issue with near enabled cache, related to ignite-910 (confirmed 
by Semyon, linked the ticket). Assertion happens because in one-phase commit 
DHT locks are released before near transaction commit and thus more than one 
near candidate might become marked as ready. Fixed this by releasing locks on 
primary node after committing transaction on near node.
After I made this fix I observed more hangs in portables test suite (added 
recently), need more time to investigate.

> Queue failover tests fail in transactional cache
> 
>
> Key: IGNITE-264
> URL: https://issues.apache.org/jira/browse/IGNITE-264
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-1
>Reporter: Valentin Kulichenko
>Assignee: Alexey Goncharuk
> Fix For: ignite-1.4
>
>
> See {{GridCachePartitionedQueueFailoverDataConsistencySelfTest}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-843) Web configuration tools development

[Dmitriy Setrakyan (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726937#comment-14726937
 ] 

Dmitriy Setrakyan commented on IGNITE-843:
--

I have clicked around and think we should add "Undo" button on every screen 
wherever it makes sense.

> Web configuration tools development
> ---
>
> Key: IGNITE-843
> URL: https://issues.apache.org/jira/browse/IGNITE-843
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: sprint-5
> Environment: Specific frameworks:
> # Main SPA stack: HTML5 / LESS / AngularJS 1.3.x / Bootstrap 3.x
> # Auxiliary: jQuery 2.x / AngularJS UI 0.x
> # HTTP server: node.js
> # Tools: Grunt, Lodash 2.x, Font-Awesome 4.x, Animate.css, ngTable
> Install node.js locally.
> Install Angular, LESS, and Grunt plugins into IDEA.
> Use LESS instead of CSS.
>Reporter: Alexey Goncharuk
>Assignee: Alexey Kuznetsov
> Fix For: ignite-1.4
>
> Attachments: ig-843.png
>
>
> Frameworks to be used:
>  # Bootstrap
>  # AngularJS
>  # NodeJS
>  # MongoDB
> Web control Center will communicate with Ignite Cluster via special 
> lightweight proxy (so called web-agent) implemented on web-sockets.
> Test server: http://104.197.2.239



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-910) Assert with near-only tx cache: Cannot have more then one ready near-local candidate

[Alexey Goncharuk (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726950#comment-14726950
 ] 

Alexey Goncharuk commented on IGNITE-910:
-

Will be fixed in IGNITE-264

> Assert with near-only tx cache: Cannot have more then one ready near-local 
> candidate
> 
>
> Key: IGNITE-910
> URL: https://issues.apache.org/jira/browse/IGNITE-910
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Alexey Goncharuk
>Priority: Critical
>
> Added test IgniteCacheNearOnlyTxTest.testNearOnlyPutMultithreaded. Test pass, 
> but there are many errors in the log:
> {noformat}
> java.lang.AssertionError: Cannot have more then one ready near-local 
> candidate [c=GridCacheMvccCandidate 
> [nodeId=1009df79-3666-4aa3-8136-0b9afbb16001, ver=GridCacheVersion 
> [topVer=43228250, nodeOrderDrId=2, globalTime=1431748254111, 
> order=1431748248330], timeout=0, ts=1431748254106, threadId=181, id=282, 
> topVer=AffinityTopologyVersion [topVer=-1, minorTopVer=0], reentry=null, 
> otherNodeId=null, otherVer=GridCacheVersion [topVer=43228250, 
> nodeOrderDrId=1, globalTime=1431748254113, order=1431748248332], 
> mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null, 
> key=KeyCacheObjectImpl [val=1, hasValBytes=true], 
> masks=local=1|owner=0|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=0|near_local=1|removed=0,
>  prevVer=null, nextVer=null], cand=GridCacheMvccCandidate 
> [nodeId=1009df79-3666-4aa3-8136-0b9afbb16001, ver=GridCacheVersion 
> [topVer=43228250, nodeOrderDrId=2, globalTime=1431748254110, 
> order=1431748248323], timeout=0, ts=1431748254106, threadId=182, id=279, 
> topVer=AffinityTopologyVersion [topVer=-1, minorTopVer=0], reentry=null, 
> otherNodeId=null, otherVer=GridCacheVersion [topVer=43228250, 
> nodeOrderDrId=1, globalTime=1431748254112, order=1431748248328], 
> mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null, 
> key=KeyCacheObjectImpl [val=1, hasValBytes=true], 
> masks=local=1|owner=0|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=0|near_local=1|removed=0,
>  prevVer=null, nextVer=null], mvcc=GridCacheMvcc 
> [locs=[GridCacheMvccCandidate [nodeId=1009df79-3666-4aa3-8136-0b9afbb16001, 
> ver=GridCacheVersion [topVer=43228250, nodeOrderDrId=2, 
> globalTime=1431748254111, order=1431748248331], timeout=0, ts=1431748254106, 
> threadId=184, id=283, topVer=AffinityTopologyVersion [topVer=-1, 
> minorTopVer=0], reentry=null, otherNodeId=null, otherVer=GridCacheVersion 
> [topVer=43228250, nodeOrderDrId=1, globalTime=1431748254113, 
> order=1431748248333], mappedDhtNodes=null, mappedNearNodes=null, 
> ownerVer=null, key=KeyCacheObjectImpl [val=1, hasValBytes=true], 
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=0|near_local=1|removed=0,
>  prevVer=null, nextVer=null], GridCacheMvccCandidate 
> [nodeId=1009df79-3666-4aa3-8136-0b9afbb16001, ver=GridCacheVersion 
> [topVer=43228250, nodeOrderDrId=2, globalTime=1431748254111, 
> order=1431748248330], timeout=0, ts=1431748254106, threadId=181, id=282, 
> topVer=AffinityTopologyVersion [topVer=-1, minorTopVer=0], reentry=null, 
> otherNodeId=null, otherVer=GridCacheVersion [topVer=43228250, 
> nodeOrderDrId=1, globalTime=1431748254113, order=1431748248332], 
> mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null, 
> key=KeyCacheObjectImpl [val=1, hasValBytes=true], 
> masks=local=1|owner=0|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=0|near_local=1|removed=0,
>  prevVer=null, nextVer=null], GridCacheMvccCandidate 
> [nodeId=1009df79-3666-4aa3-8136-0b9afbb16001, ver=GridCacheVersion 
> [topVer=43228250, nodeOrderDrId=2, globalTime=1431748254110, 
> order=1431748248323], timeout=0, ts=1431748254106, threadId=182, id=279, 
> topVer=AffinityTopologyVersion [topVer=-1, minorTopVer=0], reentry=null, 
> otherNodeId=null, otherVer=GridCacheVersion [topVer=43228250, 
> nodeOrderDrId=1, globalTime=1431748254112, order=1431748248328], 
> mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null, 
> key=KeyCacheObjectImpl [val=1, hasValBytes=true], 
> masks=local=1|owner=0|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=0|near_local=1|removed=0,
>  prevVer=null, nextVer=null], GridCacheMvccCandidate 
> [nodeId=1009df79-3666-4aa3-8136-0b9afbb16001, ver=GridCacheVersion 
> [topVer=43228250, nodeOrderDrId=2, globalTime=1431748254110, 
> order=1431748248325], timeout=0, ts=1431748254106, threadId=180, id=280, 
> topVer=AffinityTopologyVersion [topVer=-1, minorTopVer=0], reentry=null, 
> otherNodeId=null, otherVer=null, mappedDhtNodes=null, mappedNearNodes=null, 
> ownerVer=null, key=KeyCacheObjectImpl [val=1, hasValBytes=true], 
> 

[jira] [Closed] (IGNITE-1010) Wrong result for ServiceExample when it start without remote node

[Vasilisa Sidorova (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vasilisa Sidorova closed IGNITE-1010.
-
Assignee: (was: Vasilisa Sidorova)

> Wrong result for ServiceExample when it start without remote node
> -
>
> Key: IGNITE-1010
> URL: https://issues.apache.org/jira/browse/IGNITE-1010
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: sprint-6
> Environment: Ubuntu 14.04/Win7, community version 1.1.2, build 86, 
> rev. 420b6bd82501a3f47388865ecbdf53ce1162462c
>Reporter: Vasilisa Sidorova
> Fix For: ignite-1.4
>
> Attachments: ignite-6dc4264d.log
>
>
> -
> DESCRIPTION
> -
> Service Example doesn't stop running if it's running without remote node
> -
> STEPS FOR REPRODUCE
> -
> 1. Run ServiceExample
> -
> ACTUAL RESULT
> -
> Example doesn't stop running. There is TcpDiscoverySpi warning in the 
> example's node log:
> {noformat}
> [22:32:13,759][WARN ][tcp-client-disco-msg-worker-#4%null][TcpDiscoverySpi] 
> Failed to connect to any address from IP finder (will retry to join topology 
> in 2000ms): [/127.0.0.1:47507, /127.0.0.1:47504, /127.0.0.1:47502, 
> /127.0.0.1:47501, /127.0.0.1:47505, /127.0.0.1:47509, /127.0.0.1:47506, 
> /127.0.0.1:47508, /127.0.0.1:47503, /127.0.0.1:47500]
> {noformat}
> Look at the attached log
> -
> EXPECTED RESULT
> -
> Example stop running with message: "Server nodes not found (start data nodes 
> with ExampleNodeStartup class)"
> -
> ADDITIONAL INFO
> -
> 1. This is recent issue. It wasn't reproducible for community version 1.0.6 
> build #22, rev. 4b4158f752ee1565539ca4977464f8d7ee6de40b
> 2. The same  behavior is for streaming examples (StreamVisitorExample,  
> StreamTransformerExample)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1353) PortableContext.typeId() incorrectly resolves type ID for predefined system types.

[Denis Magda (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727712#comment-14727712
 ] 

Denis Magda commented on IGNITE-1353:
-

The bug, reported by this issue, wasn't reproduced in Java because a system 
type ID were used for a predefined type during serialization/deserialization 
and this was absolutely OK since the tests are using only Java nodes.

However, if the tests had been running in a cluster with both Java and platform 
(.Net, C++) notes we would have caught failures.

In any case I've added a test that will check that this bug will not appear in 
the future.

> PortableContext.typeId() incorrectly resolves type ID for predefined system 
> types.
> --
>
> Key: IGNITE-1353
> URL: https://issues.apache.org/jira/browse/IGNITE-1353
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Denis Magda
>Priority: Critical
> Fix For: ignite-1.4
>
>
> See PortableContext.typeId() method.
> First it checks whether type is "system", and only then try picking 
> predefiend ID. As a result, predefined types like IgniteBiTuple are written 
> with wrong IDs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1273) Tests from GridPortableBuilderAdditionalSelfTest were disabled.

[Alexey Goncharuk (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728539#comment-14728539
 ] 

Alexey Goncharuk commented on IGNITE-1273:
--

Changes look good to me.

> Tests from GridPortableBuilderAdditionalSelfTest were disabled.
> ---
>
> Key: IGNITE-1273
> URL: https://issues.apache.org/jira/browse/IGNITE-1273
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>
> Tests from {{GridPortableBuilderAdditionalSelfTest}} were disabled:
> - testCyclicArrayList
> - testCyclicArrays
> - testModifyObjectArray
> They have to be fixed or removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-1019) Resources are not injected on cache store factory

[Valentin Kulichenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Valentin Kulichenko closed IGNITE-1019.
---

> Resources are not injected on cache store factory
> -
>
> Key: IGNITE-1019
> URL: https://issues.apache.org/jira/browse/IGNITE-1019
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>  Labels: Usability
> Fix For: ignite-1.4
>
> Attachments: IGNITE-1019.patch
>
>
> Cache store factory may need to have access to some resources located in 
> Spring app context or node local map. Currently this is not possible because 
> {{@GridInstanceResource}}, {{@SpringApplicationContextResource}} and other 
> annotations are not processed for factories, only for created objects.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1344) Unable to build ignite examples under JDK1.8

[Artem Shutak (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728091#comment-14728091
 ] 

Artem Shutak commented on IGNITE-1344:
--

Sergey, can you provide reproduction scenario? 
I couldn't find how to build java8 examples at DEVNOTES. It should be fixed too.

> Unable to build ignite examples under JDK1.8
> 
>
> Key: IGNITE-1344
> URL: https://issues.apache.org/jira/browse/IGNITE-1344
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Artem Shutak
>Priority: Critical
> Fix For: ignite-1.4
>
>
> {noformat}
> [ERROR] COMPILATION ERROR : 
> [INFO] -
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[101,46]
>  cannot find symbol
>   symbol:   class Ignite
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[101,61]
>  cannot find symbol
>   symbol:   class IgniteMessaging
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[101,90]
>  cannot find symbol
>   symbol:   class IgniteException
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[139,9]
>  cannot find symbol
>   symbol:   class IgniteMessaging
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[140,15]
>  cannot find symbol
>   symbol:   class CountDownLatch
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[141,15]
>  cannot find symbol
>   symbol:   class CountDownLatch
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/datagrid/CacheAffinityExample.java:[44,51]
>  cannot find symbol
>   symbol:   class IgniteException
>   location: class 
> org.apache.ignite.examples.java8.datagrid.CacheAffinityExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[47,14]
>  cannot find symbol
>   symbol:   class Ignite
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[47,30]
>  cannot find symbol
>   symbol:   variable Ignition
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[48,18]
>  cannot find symbol
>   symbol:   variable ExamplesUtils
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[60,13]
>  cannot find symbol
>   symbol:   class ClusterGroup
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[65,13]
>  cannot find symbol
>   symbol:   class CountDownLatch
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[65,47]
>  cannot find symbol
>   symbol:   class CountDownLatch
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[66,13]
>  cannot find symbol
>   symbol:   

[jira] [Commented] (IGNITE-1351) Move portable API examples to Ignite

[Denis Magda (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727061#comment-14727061
 ] 

Denis Magda commented on IGNITE-1351:
-

Moved, modified the examples to Ignite. Checked that they are workable, added 
all the examples to the examples test suite.

Will check with TC that everything works fine.

> Move portable API examples to Ignite
> 
>
> Key: IGNITE-1351
> URL: https://issues.apache.org/jira/browse/IGNITE-1351
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Denis Magda
>
> We have to open source portable API examples that are a part of GridGain for 
> now.
> The examples must be reworked/enhanced in order to use the latest portable 
> API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-1145) Implement admin page

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov resolved IGNITE-1145.
--
Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

> Implement admin page
> 
>
> Key: IGNITE-1145
> URL: https://issues.apache.org/jira/browse/IGNITE-1145
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Andrey Novikov
>Assignee: Pavel Konstantinov
> Fix For: ignite-1.4
>
> Attachments: admin panel.png
>
>
> Need implement page with all users.
> For every user need display name, email, last login. Implement actions: 
> remove user, become this user, make admin.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-1266) GridUpdateNotifier needs to be fixed to return correct update version

[Andrey Novikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Novikov reassigned IGNITE-1266:
--

Assignee: Andrey Novikov

> GridUpdateNotifier needs to be fixed to return correct update version
> -
>
> Key: IGNITE-1266
> URL: https://issues.apache.org/jira/browse/IGNITE-1266
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Konstantin Boudnik
>Assignee: Andrey Novikov
>
> Currently, GridUpdateNotifier:116 points to external PHP script that returns 
> incorrect update version for currently running node software. Let's fix it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-1350) Platforms .Net: Add common cpp project to the solution

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov closed IGNITE-1350.
---

> Platforms .Net: Add common cpp project to the solution
> --
>
> Key: IGNITE-1350
> URL: https://issues.apache.org/jira/browse/IGNITE-1350
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: ignite-1.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-907) Implement generic Java -> platform communication mechanism.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov resolved IGNITE-907.

Resolution: Duplicate

> Implement generic Java -> platform communication mechanism.
> ---
>
> Key: IGNITE-907
> URL: https://issues.apache.org/jira/browse/IGNITE-907
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: sprint-4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: ignite-1.4
>
>
> Java must have ability to invoke arbitrary code on another platform. E.g., to 
> pass information about assemblies to load to .Net before other Ignite 
> components are started.
> At first glance, it should be a method like "invoke(int opType, long inData, 
> long outData)", where:
> 1) opType - type of operation to invoke on another platform.
> 2) inData - pointer to some data needs to be passed to the platform.
> 3) outData - pointer to some data written from platform back to Java.
> This method will be native. Implementors are free to pass anything to this 
> method as long as another side is able to handle it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1018) Node local map is not available when LifecycleEventType.BEFORE_NODE_START is processed in lifecycle bean

[Yakov Zhdanov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yakov Zhdanov updated IGNITE-1018:
--
Fix Version/s: (was: ignite-1.4)
   ignite-1.5

> Node local map is not available when LifecycleEventType.BEFORE_NODE_START is 
> processed in lifecycle bean
> 
>
> Key: IGNITE-1018
> URL: https://issues.apache.org/jira/browse/IGNITE-1018
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>  Labels: Usability, newbie
> Fix For: ignite-1.5
>
>
> Currently {{IgniteCluster.nodeLocalMap()}} method is guarded by gateway like 
> all others. But this is just a local concurrent map which is already 
> available at the moment LifecycleEventType.BEFORE_NODE_START is processed, so 
> I think it will be good to make it available in lifecycle bean.
> This can be useful if user needs to initialize some resources and put them to 
> node local map before node is started.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1243) HTTP REST: top command returns wrong result

[Sergey Kozlov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Kozlov updated IGNITE-1243:
--
 Assignee: (was: Sergey Kozlov)
   Labels: newbie  (was: )
Fix Version/s: (was: ignite-1.4)
   ignite-1.5
  Description: 
HTTP REST: top command returns wrong result via a client node if all server 
nodes left from topology: last server node is still in response.

Steps to repeat

1. Create client node config: copy examples/config/example-ignite.xml to 
examples/config/example-ignite-client.xml and set client mode:
{code:title=examples/config/example-ignite-client.xml|borderStyle=solid}
...





...
{code}

2. Copy libs/optional/ignite-rest-http directory into libs

3. Start two server nodes with example-ignite.xml: 
bin/ignite.sh examples/config/example-ignite.xml

4. Start client node with example-ignite-client.xml: 
bin/ignite.sh examples/config/example-ignite.xml

5. Now all nodes should print out following topology:
{noformat}
Topology snapshot [ver=3, servers=2, clients=1, CPUs=8, heap=3.0GB]
{noformat}

5. Open url http://127.0.0.1:8082/ignite?cmd=top in your browser
The response should be following
{noformat}
{"error":"","response":[{"attributes":null,"caches":null,"consistentId":"0:0:0:0:0:0:0:1,10.0.0.9,127.0.0.1,192.168.222.100,2001:0:9d38:6ab8:188c:2ebf:a1b7:c399:47500","defaultCacheMode":"","metrics":null,"nodeId":"4e5b8efb-eab9-4d24-9a3b-52e88c3220ae","tcpAddresses":["127.0.0.1","2001:0:9d38:6ab8:188c:2ebf:a1b7:c399","192.168.222.100","0:0:0:0:0:0:0:1","10.0.0.9"],"tcpHostNames":["rr","rr","rr"],"tcpPort":11211},{"attributes":null,"caches":null,"consistentId":"0:0:0:0:0:0:0:1,10.0.0.9,127.0.0.1,192.168.222.100,2001:0:9d38:6ab8:188c:2ebf:a1b7:c399:47501","defaultCacheMode":"","metrics":null,"nodeId":"c5fd0979-4f28-4e26-a3f9-37a3af78005b","tcpAddresses":["0:0:0:0:0:0:0:1","2001:0:9d38:6ab8:188c:2ebf:a1b7:c399","192.168.222.100","10.0.0.9","127.0.0.1"],"tcpHostNames":["rr","rr","rr"],"tcpPort":11212},{"attributes":null,"caches":null,"consistentId":"0:0:0:0:0:0:0:1,10.0.0.9,127.0.0.1,192.168.222.100,2001:0:9d38:6ab8:188c:2ebf:a1b7:c399:0","defaultCacheMode":"","metrics":null,"nodeId":"07bbe0ae-b0fc-4536-b5d0-64bb748e38a2","tcpAddresses":["10.0.0.9","0:0:0:0:0:0:0:1","2001:0:9d38:6ab8:188c:2ebf:a1b7:c399","192.168.222.100","127.0.0.1"],"tcpHostNames":["rr","rr","rr"],"tcpPort":11213}],"sessionToken":"","successStatus":0}
{noformat}

Take a look on NodeID:
{noformat}
{"error":"","response":[
..."nodeId":"4e5b8efb-eab9-4d24-9a3b-52e88c3220ae", 
..."nodeId":"c5fd0979-4f28-4e26-a3f9-37a3af78005b", 
..."nodeId":"07bbe0ae-b0fc-4536-b5d0-64bb748e38a2",
..."sessionToken":"","successStatus":0}
{noformat}

6. Stop both servee nodes and open the urlhttp://127.0.0.1:8082/ignite?cmd=top 
again:
{noformat}
{"error":"","response":[
..."nodeId":"c5fd0979-4f28-4e26-a3f9-37a3af78005b",
..."nodeId":"8d4c80da-3e64-43ff-aff0-112e45afa73f",],
..."sessionToken":"","successStatus":0}
{noformat}

First nodeid points out on disconnected server node, second one is non-existing 
id and there's no client node id.



  was:HTTP REST: top command returns wrong result via a client node if all 
server nodes left from topology: last server node is still in response.


> HTTP REST: top command returns wrong result 
> 
>
> Key: IGNITE-1243
> URL: https://issues.apache.org/jira/browse/IGNITE-1243
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Priority: Minor
>  Labels: newbie
> Fix For: ignite-1.5
>
>
> HTTP REST: top command returns wrong result via a client node if all server 
> nodes left from topology: last server node is still in response.
> Steps to repeat
> 1. Create client node config: copy examples/config/example-ignite.xml to 
> examples/config/example-ignite-client.xml and set client mode:
> {code:title=examples/config/example-ignite-client.xml|borderStyle=solid}
> ...
>  class="org.apache.ignite.configuration.IgniteConfiguration">
> 
> 
> 
> ...
> {code}
> 2. Copy libs/optional/ignite-rest-http directory into libs
> 3. Start two server nodes with example-ignite.xml: 
> bin/ignite.sh examples/config/example-ignite.xml
> 4. Start client node with example-ignite-client.xml: 
> bin/ignite.sh examples/config/example-ignite.xml
> 5. Now all nodes should print out following topology:
> {noformat}
> Topology snapshot [ver=3, servers=2, clients=1, CPUs=8, heap=3.0GB]
> {noformat}
> 5. Open url http://127.0.0.1:8082/ignite?cmd=top in your browser
> The response should be following
> {noformat}
> 

[jira] [Created] (IGNITE-1360) Extend platform processor lifecycle.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-1360:
---

 Summary: Extend platform processor lifecycle.
 Key: IGNITE-1360
 URL: https://issues.apache.org/jira/browse/IGNITE-1360
 Project: Ignite
  Issue Type: Sub-task
  Components: interop
Affects Versions: 1.1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: ignite-1.5


Currently platform processor lifecycle is the same as for all other processors 
wiht 4 callbacks: onStart, onKernalStart, onKernalStop, onStop.

This appears to be not enough for platforms. IN particular, it doesn't let us 
flush all write-behind store data correctly and doesn't allow for normal 
AFTER_NODE_STOP lifecycle callback.
Also it makes platfomr initialization more painful because some callbacks might 
reach the platform when it is not initialized yet.

To mitigate this problem we should extend platform processor with two more 
callbacks: "onBeforeStart" and "onAfterStop". Careful management of these 
callbacks will let us get rid of all aforementioned problems.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1353) PortableContext.typeId() incorrectly resolves type ID for predefined system types.

[Denis Magda (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727345#comment-14727345
 ] 

Denis Magda commented on IGNITE-1353:
-

Fixed conflicts between system, predefined and user types resolution.

Also found one more issue that required changes in the protocol - IGNITE-1358.
Implemented workaround as a part of this task until IGNITE-1358 is fixed.

Checking the changes with TC. 

> PortableContext.typeId() incorrectly resolves type ID for predefined system 
> types.
> --
>
> Key: IGNITE-1353
> URL: https://issues.apache.org/jira/browse/IGNITE-1353
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Denis Magda
>Priority: Critical
> Fix For: ignite-1.4
>
>
> See PortableContext.typeId() method.
> First it checks whether type is "system", and only then try picking 
> predefiend ID. As a result, predefined types like IgniteBiTuple are written 
> with wrong IDs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-1130) Daemon node says "clientMode=true" but I don't set this option in config

[Yakov Zhdanov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727349#comment-14727349
 ] 

Yakov Zhdanov edited comment on IGNITE-1130 at 9/2/15 1:39 PM:
---

According to org.apache.ignite.internal.GridKernalContextImpl, this is fine

{code}
public boolean clientNode() {
return cfg.isClientMode() || cfg.isDaemon();
}
{code}



was (Author: yzhdanov):
According to org.apache.ignite.internal.GridKernalContextImpl, this is fine

public boolean clientNode() {
return cfg.isClientMode() || cfg.isDaemon();
}


> Daemon node says "clientMode=true" but I don't set this option in config
> 
>
> Key: IGNITE-1130
> URL: https://issues.apache.org/jira/browse/IGNITE-1130
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: sprint-7
>Reporter: Pavel Konstantinov
>Assignee: Yakov Zhdanov
>Priority: Minor
> Fix For: ignite-1.4
>
>
> Start grid with any config.
> Connect visor with the same config.
> Verify visor console log.
> {code}
> >>> Local node [ID=A79AF592-72A6-4C4F-B5AD-230B9EC184B8, order=2, 
> >>> clientMode=true]
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1339) JVM Crash on TC Queries suite

[Yakov Zhdanov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yakov Zhdanov updated IGNITE-1339:
--
Attachment: logs.zip
hs_err_pid7933.log

> JVM Crash on TC Queries suite
> -
>
> Key: IGNITE-1339
> URL: https://issues.apache.org/jira/browse/IGNITE-1339
> Project: Ignite
>  Issue Type: Bug
>Reporter: Sergi Vladykin
>Priority: Critical
> Fix For: ignite-1.4
>
> Attachments: hs_err_pid7933.log, logs.zip
>
>
> {code}
> [07:13:33][org.apache.ignite:ignite-indexing] 
> [07:12:05,772][ERROR][ignite-#53702%sys-cache.IgniteCacheOffheapTieredMultithreadedSelfTest2%][GridMapQueryExecutor]
>  Failed to process message: GridQueryRequest [reqId=1712, pageSize=1024, 
> space=null, qrys=[GridCacheSqlQuery [alias=__Z0(), qry=SELECT
> [07:13:33][org.apache.ignite:ignite-indexing] "".PERSON._KEY __C0,
> [07:13:33][org.apache.ignite:ignite-indexing] "".PERSON._VAL __C1
> [07:13:33][org.apache.ignite:ignite-indexing] FROM "".PERSON
> [07:13:33][org.apache.ignite:ignite-indexing] WHERE (SALARY >= ?1) AND 
> (SALARY <= ?2), params=[9.48320472052535E8, 9.48321472052535E8]]], 
> topVer=AffinityTopologyVersion [topVer=3, minorTopVer=0], extraSpaces=null, 
> parts=[0, 1, 3, 6, 7, 8, 10, 11, 12, 13, 14, 17, 18, 19, 23, 25, 26, 27, 28, 
> 29, 30, 31, 32, 33, 34, 35, 36, 38, 39, 40, 41, 42, 44, 45, 46, 47, 51, 53, 
> 54, 55, 58, 59, 60, 61, 62, 63, 68, 69, 72, 73, 75, 76, 78, 80, 81, 82, 85, 
> 86, 87, 88, 89, 90, 91, 94, 95, 98, 101, 102, 105, 106, 109, 110, 111, 114, 
> 116, 117, 119, 120, 121, 122, 123, 125, 126, 127, 128, 129, 130, 133, 134, 
> 135, 137, 139, 140, 141, 145, 147, 149, 151, 153, 154, 155, 156, 157, 158, 
> 159, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 
> 175, 177, 178, 181, 183, 184, 186, 187, 188, 189, 190, 191, 192, 194, 195, 
> 196, 198, 199, 200, 201, 205, 206, 208, 209, 211, 212, 213, 214, 215, 217, 
> 218, 219, 220, 221, 222, 223, 224, 225, 227, 231, 232, 234, 236, 237, 240, 
> 241, 242, 243, 245, 246, 247, 248, 250, 251, 253, 254, 255, 257, 258, 259, 
> 260, 261, 263, 264, 265, 266, 268, 269, 270, 272, 273, 274, 276, 277, 278, 
> 279, 280, 282, 283, 285, 287, 288, 290, 292, 293, 294, 296, 298, 300, 301, 
> 302, 308, 309, 311, 314, 315, 317, 318, 319, 320, 321, 322, 324, 325, 327, 
> 328, 329, 330, 331, 332, 333, 334, 340, 342, 343, 345, 346, 350, 352, 353, 
> 354, 356, 358, 359, 360, 364, 365, 366, 368, 371, 372, 373, 375, 376, 379, 
> 380, 381, 382, 384, 386, 387, 388, 389, 390, 391, 392, 393, 394, 395, 396, 
> 397, 398, 399, 400, 401, 402, 403, 405, 407, 409, 410, 412, 413, 414, 416, 
> 417, 420, 421, 422, 423, 424, 429, 430, 431, 432, 433, 435, 436, 437, 438, 
> 439, 441, 442, 443, 444, 445, 446, 448, 449, 451, 453, 454, 456, 458, 459, 
> 460, 461, 462, 463, 464, 465, 466, 467, 469, 470, 471, 472, 473, 476, 477, 
> 479, 480, 482, 484, 486, 487, 488, 489, 490, 491, 492, 493, 495, 497, 501, 
> 502, 505, 507, 508, 511, 512, 513, 514, 515, 516, 517, 518, 519, 520, 521, 
> 522, 523, 524, 525, 526, 527, 528, 532, 534, 535, 537, 538, 541, 542, 543, 
> 544, 545, 546, 547, 548, 549, 550, 551, 552, 553, 557, 558, 559, 561, 562, 
> 563, 565, 566, 568, 569, 571, 573, 575, 576, 578, 579, 582, 583, 585, 586, 
> 590, 592, 593, 594, 595, 596, 597, 598, 599, 603, 604, 605, 606, 607, 608, 
> 609, 611, 612, 614, 615, 617, 618, 619, 620, 623, 624, 625, 627, 628, 629, 
> 631, 632, 633, 634, 635, 636, 637, 639, 641, 643, 644, 645, 646, 647, 648, 
> 649, 652, 654, 656, 657, 658, 659, 660, 662, 663, 664, 665, 667, 668, 669, 
> 671, 672, 673, 674, 675, 676, 677, 678, 679, 680, 681, 682, 683, 685, 686, 
> 687, 688, 689, 692, 694, 696, 698, 699, 700, 701, 703, 706, 707, 710, 712, 
> 713, 715, 716, 717, 718, 719, 723, 725, 727, 728, 729, 730, 732, 733, 734, 
> 735, 736, 738, 741, 742, 743, 744, 746, 747, 749, 751, 752, 753, 758, 759, 
> 760, 762, 764, 766, 767, 768, 769, 771, 773, 775, 776, 777, 780, 781, 782, 
> 783, 786, 789, 790, 791, 792, 796, 799, 801, 802, 804, 809, 813, 814, 815, 
> 816, 817, 819, 820, 821, 822, 824, 825, 827, 829, 830, 832, 833, 841, 843, 
> 844, 845, 846, 847, 848, 849, 850, 851, 852, 855, 857, 859, 860, 862, 864, 
> 865, 867, 868, 869, 870, 872, 874, 875, 876, 879, 881, 883, 884, 885, 886, 
> 887, 888, 889, 890, 892, 894, 896, 898, 899, 901, 902, 903, 904, 906, 908, 
> 909, 911, 912, 913, 914, 917, 918, 919, 920, 921, 922, 925, 927, 929, 931, 
> 932, 934, 935, 938, 939, 940, 941, 942, 943, 945, 946, 948, 949, 950, 952, 
> 955, 957, 959, 960, 961, 962, 964, 965, 967, 968, 969, 971, 972, 974, 975, 
> 976, 977, 979, 980, 981, 984, 985, 989, 990, 991, 993, 995, 997, 998, 999, 
> 1000, 1001, 1002, 1003, 1004, 1005, 1006, 1007, 1008, 1009, 1010, 1012, 1013, 
> 1014, 1015, 1016, 1017, 1019, 1020, 1021, 1022]]
> 

[jira] [Commented] (IGNITE-1351) Move portable API examples to Ignite

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727063#comment-14727063
 ] 

ASF GitHub Bot commented on IGNITE-1351:


GitHub user dmagda opened a pull request:

https://github.com/apache/ignite/pull/57

ignite-1351: move portable API examples

Refer to https://issues.apache.org/jira/browse/IGNITE-1351 for more info

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dmagda/incubator-ignite ignite-1351

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/57.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #57


commit ad887c16975ef4a06d19547302e455724552fe83
Author: Denis Magda 
Date:   2015-09-02T09:11:26Z

ignite-1351: moved (open sourced) portable API examples from GridGain to 
Ignite




> Move portable API examples to Ignite
> 
>
> Key: IGNITE-1351
> URL: https://issues.apache.org/jira/browse/IGNITE-1351
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Denis Magda
>
> We have to open source portable API examples that are a part of GridGain for 
> now.
> The examples must be reworked/enhanced in order to use the latest portable 
> API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-924) Add user authentication, space

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov resolved IGNITE-924.
-
Resolution: Fixed

> Add user authentication, space
> --
>
> Key: IGNITE-924
> URL: https://issues.apache.org/jira/browse/IGNITE-924
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
>Assignee: Alexey Kuznetsov
> Fix For: ignite-1.4
>
> Attachments: login.png, signup.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-924) Add user authentication, space

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov closed IGNITE-924.
---
Assignee: (was: Alexey Kuznetsov)

> Add user authentication, space
> --
>
> Key: IGNITE-924
> URL: https://issues.apache.org/jira/browse/IGNITE-924
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
> Fix For: ignite-1.4
>
> Attachments: login.png, signup.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-849) Implement header, footer and left navigation menu

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov closed IGNITE-849.
---
Assignee: (was: Alexey Kuznetsov)

> Implement header, footer and left navigation menu
> -
>
> Key: IGNITE-849
> URL: https://issues.apache.org/jira/browse/IGNITE-849
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Alexey Goncharuk
> Fix For: ignite-1.4
>
> Attachments: header_footer_menu.pdf
>
>
> Screenshot attached



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-849) Implement header, footer and left navigation menu

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov resolved IGNITE-849.
-
Resolution: Fixed

> Implement header, footer and left navigation menu
> -
>
> Key: IGNITE-849
> URL: https://issues.apache.org/jira/browse/IGNITE-849
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Alexey Goncharuk
>Assignee: Alexey Kuznetsov
> Fix For: ignite-1.4
>
> Attachments: header_footer_menu.pdf
>
>
> Screenshot attached



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-1241) Server node prints out failure detection warning if a client node connected

[Ilya Suntsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ilya Suntsov closed IGNITE-1241.


Fix confirmed

> Server node prints out failure detection warning if a client node connected
> ---
>
> Key: IGNITE-1241
> URL: https://issues.apache.org/jira/browse/IGNITE-1241
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Ilya Suntsov
>Priority: Critical
> Fix For: ignite-1.4
>
>
> 1. Start 1 server node.
> 2. Start 1 client node.
> 3. Server node prints out following message in a few seconds after topology 
> update:
> {noformat}
> [16:57:49,376][INFO][disco-event-worker-#45%null%][GridDiscoveryManager] 
> Added new node to topology: TcpDiscoveryNode [id=531641e9-a279-41d4-b2ad-75bc
> ecb1f8b3, addrs=[0:0:0:0:0:0:0:1, 10.0.0.9, 127.0.0.1, 192.168.222.100, 
> 2001:0:5ef5:79fd:34d0:3c29:f5ff:fff6], sockAddrs=[rr/192.168.222.100:0, /0:0:0
> :0:0:0:0:1:0, rr/192.168.222.100:0, /10.0.0.9:0, rr/192.168.222.100:0, 
> /127.0.0.1:0, /192.168.222.100:0, /2001:0:5ef5:79fd:34d0:3c29:f5ff:fff6:0], 
> dis
> cPort=0, order=2, intOrder=2, lastDataReceivedTime=1439387869353, loc=false, 
> ver=1.4.1#20150812-sha1:d5986c26, isClient=true]
> [16:57:49,381][INFO][disco-event-worker-#45%null%][GridDiscoveryManager] 
> Topology snapshot [ver=2, servers=1, clients=1, CPUs=8, heap=2.0GB]
> [16:57:59,362][INFO][tcp-disco-msg-worker-#2%null][TcpDiscoverySpi] Local 
> node seems to be disconnected from topology (failure detection timeout is re
> ached): [failureDetectionTimeout=1, connCheckFreq=]
> [16:57:59,464][INFO][tcp-disco-msg-worker-#2%null][TcpDiscoverySpi] Local 
> node seems to be disconnected from topology (failure detection timeout is re
> ached): [failureDetectionTimeout=1, connCheckFreq=]
> [16:58:01,464][INFO][tcp-disco-msg-worker-#2%null][TcpDiscoverySpi] Local 
> node seems to be disconnected from topology (failure detection timeout is re
> ached): [failureDetectionTimeout=1, connCheckFreq=]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-1354) Platform: AFTER_GRID_STOP lifecycle events do not work

[Pavel Tupitsyn (JIRA)]

Pavel  Tupitsyn created IGNITE-1354:
---

 Summary: Platform: AFTER_GRID_STOP lifecycle events do not work
 Key: IGNITE-1354
 URL: https://issues.apache.org/jira/browse/IGNITE-1354
 Project: Ignite
  Issue Type: Bug
  Components: interop
Affects Versions: 1.1.4
Reporter: Pavel  Tupitsyn
Assignee: Pavel  Tupitsyn
 Fix For: ignite-1.4


Grid is stopped and callback from Java does not work.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-1121) Implementation of control-center-agent as proxy between web-server and Ignite cluster

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov resolved IGNITE-1121.
--
Resolution: Fixed
  Assignee: Alexey Kuznetsov  (was: Sergey Evdokimov)

> Implementation of control-center-agent as proxy between web-server and Ignite 
> cluster
> -
>
> Key: IGNITE-1121
> URL: https://issues.apache.org/jira/browse/IGNITE-1121
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Sergey Evdokimov
>Assignee: Alexey Kuznetsov
> Fix For: ignite-1.4
>
>
> We need to implement web-agent that will work like a proxy between web-server 
> and Ignite cluster to:
>1) collect metrics for grid monitoring
>2) execute sql queries



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-1218) Show how configuration changes as the user updates the fields.

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov reassigned IGNITE-1218:


Assignee: Vasiliy Sisko  (was: Alexey Kuznetsov)

Vasiliy, I implemented preview prototype. Please finish implementation.

> Show how configuration changes as the user updates the fields.
> --
>
> Key: IGNITE-1218
> URL: https://issues.apache.org/jira/browse/IGNITE-1218
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Dmitriy Setrakyan
>Assignee: Vasiliy Sisko
> Fix For: ignite-1.5
>
>
> It would be nice if we allocated some area to show the current configuration 
> tabs (just like on summary screen) as the user keeps entering new data.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-1145) Implement admin page

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov closed IGNITE-1145.
--
Assignee: (was: Pavel Konstantinov)

> Implement admin page
> 
>
> Key: IGNITE-1145
> URL: https://issues.apache.org/jira/browse/IGNITE-1145
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Andrey Novikov
> Fix For: ignite-1.4
>
> Attachments: admin panel.png
>
>
> Need implement page with all users.
> For every user need display name, email, last login. Implement actions: 
> remove user, become this user, make admin.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1348) Move .Net platform from GridGain to Ignite.

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel  Tupitsyn updated IGNITE-1348:

Description: 
It is necessary to move the whole .Net module from GridGain to Ignite.
We must:
1) Rename GridFactory -> Ignition.
2) Rename IGrid -> IIgnite
3) Rename all other "Grid*" classes (if any) to Ignite's counterparts.
4) Set correct Apache headers everywhere.
5) Ensure RAT exclusing are set in IGNITE_HOME/parent module.

Exclude DR, Security, Product, Licensing, and corresponding events.

Once ticket is completed, it is necessary to create another one to update 
Ignite's build procedure.

Fixes to port from GG:
https://issues.apache.org/jira/browse/IGNITE-1354

  was:
It is necessary to move the whole .Net module from GridGain to Ignite.
We must:
1) Rename GridFactory -> Ignition.
2) Rename IGrid -> IIgnite
3) Rename all other "Grid*" classes (if any) to Ignite's counterparts.
4) Set correct Apache headers everywhere.
5) Ensure RAT exclusing are set in IGNITE_HOME/parent module.

Exclude DR, Security, Product, Licensing, and corresponding events.

Once ticket is completed, it is necessary to create another one to update 
Ignite's build procedure.


> Move .Net platform from GridGain to Ignite.
> ---
>
> Key: IGNITE-1348
> URL: https://issues.apache.org/jira/browse/IGNITE-1348
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Blocker
> Fix For: ignite-1.4
>
>
> It is necessary to move the whole .Net module from GridGain to Ignite.
> We must:
> 1) Rename GridFactory -> Ignition.
> 2) Rename IGrid -> IIgnite
> 3) Rename all other "Grid*" classes (if any) to Ignite's counterparts.
> 4) Set correct Apache headers everywhere.
> 5) Ensure RAT exclusing are set in IGNITE_HOME/parent module.
> Exclude DR, Security, Product, Licensing, and corresponding events.
> Once ticket is completed, it is necessary to create another one to update 
> Ignite's build procedure.
> Fixes to port from GG:
> https://issues.apache.org/jira/browse/IGNITE-1354



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1347) Create normal platform processor.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-1347:

Fix Version/s: (was: ignite-1.4)
   ignite-1.5

> Create normal platform processor.
> -
>
> Key: IGNITE-1347
> URL: https://issues.apache.org/jira/browse/IGNITE-1347
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: ignite-1.5
>
>
> Currently we have no-op platform processor implementation in "core" module. 
> We need to implement fully-fledged processor in "platforms" module.
> Processor creation sequence should be as follows:
> 1) Ask plugins for their processor. Stop in case of non-null result.
> 2) Check for PlatformConfiguration. If not null - create fully-fledged 
> processor through reflection if it is present in classpath. Stop if created.
> 3) Return no-op processor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1332) Platforms: review all TODOs in Java code.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-1332:

Fix Version/s: (was: ignite-1.4)
   ignite-1.5

> Platforms: review all TODOs in Java code.
> -
>
> Key: IGNITE-1332
> URL: https://issues.apache.org/jira/browse/IGNITE-1332
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: ignite-1.5
>
>
> It is necessary to review all "TODO" artifacts (if any) which could 
> potentially came form GridGain code base during migration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1335) Platforms .Net: Move Grid to Ignite

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-1335:

Fix Version/s: (was: ignite-1.4)
   ignite-1.5

> Platforms .Net: Move Grid to Ignite
> ---
>
> Key: IGNITE-1335
> URL: https://issues.apache.org/jira/browse/IGNITE-1335
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: ignite-1.5
>
>
> * fix PortableMarshaller.GetMetadata
> * Remove PortableMarshaller.GetAllMetadata
> * fix PortableMarshaller.FinishMarshal



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1273) Tests from GridPortableBuilderAdditionalSelfTest were disabled.

[Denis Magda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda updated IGNITE-1273:

Assignee: Alexey Goncharuk  (was: Denis Magda)

> Tests from GridPortableBuilderAdditionalSelfTest were disabled.
> ---
>
> Key: IGNITE-1273
> URL: https://issues.apache.org/jira/browse/IGNITE-1273
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>
> Tests from {{GridPortableBuilderAdditionalSelfTest}} were disabled:
> - testCyclicArrayList
> - testCyclicArrays
> - testModifyObjectArray
> They have to be fixed or removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-1320) Platforms: PlatformContext.createNativeException() must return PlatformNativeException.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov resolved IGNITE-1320.
-
Resolution: Fixed

> Platforms: PlatformContext.createNativeException() must return 
> PlatformNativeException.
> ---
>
> Key: IGNITE-1320
> URL: https://issues.apache.org/jira/browse/IGNITE-1320
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: ignite-1.4
>
>
> To achieve this we probably must move all platform exceptions from "platform" 
> to "core" module, which is perfectly fine.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1324) Optimize platform entry processor for local execution.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-1324:

Fix Version/s: (was: ignite-1.4)
   ignite-1.5

> Optimize platform entry processor for local execution.
> --
>
> Key: IGNITE-1324
> URL: https://issues.apache.org/jira/browse/IGNITE-1324
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: ignite-1.5
>
>
> Currently entry processor is passed to Java as if it was remote, even for 
> local execution. As a result, local execution require additional 
> marshal-unmarshal cycle to execute it on native platform (that is, pointer 
> field is always 0)).
> We need to optimize it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-1353) PortableContext.typeId() incorrectly resolves type ID for predefined system types.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-1353:
---

 Summary: PortableContext.typeId() incorrectly resolves type ID for 
predefined system types.
 Key: IGNITE-1353
 URL: https://issues.apache.org/jira/browse/IGNITE-1353
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: ignite-1.4


See PortableContext.typeId() method.
First it checks whether type is "system", and only then try picking predefiend 
ID. As a result, predefined types like IgniteBiTuple are written with wrong IDs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1213) Add mark and alert in case of not saved changes

[Pavel Konstantinov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727151#comment-14727151
 ] 

Pavel Konstantinov commented on IGNITE-1213:


Tested.

> Add mark and alert in case of not saved changes
> ---
>
> Key: IGNITE-1213
> URL: https://issues.apache.org/jira/browse/IGNITE-1213
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: ignite-1.4
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: ignite-1.4
>
> Attachments: #_IGNITE-1213_Confirm_on_unsaved_changes.patch, 
> ignite-1213 v1.png, ignite-1213 v2.png, ignite-1213 v3.png
>
>
> We need to add a mark (some icon, usually floppy disk) and alert when user 
> modify data, but does not hit "Save" button.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1289) Platforms .Net: Move portable marshaller to Ignite.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-1289:

Fix Version/s: (was: ignite-1.4)
   ignite-1.5

> Platforms .Net: Move portable marshaller to Ignite.
> ---
>
> Key: IGNITE-1289
> URL: https://issues.apache.org/jira/browse/IGNITE-1289
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Critical
> Fix For: ignite-1.5
>
>
> We need to move portable serialziation logic to Ignite. It is important that 
> initially we _must_not_ move pre-configured classes to Ignite. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1351) Move portable API examples to Ignite

[Denis Magda (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727081#comment-14727081
 ] 

Denis Magda commented on IGNITE-1351:
-

Link to the pull-request 
https://github.com/apache/ignite/pull/57

> Move portable API examples to Ignite
> 
>
> Key: IGNITE-1351
> URL: https://issues.apache.org/jira/browse/IGNITE-1351
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Denis Magda
>
> We have to open source portable API examples that are a part of GridGain for 
> now.
> The examples must be reworked/enhanced in order to use the latest portable 
> API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-1353) PortableContext.typeId() incorrectly resolves type ID for predefined system types.

[Denis Magda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda reassigned IGNITE-1353:
---

Assignee: Denis Magda

> PortableContext.typeId() incorrectly resolves type ID for predefined system 
> types.
> --
>
> Key: IGNITE-1353
> URL: https://issues.apache.org/jira/browse/IGNITE-1353
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Denis Magda
>Priority: Critical
> Fix For: ignite-1.4
>
>
> See PortableContext.typeId() method.
> First it checks whether type is "system", and only then try picking 
> predefiend ID. As a result, predefined types like IgniteBiTuple are written 
> with wrong IDs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1354) Platform: AFTER_GRID_STOP lifecycle events do not work

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727121#comment-14727121
 ] 

ASF GitHub Bot commented on IGNITE-1354:


GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/58

IGNITE-1354 Platform: AFTER_GRID_STOP lifecycle events do not work

Filter AfterStop events on Java side.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-1354

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/58.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #58


commit d734b6e4dfcb79c7707f3f55abc445674e23409a
Author: ptupitsyn 
Date:   2015-09-02T10:08:56Z

IGNITE-1354 Platform: AFTER_GRID_STOP lifecycle events do not work

Filter AfterStop events on Java side.




> Platform: AFTER_GRID_STOP lifecycle events do not work
> --
>
> Key: IGNITE-1354
> URL: https://issues.apache.org/jira/browse/IGNITE-1354
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: ignite-1.4
>
>
> Grid is stopped and callback from Java does not work.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1257) Implement agent download dialog for page with such functionality

[Andrey Novikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Novikov updated IGNITE-1257:
---
Description: 
* Implement common agent download dialog as template use load from metadata 
dialog.
* Generate agent archive with properties file filled by user and server 
settings (for zero configuration run of agent).
* Use token instead of login, password in agent configuration.


  was:
* Implement common agent download dialog as template use load from metadata 
dialog.
* Generate agent archive with properties file filled by user and server 
settings (for zero configuration run of agent).



> Implement agent download dialog for page with such functionality
> 
>
> Key: IGNITE-1257
> URL: https://issues.apache.org/jira/browse/IGNITE-1257
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
> Fix For: ignite-1.4
>
>
> * Implement common agent download dialog as template use load from metadata 
> dialog.
> * Generate agent archive with properties file filled by user and server 
> settings (for zero configuration run of agent).
> * Use token instead of login, password in agent configuration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-1355) Potential NPE in CacheAffinityProxy

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-1355:


 Summary: Potential NPE in CacheAffinityProxy
 Key: IGNITE-1355
 URL: https://issues.apache.org/jira/browse/IGNITE-1355
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: ignite-1.4
Reporter: Semen Boikov
Assignee: Yakov Zhdanov
 Fix For: ignite-1.5


NPE was observed on TC:
{noformat}
java.lang.NullPointerException
at 
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor$AffinityInfo.access$1800(GridAffinityProcessor.java:537)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor$CacheAffinityProxy.mapPartitionToPrimaryAndBackups(GridAffinityProcessor.java:879)
at 
org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:423)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.IgniteCacheCrossCacheTxFailoverTest.crossCacheTxFailover(IgniteCacheCrossCacheTxFailoverTest.java:355)
{noformat}

As I see method CacheAffinityProxy.cache() can return null, but there are no 
checks for null.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-1350) Platforms .Net: Add common cpp project to the solution

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel  Tupitsyn resolved IGNITE-1350.
-
Resolution: Invalid

Close because it'll be done as part of IGNITE-1348

> Platforms .Net: Add common cpp project to the solution
> --
>
> Key: IGNITE-1350
> URL: https://issues.apache.org/jira/browse/IGNITE-1350
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: ignite-1.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-908) Introduce interop handle.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov closed IGNITE-908.
--

> Introduce interop handle.
> -
>
> Key: IGNITE-908
> URL: https://issues.apache.org/jira/browse/IGNITE-908
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: sprint-4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: ignite-1.4
>
>
> We need to introduce generic handle which will be used for communication from 
> platform to Java.+



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1344) Unable to build ignite examples under JDK1.8

[Yakov Zhdanov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yakov Zhdanov updated IGNITE-1344:
--
Assignee: Artem Shutak  (was: Yakov Zhdanov)

> Unable to build ignite examples under JDK1.8
> 
>
> Key: IGNITE-1344
> URL: https://issues.apache.org/jira/browse/IGNITE-1344
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Artem Shutak
>Priority: Critical
> Fix For: ignite-1.4
>
>
> {noformat}
> [ERROR] COMPILATION ERROR : 
> [INFO] -
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[101,46]
>  cannot find symbol
>   symbol:   class Ignite
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[101,61]
>  cannot find symbol
>   symbol:   class IgniteMessaging
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[101,90]
>  cannot find symbol
>   symbol:   class IgniteException
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[139,9]
>  cannot find symbol
>   symbol:   class IgniteMessaging
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[140,15]
>  cannot find symbol
>   symbol:   class CountDownLatch
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[141,15]
>  cannot find symbol
>   symbol:   class CountDownLatch
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/datagrid/CacheAffinityExample.java:[44,51]
>  cannot find symbol
>   symbol:   class IgniteException
>   location: class 
> org.apache.ignite.examples.java8.datagrid.CacheAffinityExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[47,14]
>  cannot find symbol
>   symbol:   class Ignite
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[47,30]
>  cannot find symbol
>   symbol:   variable Ignition
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[48,18]
>  cannot find symbol
>   symbol:   variable ExamplesUtils
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[60,13]
>  cannot find symbol
>   symbol:   class ClusterGroup
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[65,13]
>  cannot find symbol
>   symbol:   class CountDownLatch
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[65,47]
>  cannot find symbol
>   symbol:   class CountDownLatch
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> /D:/1.4/gridgain-community-fabric-1.4.1-QAIS3103/examples/src/main/java8/org/apache/ignite/examples/java8/messaging/MessagingExample.java:[66,13]
>  cannot find symbol
>   symbol:   class CountDownLatch
>   location: class org.apache.ignite.examples.java8.messaging.MessagingExample
> [ERROR] 
> 

[jira] [Commented] (IGNITE-1016) Add excludeNeighbors and backupFilter to FairAffinityFunction

[Yakov Zhdanov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727274#comment-14727274
 ] 

Yakov Zhdanov commented on IGNITE-1016:
---

Val, can you please review the changes?

> Add excludeNeighbors and backupFilter to FairAffinityFunction
> -
>
> Key: IGNITE-1016
> URL: https://issues.apache.org/jira/browse/IGNITE-1016
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>  Labels: Usability
> Fix For: ignite-1.4
>
> Attachments: ignite-1016.patch, ignite-1016.patch
>
>
> These properties are currently available only for 
> {{RendezvousAffinityFunction}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1019) Resources are not injected on cache store factory

[Yakov Zhdanov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yakov Zhdanov updated IGNITE-1019:
--
Assignee: Valentin Kulichenko  (was: Yakov Zhdanov)

> Resources are not injected on cache store factory
> -
>
> Key: IGNITE-1019
> URL: https://issues.apache.org/jira/browse/IGNITE-1019
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>  Labels: Usability
> Fix For: ignite-1.4
>
> Attachments: IGNITE-1019.patch
>
>
> Cache store factory may need to have access to some resources located in 
> Spring app context or node local map. Currently this is not possible because 
> {{@GridInstanceResource}}, {{@SpringApplicationContextResource}} and other 
> annotations are not processed for factories, only for created objects.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1016) Add excludeNeighbors and backupFilter to FairAffinityFunction

[Yakov Zhdanov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yakov Zhdanov updated IGNITE-1016:
--
Assignee: Valentin Kulichenko  (was: Yakov Zhdanov)

> Add excludeNeighbors and backupFilter to FairAffinityFunction
> -
>
> Key: IGNITE-1016
> URL: https://issues.apache.org/jira/browse/IGNITE-1016
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>  Labels: Usability
> Fix For: ignite-1.4
>
> Attachments: ignite-1016.patch, ignite-1016.patch
>
>
> These properties are currently available only for 
> {{RendezvousAffinityFunction}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-993) IllegalArgumentException if two nodes create and drop caches independently

[Semen Boikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov resolved IGNITE-993.
-
Resolution: Fixed

Implemented fix for the issue with concurrent access/modification of 
'registeredCaches' collection (see attached patch), reviewed with Alexey G.

> IllegalArgumentException if two nodes create and drop caches independently 
> ---
>
> Key: IGNITE-993
> URL: https://issues.apache.org/jira/browse/IGNITE-993
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-5
>Reporter: Sergey Kozlov
>Assignee: Semen Boikov
> Fix For: ignite-1.4
>
> Attachments: 993.patch, CacheStreamerStartStopCacheTest.java, log.zip
>
>
> Note: use attached file
> The logic of test:
> Start two nodes and each node does in loop following: create cache, load 10k 
> keys via streamer, drop cache.
> Steps:
> 1. Start 1st node by CacheStreamerStartStopCache
> 2. Wait "Iteration 100" message in output
> 3. Start 2nd node by CacheStreamerStartStopCache
> 1st node output:
> {noformat}
> [15:58:33,395][INFO ][exchange-worker-#49%null%][GridDhtPreloader] 
>  Starting rebalancing in ASYNC mode: 
> server_cache_1209_884
> [15:58:33,396][INFO ][preloader-demand-worker-#824%null%][GridDhtPreloader] 
>  Completed rebalancing in ASYNC mode 
> [cache=server_cache_1209_884, time=0 ms]
> [15:58:33,433][INFO ][disco-event-worker-#46%null%][GridDiscoveryManager] 
> Added new node to topology: TcpDiscoveryNode 
> [id=407e2385-405d-4ce1-85c1-2641fd81b217, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
> 10.0.0.5, 192.168.56.1, 2001:db8:85a3:0:0:8a2e:370:7334], 
> sockAddrs=[/0:0:0:0:0:0:0:1:47501, /127.0.0.1:47501, rr/192.168.56.1:47501, 
> /10.0.0.5:47501, rr/192.168.56.1:47501, /192.168.56.1:47501, 
> rr/192.168.56.1:47501, /2001:db8:85a3:0:0:8a2e:370:7334:47501], 
> discPort=47501, order=2, intOrder=2, loc=false, 
> ver=1.1.1#20150604-sha1:a6ea325c, isClient=false]
> [15:58:33,434][INFO ][disco-event-worker-#46%null%][GridDiscoveryManager] 
> Topology snapshot [ver=2, nodes=2, CPUs=8, heap=2.0GB]
> [15:58:33] (err) Failed to execute compound future reducer: Compound future 
> listener: GridCompoundFuture [lsnrCalls=0, finished=false, rdc=null, 
> init=true, res=java.util.concurrent.atomic.AtomicMarkableReference@78237daf, 
> err=null, done=false, cancelled=false, err=null, futs=[true]]class 
> org.apache.ignite.IgniteCheckedException: Cache is not configured: 
> server_cache_1209_884
>   at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6732)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:124)
>   at 
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:304)
>   at 
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:295)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter$ArrayListener.apply(GridFutureAdapter.java:419)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter$ArrayListener.apply(GridFutureAdapter.java:402)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:241)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListeners(GridFutureAdapter.java:229)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:359)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:325)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:1256)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:235)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:690)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:58)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:653)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: Cache is not configured: 
> server_cache_1209_884
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.jcache(GridCacheProcessor.java:2715)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:91)
>   at 
> 

[jira] [Commented] (IGNITE-1099) Need to cleanup git

[Yakov Zhdanov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727325#comment-14727325
 ] 

Yakov Zhdanov commented on IGNITE-1099:
---

I dont see anything to review - patch, pull request, branch. What should I 
review?

> Need to cleanup git
> ---
>
> Key: IGNITE-1099
> URL: https://issues.apache.org/jira/browse/IGNITE-1099
> Project: Ignite
>  Issue Type: Bug
>Reporter: Yakov Zhdanov
>Assignee: Artem Shutak
> Fix For: ignite-1.5
>
>
> * Need to resurrect tool (formerly named JiraBranchesToHtml) that shows up 
> branches for closed tickets in JIRA
> * Need to go through the branches and determine what branches are useless:
> ** ignite-sprint-*
> ** branches with no activity for recent months



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1099) Need to cleanup git

[Yakov Zhdanov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yakov Zhdanov updated IGNITE-1099:
--
Assignee: Artem Shutak  (was: Yakov Zhdanov)

> Need to cleanup git
> ---
>
> Key: IGNITE-1099
> URL: https://issues.apache.org/jira/browse/IGNITE-1099
> Project: Ignite
>  Issue Type: Bug
>Reporter: Yakov Zhdanov
>Assignee: Artem Shutak
> Fix For: ignite-1.5
>
>
> * Need to resurrect tool (formerly named JiraBranchesToHtml) that shows up 
> branches for closed tickets in JIRA
> * Need to go through the branches and determine what branches are useless:
> ** ignite-sprint-*
> ** branches with no activity for recent months



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-1356) Move platforms Java public API to Ignite.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov resolved IGNITE-1356.
-
Resolution: Fixed

> Move platforms Java public API to Ignite.
> -
>
> Key: IGNITE-1356
> URL: https://issues.apache.org/jira/browse/IGNITE-1356
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: ignite-1.5
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-1357) Move Java bootstrap logic to Ignite.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-1357:
---

 Summary: Move Java bootstrap logic to Ignite.
 Key: IGNITE-1357
 URL: https://issues.apache.org/jira/browse/IGNITE-1357
 Project: Ignite
  Issue Type: Sub-task
  Components: interop
Affects Versions: 1.1.4
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Critical
 Fix For: ignite-1.5






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-1356) Move platforms Java public API to Ignite.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov closed IGNITE-1356.
---

> Move platforms Java public API to Ignite.
> -
>
> Key: IGNITE-1356
> URL: https://issues.apache.org/jira/browse/IGNITE-1356
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: ignite-1.5
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1111) Scalar ping pong example failed with NPE

[Yakov Zhdanov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yakov Zhdanov updated IGNITE-:
--
Assignee: Sergey Kozlov  (was: Yakov Zhdanov)

> Scalar ping pong example failed with NPE
> 
>
> Key: IGNITE-
> URL: https://issues.apache.org/jira/browse/IGNITE-
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: sprint-7
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
> Fix For: ignite-1.4
>
>
> Note: sporadic failure. 
> ScalarPingPongExample failed once for Windows when started with one server 
> node by bin\ignite.bat examples\config\example-ignite.xml:
> Please find below the example output:
> {noformat}
> [19:51:39,648][INFO][main][GridDiscoveryManager] Topology snapshot [ver=70, 
> server nodes=2, client nodes=0, CPUs=8, heap=2.0GB]
> [19:51:39,700][INFO][main][GridDeploymentLocalStore] Class locally deployed: 
> class org.apache.ignite.scalar.examples.ScalarPingPongExample$$anon$1
> PONG
> PONG
> PONG
> PONG
> PONG
> PONG
> PONG
> PONG
> PONG
> PONG
> [19:51:39,722][INFO][main][GridTcpRestProtocol] Command protocol successfully 
> stopped: TCP binary
> [19:51:39,726][INFO][main][GridJettyRestProtocol] Command protocol 
> successfully stopped: Jetty REST
> [19:51:39,733][SEVERE][tcp-disco-sock-reader-#11%null][TcpDiscoverySpi] 
> Runtime error caught during grid runnable execution: Socket reader [id=147, 
> name=tcp-disco-sock-reader-#11%null, nodeId=null]
> java.lang.NullPointerException
>   at 
> java.net.DualStackPlainSocketImpl.checkAndReturnNativeFD(DualStackPlainSocketImpl.java:250)
>   at 
> java.net.DualStackPlainSocketImpl.socketSetOption(DualStackPlainSocketImpl.java:179)
>   at 
> java.net.AbstractPlainSocketImpl.setOption(AbstractPlainSocketImpl.java:269)
>   at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:176)
>   at java.net.Socket.setKeepAlive(Socket.java:1268)
>   at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$SocketReader.body(ServerImpl.java:4089)
>   at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [19:51:39,734][INFO][main][GridCacheProcessor] Stopped cache: 
> ignite-marshaller-sys-cache
> [19:51:39,735][INFO][main][GridCacheProcessor] Stopped cache: ignite-sys-cache
> [19:51:39,735][INFO][main][GridCacheProcessor] Stopped cache: 
> ignite-atomics-sys-cache
> [19:51:39,735][INFO][main][GridCacheProcessor] Stopped cache: datastructures_0
> [19:51:39,735][INFO][main][GridCacheProcessor] Stopped cache: datastructures_1
> [19:51:39,736][INFO][main][GridDeploymentLocalStore] Removed undeployed 
> class: GridDeployment [ts=1436457099529, depMode=SHARED, 
> clsLdr=sun.misc.Launcher$AppClassLoader@3f677737, 
> clsLdrId=757a3837e41-e889dd6a-3dcc-4a3f-8716-59348d37edc2, userVer=0, 
> loc=true, 
> sampleClsName=org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionFullMap,
>  pendingUndeploy=false, undeployed=true, usage=0]
> [19:51:39,738][INFO][main][IgniteKernal] 
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-993) IllegalArgumentException if two nodes create and drop caches independently

[Semen Boikov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov updated IGNITE-993:

Attachment: 993.patch

Attached patch with fix.

> IllegalArgumentException if two nodes create and drop caches independently 
> ---
>
> Key: IGNITE-993
> URL: https://issues.apache.org/jira/browse/IGNITE-993
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-5
>Reporter: Sergey Kozlov
>Assignee: Semen Boikov
> Fix For: ignite-1.4
>
> Attachments: 993.patch, CacheStreamerStartStopCacheTest.java, log.zip
>
>
> Note: use attached file
> The logic of test:
> Start two nodes and each node does in loop following: create cache, load 10k 
> keys via streamer, drop cache.
> Steps:
> 1. Start 1st node by CacheStreamerStartStopCache
> 2. Wait "Iteration 100" message in output
> 3. Start 2nd node by CacheStreamerStartStopCache
> 1st node output:
> {noformat}
> [15:58:33,395][INFO ][exchange-worker-#49%null%][GridDhtPreloader] 
>  Starting rebalancing in ASYNC mode: 
> server_cache_1209_884
> [15:58:33,396][INFO ][preloader-demand-worker-#824%null%][GridDhtPreloader] 
>  Completed rebalancing in ASYNC mode 
> [cache=server_cache_1209_884, time=0 ms]
> [15:58:33,433][INFO ][disco-event-worker-#46%null%][GridDiscoveryManager] 
> Added new node to topology: TcpDiscoveryNode 
> [id=407e2385-405d-4ce1-85c1-2641fd81b217, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
> 10.0.0.5, 192.168.56.1, 2001:db8:85a3:0:0:8a2e:370:7334], 
> sockAddrs=[/0:0:0:0:0:0:0:1:47501, /127.0.0.1:47501, rr/192.168.56.1:47501, 
> /10.0.0.5:47501, rr/192.168.56.1:47501, /192.168.56.1:47501, 
> rr/192.168.56.1:47501, /2001:db8:85a3:0:0:8a2e:370:7334:47501], 
> discPort=47501, order=2, intOrder=2, loc=false, 
> ver=1.1.1#20150604-sha1:a6ea325c, isClient=false]
> [15:58:33,434][INFO ][disco-event-worker-#46%null%][GridDiscoveryManager] 
> Topology snapshot [ver=2, nodes=2, CPUs=8, heap=2.0GB]
> [15:58:33] (err) Failed to execute compound future reducer: Compound future 
> listener: GridCompoundFuture [lsnrCalls=0, finished=false, rdc=null, 
> init=true, res=java.util.concurrent.atomic.AtomicMarkableReference@78237daf, 
> err=null, done=false, cancelled=false, err=null, futs=[true]]class 
> org.apache.ignite.IgniteCheckedException: Cache is not configured: 
> server_cache_1209_884
>   at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6732)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:124)
>   at 
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:304)
>   at 
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:295)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter$ArrayListener.apply(GridFutureAdapter.java:419)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter$ArrayListener.apply(GridFutureAdapter.java:402)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:241)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListeners(GridFutureAdapter.java:229)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:359)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:325)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:1256)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:235)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:690)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:58)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:653)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: Cache is not configured: 
> server_cache_1209_884
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.jcache(GridCacheProcessor.java:2715)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:91)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:280)
>   at 
> 

[jira] [Commented] (IGNITE-1111) Scalar ping pong example failed with NPE

[Yakov Zhdanov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727300#comment-14727300
 ] 

Yakov Zhdanov commented on IGNITE-:
---

Sergey,

I looked at the code here - 
https://www.codatlas.com/github.com/lambdalab-mirror/jdk7u-jdk/HEAD/src/windows/classes/java/net/DualStackPlainSocketImpl.java?line=250

It seems to be an issue somewhere in JDK code. We get NPE because of some 
private member in package local class is null. Very weird.

Can you quickly search in JDK bug database and post the stack trace there if 
same bug missing?

> Scalar ping pong example failed with NPE
> 
>
> Key: IGNITE-
> URL: https://issues.apache.org/jira/browse/IGNITE-
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: sprint-7
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
> Fix For: ignite-1.4
>
>
> Note: sporadic failure. 
> ScalarPingPongExample failed once for Windows when started with one server 
> node by bin\ignite.bat examples\config\example-ignite.xml:
> Please find below the example output:
> {noformat}
> [19:51:39,648][INFO][main][GridDiscoveryManager] Topology snapshot [ver=70, 
> server nodes=2, client nodes=0, CPUs=8, heap=2.0GB]
> [19:51:39,700][INFO][main][GridDeploymentLocalStore] Class locally deployed: 
> class org.apache.ignite.scalar.examples.ScalarPingPongExample$$anon$1
> PONG
> PONG
> PONG
> PONG
> PONG
> PONG
> PONG
> PONG
> PONG
> PONG
> [19:51:39,722][INFO][main][GridTcpRestProtocol] Command protocol successfully 
> stopped: TCP binary
> [19:51:39,726][INFO][main][GridJettyRestProtocol] Command protocol 
> successfully stopped: Jetty REST
> [19:51:39,733][SEVERE][tcp-disco-sock-reader-#11%null][TcpDiscoverySpi] 
> Runtime error caught during grid runnable execution: Socket reader [id=147, 
> name=tcp-disco-sock-reader-#11%null, nodeId=null]
> java.lang.NullPointerException
>   at 
> java.net.DualStackPlainSocketImpl.checkAndReturnNativeFD(DualStackPlainSocketImpl.java:250)
>   at 
> java.net.DualStackPlainSocketImpl.socketSetOption(DualStackPlainSocketImpl.java:179)
>   at 
> java.net.AbstractPlainSocketImpl.setOption(AbstractPlainSocketImpl.java:269)
>   at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:176)
>   at java.net.Socket.setKeepAlive(Socket.java:1268)
>   at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$SocketReader.body(ServerImpl.java:4089)
>   at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [19:51:39,734][INFO][main][GridCacheProcessor] Stopped cache: 
> ignite-marshaller-sys-cache
> [19:51:39,735][INFO][main][GridCacheProcessor] Stopped cache: ignite-sys-cache
> [19:51:39,735][INFO][main][GridCacheProcessor] Stopped cache: 
> ignite-atomics-sys-cache
> [19:51:39,735][INFO][main][GridCacheProcessor] Stopped cache: datastructures_0
> [19:51:39,735][INFO][main][GridCacheProcessor] Stopped cache: datastructures_1
> [19:51:39,736][INFO][main][GridDeploymentLocalStore] Removed undeployed 
> class: GridDeployment [ts=1436457099529, depMode=SHARED, 
> clsLdr=sun.misc.Launcher$AppClassLoader@3f677737, 
> clsLdrId=757a3837e41-e889dd6a-3dcc-4a3f-8716-59348d37edc2, userVer=0, 
> loc=true, 
> sampleClsName=org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionFullMap,
>  pendingUndeploy=false, undeployed=true, usage=0]
> [19:51:39,738][INFO][main][IgniteKernal] 
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-1358) PortableMarshaller: 'userType' flag is not written for objects of some types

[Denis Magda (JIRA)]

Denis Magda created IGNITE-1358:
---

 Summary: PortableMarshaller: 'userType' flag is not written for 
objects of some types
 Key: IGNITE-1358
 URL: https://issues.apache.org/jira/browse/IGNITE-1358
 Project: Ignite
  Issue Type: Bug
Reporter: Denis Magda
Priority: Critical


The 'userType' flag is not written when the following classes are serialized:
- enums;
- object and enum arrays;
- classes.

This leads to the situation that the predefined types map is ignored during 
deserialization and the type is always considered as user's.

To support this feature requires changes in the portable protocol.

For now there is a workaround in the code.
 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-1347) Create normal platform processor.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov closed IGNITE-1347.
---

> Create normal platform processor.
> -
>
> Key: IGNITE-1347
> URL: https://issues.apache.org/jira/browse/IGNITE-1347
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: ignite-1.5
>
>
> Currently we have no-op platform processor implementation in "core" module. 
> We need to implement fully-fledged processor in "platforms" module.
> Processor creation sequence should be as follows:
> 1) Ask plugins for their processor. Stop in case of non-null result.
> 2) Check for PlatformConfiguration. If not null - create fully-fledged 
> processor through reflection if it is present in classpath. Stop if created.
> 3) Return no-op processor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-1347) Create normal platform processor.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov resolved IGNITE-1347.
-
Resolution: Fixed

> Create normal platform processor.
> -
>
> Key: IGNITE-1347
> URL: https://issues.apache.org/jira/browse/IGNITE-1347
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: ignite-1.5
>
>
> Currently we have no-op platform processor implementation in "core" module. 
> We need to implement fully-fledged processor in "platforms" module.
> Processor creation sequence should be as follows:
> 1) Ask plugins for their processor. Stop in case of non-null result.
> 2) Check for PlatformConfiguration. If not null - create fully-fledged 
> processor through reflection if it is present in classpath. Stop if created.
> 3) Return no-op processor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1018) Node local map is not available when LifecycleEventType.BEFORE_NODE_START is processed in lifecycle bean

[Yakov Zhdanov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yakov Zhdanov updated IGNITE-1018:
--
Labels: Usability newbie  (was: Usability)

> Node local map is not available when LifecycleEventType.BEFORE_NODE_START is 
> processed in lifecycle bean
> 
>
> Key: IGNITE-1018
> URL: https://issues.apache.org/jira/browse/IGNITE-1018
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>  Labels: Usability, newbie
> Fix For: ignite-1.5
>
>
> Currently {{IgniteCluster.nodeLocalMap()}} method is guarded by gateway like 
> all others. But this is just a local concurrent map which is already 
> available at the moment LifecycleEventType.BEFORE_NODE_START is processed, so 
> I think it will be good to make it available in lifecycle bean.
> This can be useful if user needs to initialize some resources and put them to 
> node local map before node is started.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-1357) Move Java bootstrap logic to Ignite.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov resolved IGNITE-1357.
-
Resolution: Fixed

> Move Java bootstrap logic to Ignite.
> 
>
> Key: IGNITE-1357
> URL: https://issues.apache.org/jira/browse/IGNITE-1357
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: ignite-1.5
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-1040) NPE if indexing fails with exception

[Anton Vinogradov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov reassigned IGNITE-1040:


Assignee: Anton Vinogradov

> NPE if indexing fails with exception
> 
>
> Key: IGNITE-1040
> URL: https://issues.apache.org/jira/browse/IGNITE-1040
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: ignite-1.4
>
>
> If cache start process fails with exception during indexing, it doesn't 
> actually stop and fails with NPE because some other components were not 
> started.
> {code}
> Jun 19, 2015 11:44:26 AM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Failed to reinitialize local partitions (preloading will be stopped): 
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=1, 
> minorTopVer=1], nodeId=8aec2f87, evt=DISCOVERY_CUSTOM_EVT]
> class org.apache.ignite.IgniteCheckedException: Property with name 'id' 
> already exists.
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$TypeDescriptor.addProperty(GridQueryProcessor.java:1736)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.processAnnotationsInClass(GridQueryProcessor.java:978)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.processAnnotation(GridQueryProcessor.java:1017)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.processAnnotationsInClass(GridQueryProcessor.java:976)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.processKeyAndValueClasses(GridQueryProcessor.java:210)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:163)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:242)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:867)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1450)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCachesStart(GridCacheProcessor.java:1372)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.startCaches(GridDhtPartitionsExchangeFuture.java:735)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:458)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:997)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
>   at java.lang.Thread.run(Thread.java:744)
> Jun 19, 2015 11:44:26 AM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Runtime error caught during grid runnable execution: GridWorker 
> [name=partition-exchanger, gridName=null, finished=false, isCancelled=false, 
> hashCode=1158985979, interrupted=false, runner=exchange-worker-#49%null%]
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onExchangeDone(GridCacheProcessor.java:1519)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:851)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:52)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:313)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:632)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:997)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
>   at java.lang.Thread.run(Thread.java:744)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-1243) HTTP REST: top command returns wrong result

[Sergey Kozlov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Kozlov reassigned IGNITE-1243:
-

Assignee: Sergey Kozlov

> HTTP REST: top command returns wrong result 
> 
>
> Key: IGNITE-1243
> URL: https://issues.apache.org/jira/browse/IGNITE-1243
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Minor
> Fix For: ignite-1.4
>
>
> HTTP REST: top command returns wrong result via a client node if all server 
> nodes left from topology: last server node is still in response.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1339) JVM Crash on TC Queries suite

[Yakov Zhdanov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727313#comment-14727313
 ] 

Yakov Zhdanov commented on IGNITE-1339:
---

Are hs_err file or coredump available?

> JVM Crash on TC Queries suite
> -
>
> Key: IGNITE-1339
> URL: https://issues.apache.org/jira/browse/IGNITE-1339
> Project: Ignite
>  Issue Type: Bug
>Reporter: Sergi Vladykin
>Priority: Critical
> Fix For: ignite-1.4
>
>
> {code}
> [07:13:33][org.apache.ignite:ignite-indexing] 
> [07:12:05,772][ERROR][ignite-#53702%sys-cache.IgniteCacheOffheapTieredMultithreadedSelfTest2%][GridMapQueryExecutor]
>  Failed to process message: GridQueryRequest [reqId=1712, pageSize=1024, 
> space=null, qrys=[GridCacheSqlQuery [alias=__Z0(), qry=SELECT
> [07:13:33][org.apache.ignite:ignite-indexing] "".PERSON._KEY __C0,
> [07:13:33][org.apache.ignite:ignite-indexing] "".PERSON._VAL __C1
> [07:13:33][org.apache.ignite:ignite-indexing] FROM "".PERSON
> [07:13:33][org.apache.ignite:ignite-indexing] WHERE (SALARY >= ?1) AND 
> (SALARY <= ?2), params=[9.48320472052535E8, 9.48321472052535E8]]], 
> topVer=AffinityTopologyVersion [topVer=3, minorTopVer=0], extraSpaces=null, 
> parts=[0, 1, 3, 6, 7, 8, 10, 11, 12, 13, 14, 17, 18, 19, 23, 25, 26, 27, 28, 
> 29, 30, 31, 32, 33, 34, 35, 36, 38, 39, 40, 41, 42, 44, 45, 46, 47, 51, 53, 
> 54, 55, 58, 59, 60, 61, 62, 63, 68, 69, 72, 73, 75, 76, 78, 80, 81, 82, 85, 
> 86, 87, 88, 89, 90, 91, 94, 95, 98, 101, 102, 105, 106, 109, 110, 111, 114, 
> 116, 117, 119, 120, 121, 122, 123, 125, 126, 127, 128, 129, 130, 133, 134, 
> 135, 137, 139, 140, 141, 145, 147, 149, 151, 153, 154, 155, 156, 157, 158, 
> 159, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 
> 175, 177, 178, 181, 183, 184, 186, 187, 188, 189, 190, 191, 192, 194, 195, 
> 196, 198, 199, 200, 201, 205, 206, 208, 209, 211, 212, 213, 214, 215, 217, 
> 218, 219, 220, 221, 222, 223, 224, 225, 227, 231, 232, 234, 236, 237, 240, 
> 241, 242, 243, 245, 246, 247, 248, 250, 251, 253, 254, 255, 257, 258, 259, 
> 260, 261, 263, 264, 265, 266, 268, 269, 270, 272, 273, 274, 276, 277, 278, 
> 279, 280, 282, 283, 285, 287, 288, 290, 292, 293, 294, 296, 298, 300, 301, 
> 302, 308, 309, 311, 314, 315, 317, 318, 319, 320, 321, 322, 324, 325, 327, 
> 328, 329, 330, 331, 332, 333, 334, 340, 342, 343, 345, 346, 350, 352, 353, 
> 354, 356, 358, 359, 360, 364, 365, 366, 368, 371, 372, 373, 375, 376, 379, 
> 380, 381, 382, 384, 386, 387, 388, 389, 390, 391, 392, 393, 394, 395, 396, 
> 397, 398, 399, 400, 401, 402, 403, 405, 407, 409, 410, 412, 413, 414, 416, 
> 417, 420, 421, 422, 423, 424, 429, 430, 431, 432, 433, 435, 436, 437, 438, 
> 439, 441, 442, 443, 444, 445, 446, 448, 449, 451, 453, 454, 456, 458, 459, 
> 460, 461, 462, 463, 464, 465, 466, 467, 469, 470, 471, 472, 473, 476, 477, 
> 479, 480, 482, 484, 486, 487, 488, 489, 490, 491, 492, 493, 495, 497, 501, 
> 502, 505, 507, 508, 511, 512, 513, 514, 515, 516, 517, 518, 519, 520, 521, 
> 522, 523, 524, 525, 526, 527, 528, 532, 534, 535, 537, 538, 541, 542, 543, 
> 544, 545, 546, 547, 548, 549, 550, 551, 552, 553, 557, 558, 559, 561, 562, 
> 563, 565, 566, 568, 569, 571, 573, 575, 576, 578, 579, 582, 583, 585, 586, 
> 590, 592, 593, 594, 595, 596, 597, 598, 599, 603, 604, 605, 606, 607, 608, 
> 609, 611, 612, 614, 615, 617, 618, 619, 620, 623, 624, 625, 627, 628, 629, 
> 631, 632, 633, 634, 635, 636, 637, 639, 641, 643, 644, 645, 646, 647, 648, 
> 649, 652, 654, 656, 657, 658, 659, 660, 662, 663, 664, 665, 667, 668, 669, 
> 671, 672, 673, 674, 675, 676, 677, 678, 679, 680, 681, 682, 683, 685, 686, 
> 687, 688, 689, 692, 694, 696, 698, 699, 700, 701, 703, 706, 707, 710, 712, 
> 713, 715, 716, 717, 718, 719, 723, 725, 727, 728, 729, 730, 732, 733, 734, 
> 735, 736, 738, 741, 742, 743, 744, 746, 747, 749, 751, 752, 753, 758, 759, 
> 760, 762, 764, 766, 767, 768, 769, 771, 773, 775, 776, 777, 780, 781, 782, 
> 783, 786, 789, 790, 791, 792, 796, 799, 801, 802, 804, 809, 813, 814, 815, 
> 816, 817, 819, 820, 821, 822, 824, 825, 827, 829, 830, 832, 833, 841, 843, 
> 844, 845, 846, 847, 848, 849, 850, 851, 852, 855, 857, 859, 860, 862, 864, 
> 865, 867, 868, 869, 870, 872, 874, 875, 876, 879, 881, 883, 884, 885, 886, 
> 887, 888, 889, 890, 892, 894, 896, 898, 899, 901, 902, 903, 904, 906, 908, 
> 909, 911, 912, 913, 914, 917, 918, 919, 920, 921, 922, 925, 927, 929, 931, 
> 932, 934, 935, 938, 939, 940, 941, 942, 943, 945, 946, 948, 949, 950, 952, 
> 955, 957, 959, 960, 961, 962, 964, 965, 967, 968, 969, 971, 972, 974, 975, 
> 976, 977, 979, 980, 981, 984, 985, 989, 990, 991, 993, 995, 997, 998, 999, 
> 1000, 1001, 1002, 1003, 1004, 1005, 1006, 1007, 1008, 1009, 1010, 1012, 1013, 
> 1014, 1015, 1016, 1017, 1019, 1020, 1021, 1022]]
> [07:13:33][org.apache.ignite:ignite-indexing] class 
>