[jira] [Updated] (IGNITE-967) Internal thread locals are not always cleaned

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-967:
---
Priority: Blocker  (was: Major)

> Internal thread locals are not always cleaned
> -
>
> Key: IGNITE-967
> URL: https://issues.apache.org/jira/browse/IGNITE-967
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> One of our users reported that he sees warnings in Tomcat's log when the 
> application that's running Ignite in embedded mode is undeployed:
> {code}
> SEVERE: The web application [/XXX] created a ThreadLocal with key of type 
> [org.apache.ignite.internal.util.GridSpinReadWriteLock$1] (value 
> [org.apache.ignite.internal.util.GridSpinReadWriteLock$1@2c2858af]) and a 
> value of type [java.lang.Integer] (value [0]) but failed to remove it when 
> the web application was stopped. Threads are going to be renewed over time to 
> try and avoid a probable memory leak.
> {code}
> There is also the similar warning for {{GridToStringBuilder.threadCache}}. 
> While it's usually OK not to clean thread locals on standalone node, in app 
> server it can cause a memory leak.
> To avoid such issues I suggest to add a special step after all test suites 
> that will check thread locals in test runner thread. If we have this check in 
> CI, we will fix it once and for always.
> Thread local values can be introspected through {{Thread.threadLocals}} 
> variable. It would also be a good idea to check Tomcat's sources on how it's 
> done there.



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

[jira] [Updated] (IGNITE-1416) .Net: Implement AtomicLong data structure

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn updated IGNITE-1416:

Description: (was: This includes:
- atomicLong;
- atomicSequence;
- atomicStamped;
- atomicReference.)

> .Net: Implement AtomicLong data structure
> -
>
> Key: IGNITE-1416
> URL: https://issues.apache.org/jira/browse/IGNITE-1416
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Critical
> Fix For: ignite-1.5
>
>




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

[jira] [Updated] (IGNITE-1416) .Net: Implement AtomicLong data structure.

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn updated IGNITE-1416:

Summary: .Net: Implement AtomicLong data structure.  (was: .Net: Implement 
"atomic" data structures.)

> .Net: Implement AtomicLong data structure.
> --
>
> Key: IGNITE-1416
> URL: https://issues.apache.org/jira/browse/IGNITE-1416
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Critical
> Fix For: ignite-1.5
>
>
> This includes:
> - atomicLong;
> - atomicSequence;
> - atomicStamped;
> - atomicReference.



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

[jira] [Commented] (IGNITE-1526) IBM JDK is not fully supported by the platfrom

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov commented on IGNITE-1526:
---

Andrey,

Sam has proposed changing code not to send anynymous classes, e.g. replace 
collections from gridfunc with array lists, create static classes for 
iterators, etc. This will definitely work as long as receiving side most likely 
does not require GridFunc$2$3$5, but some Iterator instance.

This seems to be much easier than updating hundreds of anonymous classes.

> IBM JDK is not fully supported by the platfrom
> --
>
> Key: IGNITE-1526
> URL: https://issues.apache.org/jira/browse/IGNITE-1526
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Andrey Gura
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> There are several issue related to IBM JDK.
> 1) It's not possible to compile the platform using IBM JDK ver 1.7;
> 2) Besides of the fact that two IBM nodes can connect to each other some 
> functionality still doesn't work. As an example 
> {{CacheClientPortablePutGetExample}} fails with the following stack trace
> {noformat}
> [14:38:56,930][ERROR][grid-nio-worker-0-#26%null%][TcpCommunicationSpi] 
> Caught unhandled exception in NIO worker thread (restart the node).
> class org.apache.ignite.IgniteException: Invalid field type: 0
>   at 
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readRemovedField(PortableDirectMessageReader.java:670)
>   at 
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readFieldHeader(PortableDirectMessageReader.java:520)
>   at 
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readMessage(PortableDirectMessageReader.java:339)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:248)
>   at 
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:76)
>   at 
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:103)
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
>   at 
> org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:122)
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:2078)
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:172)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:858)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeys(GridNioServer.java:1397)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1339)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1223)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
>   at java.lang.Thread.run(Thread.java:801)
> {noformat}
> 3) Oracle JVM based server node fails to connect to IBM server node producing 
> the stack trace below. Tested with JDK and Portable marshallers.
> {noformat}
> [13:47:33,935][SEVERE][tcp-disco-msg-worker-#2%null][TcpDiscoverySpi] Failed 
> to
> unmarshal discovery data for component: 0
> class org.apache.ignite.IgniteCheckedException: Failed to deserialize object 
> wit
> h given class loader: sun.misc.Launcher$AppClassLoader@56092666
> at 
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshalle
> r.java:105)
> at 
> org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMar
> shaller.java:68)
> at 
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDis
> coverySpi.java:1697)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.proc
> essNodeAddedMessage(ServerImpl.java:3258)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.proc
> essMessage(ServerImpl.java:1993)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.b
> ody(ServerImpl.java:5206)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> Caused by: java.io.InvalidClassException: 
> org.apache.ignite.internal.util.lang.G
> ridFunc$38; local class incompatible: stream classdesc serialVersionUID = 
> -55433
> 49853748590486, local class serialVersionUID = 

[jira] [Updated] (IGNITE-1523) Need to always serialize user objects with configured marshaller

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-1523:

Summary: Need to always serialize user objects with configured marshaller  
(was: Need to make marshaller in discovery pluggable)

> Need to always serialize user objects with configured marshaller
> 
>
> Key: IGNITE-1523
> URL: https://issues.apache.org/jira/browse/IGNITE-1523
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
>  Labels: user-request
> Fix For: ignite-1.5
>
>
> Currently we always use {{JdkMarshaller}}. It can be useful to use a custom 
> one. Need to add {{TcpDiscoverySpi.setMarshaller()}} method to allow this.



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

[jira] [Updated] (IGNITE-1534) Failed to map keys for cache (all partition nodes left the grid).

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-1534:
-
Issue Type: Sub-task  (was: Bug)
Parent: IGNITE-1345

> Failed to map keys for cache (all partition nodes left the grid).
> -
>
> Key: IGNITE-1534
> URL: https://issues.apache.org/jira/browse/IGNITE-1534
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Andrey Gura
>Assignee: Semen Boikov
> Fix For: ignite-1.5
>
>
> During testing changes related with IGNITE-1171 the following problem was 
> found:
> {panel}
> Unhandled exception 
> org.apache.ignite.cache.CacheServerNotFoundException: Failed to map keys for 
> cache (all partition nodes left the grid).
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1612)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1744)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.getAndPut(IgniteCacheProxy.java:1043)
>   at io.vertx.spi.cluster.ignite.impl.MapImpl.put(MapImpl.java:85)
>   at io.vertx.core.impl.HAManager.(HAManager.java:147)
>   at io.vertx.core.impl.VertxImpl.lambda$null$143(VertxImpl.java:156)
>   at io.vertx.core.impl.VertxImpl$$Lambda$35/2107573573.handle(Unknown 
> Source)
>   at 
> io.vertx.core.net.impl.NetServerImpl.lambda$null$34(NetServerImpl.java:252)
>   at 
> io.vertx.core.net.impl.NetServerImpl$$Lambda$39/1662210125.handle(Unknown 
> Source)
>   at 
> io.vertx.core.impl.ContextImpl.lambda$wrapTask$20(ContextImpl.java:324)
>   at io.vertx.core.impl.ContextImpl$$Lambda$31/1504729381.run(Unknown 
> Source)
>   at 
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)
>   at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
>   at 
> io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class 
> org.apache.ignite.internal.cluster.ClusterTopologyServerNotFoundException: 
> Failed to map keys for cache (all partition nodes left the grid).
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(GridNearAtomicUpdateFuture.java:808)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:422)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$100(GridNearAtomicUpdateFuture.java:73)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$1$1.run(GridNearAtomicUpdateFuture.java:406)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6427)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:788)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   ... 1 more
> {panel}
> This exception occures on topology from 3 nodes that start dynamic cache with 
> the same configuration on all nodes and performs {{put}} operation. All 3 
> nodes are alive.
> The problem reproduces periodically.



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

[jira] [Updated] (IGNITE-1534) Failed to map keys for cache (all partition nodes left the grid).

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-1534:
-
Fix Version/s: ignite-1.5

> Failed to map keys for cache (all partition nodes left the grid).
> -
>
> Key: IGNITE-1534
> URL: https://issues.apache.org/jira/browse/IGNITE-1534
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Gura
> Fix For: ignite-1.5
>
>
> During testing changes related with IGNITE-1171 the following problem was 
> found:
> {panel}
> Unhandled exception 
> org.apache.ignite.cache.CacheServerNotFoundException: Failed to map keys for 
> cache (all partition nodes left the grid).
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1612)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1744)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.getAndPut(IgniteCacheProxy.java:1043)
>   at io.vertx.spi.cluster.ignite.impl.MapImpl.put(MapImpl.java:85)
>   at io.vertx.core.impl.HAManager.(HAManager.java:147)
>   at io.vertx.core.impl.VertxImpl.lambda$null$143(VertxImpl.java:156)
>   at io.vertx.core.impl.VertxImpl$$Lambda$35/2107573573.handle(Unknown 
> Source)
>   at 
> io.vertx.core.net.impl.NetServerImpl.lambda$null$34(NetServerImpl.java:252)
>   at 
> io.vertx.core.net.impl.NetServerImpl$$Lambda$39/1662210125.handle(Unknown 
> Source)
>   at 
> io.vertx.core.impl.ContextImpl.lambda$wrapTask$20(ContextImpl.java:324)
>   at io.vertx.core.impl.ContextImpl$$Lambda$31/1504729381.run(Unknown 
> Source)
>   at 
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)
>   at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
>   at 
> io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class 
> org.apache.ignite.internal.cluster.ClusterTopologyServerNotFoundException: 
> Failed to map keys for cache (all partition nodes left the grid).
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(GridNearAtomicUpdateFuture.java:808)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:422)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$100(GridNearAtomicUpdateFuture.java:73)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$1$1.run(GridNearAtomicUpdateFuture.java:406)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6427)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:788)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   ... 1 more
> {panel}
> This exception occures on topology from 3 nodes that start dynamic cache with 
> the same configuration on all nodes and performs {{put}} operation. All 3 
> nodes are alive.
> The problem reproduces periodically.



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

[jira] [Created] (IGNITE-1561) Cross cache tx tests with near cache fail with asserts

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-1561:


 Summary: Cross cache tx tests with near cache fail with asserts
 Key: IGNITE-1561
 URL: https://issues.apache.org/jira/browse/IGNITE-1561
 Project: Ignite
  Issue Type: Sub-task
  Components: cache
Reporter: Semen Boikov
Assignee: Alexey Goncharuk
Priority: Blocker
 Fix For: ignite-1.5


I added in master cross cache txs test from ignite-80 branch 
(IgniteCrossCacheTxNearEnabledSelfTest), it fails with various asserts, e.g.:
{noformat}
java.lang.AssertionError
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxMapping.initLast(GridDhtTxMapping.java:86)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepare(GridNearOptimisticTxPrepareFuture.java:544)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepare0(GridNearOptimisticTxPrepareFuture.java:452)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepareOnTopology(GridNearOptimisticTxPrepareFuture.java:341)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.prepare(GridNearOptimisticTxPrepareFuture.java:279)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.prepareAsync(GridNearTxLocal.java:758)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.commitAsync(GridNearTxLocal.java:769)
at 
org.apache.ignite.internal.processors.cache.GridCacheSharedContext.commitTxAsync(GridCacheSharedContext.java:642)
at 
org.apache.ignite.internal.processors.cache.transactions.TransactionProxyImpl.commit(TransactionProxyImpl.java:256)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.IgniteCrossCacheTxSelfTest.checkTxsSingleOp(IgniteCrossCacheTxSelfTest.java:170)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.IgniteCrossCacheTxSelfTest.testOptimisticRepeatableRead(IgniteCrossCacheTxSelfTest.java:136)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
{noformat}

Test pass is near cache is disabled (added separate test for this mode: 
IgniteCrossCacheTxSelfTest).



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

[jira] [Updated] (IGNITE-940) Need to expose SQL metadata to public API

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-940:
---
Priority: Minor  (was: Trivial)

> Need to expose SQL metadata to public API
> -
>
> Key: IGNITE-940
> URL: https://issues.apache.org/jira/browse/IGNITE-940
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-5
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Minor
>  Labels: Usability, user-request
> Fix For: ignite-1.5
>
>
> This is the request from one of our users.
> We already have {{GridCacheSqlMetadata}} and {{GridCacheSqlIndexMetadata}} 
> interfaces and {{GridCacheQueryManager.sqlMetadata()}} method.
> Need to move interfaces to public package and add a new method on 
> {{IgniteCache}}.



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

[jira] [Updated] (IGNITE-995) Nodes on one host doesn't discover each other if IP finder doesn't explicitly provide port

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-995:
---
Priority: Trivial  (was: Major)

> Nodes on one host doesn't discover each other if IP finder doesn't explicitly 
> provide port
> --
>
> Key: IGNITE-995
> URL: https://issues.apache.org/jira/browse/IGNITE-995
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Trivial
>  Labels: Usability
> Fix For: ignite-1.5
>
>




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

[jira] [Created] (IGNITE-1562) .Net: Remove "Generic" word from "WriteGenericCollection" and "WriteGenericDictionary".

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-1562:
---

 Summary: .Net: Remove "Generic" word from "WriteGenericCollection" 
and "WriteGenericDictionary".
 Key: IGNITE-1562
 URL: https://issues.apache.org/jira/browse/IGNITE-1562
 Project: Ignite
  Issue Type: Task
  Components: interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: ignite-1.5


Normally users will use these methods instead of non-generic. Lets make their 
names as simple as possible.



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

[jira] [Created] (IGNITE-1566) Hadoop: In case if IGFS name is missing in the URI, the connection failure message should be more informative.

[Ivan Veselovsky (JIRA)]

Ivan Veselovsky created IGNITE-1566:
---

 Summary: Hadoop: In case if IGFS name is missing in the URI, the 
connection failure message should be more informative.
 Key: IGNITE-1566
 URL: https://issues.apache.org/jira/browse/IGNITE-1566
 Project: Ignite
  Issue Type: Bug
  Components: hadoop
Affects Versions: ignite-1.4
Reporter: Ivan Veselovsky
Assignee: Ivan Veselovsky


User has IGFS "igfs" configured in Ignite node.
After that he tries to connect to it with hadoop client using command
{code}
$ hadoop fs -ls igfs://127.0.0.1:10500/
{code}

And gets the following error message:
{code}ls: Failed to communicate with IGFS.{code} .

The problem is that IGFS name is missing in the URI. But the error message does 
not give any hint about that.




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

[jira] [Commented] (IGNITE-1559) Need to improve tests, javadoc and documentation of UriDeploymentHttpScanner.

[Artem Shutak (JIRA)]

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

Artem Shutak commented on IGNITE-1559:
--

In process of improvement javadocs for UriDeploymentSpi I've found that 
"classes"-protocol currently not supported. So, I will remove this part from 
javadoc.

Checked with
{code}
deploymentSpi.setUriList(Arrays.asList("classes://freq=5000@localhost/c:/Program
 files/ignite/deployment"));
{code}

I've got next exception:
{noformat}
Exception in thread "main" class org.apache.ignite.IgniteException: Failed to 
start manager: GridManagerAdapter [enabled=true, 
name=org.apache.ignite.internal.managers.deployment.GridDeploymentManager]
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:881)
at org.apache.ignite.Ignition.start(Ignition.java:324)
at 
org.apache.ignite.TmpUriDeploymentTest.main(TmpUriDeploymentTest.java:37)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start 
manager: GridManagerAdapter [enabled=true, 
name=org.apache.ignite.internal.managers.deployment.GridDeploymentManager]
at 
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1488)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:856)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1617)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1484)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:965)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:526)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:507)
at org.apache.ignite.Ignition.start(Ignition.java:321)
... 1 more
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start SPI: 
UriDeploymentSpi [tmpDirPath=/tmp, 
deployTmpDirPath=/tmp/gg.uri.deployment.tmp/b2bf7e0f-efa2-47e6-9c56-57a2ed44b27c,
 checkMd5=false, 
unitComp=org.apache.ignite.spi.deployment.uri.UriDeploymentSpi$LastTimeUnitDescriptorComparator@434ce06a,
 encodeUri=true, firstScanCntr=0, lsnr=null, delayOnNewOrUpdatedFile=false]
at 
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:255)
at 
org.apache.ignite.internal.managers.deployment.GridDeploymentManager.start(GridDeploymentManager.java:101)
at 
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1485)
... 8 more
Caused by: class org.apache.ignite.spi.IgniteSpiException: Unsupported URI 
(please configure appropriate scanner): 
classes://freq=5000@localhost/c:/Program%20files/ignite/deployment
at 
org.apache.ignite.spi.deployment.uri.UriDeploymentSpi.spiStart(UriDeploymentSpi.java:630)
at 
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:252)
... 10 more
{noformat}

> Need to improve tests, javadoc and documentation of UriDeploymentHttpScanner.
> -
>
> Key: IGNITE-1559
> URL: https://issues.apache.org/jira/browse/IGNITE-1559
> Project: Ignite
>  Issue Type: Task
>Reporter: Artem Shutak
>Assignee: Artem Shutak
> Fix For: ignite-1.5
>
>
> Need to improve tests, javadoc and documentation of UriDeploymentHttpScanner. 
> It's not possible to understand from current javadoc of 
> UriDeploymentHttpScanner how it works.
> There's only one simple test in GridHttpDeploymentSelfTest.



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

[jira] [Updated] (IGNITE-1523) Need to always serialize user objects with configured marshaller

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-1523:

Description: Currently some components (at least discovery) use 
{{JdkMarshaller}} for all objects.  (was: Currently we always use 
{{JdkMarshaller}}. It can be useful to use a custom one. Need to add 
{{TcpDiscoverySpi.setMarshaller()}} method to allow this.)

> Need to always serialize user objects with configured marshaller
> 
>
> Key: IGNITE-1523
> URL: https://issues.apache.org/jira/browse/IGNITE-1523
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
>  Labels: user-request
> Fix For: ignite-1.5
>
>
> Currently some components (at least discovery) use {{JdkMarshaller}} for all 
> objects.



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

[jira] [Created] (IGNITE-1570) Move .Net local benchmarks project to Ignite.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-1570:
---

 Summary: Move .Net local benchmarks project to Ignite.
 Key: IGNITE-1570
 URL: https://issues.apache.org/jira/browse/IGNITE-1570
 Project: Ignite
  Issue Type: Task
  Components: interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
 Fix For: ignite-1.5






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

[jira] [Created] (IGNITE-1567) Optimize portable object fields read/write in .Net.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-1567:
---

 Summary: Optimize portable object fields read/write in .Net.
 Key: IGNITE-1567
 URL: https://issues.apache.org/jira/browse/IGNITE-1567
 Project: Ignite
  Issue Type: Sub-task
  Components: interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: ignite-1.5






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

[jira] [Commented] (IGNITE-1565) Platform .Net: Fix examples

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-1565:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-1565 Platform .Net: Fix examples



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

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

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

https://github.com/apache/ignite/pull/112.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 #112


commit cc0725ec0ac7b152ba6020891308b98102211360
Author: ptupitsyn 
Date:   2015-09-29T12:27:19Z

IGNITE-1565 Platform .Net: Fix examples




> Platform .Net: Fix examples
> ---
>
> Key: IGNITE-1565
> URL: https://issues.apache.org/jira/browse/IGNITE-1565
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: ignite-1.5
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: ignite-1.5
>
>
> Paths have changed in ignite-1282 branch:
> * config paths should be fixed in examples
> * example files paths should be fixed in example tests



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

[jira] [Updated] (IGNITE-1125) Failed to send time request to remote node

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-1125:
--
Assignee: Artem Shutak  (was: Semen Boikov)

>  Failed to send time request to remote node
> ---
>
> Key: IGNITE-1125
> URL: https://issues.apache.org/jira/browse/IGNITE-1125
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-7
> Environment: OS X 10.10.3
> IDEA 14
> VirtualBox 4.3.26 - ubuntu 14.04.2 LST
>Reporter: Ilya Suntsov
>Assignee: Artem Shutak
> Fix For: ignite-1.5
>
> Attachments: client.log, s01.log, s02.log
>
>
> 1. Set specific ip-addresses for client and servers in 
> {noformat}org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder{noformat}
> 2. Start 2 servers in VirtualBox
> 3. Start client on host OS
> Result:
> One of servers prints warning until stop:
> {noformat}
> ..
> [17:21:46,290][WARN 
> ][grid-time-coordinator-#41%null%][GridClockSyncProcessor] Failed to send 
> time request to remote node [rmtNodeId=7b2fd844-4773-4fd2-81e2-9d9f6010230e, 
> addr=/2001:db8:85a3:0:0:8a2e:370:7334, port=31100]
> [17:21:47,291][WARN 
> ][grid-time-coordinator-#41%null%][GridClockSyncProcessor] Failed to send 
> time request to remote node [rmtNodeId=7b2fd844-4773-4fd2-81e2-9d9f6010230e, 
> addr=/2001:db8:85a3:0:0:8a2e:370:7334, port=31100]
> [17:21:48,292][WARN 
> ][grid-time-coordinator-#41%null%][GridClockSyncProcessor] Failed to send 
> time request to remote node [rmtNodeId=7b2fd844-4773-4fd2-81e2-9d9f6010230e, 
> addr=/2001:db8:85a3:0:0:8a2e:370:7334, port=31100]
> [17:21:49,293][WARN 
> ][grid-time-coordinator-#41%null%][GridClockSyncProcessor] Failed to send 
> time request to remote node [rmtNodeId=7b2fd844-4773-4fd2-81e2-9d9f6010230e, 
> addr=/2001:db8:85a3:0:0:8a2e:370:7334, port=31100]
> [17:21:50,294][WARN 
> ][grid-time-coordinator-#41%null%][GridClockSyncProcessor] Failed to send 
> time request to remote node [rmtNodeId=7b2fd844-4773-4fd2-81e2-9d9f6010230e, 
> addr=/2001:db8:85a3:0:0:8a2e:370:7334, port=31100]
> [17:21:51,298][WARN 
> ][grid-time-coordinator-#41%null%][GridClockSyncProcessor] Failed to send 
> time request to remote node [rmtNodeId=7b2fd844-4773-4fd2-81e2-9d9f6010230e, 
> addr=/2001:db8:85a3:0:0:8a2e:370:7334, port=31100]
> [17:21:52,299][WARN 
> ][grid-time-coordinator-#41%null%][GridClockSyncProcessor] Failed to send 
> time request to remote node [rmtNodeId=7b2fd844-4773-4fd2-81e2-9d9f6010230e, 
> addr=/2001:db8:85a3:0:0:8a2e:370:7334, port=31100]
> ..
> {noformat}
> Full logs in attachment.



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

[jira] [Assigned] (IGNITE-1570) Move .Net local benchmarks project to Ignite.

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn reassigned IGNITE-1570:
---

Assignee: Pavel  Tupitsyn

> Move .Net local benchmarks project to Ignite.
> -
>
> Key: IGNITE-1570
> URL: https://issues.apache.org/jira/browse/IGNITE-1570
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
> Fix For: ignite-1.5
>
>




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

[jira] [Updated] (IGNITE-601) IgniteCache.isLocalLocked is broken

[Yakov Zhdanov (JIRA)]

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

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

> IgniteCache.isLocalLocked is broken
> ---
>
> Key: IGNITE-601
> URL: https://issues.apache.org/jira/browse/IGNITE-601
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>Assignee: Semen Boikov
>  Labels: failedtest
>
> To reproduce change GridCachePartitionedBasicApiTest to use PARTITIONED_ONLY 
> cache instead of NEAR_PARTITIONED.
> See GG-7437. Comments from origin Jira:
> - Fixed in gg-7434-1
> - Reopening since there are left TODOs in data grid test suite.
> Now, see GridCacheReplicatedNearOnlyMultiNodeFullApiSelfTest # lockingEnabled



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

[jira] [Commented] (IGNITE-1552) Table function doesn't work properly in SQL query

[Sergi Vladykin (JIRA)]

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

Sergi Vladykin commented on IGNITE-1552:


Please review.

> Table function doesn't work properly in SQL query
> -
>
> Key: IGNITE-1552
> URL: https://issues.apache.org/jira/browse/IGNITE-1552
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Sergi Vladykin
>Priority: Critical
>  Labels: user-request
> Fix For: ignite-1.5
>
> Attachments: QueryInStatementTest.java
>
>
> IN operator replacement query described in [1] doesn't seem to work properly. 
> Test reproducing the issue is attached.
> [1] 
> https://apacheignite.readme.io/docs/sql-queries#performance-and-usability-considerations



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

[jira] [Commented] (IGNITE-1416) .Net: Implement AtomicLong data structure

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-1416:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-1416 .Net: Implement AtomicLong data structure



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

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

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

https://github.com/apache/ignite/pull/111.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 #111


commit a9b070c7b3d88599e4b0e5a3ccfbfbe87296ba06
Author: ptupitsyn 
Date:   2015-09-17T12:11:12Z

IGNITE-1416 .Net: Implement "atomic" data structures.

IAtomicLong interface

commit 4e82fa65c2be9af3d0b753d868b50ea58ef47729
Author: ptupitsyn 
Date:   2015-09-17T12:27:15Z

wip

commit 08ac1cd51afb00a53b5b096467ea4ca398f49b6b
Author: ptupitsyn 
Date:   2015-09-17T12:28:58Z

wip

commit ca39048cd009c995de802a4445bd3c5301eb1a10
Author: ptupitsyn 
Date:   2015-09-17T12:34:07Z

Implement CompareAndSetAndGet in Java

commit c237137cc1fea9530bb36458cf90b49d3140eab8
Author: ptupitsyn 
Date:   2015-09-17T12:36:14Z

iface done

commit bc37efeb7cdad0fe395135c6eb3d04e29fa87ef2
Author: ptupitsyn 
Date:   2015-09-17T12:42:00Z

wip

commit b79e9a0652844dfadd9ff80779b5c8fc6fff8dc2
Author: ptupitsyn 
Date:   2015-09-17T12:43:02Z

wip

commit b670241dbe4c5bbf91152082336671dab37d45ca
Author: ptupitsyn 
Date:   2015-09-17T13:53:07Z

Merge remote-tracking branch 'remotes/upstream/ignite-1282' into ignite-1416

Conflicts:
modules/platform/src/main/dotnet/Apache.Ignite.Core/IIgnite.cs

commit d47aacfdd8c145bf2760d607230410b19ef8fdab
Author: ptupitsyn 
Date:   2015-09-17T14:30:32Z

Merge remote-tracking branch 'remotes/upstream/ignite-1282' into ignite-1416

commit fa9d8ad4e3bb516de71ee9a78cbec50494162a5b
Author: ptupitsyn 
Date:   2015-09-17T14:32:34Z

wip

commit 435a3bd895b0c656fbf9362bb0c58af4e5aa6e62
Author: ptupitsyn 
Date:   2015-09-17T14:42:45Z

wip

commit 1049b6d4251652f72984fcf12c399f090b69fedc
Author: ptupitsyn 
Date:   2015-09-17T15:04:58Z

wip

commit 0310fadb30a9718fcbd4f248aeacb583c40a190e
Author: ptupitsyn 
Date:   2015-09-17T15:21:33Z

wip

commit 91602718b23be06d326dd34744eb62afbd580e38
Author: ptupitsyn 
Date:   2015-09-17T15:24:28Z

wip

commit b89db5964c4a35302337d91762880b5b5ed65026
Author: ptupitsyn 
Date:   2015-09-17T15:27:27Z

wip

commit 072b01c192e71e9db213fc90c9e4fbc37328e3b9
Author: ptupitsyn 
Date:   2015-09-17T15:34:11Z

CPP interop

commit 7112d997bf6465dcf9c0e78019ff112b71518224
Author: ptupitsyn 
Date:   2015-09-17T15:48:19Z

wip

commit db6aa6819bfc149d38e0fbab709adae9016ab710
Author: ptupitsyn 
Date:   2015-09-17T15:49:10Z

wip

commit 9c689050d466f08bee0a8f208460d1e8ac103bb2
Author: ptupitsyn 
Date:   2015-09-17T15:49:56Z

wip

commit 3de8e21f3cc682d28d37a90a4a041c7da7160828
Author: ptupitsyn 
Date:   2015-09-17T15:54:24Z

wip test works

commit 90d6ef9ccdb30fc5f12f6049e281cc0ecaa46ca3
Author: ptupitsyn 
Date:   2015-09-18T09:39:38Z

Merge remote-tracking branch 'remotes/upstream/ignite-1282' into ignite-1416

commit daff1f804f09cff60b4d1167ee6287ce09ee6294
Author: ptupitsyn 
Date:   2015-09-18T09:41:21Z

wip

commit 1b83488f957fa32edb58adf77b68a425c900a628
Author: ptupitsyn 
Date:   2015-09-18T09:59:39Z

Java impl

commit 97627826efb787f4b3d66a3c436e2c30fca3338b
Author: ptupitsyn 
Date:   2015-09-18T10:49:38Z

wip

commit 208ead4588d7a716498772006f9cfb40504682ec
Author: ptupitsyn 
Date:   2015-09-18T11:00:45Z

wip

commit 66685ea2dda6a846ac625dcdd223b7eadb10d2fd
Author: ptupitsyn 
Date:   2015-09-18T11:08:21Z

wip

commit 66f3367b2bc9a34d2dc891b4a101b42cdfa29655
Author: ptupitsyn 
Date:   2015-09-18T11:08:49Z

wip

commit 584780933922175ab7bfaae0d4f56cb8d207ce84
Author: ptupitsyn 
Date:   2015-09-18T11:19:38Z

wip

commit 2612a0b861c2af0a4fd2d11fcf17832c44b09f59
Author: ptupitsyn 

[jira] [Updated] (IGNITE-1564) Cannot recover from org.apache.ignite.IgniteClientDisconnectedException

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-1564:
-
Fix Version/s: ignite-1.5

> Cannot recover from org.apache.ignite.IgniteClientDisconnectedException
> ---
>
> Key: IGNITE-1564
> URL: https://issues.apache.org/jira/browse/IGNITE-1564
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: ignite-1.4
>Reporter: Enrico Olivelli
>Assignee: Semen Boikov
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> Using Apache Ignite 1.4, I get this problem.
> I have two "server" nodes.
> Stop all the server nodes.
> The clients gets "IgniteClientDisconnectedException"
> Restart all the server nodes
> On client I get this error and the client cannot recover from that state.
> client has forceservermode=true
> {code}
> 15-09-29-11-06-28 SEVERE Sep 29, 2015 11:06:28 AM 
> org.apache.ignite.logger.java.JavaLogger error
> GRAVE: Runtime error caught during grid runnable execution: IgniteSpiThread 
> [name=tcp-client-disco-msg-worker-#4%SVILUPPOREF]
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.addClientNode(GridDiscoveryManager.java:338)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onDiscoveryDataReceived(GridCacheProcessor.java:1903)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$6.onExchange(GridDiscoveryManager.java:659)
>   at 
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1706)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddedMessage(ClientImpl.java:1625)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1535)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1465)
>   at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {code}
> and 
> {code}
> 15-09-14-11-14-56   SEVERE Sep 14, 2015 11:14:56 AM 
> org.apache.ignite.logger.java.JavaLogger error
> GRAVE: Unexpected exception in listener notification for event: 
> DiscoveryEvent [evtNode=TcpDiscoveryNode 
> [id=d5426d82-48ee-4a99-9737-4cf2f0cb5124, addrs=[10.168.10.81], 
> sockAddrs=[sviluppo-ref.sviluppo.dna/10.168.10.81:47500, 
> /10.168.10.81:47500], discPort=47500, order=6, intOrder=4, loc=false, 
> ver=1.3.0#20150710-sha1:2ade6d00, isClient=false], topVer=7, 
> nodeId8=a86f4ae8, msg=Node left: TcpDiscoveryNode 
> [id=d5426d82-48ee-4a99-9737-4cf2f0cb5124, addrs=[10.168.10.81], 
> sockAddrs=[sviluppo-ref.sviluppo.dna/10.168.10.81:47500, 
> /10.168.10.81:47500], discPort=47500, order=6, intOrder=4, loc=false, 
> ver=1.3.0#20150710-sha1:2ade6d00, isClient=false], type=NODE_LEFT, 
> tstamp=144096055]
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.futureId(GridNearAtomicUpdateFuture.java:239)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$3.onEvent(GridCacheMvccManager.java:200)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:745)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:730)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:270)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:1740)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:1931)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:1779)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}



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

[jira] [Commented] (IGNITE-1564) Cannot recover from org.apache.ignite.IgniteClientDisconnectedException

[Enrico Olivelli (JIRA)]

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

Enrico Olivelli commented on IGNITE-1564:
-

I compared the stacktrace with the source code published on Maven and I found 
that the second stacktrace is from a 1.3 client. Maybe the problem appears only 
during a "rolling restart upgrade" ?

I found the first stacktrace  both on a 1.4 client and a 1.3 client



> Cannot recover from org.apache.ignite.IgniteClientDisconnectedException
> ---
>
> Key: IGNITE-1564
> URL: https://issues.apache.org/jira/browse/IGNITE-1564
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: ignite-1.4
>Reporter: Enrico Olivelli
>Assignee: Semen Boikov
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> Using Apache Ignite 1.4, I get this problem.
> I have two "server" nodes.
> Stop all the server nodes.
> The clients gets "IgniteClientDisconnectedException"
> Restart all the server nodes
> On client I get this error and the client cannot recover from that state.
> client has forceservermode=true
> {code}
> 15-09-29-11-06-28 SEVERE Sep 29, 2015 11:06:28 AM 
> org.apache.ignite.logger.java.JavaLogger error
> GRAVE: Runtime error caught during grid runnable execution: IgniteSpiThread 
> [name=tcp-client-disco-msg-worker-#4%SVILUPPOREF]
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.addClientNode(GridDiscoveryManager.java:338)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onDiscoveryDataReceived(GridCacheProcessor.java:1903)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$6.onExchange(GridDiscoveryManager.java:659)
>   at 
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1706)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddedMessage(ClientImpl.java:1625)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1535)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1465)
>   at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {code}
> and 
> {code}
> 15-09-14-11-14-56   SEVERE Sep 14, 2015 11:14:56 AM 
> org.apache.ignite.logger.java.JavaLogger error
> GRAVE: Unexpected exception in listener notification for event: 
> DiscoveryEvent [evtNode=TcpDiscoveryNode 
> [id=d5426d82-48ee-4a99-9737-4cf2f0cb5124, addrs=[10.168.10.81], 
> sockAddrs=[sviluppo-ref.sviluppo.dna/10.168.10.81:47500, 
> /10.168.10.81:47500], discPort=47500, order=6, intOrder=4, loc=false, 
> ver=1.3.0#20150710-sha1:2ade6d00, isClient=false], topVer=7, 
> nodeId8=a86f4ae8, msg=Node left: TcpDiscoveryNode 
> [id=d5426d82-48ee-4a99-9737-4cf2f0cb5124, addrs=[10.168.10.81], 
> sockAddrs=[sviluppo-ref.sviluppo.dna/10.168.10.81:47500, 
> /10.168.10.81:47500], discPort=47500, order=6, intOrder=4, loc=false, 
> ver=1.3.0#20150710-sha1:2ade6d00, isClient=false], type=NODE_LEFT, 
> tstamp=144096055]
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.futureId(GridNearAtomicUpdateFuture.java:239)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$3.onEvent(GridCacheMvccManager.java:200)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:745)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:730)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:270)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:1740)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:1931)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:1779)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}



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

[jira] [Created] (IGNITE-1565) Platform .Net: Fix examples

[Pavel Tupitsyn (JIRA)]

Pavel  Tupitsyn created IGNITE-1565:
---

 Summary: Platform .Net: Fix examples
 Key: IGNITE-1565
 URL: https://issues.apache.org/jira/browse/IGNITE-1565
 Project: Ignite
  Issue Type: Sub-task
  Components: interop
Affects Versions: ignite-1.5
Reporter: Pavel  Tupitsyn
Assignee: Pavel  Tupitsyn
 Fix For: ignite-1.5


Paths have changed in ignite-1282 branch:
* config paths should be fixed in examples
* example files paths should be fixed in example tests



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

[jira] [Assigned] (IGNITE-533) Implement IgniteZeromqStreamer to stream data from ZeroMQ

[Chandresh Pancholi (JIRA)]

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

Chandresh Pancholi reassigned IGNITE-533:
-

Assignee: Chandresh Pancholi

> Implement IgniteZeromqStreamer to stream data from ZeroMQ
> -
>
> Key: IGNITE-533
> URL: https://issues.apache.org/jira/browse/IGNITE-533
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Chandresh Pancholi
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [ZeroMQ|http://zeromq.org/] for more info.
> We should create {{IgniteZeroMqStreamer}} which will consume messages from 
> Twitter and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert ZeroMQ messages to Ignite data using an optional pluggable 
> converter. If not provided, we should have some default mechanism.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.



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

[jira] [Assigned] (IGNITE-1560) ClassNotFoundException on AWS

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov reassigned IGNITE-1560:


Assignee: Nikolay Tikhonov

> ClassNotFoundException on AWS
> -
>
> Key: IGNITE-1560
> URL: https://issues.apache.org/jira/browse/IGNITE-1560
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
> Environment: AWS
>Reporter: Alexandre Boudnik
>Assignee: Nikolay Tikhonov
>Priority: Critical
>  Labels: maven
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Optional {{ignite-aws}} has outdated (2012) dependency:
> {code}
> 
>   com.amazonaws
>   aws-java-sdk
>   1.3.21.1
>   compile
> 
> {code}
> that depends on
> {code}
> 
> org.codehaus.jackson
> jackson-core-asl
> 1.8.9
> jar
> compile
> 
> 
> org.codehaus.jackson
> jackson-mapper-asl
> 1.8.9
> jar
> compile
> 
> {code}
> As results it produces {{ClassNotFoundException}} for 
> {{org.codehaus.jackson.JsonNode}} and 
> {{org.codehaus.jackson.map.ObjectMapper}} classes
> I would recommend to switch to newer version of {{aws-java-sdk}}, which is 
> has no external dependencies.



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

[jira] [Assigned] (IGNITE-1564) Cannot recover from org.apache.ignite.IgniteClientDisconnectedException

[Semen Boikov (JIRA)]

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

Semen Boikov reassigned IGNITE-1564:


Assignee: Semen Boikov

> Cannot recover from org.apache.ignite.IgniteClientDisconnectedException
> ---
>
> Key: IGNITE-1564
> URL: https://issues.apache.org/jira/browse/IGNITE-1564
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: ignite-1.4
>Reporter: Enrico Olivelli
>Assignee: Semen Boikov
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> Using Apache Ignite 1.4, I get this problem.
> I have two "server" nodes.
> Stop all the server nodes.
> The clients gets "IgniteClientDisconnectedException"
> Restart all the server nodes
> On client I get this error and the client cannot recover from that state.
> client has forceservermode=true
> {code}
> 15-09-29-11-06-28 SEVERE Sep 29, 2015 11:06:28 AM 
> org.apache.ignite.logger.java.JavaLogger error
> GRAVE: Runtime error caught during grid runnable execution: IgniteSpiThread 
> [name=tcp-client-disco-msg-worker-#4%SVILUPPOREF]
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.addClientNode(GridDiscoveryManager.java:338)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onDiscoveryDataReceived(GridCacheProcessor.java:1903)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$6.onExchange(GridDiscoveryManager.java:659)
>   at 
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1706)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddedMessage(ClientImpl.java:1625)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1535)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1465)
>   at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {code}
> and 
> {code}
> 15-09-14-11-14-56   SEVERE Sep 14, 2015 11:14:56 AM 
> org.apache.ignite.logger.java.JavaLogger error
> GRAVE: Unexpected exception in listener notification for event: 
> DiscoveryEvent [evtNode=TcpDiscoveryNode 
> [id=d5426d82-48ee-4a99-9737-4cf2f0cb5124, addrs=[10.168.10.81], 
> sockAddrs=[sviluppo-ref.sviluppo.dna/10.168.10.81:47500, 
> /10.168.10.81:47500], discPort=47500, order=6, intOrder=4, loc=false, 
> ver=1.3.0#20150710-sha1:2ade6d00, isClient=false], topVer=7, 
> nodeId8=a86f4ae8, msg=Node left: TcpDiscoveryNode 
> [id=d5426d82-48ee-4a99-9737-4cf2f0cb5124, addrs=[10.168.10.81], 
> sockAddrs=[sviluppo-ref.sviluppo.dna/10.168.10.81:47500, 
> /10.168.10.81:47500], discPort=47500, order=6, intOrder=4, loc=false, 
> ver=1.3.0#20150710-sha1:2ade6d00, isClient=false], type=NODE_LEFT, 
> tstamp=144096055]
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.futureId(GridNearAtomicUpdateFuture.java:239)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$3.onEvent(GridCacheMvccManager.java:200)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:745)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:730)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:270)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:1740)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:1931)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:1779)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}



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

[jira] [Commented] (IGNITE-530) Implement IgniteTwitterStreamer to stream data from Twitter feeds

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-530:
-

Lalit, Thanks for fixes!

But pull request still contains a lot of codestyle issues.
for example: 
1) 
   if (value != null){
getStreamer().addData(value);
   }
//redundant braces should re removed.

2) 
BlockingQueue tweetQueue = new 
LinkedBlockingQueue(bufferCapacity);
client = getStreamingEndpoint(tweetQueue);
//newline missed

3)
 }catch (Exception e){
  //no op
}
//No-op instead of //no op. 
Possible, error should be logged instead of //No-op.
Possible, more specified type of Exception should be handled.

4) please check that 120 symbols limit is not exceeded at code & comments.

Please check and fix all simillar issues.


> Implement IgniteTwitterStreamer to stream data from Twitter feeds
> -
>
> Key: IGNITE-530
> URL: https://issues.apache.org/jira/browse/IGNITE-530
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Lalit Kumar Jha
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> We should create {{IgniteTwitterStreamer}} which will consume messages from 
> Twitter and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert Twitter data to Ignite data using an optional pluggable converter.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.



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

[jira] [Updated] (IGNITE-1564) Cannot recover from org.apache.ignite.IgniteClientDisconnectedException

[Enrico Olivelli (JIRA)]

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

Enrico Olivelli updated IGNITE-1564:

Summary: Cannot recover from 
org.apache.ignite.IgniteClientDisconnectedException  (was: Cannot revoer from 
org.apache.ignite.IgniteClientDisconnectedException)

> Cannot recover from org.apache.ignite.IgniteClientDisconnectedException
> ---
>
> Key: IGNITE-1564
> URL: https://issues.apache.org/jira/browse/IGNITE-1564
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: ignite-1.4
>Reporter: Enrico Olivelli
>Priority: Blocker
>
> Using Apache Ignite 1.4, I get this problem.
> I have two "server" nodes.
> Stop all the server nodes.
> The clients gets "IgniteClientDisconnectedException"
> Restart all the server nodes
> On client I get this error and the client cannot recover from that state.
> client has forceservermode=true
> {code}
> 15-09-29-11-06-28 SEVERE Sep 29, 2015 11:06:28 AM 
> org.apache.ignite.logger.java.JavaLogger error
> GRAVE: Runtime error caught during grid runnable execution: IgniteSpiThread 
> [name=tcp-client-disco-msg-worker-#4%SVILUPPOREF]
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.addClientNode(GridDiscoveryManager.java:338)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onDiscoveryDataReceived(GridCacheProcessor.java:1903)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$6.onExchange(GridDiscoveryManager.java:659)
>   at 
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1706)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddedMessage(ClientImpl.java:1625)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1535)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1465)
>   at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {code}
> and 
> {code}
> 15-09-14-11-14-56   SEVERE Sep 14, 2015 11:14:56 AM 
> org.apache.ignite.logger.java.JavaLogger error
> GRAVE: Unexpected exception in listener notification for event: 
> DiscoveryEvent [evtNode=TcpDiscoveryNode 
> [id=d5426d82-48ee-4a99-9737-4cf2f0cb5124, addrs=[10.168.10.81], 
> sockAddrs=[sviluppo-ref.sviluppo.dna/10.168.10.81:47500, 
> /10.168.10.81:47500], discPort=47500, order=6, intOrder=4, loc=false, 
> ver=1.3.0#20150710-sha1:2ade6d00, isClient=false], topVer=7, 
> nodeId8=a86f4ae8, msg=Node left: TcpDiscoveryNode 
> [id=d5426d82-48ee-4a99-9737-4cf2f0cb5124, addrs=[10.168.10.81], 
> sockAddrs=[sviluppo-ref.sviluppo.dna/10.168.10.81:47500, 
> /10.168.10.81:47500], discPort=47500, order=6, intOrder=4, loc=false, 
> ver=1.3.0#20150710-sha1:2ade6d00, isClient=false], type=NODE_LEFT, 
> tstamp=144096055]
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.futureId(GridNearAtomicUpdateFuture.java:239)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$3.onEvent(GridCacheMvccManager.java:200)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:745)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:730)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:270)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:1740)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:1931)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:1779)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}



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

[jira] [Commented] (IGNITE-1564) Cannot recover from org.apache.ignite.IgniteClientDisconnectedException

[Semen Boikov (JIRA)]

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

Semen Boikov commented on IGNITE-1564:
--

Found bug in client reconnect handling which can cause NPE from the first 
stacktrace in case when multiple clients try to reconnect at the same time. 
Fixed it in branch ignite-1564, added more tests for this scenario, waiting for 
TeamCity results.

Second stacktrace is for code from 1.3, this issue should be already fixed in 
1.4.

> Cannot recover from org.apache.ignite.IgniteClientDisconnectedException
> ---
>
> Key: IGNITE-1564
> URL: https://issues.apache.org/jira/browse/IGNITE-1564
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: ignite-1.4
>Reporter: Enrico Olivelli
>Assignee: Semen Boikov
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> Using Apache Ignite 1.4, I get this problem.
> I have two "server" nodes.
> Stop all the server nodes.
> The clients gets "IgniteClientDisconnectedException"
> Restart all the server nodes
> On client I get this error and the client cannot recover from that state.
> client has forceservermode=true
> {code}
> 15-09-29-11-06-28 SEVERE Sep 29, 2015 11:06:28 AM 
> org.apache.ignite.logger.java.JavaLogger error
> GRAVE: Runtime error caught during grid runnable execution: IgniteSpiThread 
> [name=tcp-client-disco-msg-worker-#4%SVILUPPOREF]
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.addClientNode(GridDiscoveryManager.java:338)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onDiscoveryDataReceived(GridCacheProcessor.java:1903)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$6.onExchange(GridDiscoveryManager.java:659)
>   at 
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1706)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddedMessage(ClientImpl.java:1625)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1535)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1465)
>   at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {code}
> and 
> {code}
> 15-09-14-11-14-56   SEVERE Sep 14, 2015 11:14:56 AM 
> org.apache.ignite.logger.java.JavaLogger error
> GRAVE: Unexpected exception in listener notification for event: 
> DiscoveryEvent [evtNode=TcpDiscoveryNode 
> [id=d5426d82-48ee-4a99-9737-4cf2f0cb5124, addrs=[10.168.10.81], 
> sockAddrs=[sviluppo-ref.sviluppo.dna/10.168.10.81:47500, 
> /10.168.10.81:47500], discPort=47500, order=6, intOrder=4, loc=false, 
> ver=1.3.0#20150710-sha1:2ade6d00, isClient=false], topVer=7, 
> nodeId8=a86f4ae8, msg=Node left: TcpDiscoveryNode 
> [id=d5426d82-48ee-4a99-9737-4cf2f0cb5124, addrs=[10.168.10.81], 
> sockAddrs=[sviluppo-ref.sviluppo.dna/10.168.10.81:47500, 
> /10.168.10.81:47500], discPort=47500, order=6, intOrder=4, loc=false, 
> ver=1.3.0#20150710-sha1:2ade6d00, isClient=false], type=NODE_LEFT, 
> tstamp=144096055]
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.futureId(GridNearAtomicUpdateFuture.java:239)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$3.onEvent(GridCacheMvccManager.java:200)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:745)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:730)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:270)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:1740)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:1931)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:1779)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {code}



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

[jira] [Commented] (IGNITE-1570) Move .Net local benchmarks project to Ignite.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-1570:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-1570 Move .Net local benchmarks project to Ignite.



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

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

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

https://github.com/apache/ignite/pull/113.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 #113


commit 19e1148366f6390bcc8fea5bd57ca7d17bddfa48
Author: ptupitsyn 
Date:   2015-09-29T13:23:36Z

IGNITE-1570 Move .Net local benchmarks project to Ignite.

commit 8de6c7ce19de0f59222f6219f5a339a682808bd1
Author: ptupitsyn 
Date:   2015-09-29T13:25:07Z

IGNITE-1570 Move .Net local benchmarks project to Ignite.

commit 883bb320c0c9784c81c683deed66f0042deffcd7
Author: ptupitsyn 
Date:   2015-09-29T13:26:33Z

IGNITE-1570 Move .Net local benchmarks project to Ignite.

commit b42e2e4acdae0ac156861f4e51e1926952ab23b3
Author: ptupitsyn 
Date:   2015-09-29T13:30:42Z

IGNITE-1570 Move .Net local benchmarks project to Ignite - fix headers and 
references

commit c8d3673eb7027f0c47d051531dbdad2ba552c158
Author: ptupitsyn 
Date:   2015-09-29T14:04:18Z

Refactor Classpath & IgniteHome resolving code

commit 4342c94060f91cb854c8c1b31edf43e5cc7172c7
Author: ptupitsyn 
Date:   2015-09-29T14:07:45Z

wip

commit 264616f60143daedbd8c4f971718c15b8245bf8a
Author: ptupitsyn 
Date:   2015-09-29T14:10:30Z

wip

commit 32027f36e2069b1d841f926bb5b24fe5edcd2503
Author: ptupitsyn 
Date:   2015-09-29T14:13:32Z

Fix namespaces

commit 96f7a74516d1ed764e0a385fbb935328e5414ea8
Author: ptupitsyn 
Date:   2015-09-29T14:26:00Z

wip

commit fb4b01d64e7dc8eec501e98031462ba4bc400350
Author: ptupitsyn 
Date:   2015-09-29T14:29:47Z

renaming

commit f4132826a793707c421bda432e8acc08a7e7b27a
Author: ptupitsyn 
Date:   2015-09-29T14:30:13Z

renaming

commit b37406126b11587b64fb8a8fc1f75ceadc133116
Author: ptupitsyn 
Date:   2015-09-29T14:32:18Z

renaming

commit 7514b1eb2bc38a23a788307b7b043ea33909e2e1
Author: ptupitsyn 
Date:   2015-09-29T14:32:28Z

wip

commit b255c208478e86a7594703baf92fe676a9f35ebd
Author: ptupitsyn 
Date:   2015-09-29T14:37:03Z

renaming

commit d88e3c8a0e3e6a93b875be1836ac46d290e2ba9b
Author: ptupitsyn 
Date:   2015-09-29T14:37:19Z

renaming

commit 858de941d1fe335e6ca0fa1ec9677ae266036524
Author: ptupitsyn 
Date:   2015-09-29T14:39:15Z

Fix naming

commit 9f6cf5d1e3d2307dd3311987f199dec4ddcbb780
Author: ptupitsyn 
Date:   2015-09-29T14:42:33Z

code cleanup

commit eb6559d9d4ab133da3ee5f148f14f35f10b9608c
Author: ptupitsyn 
Date:   2015-09-29T14:44:30Z

cleanup

commit 1bd3e9664c87a69efb43a9f4be634f167cd5889f
Author: ptupitsyn 
Date:   2015-09-29T14:47:14Z

wip

commit d66d64c2f991f34f8a6d0a261c6788f82b30716b
Author: ptupitsyn 
Date:   2015-09-29T14:50:03Z

cleanup

commit 9a20ae9023d714b10f87f2ff6da415129a2197b5
Author: ptupitsyn 
Date:   2015-09-29T14:52:54Z

wip

commit 1801a163c413c32bd199d81f64c7e713e47334e2
Author: ptupitsyn 
Date:   2015-09-29T15:00:33Z

Code cleanup

commit 5169f81333fd0150de0a30f9656b6230f8213886
Author: ptupitsyn 
Date:   2015-09-29T15:03:36Z

xmldoc

commit 1597c62e83172ae31f0a0ed6594b9554987b2037
Author: ptupitsyn 
Date:   2015-09-29T15:05:40Z

wip

commit d434e765869589bac4efaf3d247b86cc79223da3
Author: ptupitsyn 
Date:   2015-09-29T15:10:10Z

config file

commit 3ac2a8d547a6604a0896cc15921640a813e6ce43
Author: ptupitsyn 
Date:   2015-09-29T15:11:12Z

wip

commit ebc857b3553f4e440cd98ae4c90e43eef2abffb5
Author: ptupitsyn 
Date:   2015-09-29T15:13:24Z

fix config

commit 7b698dedcb3ea144c636a02f1420350608fbf6bd
Author: ptupitsyn 
Date:   2015-09-29T15:14:45Z

Enable GC server mode

commit 2019905b392a1c90a41c9565ce77fddbdd96bb1c
Author: ptupitsyn 
Date:   2015-09-29T15:15:18Z

Fix header

commit 

[jira] [Resolved] (IGNITE-1504) Add cache name to the warning

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov resolved IGNITE-1504.
---
Resolution: Won't Fix

> Add cache name to the warning
> -
>
> Key: IGNITE-1504
> URL: https://issues.apache.org/jira/browse/IGNITE-1504
> Project: Ignite
>  Issue Type: Task
>  Components: UI
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Yakov Zhdanov
>Priority: Trivial
> Fix For: ignite-1.5
>
>
> I got this warning but I don't understand what cache this warning is about.
> Please add cache name.
> {code}
> [10:58:21,931][WARNING][ignite-#21%sys-tester%][GridDhtPartitionsExchangeFuture]
>  Retrying preload partition exchange due to timeout [done=false, dummy=false, 
> exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=4, 
> minorTopVer=0], nodeId=2135f8b4, evt=NODE_JOINED], rcvdIds=[], 
> rmtIds=[dec935df, 0237a5ca], remaining=[dec935df, 0237a5ca], init=true, 
> initFut=true, ready=true, replied=false, added=true, oldest=dec935df, 
> oldestOrder=1, evtLatch=0, locNodeOrder=4, locNodeId=2135f8b
> 4-9633-447e-be13-b7285e76bab3]
> {code}



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

[jira] [Updated] (IGNITE-1270) OSGi support for Ignite

[JIRA]

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

Raúl Kripalani updated IGNITE-1270:
---
Fix Version/s: ignite-1.5

> OSGi support for Ignite
> ---
>
> Key: IGNITE-1270
> URL: https://issues.apache.org/jira/browse/IGNITE-1270
> Project: Ignite
>  Issue Type: New Feature
>  Components: general
>Reporter: Raúl Kripalani
>Assignee: Raúl Kripalani
> Fix For: ignite-1.5
>
>
> Basics for a first iteration:
> * Manifest creation for all Java-based modules.
> * Apache Karaf features file to facilitate deployment (along with 
> dependencies).
> Future:
> * Support peer class-loading.
> * Potentially support remote 3rd dependency class-loading for Apache Karaf 
> (via Pax Mvn URL and Aether, one can fetch a bundle from Maven repositories).



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

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

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-1355:
--
Priority: Critical  (was: Major)

> 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: Artem Shutak
>Priority: Critical
> 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] [Commented] (IGNITE-1564) Cannot recover from org.apache.ignite.IgniteClientDisconnectedException

[Enrico Olivelli (JIRA)]

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

Enrico Olivelli commented on IGNITE-1564:
-

I found a workaround.
My previuos  code was like this:
{code}
Ignite ignite = 
set forceservermode = true
IgniteCache cache = ignite.getOrCreateNearCache();
while (true) {
try {
  cache.get(...)
   } catch (Exception tryagain) {
  tryagain.printStackTrace();  
   }
   Thread.sleep();
}
{code}

New code which recovers from servers shutdown:
{code}
Ignite ignite = 
set forceservermode = false
whiel (true) {
   try {
IgniteCache cache = ignite.getOrCreateNearCache();
cache.get(...)
   } catch (Exception tryagain) {
  tryagain.printStackTrace();  
   }
   Thread.sleep();
}
{code}





> Cannot recover from org.apache.ignite.IgniteClientDisconnectedException
> ---
>
> Key: IGNITE-1564
> URL: https://issues.apache.org/jira/browse/IGNITE-1564
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: ignite-1.4
>Reporter: Enrico Olivelli
>Assignee: Semen Boikov
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> Using Apache Ignite 1.4, I get this problem.
> I have two "server" nodes.
> Stop all the server nodes.
> The clients gets "IgniteClientDisconnectedException"
> Restart all the server nodes
> On client I get this error and the client cannot recover from that state.
> client has forceservermode=true
> {code}
> 15-09-29-11-06-28 SEVERE Sep 29, 2015 11:06:28 AM 
> org.apache.ignite.logger.java.JavaLogger error
> GRAVE: Runtime error caught during grid runnable execution: IgniteSpiThread 
> [name=tcp-client-disco-msg-worker-#4%SVILUPPOREF]
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.addClientNode(GridDiscoveryManager.java:338)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onDiscoveryDataReceived(GridCacheProcessor.java:1903)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$6.onExchange(GridDiscoveryManager.java:659)
>   at 
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1706)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddedMessage(ClientImpl.java:1625)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1535)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1465)
>   at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {code}
> and 
> {code}
> 15-09-14-11-14-56   SEVERE Sep 14, 2015 11:14:56 AM 
> org.apache.ignite.logger.java.JavaLogger error
> GRAVE: Unexpected exception in listener notification for event: 
> DiscoveryEvent [evtNode=TcpDiscoveryNode 
> [id=d5426d82-48ee-4a99-9737-4cf2f0cb5124, addrs=[10.168.10.81], 
> sockAddrs=[sviluppo-ref.sviluppo.dna/10.168.10.81:47500, 
> /10.168.10.81:47500], discPort=47500, order=6, intOrder=4, loc=false, 
> ver=1.3.0#20150710-sha1:2ade6d00, isClient=false], topVer=7, 
> nodeId8=a86f4ae8, msg=Node left: TcpDiscoveryNode 
> [id=d5426d82-48ee-4a99-9737-4cf2f0cb5124, addrs=[10.168.10.81], 
> sockAddrs=[sviluppo-ref.sviluppo.dna/10.168.10.81:47500, 
> /10.168.10.81:47500], discPort=47500, order=6, intOrder=4, loc=false, 
> ver=1.3.0#20150710-sha1:2ade6d00, isClient=false], type=NODE_LEFT, 
> tstamp=144096055]
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.futureId(GridNearAtomicUpdateFuture.java:239)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$3.onEvent(GridCacheMvccManager.java:200)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:745)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:730)
> at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:270)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:1740)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:1931)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:1779)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> 

[jira] [Commented] (IGNITE-950) OptimizedMarshaller: add ability to unmarshal a particular field

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-950:
-

My original design with adding methods on the Marshaller interface does not 
really work well because in order to truly plug into cache mechanics the cache 
object manager (introduced) should be pluggable.
Since we still want to configure a marshaller per cache, I suggest using an 
annotation attached to a marshaller indicating that another cache object 
manager should be used for a cache:
{code}
@CacheObjectManager(PortableObjectManager.class)
public class PortableMarshaller extends MarshallerAdapter {
}
{code}

> OptimizedMarshaller: add ability to unmarshal a particular field
> 
>
> Key: IGNITE-950
> URL: https://issues.apache.org/jira/browse/IGNITE-950
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: sprint-5
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
> Fix For: ignite-1.5
>
>
> When field names of an object are used in SQL, text or other kind of queries, 
> object, that owns a field, is fully deserialized.
> This is bad from performance perspective. 
> The task is to support peer field deserialization by looking it up in a 
> marshalled byte array and unmarshalling it from a concrete offset with 
> OptimizedMarshaller later. 



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

[jira] [Created] (IGNITE-1572) .Net: Check if we can get rid of "WritePortableOrSerializable" method.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-1572:
---

 Summary: .Net: Check if we can get rid of 
"WritePortableOrSerializable" method.
 Key: IGNITE-1572
 URL: https://issues.apache.org/jira/browse/IGNITE-1572
 Project: Ignite
  Issue Type: Task
  Components: interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: ignite-1.5


We have lots of places where "WritePortableOrSerializable" routine is invoked. 
It is not clear why do we need it provided that we already handle 
[Serializable] classes properly. 
Looks like we are able to get rid of it safely, aren't we? Need to double-check.



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

[jira] [Updated] (IGNITE-1528) Support client mode with Ignite OSGi

[JIRA]

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

Raúl Kripalani updated IGNITE-1528:
---
Fix Version/s: ignite-1.5

> Support client mode with Ignite OSGi
> 
>
> Key: IGNITE-1528
> URL: https://issues.apache.org/jira/browse/IGNITE-1528
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Reporter: Raúl Kripalani
>Assignee: Raúl Kripalani
> Fix For: ignite-1.5
>
>




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

[jira] [Assigned] (IGNITE-1567) Optimize portable object fields read/write in .Net.

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn reassigned IGNITE-1567:
---

Assignee: Pavel  Tupitsyn

> Optimize portable object fields read/write in .Net.
> ---
>
> Key: IGNITE-1567
> URL: https://issues.apache.org/jira/browse/IGNITE-1567
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Critical
>




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

[jira] [Commented] (IGNITE-1504) Add cache name to the warning

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-1504:
--

It is actually impossible to say which cache causes this warning because 
partition exchange is executed once for all caches. Whenever possible, we 
already print out all possible objects that may have caused partition exchange 
timeout (see {{dumpPendingObjects}} in partition exchange future).

I think this should be closed.

> Add cache name to the warning
> -
>
> Key: IGNITE-1504
> URL: https://issues.apache.org/jira/browse/IGNITE-1504
> Project: Ignite
>  Issue Type: Task
>  Components: UI
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Yakov Zhdanov
>Priority: Trivial
> Fix For: ignite-1.5
>
>
> I got this warning but I don't understand what cache this warning is about.
> Please add cache name.
> {code}
> [10:58:21,931][WARNING][ignite-#21%sys-tester%][GridDhtPartitionsExchangeFuture]
>  Retrying preload partition exchange due to timeout [done=false, dummy=false, 
> exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=4, 
> minorTopVer=0], nodeId=2135f8b4, evt=NODE_JOINED], rcvdIds=[], 
> rmtIds=[dec935df, 0237a5ca], remaining=[dec935df, 0237a5ca], init=true, 
> initFut=true, ready=true, replied=false, added=true, oldest=dec935df, 
> oldestOrder=1, evtLatch=0, locNodeOrder=4, locNodeId=2135f8b
> 4-9633-447e-be13-b7285e76bab3]
> {code}



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

[jira] [Assigned] (IGNITE-1380) Random eviction policy for near cache works incorrectly

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov reassigned IGNITE-1380:
-

Assignee: Andrey Gura  (was: Yakov Zhdanov)

> Random eviction policy for near cache works incorrectly
> ---
>
> Key: IGNITE-1380
> URL: https://issues.apache.org/jira/browse/IGNITE-1380
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Andrey Gura
> Fix For: ignite-1.5
>
>
> Start two server nodes with cache with near cache with configuration below 
> (node with load generation and one more data node).
> Put 2000 keys (from 1 to 2000), read 200 key (from 1 to 200) using first 
> node. 
> {code}
> 
> 
> 
> 
> 
>  class="org.apache.ignite.configuration.NearCacheConfiguration">
> 
>  class="org.apache.ignite.cache.eviction.random.RandomEvictionPolicy">
> 
> 
> 
> 
> 
> 
> {code}
> Near cache contains more keys then I set in configuration (maxSize=100).
> Others eviction policies are  works correctly.



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

[jira] [Updated] (IGNITE-1450) Excessive exceptions are printed out during cache/node stop

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-1450:
--
Priority: Minor  (was: Major)

> Excessive exceptions are printed out during cache/node stop
> ---
>
> Key: IGNITE-1450
> URL: https://issues.apache.org/jira/browse/IGNITE-1450
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.1.4
>Reporter: Alexey Goncharuk
>Assignee: Yakov Zhdanov
>Priority: Minor
> Fix For: ignite-1.5
>
>
> In my unit tests, I start and stop caches in quick succession and my logs are 
> full of the following exceptions:
> 6983 [exchange-worker-#114%t1-1%] ERROR GridCachePartitionExchangeManager - 
> Runtime error caught during grid runnable execution: GridWorker 
> [name=partition-exchanger, gridName=t1-1, finished=false, isCancelled=false, 
> hashCode=1934136092, interrupted=false, runner=exchange-worker-#114%t1-1%]
> class org.apache.ignite.IgniteException: Failed to wait for affinity ready 
> future for topology version: AffinityTopologyVersion [topVer=2, minorTopVer=2]
> at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.awaitTopologyVersion(GridAffinityAssignmentCache.java:443)
> at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:398)
> at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.nodes(GridAffinityAssignmentCache.java:363)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.nodes(GridCacheAffinityManager.java:201)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.localNode(GridCacheAffinityManager.java:303)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemandPool.assign(GridDhtPartitionDemandPool.java:1028)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.assign(GridDhtPreloader.java:260)
> at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1076)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to wait for 
> topology update, cache (or node) is stopping.
> at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.readyFuture(GridAffinityAssignmentCache.java:316)
> at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.awaitTopologyVersion(GridAffinityAssignmentCache.java:437)
> ... 9 more



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

[jira] [Updated] (IGNITE-1527) Add OSGi manifest headers to all ignite-core + basic bundles

[JIRA]

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

Raúl Kripalani updated IGNITE-1527:
---
Fix Version/s: ignite-1.5

> Add OSGi manifest headers to all ignite-core + basic bundles
> 
>
> Key: IGNITE-1527
> URL: https://issues.apache.org/jira/browse/IGNITE-1527
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Reporter: Raúl Kripalani
>Assignee: Raúl Kripalani
> Fix For: ignite-1.5
>
>
> And make sure they interoperate properly with each other.



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

[jira] [Commented] (IGNITE-1559) Need to improve tests, javadoc and documentation of UriDeploymentHttpScanner.

[Artem Shutak (JIRA)]

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

Artem Shutak commented on IGNITE-1559:
--

PR: https://github.com/apache/ignite/pull/114.

The PR contains changes at 'uri/pom.xml' it should be run on TC.

> Need to improve tests, javadoc and documentation of UriDeploymentHttpScanner.
> -
>
> Key: IGNITE-1559
> URL: https://issues.apache.org/jira/browse/IGNITE-1559
> Project: Ignite
>  Issue Type: Task
>Reporter: Artem Shutak
>Assignee: Artem Shutak
> Fix For: ignite-1.5
>
>
> Need to improve tests, javadoc and documentation of UriDeploymentHttpScanner. 
> It's not possible to understand from current javadoc of 
> UriDeploymentHttpScanner how it works.
> There's only one simple test in GridHttpDeploymentSelfTest.



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

[jira] [Updated] (IGNITE-1567) Optimize portable object fields read/write in .Net.

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn updated IGNITE-1567:

Description: 
1) Infer field length for primitive types
2) Optimize Zero const writing
3) ...

  was:
1) Infer field length for primitive types
2) Optimize Zero const writing


> Optimize portable object fields read/write in .Net.
> ---
>
> Key: IGNITE-1567
> URL: https://issues.apache.org/jira/browse/IGNITE-1567
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Critical
>
> 1) Infer field length for primitive types
> 2) Optimize Zero const writing
> 3) ...



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

[jira] [Updated] (IGNITE-1567) Optimize portable object fields read/write in .Net.

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn updated IGNITE-1567:

Description: 
1) Infer field length for primitive types
2) Optimize Zero const writing

  was:
1) Infer field length for primitive types
2) ...


> Optimize portable object fields read/write in .Net.
> ---
>
> Key: IGNITE-1567
> URL: https://issues.apache.org/jira/browse/IGNITE-1567
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel  Tupitsyn
>Priority: Critical
>
> 1) Infer field length for primitive types
> 2) Optimize Zero const writing



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

[jira] [Commented] (IGNITE-1559) Need to improve tests, javadoc and documentation of UriDeploymentHttpScanner.

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-1559:
-

Artem,

I moved the article here: https://apacheignite.readme.io/docs/deployment-spi. I 
also made several fixes there. Can you please go through it and fix javadoc 
accordingly? I will merge after that.

> Need to improve tests, javadoc and documentation of UriDeploymentHttpScanner.
> -
>
> Key: IGNITE-1559
> URL: https://issues.apache.org/jira/browse/IGNITE-1559
> Project: Ignite
>  Issue Type: Task
>Reporter: Artem Shutak
>Assignee: Valentin Kulichenko
> Fix For: ignite-1.5
>
>
> Need to improve tests, javadoc and documentation of UriDeploymentHttpScanner. 
> It's not possible to understand from current javadoc of 
> UriDeploymentHttpScanner how it works.
> There's only one simple test in GridHttpDeploymentSelfTest.



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

[jira] [Updated] (IGNITE-1272) PortableMarshaller: issues when different class loaders are used

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-1272:

Assignee: Denis Magda  (was: Valentin Kulichenko)

> PortableMarshaller: issues when different class loaders are used
> 
>
> Key: IGNITE-1272
> URL: https://issues.apache.org/jira/browse/IGNITE-1272
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Blocker
> Fix For: ignite-1.5
>
> Attachments: ignite-1272.patch
>
>
> The reason is that a loader is not passed to required places when needed.
> Reproduced with the following tests:
> - {{IgniteCacheAbstractExecutionContextTest.testUserClassLoader()}} fails 
> with PortableMarshaller enabled.
> - {{GridDeploymentMessageCountSelfTest.testCacheValueDeploymentOnPut()}}
> Another issue is when {{PortableContext}} returns {{PortableClassDescriptor}} 
> by type id. Returned descriptor has a constructor which already has been 
> loaded with another class loader. Fix is not trivial and issue is reproduced 
> with {{GridP2PRemoteClassLoadersSelfTest}}
> Look for corresponding TODOs in the code.
> Unmute tests when fixed



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

[jira] [Commented] (IGNITE-1272) PortableMarshaller: issues when different class loaders are used

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-1272:
-

Denis,

I'm not sure I understood the purpose of {{descriptorLoadingFailover(...)}} 
method. Can you please provide details? Also why you get the descriptor from 
the {{userTypes}} map, but return it only if was loaded by default loader? Why 
do we need it in this map then?

Thanks!

> PortableMarshaller: issues when different class loaders are used
> 
>
> Key: IGNITE-1272
> URL: https://issues.apache.org/jira/browse/IGNITE-1272
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Fix For: ignite-1.5
>
> Attachments: ignite-1272.patch
>
>
> The reason is that a loader is not passed to required places when needed.
> Reproduced with the following tests:
> - {{IgniteCacheAbstractExecutionContextTest.testUserClassLoader()}} fails 
> with PortableMarshaller enabled.
> - {{GridDeploymentMessageCountSelfTest.testCacheValueDeploymentOnPut()}}
> Another issue is when {{PortableContext}} returns {{PortableClassDescriptor}} 
> by type id. Returned descriptor has a constructor which already has been 
> loaded with another class loader. Fix is not trivial and issue is reproduced 
> with {{GridP2PRemoteClassLoadersSelfTest}}
> Look for corresponding TODOs in the code.
> Unmute tests when fixed



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

[jira] [Resolved] (IGNITE-925) We should correctly handle cross-cache query exceptions

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov resolved IGNITE-925.
---
Resolution: Cannot Reproduce

Cannot reproduce anymore. Closed.

> We should correctly handle cross-cache query exceptions
> ---
>
> Key: IGNITE-925
> URL: https://issues.apache.org/jira/browse/IGNITE-925
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-5
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: ignite-1.5
>
>
> Grid with two nodes.
> Node1 contains cache1 with Type1
> Node2 contains cache2 with Type2
> Query: select * from 'cache1'.type1



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

[jira] [Updated] (IGNITE-1168) REST API: type metadata for cache

[Andrey Novikov (JIRA)]

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

Andrey Novikov updated IGNITE-1168:
---
Attachment: master_7402918_ignite-1168.patch

> REST API: type metadata for cache
> -
>
> Key: IGNITE-1168
> URL: https://issues.apache.org/jira/browse/IGNITE-1168
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
>Assignee: Semen Boikov
> Fix For: ignite-1.5
>
> Attachments: IGNITE-1168.patch, master_7402918_ignite-1168.patch
>
>
> Apache Ignite supports query so will be useful to implement command that 
> return type metadata for display in SQL query editor.



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

[jira] [Updated] (IGNITE-1168) REST API: type metadata for cache

[Andrey Novikov (JIRA)]

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

Andrey Novikov updated IGNITE-1168:
---
Attachment: (was: master_0a41ae5_ignite-1168.patch)

> REST API: type metadata for cache
> -
>
> Key: IGNITE-1168
> URL: https://issues.apache.org/jira/browse/IGNITE-1168
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
>Assignee: Semen Boikov
> Fix For: ignite-1.5
>
> Attachments: IGNITE-1168.patch, master_7402918_ignite-1168.patch
>
>
> Apache Ignite supports query so will be useful to implement command that 
> return type metadata for display in SQL query editor.



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

[jira] [Created] (IGNITE-1574) Exception is not rethrown if entry processor fails during commit

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-1574:
---

 Summary: Exception is not rethrown if entry processor fails during 
commit
 Key: IGNITE-1574
 URL: https://issues.apache.org/jira/browse/IGNITE-1574
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Valentin Kulichenko
 Fix For: ignite-1.5


See user@ thread: 
http://apache-ignite-users.70518.x6.nabble.com/CacheEntryProcessor-failing-on-transactional-cache-td1501.html

Entry processor fails during commit, transaction is correctly rolled back, but 
the exception is not rethrown to the client.



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

[jira] [Created] (IGNITE-1575) NPE when cache is started concurrently with the node stop

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-1575:
---

 Summary: NPE when cache is started concurrently with the node stop
 Key: IGNITE-1575
 URL: https://issues.apache.org/jira/browse/IGNITE-1575
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Valentin Kulichenko
Priority: Minor
 Fix For: ignite-1.5


It's not causing any harm, but it's possible to get the NPE below during the 
node stop.

{noformat}
57724 [main] ERROR IgniteKernal%t1-1 - Got exception while starting (will 
rollback startup routine).
java.lang.NullPointerException
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onKernalStart0(CacheContinuousQueryManager.java:91)
at 
org.apache.ignite.internal.processors.cache.GridCacheManagerAdapter.onKernalStart(GridCacheManagerAdapter.java:97)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:1058)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:833)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:829)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1549)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1416)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:916)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:477)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:458)
at org.apache.ignite.Ignition.start(Ignition.java:321)
.. application stack frames ...
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
{noformat}



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

[jira] [Updated] (IGNITE-1575) NPE when cache is started concurrently with the node stop

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-1575:

Labels: usability  (was: )

> NPE when cache is started concurrently with the node stop
> -
>
> Key: IGNITE-1575
> URL: https://issues.apache.org/jira/browse/IGNITE-1575
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Valentin Kulichenko
>Priority: Minor
>  Labels: usability
> Fix For: ignite-1.5
>
>
> It's not causing any harm, but it's possible to get the NPE below during the 
> node stop.
> {noformat}
> 57724 [main] ERROR IgniteKernal%t1-1 - Got exception while starting (will 
> rollback startup routine).
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onKernalStart0(CacheContinuousQueryManager.java:91)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheManagerAdapter.onKernalStart(GridCacheManagerAdapter.java:97)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:1058)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:833)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:829)
> at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1549)
> at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1416)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:916)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:477)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:458)
> at org.apache.ignite.Ignition.start(Ignition.java:321)
> .. application stack frames ...
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
> at 
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
> at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> {noformat}



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

[jira] [Commented] (IGNITE-1272) PortableMarshaller: issues when different class loaders are used

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-1272:
-

Val, thanks for the review.

1) Also why you get the descriptor from the userTypes map, but return it only 
if was loaded by default loader?

Because if it's a custom class loader like {{GridDeploymentClassLoader}} we 
have to give him a chance to reload a class. It least this is required for 
compute engine to be fully workable in conjunction with {{PortableMarshaller}}.

2) Why do we need it in this map then?

We store class descriptors of custom class loaders in a map for cases when it 
wasn't possible to load a class from the cache ({{marshCtx.getClass}}).
It may happen when during serialization we don't manage to register it in the 
cache {{registered = marshCtx.registerClass(typeId, cls)}} and write full class 
name into the serialization form. When it's time to deserialize such a object 
we won't be able to get its class from {{marshCtx.getClass}} but will be able 
from {{userTypes}}.

3) I'm not sure I understood the purpose of {{descriptorLoadingFailover(...)}} 
method. 

First, it's is needed for the reason described in 2).

Second. The user may register types with {{PortableTypeConfiguration}}. Most 
likely class descriptors registered this way will be bound to default class 
loader in {{userTypes}}.
Then there can be a case when {{CacheClassLoader}} tries to deserialize on 
object of a type registered with {{PortableTypeConfiguration}}. 
{{CacheClassLoader}} won't be able to load this class (it seems that it doesn't 
perform lookup in the classpath) and {{descriptorLoadingFailover(...)}} will 
try to find class descriptor using the default class loader.

> PortableMarshaller: issues when different class loaders are used
> 
>
> Key: IGNITE-1272
> URL: https://issues.apache.org/jira/browse/IGNITE-1272
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Blocker
> Fix For: ignite-1.5
>
> Attachments: ignite-1272.patch
>
>
> The reason is that a loader is not passed to required places when needed.
> Reproduced with the following tests:
> - {{IgniteCacheAbstractExecutionContextTest.testUserClassLoader()}} fails 
> with PortableMarshaller enabled.
> - {{GridDeploymentMessageCountSelfTest.testCacheValueDeploymentOnPut()}}
> Another issue is when {{PortableContext}} returns {{PortableClassDescriptor}} 
> by type id. Returned descriptor has a constructor which already has been 
> loaded with another class loader. Fix is not trivial and issue is reproduced 
> with {{GridP2PRemoteClassLoadersSelfTest}}
> Look for corresponding TODOs in the code.
> Unmute tests when fixed



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

[jira] [Created] (IGNITE-1577) IlligateStateException when removing index during stop

[Dmitriy Setrakyan (JIRA)]

Dmitriy Setrakyan created IGNITE-1577:
-

 Summary: IlligateStateException when removing index during stop
 Key: IGNITE-1577
 URL: https://issues.apache.org/jira/browse/IGNITE-1577
 Project: Ignite
  Issue Type: Bug
  Components: SQL
Reporter: Dmitriy Setrakyan
Assignee: Sergi Vladykin
Priority: Critical
 Fix For: ignite-1.5


I ran string example which queries the streamed words on 2 nodes (2GB each), 
and while running, killed 1 node.

Got this error.
{code}
java.lang.IllegalStateException: Failed to remove from index (grid is stopping).
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.remove(GridQueryProcessor.java:837)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.remove(GridCacheQueryManager.java:433)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.clearIndex(GridCacheMapEntry.java:3553)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.onTtlExpired(GridCacheMapEntry.java:3374)
at 
org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:117)
at 
org.apache.ignite.internal.processors.cache.GridCacheTtlManager$CleanupWorker.body(GridCacheTtlManager.java:136)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
{code}



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

[jira] [Closed] (IGNITE-925) We should correctly handle cross-cache query exceptions

[Pavel Konstantinov (JIRA)]

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

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

> We should correctly handle cross-cache query exceptions
> ---
>
> Key: IGNITE-925
> URL: https://issues.apache.org/jira/browse/IGNITE-925
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-5
>Reporter: Pavel Konstantinov
> Fix For: ignite-1.5
>
>
> Grid with two nodes.
> Node1 contains cache1 with Type1
> Node2 contains cache2 with Type2
> Query: select * from 'cache1'.type1



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

[jira] [Comment Edited] (IGNITE-1526) IBM JDK is not fully supported by the platfrom

[Andrey Gura (JIRA)]

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

Andrey Gura edited comment on IGNITE-1526 at 9/29/15 7:13 PM:
--

{{serialVersionUID}} was added to some anonymous classes in {{ignite-core}}. 
Discovery works, but requires additional testing.

{{OptimizedMarshaller}} uses JDK {{serialVersionUID}} for classes that 
implement {{Serializable}} interface. It is incorrect behavior for cases with 
different JVMs in cluster. In order to provide backward compatibility this code 
will execute only if special flag switched on via system properties. Otherwise, 
another mechanism will be used for checksum (based on {{serialVersionUID}}) 
calculation. {{IgniteCacheFullApiMultiJvmSelfTestSuite}} with 
{{OptimizedMarshaller}} passed successfully with Oracle JDK on local node and 
IBM JDK on remote nodes.

{{IgniteCacheFullApiMultiJvmSelfTestSuite}} with {{PortableMarshaller}} passed 
almost successfully with different JDKs. But there is one problem in some tests:

{noformat}
class org.apache.ignite.IgniteException: Duplicate ID [id=-1996663899, 
oldCls=org.apache.ignite.testframework.junits.multijvm.IgniteProcessProxy$LocalNodeCallable,
 
newCls=org.apache.ignite.testframework.junits.multijvm.IgniteClusterProcessProxy$LocalNodeCallable
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:881)
at 
org.apache.ignite.internal.IgniteComputeImpl.call(IgniteComputeImpl.java:355)
at 
org.apache.ignite.testframework.junits.multijvm.IgniteClusterProcessProxy.localNode(IgniteClusterProcessProxy.java:87)
at 
org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testEvictExpired(GridCacheAbstractFullApiSelfTest.java:3176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1670)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1608)
Caused by: class org.apache.ignite.IgniteCheckedException: Duplicate ID 
[id=-1996663899, 
oldCls=org.apache.ignite.testframework.junits.multijvm.IgniteProcessProxy$LocalNodeCallable,
 
newCls=org.apache.ignite.testframework.junits.multijvm.IgniteClusterProcessProxy$LocalNodeCallable
at 
org.apache.ignite.internal.MarshallerContextAdapter.registerClass(MarshallerContextAdapter.java:163)
at 
org.apache.ignite.internal.portable.PortableContext.registerUserClassDescriptor(PortableContext.java:549)
at 
org.apache.ignite.internal.portable.PortableContext.registerClassDescriptor(PortableContext.java:528)
at 
org.apache.ignite.internal.portable.PortableContext.descriptorForClass(PortableContext.java:443)
at 
org.apache.ignite.internal.portable.PortableWriterExImpl.marshal(PortableWriterExImpl.java:194)
at 
org.apache.ignite.internal.portable.PortableWriterExImpl.doWriteObject(PortableWriterExImpl.java:534)
at 
org.apache.ignite.internal.portable.PortableWriterExImpl.writeObject(PortableWriterExImpl.java:1471)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.writeExternal(GridClosureProcessor.java:1803)
at 
org.apache.ignite.internal.portable.PortableClassDescriptor.write(PortableClassDescriptor.java:543)
at 
org.apache.ignite.internal.portable.PortableWriterExImpl.marshal(PortableWriterExImpl.java:261)
at 
org.apache.ignite.internal.portable.GridPortableMarshaller.marshal(GridPortableMarshaller.java:228)
at 
org.apache.ignite.internal.portable.api.PortableMarshaller.marshal(PortableMarshaller.java:317)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1203)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:609)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:501)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:678)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:403)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:583)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:423)
at 

[jira] [Comment Edited] (IGNITE-1526) IBM JDK is not fully supported by the platfrom

[Andrey Gura (JIRA)]

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

Andrey Gura edited comment on IGNITE-1526 at 9/29/15 7:12 PM:
--

{{serialVersionUID}} was added to some anonymous classes in {{ignite-core}}. 
Discovery works, but requires additional testing.

{{OptimizedMarshaller}} uses JDK {{serialVersionUID}} for classes that 
implement {{Serializable}} interface. It is incorrect behavior for cases with 
different JVMs in cluster. In order to provide backward compatibility this code 
will execute only if special flag switched on via system properties. Otherwise, 
another mechanism will be used for checksum (based on {{serialVersionUID}}) 
calculation. {{IgniteCacheFullApiMultiJvmSelfTestSuite}} with 
{{OptimizedMarshaller}} passed successfully with Oracle JDK on lolcal node and 
IBM JDK on remote nodes.

{{IgniteCacheFullApiMultiJvmSelfTestSuite}} with {{PortableMarshaller}} passed 
almost successfully with different JDKs. But there is one problem in some tests:

{noformat}
class org.apache.ignite.IgniteException: Duplicate ID [id=-1996663899, 
oldCls=org.apache.ignite.testframework.junits.multijvm.IgniteProcessProxy$LocalNodeCallable,
 
newCls=org.apache.ignite.testframework.junits.multijvm.IgniteClusterProcessProxy$LocalNodeCallable
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:881)
at 
org.apache.ignite.internal.IgniteComputeImpl.call(IgniteComputeImpl.java:355)
at 
org.apache.ignite.testframework.junits.multijvm.IgniteClusterProcessProxy.localNode(IgniteClusterProcessProxy.java:87)
at 
org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testEvictExpired(GridCacheAbstractFullApiSelfTest.java:3176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1670)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1608)
Caused by: class org.apache.ignite.IgniteCheckedException: Duplicate ID 
[id=-1996663899, 
oldCls=org.apache.ignite.testframework.junits.multijvm.IgniteProcessProxy$LocalNodeCallable,
 
newCls=org.apache.ignite.testframework.junits.multijvm.IgniteClusterProcessProxy$LocalNodeCallable
at 
org.apache.ignite.internal.MarshallerContextAdapter.registerClass(MarshallerContextAdapter.java:163)
at 
org.apache.ignite.internal.portable.PortableContext.registerUserClassDescriptor(PortableContext.java:549)
at 
org.apache.ignite.internal.portable.PortableContext.registerClassDescriptor(PortableContext.java:528)
at 
org.apache.ignite.internal.portable.PortableContext.descriptorForClass(PortableContext.java:443)
at 
org.apache.ignite.internal.portable.PortableWriterExImpl.marshal(PortableWriterExImpl.java:194)
at 
org.apache.ignite.internal.portable.PortableWriterExImpl.doWriteObject(PortableWriterExImpl.java:534)
at 
org.apache.ignite.internal.portable.PortableWriterExImpl.writeObject(PortableWriterExImpl.java:1471)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.writeExternal(GridClosureProcessor.java:1803)
at 
org.apache.ignite.internal.portable.PortableClassDescriptor.write(PortableClassDescriptor.java:543)
at 
org.apache.ignite.internal.portable.PortableWriterExImpl.marshal(PortableWriterExImpl.java:261)
at 
org.apache.ignite.internal.portable.GridPortableMarshaller.marshal(GridPortableMarshaller.java:228)
at 
org.apache.ignite.internal.portable.api.PortableMarshaller.marshal(PortableMarshaller.java:317)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1203)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:609)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:501)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:678)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:403)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:583)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:423)
at 

[jira] [Created] (IGNITE-1573) IGFS: mkdirs operations should be truly thread-safe

[Ivan Veselovsky (JIRA)]

Ivan Veselovsky created IGNITE-1573:
---

 Summary: IGFS: mkdirs operations should be truly thread-safe
 Key: IGNITE-1573
 URL: https://issues.apache.org/jira/browse/IGNITE-1573
 Project: Ignite
  Issue Type: Bug
  Components: hadoop
Affects Versions: ignite-1.4
Reporter: Ivan Veselovsky
Assignee: Ivan Veselovsky
 Fix For: ignite-1.5


Need to lock all the existing parents and try to add the missing path in one 
transaction.
If failed due to concurrent creation, retry from the beginning.



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

[jira] [Commented] (IGNITE-1526) IBM JDK is not fully supported by the platfrom

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-1526:
-

{{serialVersionUID}} was added to some anonymous classes in {{ignite-core}}. 
Discovery works, but requires additional testing.

{{OptimizedMarshaller}} uses JDK {{serialVersionUID}} for classes that 
implement {{Serializable}} interface. It is incorrect behavior for cases with 
different JVMs in cluster. In order to provide backward compatibility this code 
will execute only if special flag switched on via system properties. Otherwise, 
another mechanism will be used for checksum (based on {{serialVersionUID}}) 
calculation. {{IgniteCacheFullApiMultiJvmSelfTestSuite}} with 
{{OptimizedMarshaller}} passed successfully with Oracle JDK on lolcal node and 
IBM JDK on remote nodes.

{{IgniteCacheFullApiMultiJvmSelfTestSuite}} with {{PortableMarshaller}} passed 
almost successfully with different JDKs. But there is one problem in some tests:

{noformat}
class org.apache.ignite.IgniteException: Duplicate ID [id=-1996663899, 
oldCls=org.apache.ignite.testframework.junits.multijvm.IgniteProcessProxy$LocalNodeCallable,
 
newCls=org.apache.ignite.testframework.junits.multijvm.IgniteClusterProcessProxy$LocalNodeCallable
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:881)
at 
org.apache.ignite.internal.IgniteComputeImpl.call(IgniteComputeImpl.java:355)
at 
org.apache.ignite.testframework.junits.multijvm.IgniteClusterProcessProxy.localNode(IgniteClusterProcessProxy.java:87)
at 
org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testEvictExpired(GridCacheAbstractFullApiSelfTest.java:3176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1670)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1608)
Caused by: class org.apache.ignite.IgniteCheckedException: Duplicate ID 
[id=-1996663899, 
oldCls=org.apache.ignite.testframework.junits.multijvm.IgniteProcessProxy$LocalNodeCallable,
 
newCls=org.apache.ignite.testframework.junits.multijvm.IgniteClusterProcessProxy$LocalNodeCallable
at 
org.apache.ignite.internal.MarshallerContextAdapter.registerClass(MarshallerContextAdapter.java:163)
at 
org.apache.ignite.internal.portable.PortableContext.registerUserClassDescriptor(PortableContext.java:549)
at 
org.apache.ignite.internal.portable.PortableContext.registerClassDescriptor(PortableContext.java:528)
at 
org.apache.ignite.internal.portable.PortableContext.descriptorForClass(PortableContext.java:443)
at 
org.apache.ignite.internal.portable.PortableWriterExImpl.marshal(PortableWriterExImpl.java:194)
at 
org.apache.ignite.internal.portable.PortableWriterExImpl.doWriteObject(PortableWriterExImpl.java:534)
at 
org.apache.ignite.internal.portable.PortableWriterExImpl.writeObject(PortableWriterExImpl.java:1471)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.writeExternal(GridClosureProcessor.java:1803)
at 
org.apache.ignite.internal.portable.PortableClassDescriptor.write(PortableClassDescriptor.java:543)
at 
org.apache.ignite.internal.portable.PortableWriterExImpl.marshal(PortableWriterExImpl.java:261)
at 
org.apache.ignite.internal.portable.GridPortableMarshaller.marshal(GridPortableMarshaller.java:228)
at 
org.apache.ignite.internal.portable.api.PortableMarshaller.marshal(PortableMarshaller.java:317)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1203)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:609)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:501)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:678)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:403)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:583)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:423)
at