[jira] [Commented] (IGNITE-2250) Client section on Summary contains ServerConfigurationFactory java class

[Andrey Novikov (JIRA)]

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

Andrey Novikov commented on IGNITE-2250:


Reviewed, merged.

> Client section on Summary contains ServerConfigurationFactory java class
> 
>
> Key: IGNITE-2250
> URL: https://issues.apache.org/jira/browse/IGNITE-2250
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Andrey Novikov
> Fix For: 1.6
>
>
> Should contain ClientConfigurationFactory



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

[jira] [Assigned] (IGNITE-647) org.apache.ignite.IgniteCacheAffinitySelfTest.testAffinity() hangs

[Semen Boikov (JIRA)]

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

Semen Boikov reassigned IGNITE-647:
---

Assignee: Semen Boikov  (was: Alexey Goncharuk)

> org.apache.ignite.IgniteCacheAffinitySelfTest.testAffinity() hangs
> --
>
> Key: IGNITE-647
> URL: https://issues.apache.org/jira/browse/IGNITE-647
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Yakov Zhdanov
>Assignee: Semen Boikov
>Priority: Blocker
>  Labels: Muted_test
> Attachments: FairAffinityDynamicCacheSelfTest.testStartStopCache.txt, 
> threaddump.txt
>
>
> 1-2 runs out of ~10 local runs hanged for me



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

[jira] [Comment Edited] (IGNITE-647) org.apache.ignite.IgniteCacheAffinitySelfTest.testAffinity() hangs

[Semen Boikov (JIRA)]

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

Semen Boikov edited comment on IGNITE-647 at 12/23/15 10:26 AM:


There is one more race here:
- node 1 starts, exchange is finished
- node 2 starts, exchange is finished
- node 2 starts cache with fair affinity function, starts exchange and sends 
GridDhtAffinityAssignmentRequest to node1. At this point node1 started exchange 
process, but did start cache yet and did not register required message handler 
so message will be ignored.

So any dynamic cache start with fair affinity initiated from non-oldest node 
can easily hang.

This behaviour is caused by wrong logic in 
GridDhtPartitionsExchangeFuture#canCalculateAffinity - when cache is started 
then all nodes can calculate affinity and there is no need in 
GridDhtAffinityAssignmentRequest send.


was (Author: sboikov):
There is one more race here:
- node 1 starts, exchange is finished
- node 2 starts, exchange is finished
- node 2 starts cache with fair affinity function, starts exchange and sends 
GridDhtAffinityAssignmentRequest to node1. At this point node1 started exchange 
process, but did start cache yet and did not register required message handler 
so message will be ignored.

So any dynamic cache start with fair affinity initiated from non-oldest node 
can easily hang.

> org.apache.ignite.IgniteCacheAffinitySelfTest.testAffinity() hangs
> --
>
> Key: IGNITE-647
> URL: https://issues.apache.org/jira/browse/IGNITE-647
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Yakov Zhdanov
>Assignee: Semen Boikov
>Priority: Blocker
>  Labels: Muted_test
> Attachments: FairAffinityDynamicCacheSelfTest.testStartStopCache.txt, 
> threaddump.txt
>
>
> 1-2 runs out of ~10 local runs hanged for me



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

[jira] [Commented] (IGNITE-2016) Update KafkaStreamer to fit new features introduced in Kafka 0.9

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-2016:
-

Roman, 

Ok, finally I've figured out what is the difference between streamers, that we 
already have, and connectors that were supported by Kafka in 0.9 release.
Agree, that a Kafka sink is absolutely different concept and it mustn't be 
mixed with streamers.

So far I have the following high-level (design related) review comments. Please 
address them first and after that I'll start reviewing the code in detail.

1) In any case let's put Kafka sink implementation in existed {{ignite-kafka}} 
module. There is no need to introduce additional module cause all Kafka related 
stuff will be located in one single place.
Module structure should look like this:
- {{org.apache.ignite.stream.kafka}} package will contain {{KafkaStreamer}}. 
Later we can add {{KafkaStreamerV2}} to this package that will be implemented 
using the new consumer API;
- {{org.apache.ignite.stream.kafka.connect}} package will contain your current 
Kafka Connect based implementation.

2) Update {{kafka.version}} referred from {{ignite-kafka/pom.xml}} to the 
latest 0.9 version and check that the all streamer works perfectly well (it 
should according to Kafka docs).

3) {{IgniteSinkTask.flush()}} method delivers data to the grid using 
{{cache.putAll(...)}}. Instead of this approach I would switch to 
{{IgniteDataStreamer}} and use it data streaming to Ignite. The reason is that 
{{IgniteDataStreamer}} will upload data to the grid much faster than 
{{cache.putAll(...)}}.

4) {{IgniteSinkTask.put(...)}} buffers data in some internal data structure. Is 
there any Kafka API requirement saying that the data mustn't been flushed until 
{{flush}} method is called explicitly? Generally speaking I would reuse 
{{IgniteDataStreamer}} here as well by setting 
{{IgniteDataStreamer.autoFlushFrequency(...)}} that will be equal to sink flush 
frequence and just forward all the data to the streamer as soon as it's 
delivered via  {{IgniteSinkTask.put(...)}}. The streamer will buffer the data 
and flush it to the grid with specified frequency or when the internal buffer 
reaches some limit.
 

> Update KafkaStreamer to fit new features introduced in Kafka 0.9
> 
>
> Key: IGNITE-2016
> URL: https://issues.apache.org/jira/browse/IGNITE-2016
> Project: Ignite
>  Issue Type: New Feature
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> Particularly,
> - new consumer
> - Kafka Connect (Copycat)
> http://www.confluent.io/blog/apache-kafka-0.9-is-released
> This can be a a different integration task or a complete re-write of the 
> current implementation, considering the fact that Kafka Connect is a new 
> standard way for "large-scale, real-time data import and export for Kafka."



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

[jira] [Resolved] (IGNITE-2200) CacheQueryExample failes after CacheClientBinaryQueryExample and vice versa

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk resolved IGNITE-2200.
--
Resolution: Fixed

The fix is merged to ignite-1.5

> CacheQueryExample failes after CacheClientBinaryQueryExample and vice versa
> ---
>
> Key: IGNITE-2200
> URL: https://issues.apache.org/jira/browse/IGNITE-2200
> Project: Ignite
>  Issue Type: Bug
>Reporter: Sergey Kozlov
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 1.5
>
>
> 1. Start remote node with config examples/config/example-ignite.xml
> 2. Run CacheClientBinaryQueryExample. It passed
> 3. Run CacheQueryExample. It failes:
> {noformat}
> >>> Cache query example started.
> Exception in thread "main" javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Type ID collision detected 
> [id=1178922291, clsName1=org.apache.ignite.examples.model.Organization, 
> clsName2=org.apache.ignite.examples.model.binary.Organization]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1618)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1078)
>   at 
> org.apache.ignite.examples.datagrid.CacheQueryExample.initialize(CacheQueryExample.java:276)
>   at 
> org.apache.ignite.examples.datagrid.CacheQueryExample.main(CacheQueryExample.java:97)
>   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)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: class org.apache.ignite.IgniteCheckedException: Type ID collision 
> detected [id=1178922291, 
> clsName1=org.apache.ignite.examples.model.Organization, 
> clsName2=org.apache.ignite.examples.model.binary.Organization]
>   at 
> org.apache.ignite.internal.MarshallerContextImpl.registerClassName(MarshallerContextImpl.java:116)
>   at 
> org.apache.ignite.internal.MarshallerContextAdapter.registerClass(MarshallerContextAdapter.java:157)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:576)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:555)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForClass(BinaryContext.java:457)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:145)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:132)
>   at 
> org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:225)
>   at 
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.marshalToBinary(CacheObjectBinaryProcessorImpl.java:438)
>   at 
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toBinary(CacheObjectBinaryProcessorImpl.java:777)
>   at 
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toCacheObject(CacheObjectBinaryProcessorImpl.java:724)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheContext.toCacheObject(GridCacheContext.java:1798)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.mapSingleUpdate(GridNearAtomicUpdateFuture.java:1137)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(GridNearAtomicUpdateFuture.java:868)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:418)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:284)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$18.apply(GridDhtAtomicCache.java:924)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$18.apply(GridDhtAtomicCache.java:922)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:699)
>   at 
> 

[jira] [Commented] (IGNITE-2135) ClassNotFoundException for CacheContinuousQueryExample

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-2135:
--

This should be fixed in ignite-2200

> ClassNotFoundException for CacheContinuousQueryExample
> --
>
> Key: IGNITE-2135
> URL: https://issues.apache.org/jira/browse/IGNITE-2135
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Saikat Maitra
>Priority: Critical
> Fix For: 1.6
>
>
> 1. Start 3 nodes with examples/config/example-ignite.xml
> 2. Run CacheContinuousQueryExample in IDEA
> 3. The example fails:
> {noformat}
> >>> Cache continuous query example started.
> [14:15:07] Ignite node stopped OK [uptime=00:00:00:898]
> Exception in thread "main" javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Query execution failed: 
> GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN, clsName=null, 
> clause=null, 
> filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
>  part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
> maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
> pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
> prj=null, keepPortable=false, subjId=2908e088-371e-4528-9141-52efb5ef42d6, 
> taskHash=0], rdc=null, trans=null]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1634)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:181)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy$5.onHasNext(IgniteCacheProxy.java:528)
>   at 
> org.apache.ignite.internal.util.GridCloseableIteratorAdapter.hasNextX(GridCloseableIteratorAdapter.java:53)
>   at 
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
>   at 
> org.apache.ignite.examples.datagrid.CacheContinuousQueryExample.main(CacheContinuousQueryExample.java:92)
>   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)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: class org.apache.ignite.IgniteCheckedException: Query execution 
> failed: GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN, 
> clsName=null, clause=null, 
> filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
>  part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
> maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
> pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
> prj=null, keepPortable=false, subjId=2908e088-371e-4528-9141-52efb5ef42d6, 
> taskHash=0], rdc=null, trans=null]
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.checkError(GridCacheQueryFutureAdapter.java:267)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.internalIterator(GridCacheQueryFutureAdapter.java:325)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:171)
>   ... 9 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute 
> query on node [query=GridCacheQueryBean [qry=GridCacheQueryAdapter 
> [type=SCAN, clsName=null, clause=null, 
> filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
>  part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
> maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
> pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
> prj=null, keepPortable=false, subjId=2908e088-371e-4528-9141-52efb5ef42d6, 
> taskHash=0], rdc=null, trans=null], 
> nodeId=a17e9748-7771-441c-a594-122c598b7b8e]
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.onPage(GridCacheQueryFutureAdapter.java:390)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.processQueryResponse(GridCacheDistributedQueryManager.java:395)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.access$000(GridCacheDistributedQueryManager.java:60)
>   at 
> 

[jira] [Comment Edited] (IGNITE-2016) Update KafkaStreamer to fit new features introduced in Kafka 0.9

[Roman Shtykh (JIRA)]

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

Roman Shtykh edited comment on IGNITE-2016 at 12/23/15 12:12 PM:
-

Denis,

Thanks for your suggestions. I agree and will address them.

As for flushing, it must be safe to do it before *flush* method is called 
explicitly. It should be ok to use *IgniteDataStreamer*'s buffer, but we might 
need to have a closer look at it if we want, for instance, exactly-once 
delivery in future.


was (Author: roman_s):
Denis,

Thanks for your suggestions. I agree and will address them.

As for flushing, it must be safe to do it before *flush* method is called 
explicitly. It should be ok to use *IgniteDataStreamer*'s buffer, but we might 
need to have a closer look at it if we want exactly-once delivery in future.

> Update KafkaStreamer to fit new features introduced in Kafka 0.9
> 
>
> Key: IGNITE-2016
> URL: https://issues.apache.org/jira/browse/IGNITE-2016
> Project: Ignite
>  Issue Type: New Feature
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> Particularly,
> - new consumer
> - Kafka Connect (Copycat)
> http://www.confluent.io/blog/apache-kafka-0.9-is-released
> This can be a a different integration task or a complete re-write of the 
> current implementation, considering the fact that Kafka Connect is a new 
> standard way for "large-scale, real-time data import and export for Kafka."



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

[jira] [Commented] (IGNITE-2016) Update KafkaStreamer to fit new features introduced in Kafka 0.9

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-2016:
--

Denis,

Thanks for your suggestions. I agree and will address them.

As for flushing, it must be safe to do it before *flush* method is called 
explicitly. It should be ok to use *IgniteDataStreamer*'s buffer, but we might 
need to have a closer look at it if we want exactly-once delivery in future.

> Update KafkaStreamer to fit new features introduced in Kafka 0.9
> 
>
> Key: IGNITE-2016
> URL: https://issues.apache.org/jira/browse/IGNITE-2016
> Project: Ignite
>  Issue Type: New Feature
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> Particularly,
> - new consumer
> - Kafka Connect (Copycat)
> http://www.confluent.io/blog/apache-kafka-0.9-is-released
> This can be a a different integration task or a complete re-write of the 
> current implementation, considering the fact that Kafka Connect is a new 
> standard way for "large-scale, real-time data import and export for Kafka."



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

[jira] [Updated] (IGNITE-2219) ClassCastException from NodeIdMessage to AffinityTopologyVersion

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-2219:
-
Fix Version/s: 1.6

> ClassCastException from NodeIdMessage to AffinityTopologyVersion
> 
>
> Key: IGNITE-2219
> URL: https://issues.apache.org/jira/browse/IGNITE-2219
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
> Environment: Ubuntu 12.04 64 bit
> java version "1.8.0_60"
> Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
> Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
> Ignite 1.4.0
>Reporter: Avihai Berkovitz
>Assignee: Semen Boikov
> Fix For: 1.6
>
> Attachments: message-hex.txt
>
>
> We had a cluster up and running for a couple of days. Without doing anything 
> new, we got the following error in one of the nodes:
> {noformat}
> Caught unhandled exception in NIO worker thread (restart the node). 
> java.lang.ClassCastException: 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$NodeIdMessage 
> cannot be cast to 
> org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsFullMessage.readFrom(GridDhtPartitionsFullMessage.java:176)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.direct.DirectByteBufferStream.readMessage(DirectByteBufferStream.java:963)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.direct.DirectMessageReader.readMessage(DirectMessageReader.java:252)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:249)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:79)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:104)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:78)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:2124)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:173)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:898)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeys(GridNioServer.java:1437)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1379)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1263)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
> [ignite-core-1.4.0.jar:1.4.0]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
> {noformat}
> It happened only once so far, but killed the communication from this node.



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

[jira] [Resolved] (IGNITE-2251) Please add a tooltip on Client Summary on POJO tab...

[Alexey Kuznetsov (JIRA)]

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

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

Tooltips added.

> Please add a tooltip on Client Summary on POJO tab...
> -
>
> Key: IGNITE-2251
> URL: https://issues.apache.org/jira/browse/IGNITE-2251
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
>
> ...for 'Generate constructors' and 'Include key fields' checkboxes



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

[jira] [Commented] (IGNITE-2175) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 7)

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-2175:
--

found unused test IgniteBinaryObjectFieldsQuerySelfTest
I'll add one more similar and add both to *CacheQueryTestSuite

> Not valid exceptions in case when example can't works with remote node 
> started with server classpath (Java 7)
> -
>
> Key: IGNITE-2175
> URL: https://issues.apache.org/jira/browse/IGNITE-2175
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.5
>
>
> Steps for reproduce:
> 1. Start one node form IDEA and one more from terminal
> 2. Run StreamVisitorExample.
> Exception:
> {noformat}
> 16:41:23,807][SEVERE][pub-#13%null%][DataStreamProcessor] Failed to finish 
> update job.
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1634)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:870)
>   at 
> org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:83)
>   at 
> org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:77)
>   at org.apache.ignite.stream.StreamVisitor.receive(StreamVisitor.java:38)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:137)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:298)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException: 
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
>   at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7005)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4522)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1378)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:299)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:863)
>   ... 13 more
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:274)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
>   at 
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
>  

[jira] [Updated] (IGNITE-2139) Expose indexing metrics using MBean

[Vladimir Ershov (JIRA)]

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

Vladimir Ershov updated IGNITE-2139:

Description: 
We should analyze existing metrics for Ignite Indexing and support 

See TODO @ org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java

  was:See TODO @ 
org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java


> Expose indexing metrics using MBean
> ---
>
> Key: IGNITE-2139
> URL: https://issues.apache.org/jira/browse/IGNITE-2139
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Vladimir Ershov
>Assignee: Vladimir Ershov
>
> We should analyze existing metrics for Ignite Indexing and support 
> See TODO @ 
> org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java



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

[jira] [Commented] (IGNITE-2228) .NET: Ensure async Task can be cancelled.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2228:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-2228 .NET: Ensure async Task can be cancelled.



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

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

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

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


commit 717dab259e3f0287046ffcefa28cf9214ab65ff7
Author: sboikov 
Date:   2015-12-14T07:00:57Z

ignite-1.5 Fixed TcpDiscoveryMulticastIpFinder to request address on each 
getRegisteredAddresses call

commit 6d96bb6a3219255b62af826e6806b1aa564bb005
Author: vozerov-gridgain 
Date:   2015-12-14T07:08:00Z

Fix to GridBinaryWildcardsSelfTest.

commit 4ae6292cface325f21237db5d18ce77dee380072
Author: vozerov-gridgain 
Date:   2015-12-14T07:08:29Z

Fixed failure in BinaryObjectBuilderSelfTest.testCopyFromInnerObject.

commit ed27fbdab9d8307b4db427866ed1094526c117c8
Author: vozerov-gridgain 
Date:   2015-12-14T07:08:47Z

Merge remote-tracking branch 'origin/ignite-1.5' into ignite-1.5

commit 3db14482091d01e96e1ae40a15cb903c3adcddbd
Author: vozerov-gridgain 
Date:   2015-12-14T07:19:24Z

Fixed failure in BinaryObjectBuilderSelfTest.testSetBinaryObject.

commit acb57c5eb95d11ebde5557618226d80f25ac610c
Author: sboikov 
Date:   2015-12-14T07:40:57Z

ignite-1.5 Fixed NPE in IgniteKernal.dumpDebugInfo.

commit ec2a64714c176f3a5aca60a058686d3354dc6a76
Author: sboikov 
Date:   2015-12-14T07:41:18Z

Merge remote-tracking branch 'origin/ignite-1.5' into ignite-1.5

commit 484a3afd05b9ad5a524a28c517ddc0a6b9dffcbc
Author: sboikov 
Date:   2015-12-14T07:58:57Z

ignite-1.5 Added waitForCondition in tests with TTL.

commit 47f1ced214b4176b13293386c1e2042c9cc20b32
Author: sboikov 
Date:   2015-12-14T08:09:17Z

ignite-1.5 Fixed test to override correct 'getConfiguration' method.

commit 4d086734833d96b7e2403ce4f17f763a1c75caab
Author: sboikov 
Date:   2015-12-14T08:27:33Z

ignite-1.5 Use TcpDiscoveryVmIpFinder in test.

commit de0b1badbf34538e04e7cf4be5378ef929fb6201
Author: Alexey Kuznetsov 
Date:   2015-12-14T08:33:09Z

ignite-1.5 Updated classnames.properties

commit beb64c34c271b7eac1388179b11f042b34fa0d60
Author: sboikov 
Date:   2015-12-14T08:34:07Z

ignite-1.5 Increased test timeouts.

commit 72e5b9adfdcfcad4b0002bbfc1cf20fd3a0ed149
Author: sboikov 
Date:   2015-12-14T08:34:32Z

Merge remote-tracking branch 'origin/ignite-1.5' into ignite-1.5

commit 4291edca326be4eafde331001238a9181333fbfc
Author: sboikov 
Date:   2015-12-14T09:01:51Z

ignite-1.5 Fixed CacheContinuousQueryFailoverAbstractSelfTest to do not 
hang in case of errors.

commit 345fc27d90f8ae28697fc021d55c7b7a015faeee
Author: sboikov 
Date:   2015-12-14T09:18:16Z

ignite-1.5 Fixed test for offheap mode.

commit fdea7cfaf6ea26834d2694cbfc9634de8d24209b
Author: vozerov-gridgain 
Date:   2015-12-14T09:21:17Z

IGNITE-2150: Fixed invalid test scenario.

commit f3cc98b189dd4c4a4ad6325e6b9a6fa6db795099
Author: vozerov-gridgain 
Date:   2015-12-14T09:21:38Z

Merge remote-tracking branch 'origin/ignite-1.5' into ignite-1.5

commit f87b80f7bf6e38b3ebd21088d4e8aa11a505ed59
Author: vozerov-gridgain 
Date:   2015-12-14T09:40:22Z

IGNITE-2152: .NET: Intro text is added.

commit 6bf716afc490a3bec987e788d795fd979edbdd23
Author: sboikov 
Date:   2015-12-14T09:42:41Z

ignite-1.5 More info in GridPartitionedSingleGetFuture.toString.

commit 68d317952485dd0a4e09844a9cdbb3a0f23ae399
Author: sboikov 
Date:   2015-12-14T09:43:14Z

Merge remote-tracking branch 'origin/ignite-1.5' into ignite-1.5

commit 1224658fe0d4b572b9980fa5de65bbb043646377
Author: sboikov 
Date:   2015-12-14T10:17:06Z

ignite-1.5 Fixed NPE in GridPartitionedSingleGetFuture.

commit 3d9be34c104cc2e89e2422e4f9c3f126449c8162
Author: sboikov 
Date:   2015-12-14T10:31:40Z

ignite-1.5 Less unnecessary logging in test.

commit d6b46115147704f13c36aa59f307f77baf954e3f
Author: ashutak 
Date:   2015-12-14T11:17:37Z

ignite-2065: portable -> 

[jira] [Closed] (IGNITE-2149) Build Apache Ignite failed for Java8

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-2149.
-

> Build Apache Ignite failed for Java8
> 
>
> Key: IGNITE-2149
> URL: https://issues.apache.org/jira/browse/IGNITE-2149
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Blocker
> Fix For: 1.5
>
>
> {noformat}
> [19:20:12] :   [exec] [WARNING] 
> COMPILATION WARNING : 
> [19:20:12] :   [exec] [INFO] 
> -
> [19:20:12] :   [exec] [WARNING] 
> /home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/ttl/CacheTtlAbstractSelfTest.java:
>  Some input files use unchecked or unsafe operations.
> [19:20:12] :   [exec] [WARNING] 
> /home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/ttl/CacheTtlAbstractSelfTest.java:
>  Recompile with -Xlint:unchecked for details.
> [19:20:12] :   [exec] [INFO] 2 
> warnings 
> [19:20:12] :   [exec] [INFO] 
> -
> [19:20:12] :   [exec] [INFO] 
> -
> [19:20:12] :   [exec] [ERROR] 
> COMPILATION ERROR : 
> [19:20:12] :   [exec] [INFO] 
> -
> [19:20:12] :   [exec] [ERROR] 
> /home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/IgniteBinaryObjectFieldsQuerySelfTest.java:[213,17]
>  reference to assertEquals is ambiguous
> [19:20:12] :   [exec]   both method 
> assertEquals(java.lang.Object,java.lang.Object) in junit.framework.TestCase 
> and method assertEquals(int,int) in junit.framework.TestCase match
> [19:20:12] :   [exec] [INFO] 1 error
> [19:20:12] :   [exec] [INFO] 
> -
> [19:20:12] :   [exec] [INFO] 
> 
> [19:20:12] :   [exec] [INFO] Reactor 
> Summary:
> [19:20:12] :   [exec] [INFO] 
> [19:20:12] :   [exec] [INFO] 
> ignite-apache-license-gen . SUCCESS [1.177s]
> [19:20:12] :   [exec] [INFO] 
> ignite-tools .. SUCCESS [6.047s]
> [19:20:12] :   [exec] [INFO] 
> ignite-core ... SUCCESS [1:11.104s]
> [19:20:12] :   [exec] [INFO] 
> ignite-log4j .. SUCCESS [1.929s]
> [19:20:12] :   [exec] [INFO] 
> ignite-urideploy .. SUCCESS [2.380s]
> [19:20:12] :   [exec] [INFO] 
> ignite-spring . SUCCESS [2.634s]
> [19:20:12] :   [exec] [INFO] 
> ignite-hadoop . SUCCESS [5.968s]
> [19:20:12] :   [exec] [INFO] 
> ignite-extdata-p2p  SUCCESS [2.085s]
> [19:20:12] :   [exec] [INFO] 
> ignite-extdata-uri-dep  SUCCESS [1.272s]
> [19:20:12] :   [exec] [INFO] 
> ignite-extdata-uri  SUCCESS [0.388s]
> [19:20:12] :   [exec] [INFO] 
> ignite-indexing ... FAILURE [1.375s]
> [19:20:12] :   [exec] [INFO] 
> ignite-rest-http .. SKIPPED
> [19:20:12] :   [exec] [INFO] 
> ignite-clients  SKIPPED
> [19:20:12] :

[jira] [Updated] (IGNITE-2139) Expose indexing metrics using MBean

[Vladimir Ershov (JIRA)]

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

Vladimir Ershov updated IGNITE-2139:

Description: 
We should analyze existing metrics for Ignite Indexing, add some new if needed, 
and support everything at JMX.

See TODO @ org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java

  was:
We should analyze existing metrics for Ignite Indexing and support 

See TODO @ org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java


> Expose indexing metrics using MBean
> ---
>
> Key: IGNITE-2139
> URL: https://issues.apache.org/jira/browse/IGNITE-2139
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Vladimir Ershov
>Assignee: Vladimir Ershov
>
> We should analyze existing metrics for Ignite Indexing, add some new if 
> needed, and support everything at JMX.
> See TODO @ 
> org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java



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

[jira] [Assigned] (IGNITE-2139) Expose indexing metrics using MBean

[Vladimir Ershov (JIRA)]

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

Vladimir Ershov reassigned IGNITE-2139:
---

Assignee: (was: Vladimir Ershov)

> Expose indexing metrics using MBean
> ---
>
> Key: IGNITE-2139
> URL: https://issues.apache.org/jira/browse/IGNITE-2139
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Vladimir Ershov
>
> We should analyze existing metrics for Ignite Indexing, add some new if 
> needed, and support everything at JMX.
> See TODO @ 
> org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java



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

[jira] [Closed] (IGNITE-2200) CacheQueryExample failes after CacheClientBinaryQueryExample and vice versa

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-2200.
-

> CacheQueryExample failes after CacheClientBinaryQueryExample and vice versa
> ---
>
> Key: IGNITE-2200
> URL: https://issues.apache.org/jira/browse/IGNITE-2200
> Project: Ignite
>  Issue Type: Bug
>Reporter: Sergey Kozlov
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 1.5
>
>
> 1. Start remote node with config examples/config/example-ignite.xml
> 2. Run CacheClientBinaryQueryExample. It passed
> 3. Run CacheQueryExample. It failes:
> {noformat}
> >>> Cache query example started.
> Exception in thread "main" javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Type ID collision detected 
> [id=1178922291, clsName1=org.apache.ignite.examples.model.Organization, 
> clsName2=org.apache.ignite.examples.model.binary.Organization]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1618)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1078)
>   at 
> org.apache.ignite.examples.datagrid.CacheQueryExample.initialize(CacheQueryExample.java:276)
>   at 
> org.apache.ignite.examples.datagrid.CacheQueryExample.main(CacheQueryExample.java:97)
>   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)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: class org.apache.ignite.IgniteCheckedException: Type ID collision 
> detected [id=1178922291, 
> clsName1=org.apache.ignite.examples.model.Organization, 
> clsName2=org.apache.ignite.examples.model.binary.Organization]
>   at 
> org.apache.ignite.internal.MarshallerContextImpl.registerClassName(MarshallerContextImpl.java:116)
>   at 
> org.apache.ignite.internal.MarshallerContextAdapter.registerClass(MarshallerContextAdapter.java:157)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:576)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:555)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForClass(BinaryContext.java:457)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:145)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:132)
>   at 
> org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:225)
>   at 
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.marshalToBinary(CacheObjectBinaryProcessorImpl.java:438)
>   at 
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toBinary(CacheObjectBinaryProcessorImpl.java:777)
>   at 
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toCacheObject(CacheObjectBinaryProcessorImpl.java:724)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheContext.toCacheObject(GridCacheContext.java:1798)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.mapSingleUpdate(GridNearAtomicUpdateFuture.java:1137)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(GridNearAtomicUpdateFuture.java:868)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:418)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:284)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$18.apply(GridDhtAtomicCache.java:924)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$18.apply(GridDhtAtomicCache.java:922)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:699)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsync0(GridDhtAtomicCache.java:922)
>   at 
> 

[jira] [Comment Edited] (IGNITE-2175) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 7)

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov edited comment on IGNITE-2175 at 12/23/15 2:57 PM:


Fix done & merged to 1.5 


was (Author: avinogradov):
Fix dome & merged to 1.5 

> Not valid exceptions in case when example can't works with remote node 
> started with server classpath (Java 7)
> -
>
> Key: IGNITE-2175
> URL: https://issues.apache.org/jira/browse/IGNITE-2175
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.5
>
>
> Steps for reproduce:
> 1. Start one node form IDEA and one more from terminal
> 2. Run StreamVisitorExample.
> Exception:
> {noformat}
> 16:41:23,807][SEVERE][pub-#13%null%][DataStreamProcessor] Failed to finish 
> update job.
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1634)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:870)
>   at 
> org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:83)
>   at 
> org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:77)
>   at org.apache.ignite.stream.StreamVisitor.receive(StreamVisitor.java:38)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:137)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:298)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException: 
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
>   at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7005)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4522)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1378)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:299)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:863)
>   ... 13 more
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:274)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
>   at 
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
>   at 
> 

[jira] [Commented] (IGNITE-2175) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 7)

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-2175:
--

Fix dome & merged to 1.5 

> Not valid exceptions in case when example can't works with remote node 
> started with server classpath (Java 7)
> -
>
> Key: IGNITE-2175
> URL: https://issues.apache.org/jira/browse/IGNITE-2175
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.5
>
>
> Steps for reproduce:
> 1. Start one node form IDEA and one more from terminal
> 2. Run StreamVisitorExample.
> Exception:
> {noformat}
> 16:41:23,807][SEVERE][pub-#13%null%][DataStreamProcessor] Failed to finish 
> update job.
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1634)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:870)
>   at 
> org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:83)
>   at 
> org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:77)
>   at org.apache.ignite.stream.StreamVisitor.receive(StreamVisitor.java:38)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:137)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:298)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException: 
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
>   at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7005)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4522)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1378)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:299)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:863)
>   ... 13 more
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:274)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
>   at 
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
>   at 
> 

[jira] [Resolved] (IGNITE-2175) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 7)

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov resolved IGNITE-2175.
--
Resolution: Fixed

checked, merged to 1.5

> Not valid exceptions in case when example can't works with remote node 
> started with server classpath (Java 7)
> -
>
> Key: IGNITE-2175
> URL: https://issues.apache.org/jira/browse/IGNITE-2175
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.5
>
>
> Steps for reproduce:
> 1. Start one node form IDEA and one more from terminal
> 2. Run StreamVisitorExample.
> Exception:
> {noformat}
> 16:41:23,807][SEVERE][pub-#13%null%][DataStreamProcessor] Failed to finish 
> update job.
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1634)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:870)
>   at 
> org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:83)
>   at 
> org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:77)
>   at org.apache.ignite.stream.StreamVisitor.receive(StreamVisitor.java:38)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:137)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:298)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException: 
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
>   at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7005)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4522)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1378)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:299)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:863)
>   ... 13 more
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:274)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
>   at 
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1443)
> 

[jira] [Closed] (IGNITE-2175) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 7)

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov closed IGNITE-2175.


Fix confirmed

> Not valid exceptions in case when example can't works with remote node 
> started with server classpath (Java 7)
> -
>
> Key: IGNITE-2175
> URL: https://issues.apache.org/jira/browse/IGNITE-2175
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.5
>
>
> Steps for reproduce:
> 1. Start one node form IDEA and one more from terminal
> 2. Run StreamVisitorExample.
> Exception:
> {noformat}
> 16:41:23,807][SEVERE][pub-#13%null%][DataStreamProcessor] Failed to finish 
> update job.
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1634)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:870)
>   at 
> org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:83)
>   at 
> org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:77)
>   at org.apache.ignite.stream.StreamVisitor.receive(StreamVisitor.java:38)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:137)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:298)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException: 
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
>   at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7005)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4522)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1378)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:299)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:863)
>   ... 13 more
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:274)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
>   at 
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1443)
>   at 
> 

[jira] [Commented] (IGNITE-2168) Examples should destroy created caches: SpringBeanExample fails after CacheBinaryAutoStoreExample

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2168:


GitHub user VladimirErshov opened a pull request:

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

IGNITE-2168  Examples should destroy created caches: SpringBeanExample 
fails after CacheBinaryAutoStoreExample

IGNITE-2168
Examples should destroy created caches: SpringBeanExample fails after 
CacheBinaryAutoStoreExample

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

$ git pull https://github.com/VladimirErshov/ignite ignite-2168

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

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


commit 717dab259e3f0287046ffcefa28cf9214ab65ff7
Author: sboikov 
Date:   2015-12-14T07:00:57Z

ignite-1.5 Fixed TcpDiscoveryMulticastIpFinder to request address on each 
getRegisteredAddresses call

commit 6d96bb6a3219255b62af826e6806b1aa564bb005
Author: vozerov-gridgain 
Date:   2015-12-14T07:08:00Z

Fix to GridBinaryWildcardsSelfTest.

commit 4ae6292cface325f21237db5d18ce77dee380072
Author: vozerov-gridgain 
Date:   2015-12-14T07:08:29Z

Fixed failure in BinaryObjectBuilderSelfTest.testCopyFromInnerObject.

commit ed27fbdab9d8307b4db427866ed1094526c117c8
Author: vozerov-gridgain 
Date:   2015-12-14T07:08:47Z

Merge remote-tracking branch 'origin/ignite-1.5' into ignite-1.5

commit 3db14482091d01e96e1ae40a15cb903c3adcddbd
Author: vozerov-gridgain 
Date:   2015-12-14T07:19:24Z

Fixed failure in BinaryObjectBuilderSelfTest.testSetBinaryObject.

commit acb57c5eb95d11ebde5557618226d80f25ac610c
Author: sboikov 
Date:   2015-12-14T07:40:57Z

ignite-1.5 Fixed NPE in IgniteKernal.dumpDebugInfo.

commit ec2a64714c176f3a5aca60a058686d3354dc6a76
Author: sboikov 
Date:   2015-12-14T07:41:18Z

Merge remote-tracking branch 'origin/ignite-1.5' into ignite-1.5

commit 484a3afd05b9ad5a524a28c517ddc0a6b9dffcbc
Author: sboikov 
Date:   2015-12-14T07:58:57Z

ignite-1.5 Added waitForCondition in tests with TTL.

commit 47f1ced214b4176b13293386c1e2042c9cc20b32
Author: sboikov 
Date:   2015-12-14T08:09:17Z

ignite-1.5 Fixed test to override correct 'getConfiguration' method.

commit 4d086734833d96b7e2403ce4f17f763a1c75caab
Author: sboikov 
Date:   2015-12-14T08:27:33Z

ignite-1.5 Use TcpDiscoveryVmIpFinder in test.

commit de0b1badbf34538e04e7cf4be5378ef929fb6201
Author: Alexey Kuznetsov 
Date:   2015-12-14T08:33:09Z

ignite-1.5 Updated classnames.properties

commit beb64c34c271b7eac1388179b11f042b34fa0d60
Author: sboikov 
Date:   2015-12-14T08:34:07Z

ignite-1.5 Increased test timeouts.

commit 72e5b9adfdcfcad4b0002bbfc1cf20fd3a0ed149
Author: sboikov 
Date:   2015-12-14T08:34:32Z

Merge remote-tracking branch 'origin/ignite-1.5' into ignite-1.5

commit 4291edca326be4eafde331001238a9181333fbfc
Author: sboikov 
Date:   2015-12-14T09:01:51Z

ignite-1.5 Fixed CacheContinuousQueryFailoverAbstractSelfTest to do not 
hang in case of errors.

commit 345fc27d90f8ae28697fc021d55c7b7a015faeee
Author: sboikov 
Date:   2015-12-14T09:18:16Z

ignite-1.5 Fixed test for offheap mode.

commit fdea7cfaf6ea26834d2694cbfc9634de8d24209b
Author: vozerov-gridgain 
Date:   2015-12-14T09:21:17Z

IGNITE-2150: Fixed invalid test scenario.

commit f3cc98b189dd4c4a4ad6325e6b9a6fa6db795099
Author: vozerov-gridgain 
Date:   2015-12-14T09:21:38Z

Merge remote-tracking branch 'origin/ignite-1.5' into ignite-1.5

commit f87b80f7bf6e38b3ebd21088d4e8aa11a505ed59
Author: vozerov-gridgain 
Date:   2015-12-14T09:40:22Z

IGNITE-2152: .NET: Intro text is added.

commit 6bf716afc490a3bec987e788d795fd979edbdd23
Author: sboikov 
Date:   2015-12-14T09:42:41Z

ignite-1.5 More info in GridPartitionedSingleGetFuture.toString.

commit 68d317952485dd0a4e09844a9cdbb3a0f23ae399
Author: sboikov 
Date:   2015-12-14T09:43:14Z

Merge remote-tracking branch 'origin/ignite-1.5' into ignite-1.5

commit 1224658fe0d4b572b9980fa5de65bbb043646377
Author: sboikov 
Date:   2015-12-14T10:17:06Z

ignite-1.5 Fixed NPE in GridPartitionedSingleGetFuture.

commit 3d9be34c104cc2e89e2422e4f9c3f126449c8162
Author: sboikov 
Date:   2015-12-14T10:31:40Z

[jira] [Closed] (IGNITE-2033) Refactoring summary page

[Andrey Novikov (JIRA)]

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

Andrey Novikov closed IGNITE-2033.
--

Reviewed, merged.

> Refactoring summary page
> 
>
> Key: IGNITE-2033
> URL: https://issues.apache.org/jira/browse/IGNITE-2033
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Dmitriyff
>Assignee: Andrey Novikov
> Fix For: 1.6
>
>




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

[jira] [Updated] (IGNITE-2033) Refactoring summary page

[Andrey Novikov (JIRA)]

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

Andrey Novikov updated IGNITE-2033:
---
Assignee: (was: Andrey Novikov)

> Refactoring summary page
> 
>
> Key: IGNITE-2033
> URL: https://issues.apache.org/jira/browse/IGNITE-2033
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Dmitriyff
> Fix For: 1.6
>
>




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

[jira] [Assigned] (IGNITE-2217) Add BinaryConfiguration support to cluster screen

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-2217:
-

Assignee: Vasiliy Sisko  (was: Alexey Kuznetsov)

> Add BinaryConfiguration support to cluster screen
> -
>
> Key: IGNITE-2217
> URL: https://issues.apache.org/jira/browse/IGNITE-2217
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Vasiliy Sisko
> Fix For: 1.6
>
>




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

[jira] [Updated] (IGNITE-2227) Please add support of cache sql Schema on web console

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2227:
-
Summary: Please add support of cache sql Schema on web console  (was: 
Please add support of cache alias on web console)

> Please add support of cache sql Schema on web console
> -
>
> Key: IGNITE-2227
> URL: https://issues.apache.org/jira/browse/IGNITE-2227
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
>
> https://issues.apache.org/jira/browse/IGNITE-1979



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

[jira] [Comment Edited] (IGNITE-2154) .NET: doxygen docs generation must be included into Maven build process.

[Roman Shtykh (JIRA)]

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

Roman Shtykh edited comment on IGNITE-2154 at 12/24/15 1:28 AM:


[~avinogradov] [~vozerov] A minor comment.
With these changes doxygen will be triggered when building from sources if no 
_skipClientDocs_ property is set. I think it is good to mention you have to 
specify it when building or install doxygen on the documentation page 
http://apacheignite.gridgain.org/docs/getting-started


was (Author: roman_s):
[~avinogradov] A minor comment.
With these changes doxygen will be triggered when building from sources if no 
_skipClientDocs_ property is set. I think it is good to mention you have to 
specify it when building or install doxygen on the documentation page 
http://apacheignite.gridgain.org/docs/getting-started

> .NET: doxygen docs generation must be included into Maven build process.
> 
>
> Key: IGNITE-2154
> URL: https://issues.apache.org/jira/browse/IGNITE-2154
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>




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

[jira] [Resolved] (IGNITE-2227) Please add support of cache alias on web console

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov resolved IGNITE-2227.
--
Resolution: Fixed
  Assignee: Pavel Konstantinov

I added sql schema to Caches screen.
Please test UI + XML + java code generation

We also need to support sql schema  on SQL screen, please create separate issue 
for that.

> Please add support of cache alias on web console
> 
>
> Key: IGNITE-2227
> URL: https://issues.apache.org/jira/browse/IGNITE-2227
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
>
> https://issues.apache.org/jira/browse/IGNITE-1979



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

[jira] [Commented] (IGNITE-2154) .NET: doxygen docs generation must be included into Maven build process.

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-2154:
--

[~avinogradov] A minor comment.
With these changes doxygen will be triggered when building from sources if no 
_skipClientDocs_ property is set. I think it is good to mention you have to 
specify it when building or install doxygen on the documentation page 
http://apacheignite.gridgain.org/docs/getting-started

> .NET: doxygen docs generation must be included into Maven build process.
> 
>
> Key: IGNITE-2154
> URL: https://issues.apache.org/jira/browse/IGNITE-2154
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>




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

[jira] [Commented] (IGNITE-2016) Update KafkaStreamer to fit new features introduced in Kafka 0.9

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-2016:
--

I think using _IgniteDataStreamer_ is not a very good idea for this 
integration. I'd like to stay with _IgniteCache.putAll(...)_. And here is the 
reasoning.

To put it simply, Kafka sends data to _IgniteSinkTask_ and records offsets of 
messages delivered on _flush(...)_. If something goes wrong with processing, it 
can be restarted from the last recorded offset.
So to guarantee the data that is delivered from Kafka is transferred to Ignite 
and safe, we need to be sure the transfer is complete, and only after that 
complete _flush(...)_. On the other hand, _IgniteDataStreamer_ has its own 
buffer and flushes the data whenever it feels like doing so (specified by 
_autoFlushFrequency(...)_). Of course, we can invoke _get()_ on IgniteFuture's 
returned by _IgniteDataStreamer.addData()_ and call 
_IgniteDataStreamer.flush()_ to be sure all data transfer is complete, but it 
cancels advantages _IgniteDataStreamer_'s buffer.

Also, I think it is more reasonable to rely on Kafka Connect's flushing 
interval instead (by exposing _autoFlushFrequency(...)_ to the user, we'll have 
two flushing mechanism which will most likely be out of sync), have a buffer 
which will be flushed with blocking _cache.putAll(...)_ and safely commit 
offsets to Kafka.

This way, if something goes wrong with processing, the data will be redelivered 
from the last recorded offset -- i.e., we guarantee no data loss in transfer 
process and provide at-least-once delivery. Supporting exactly-once delivery 
semantics is probably not needed for cache (as invoking _put()_ with the same 
entry will give the same result in the cache) unless there is a special request 
in future.

> Update KafkaStreamer to fit new features introduced in Kafka 0.9
> 
>
> Key: IGNITE-2016
> URL: https://issues.apache.org/jira/browse/IGNITE-2016
> Project: Ignite
>  Issue Type: New Feature
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> Particularly,
> - new consumer
> - Kafka Connect (Copycat)
> http://www.confluent.io/blog/apache-kafka-0.9-is-released
> This can be a a different integration task or a complete re-write of the 
> current implementation, considering the fact that Kafka Connect is a new 
> standard way for "large-scale, real-time data import and export for Kafka."



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

[jira] [Updated] (IGNITE-2253) Refactoring fields on cluster page

[Dmitriyff (JIRA)]

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

Dmitriyff updated IGNITE-2253:
--
Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-2047)

> Refactoring fields on cluster page
> --
>
> Key: IGNITE-2253
> URL: https://issues.apache.org/jira/browse/IGNITE-2253
> Project: Ignite
>  Issue Type: Task
>Reporter: Dmitriyff
>Assignee: Dmitriyff
> Fix For: 1.6
>
>




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

[jira] [Commented] (IGNITE-2080) JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-2080:
-

`GridUnsafeMap` is fixed. But the following tests fail under Solaris:

  * {{GridUnsafeMemorySelfTest}}
  * {{GridUnsafeMapSelfTest}}
  * {{GridUnsafePartitionedMapSelfTest}}
  * {{OptimizedObjectStreamSelfTest}}
  * {{OffHeapTieredTransactionSelfTest}}
  * {{GridEmbeddedFutureSelfTest}}
  * {{SocketStreamerSelfTest}}
  * {{GridCacheAbstractReduceFieldsQuerySelfTest.testIncludeBackups}}
  * {{GridCacheSwapScanQuerySelfTest}}

Failures don't related with JVM crash. Need to investigate.

> JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438]  
> Unsafe_SetInt+0x14c
> -
>
> Key: IGNITE-2080
> URL: https://issues.apache.org/jira/browse/IGNITE-2080
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5, 1.4
> Environment: SunOS 5.11, JDK 7
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 1.6
>
> Attachments: 054424_0_localhost.log, benchmark-offheap.properties, 
> hs_err_pid10523.log
>
>
> JVM crashes on SunOS 5.11 with the following message:
> {noformat}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGBUS (0xa) at pc=0x76a7c438, pid=10523, tid=652
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 
> 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode 
> solaris-sparc )
> # Problematic frame:
> # V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> {noformat}
> Stack trace:
> {noformat}
> Stack: [0xfff0f6f0,0xfff0f700],  sp=0xfff0f6ffd1f0,  free 
> space=1012k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native 
> code)
> V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+-1763873616
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+0
> j  
> org.apache.ignite.internal.util.IgniteUtils.writeVersion([BJLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;)J+135
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapEntryImpl.marshal()[B+128
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapManager.write(Lorg/apache/ignite/internal/processors/cache/KeyCacheObject;Ljava/nio/ByteBuffer;BLorg/apache/
> ignite/internal/processors/cache/version/GridCacheVersion;JJLorg/apache/ignite/lang/IgniteUuid;Lorg/apache/ignite/lang/IgniteUuid;)V+86
> j  org.apache.ignite.internal.processors.cache.GridCacheMapEntry.swap()V+333
> j  
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.evictInternal(ZLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignit
> e/internal/processors/cache/CacheEntryPredicate;)Z+122
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.evict0(Lorg/apache/ignite/internal/processors/cache/GridCacheAdapter;Lorg/apache/ignite/internal
> /processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignite/internal/processors/cache/CacheEntryPredica
> te;Z)Z+117
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(Lorg/apache/ignite/internal/processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/
> processors/affinity/AffinityTopologyVersion;)V+123
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(Ljava/util/Collection;Lorg/apache/ignite/internal/processors/affi
> nity/AffinityTopologyVersion;)V+331
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/
> cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+1023
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/c
> ache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+33
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapSingle(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/cache/
> distributed/dht/atomic/GridNearAtomicUpdateRequest;)V+28
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$1200(Lorg/apache/ignite/internal/processors/cache/distributed/dh
> t/atomic/GridNearAtomicUpdateFuture;Ljava/util/UUID;Lorg/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;)V+3
> j  
> 

[jira] [Comment Edited] (IGNITE-2080) JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c

[Andrey Gura (JIRA)]

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

Andrey Gura edited comment on IGNITE-2080 at 12/24/15 1:47 AM:
---

Fixed: https://github.com/apache/ignite/pull/362

Waiting for TC and benchmarks results.

This PR also should fix https://issues.apache.org/jira/browse/IGNITE-1493 issue.


was (Author: agura):
Fixed: https://github.com/apache/ignite/pull/305

Waiting for TC and benchmarks results.

This PR also should fix https://issues.apache.org/jira/browse/IGNITE-1493 issue.

> JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438]  
> Unsafe_SetInt+0x14c
> -
>
> Key: IGNITE-2080
> URL: https://issues.apache.org/jira/browse/IGNITE-2080
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5, 1.4
> Environment: SunOS 5.11, JDK 7
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 1.6
>
> Attachments: 054424_0_localhost.log, benchmark-offheap.properties, 
> hs_err_pid10523.log
>
>
> JVM crashes on SunOS 5.11 with the following message:
> {noformat}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGBUS (0xa) at pc=0x76a7c438, pid=10523, tid=652
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 
> 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode 
> solaris-sparc )
> # Problematic frame:
> # V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> {noformat}
> Stack trace:
> {noformat}
> Stack: [0xfff0f6f0,0xfff0f700],  sp=0xfff0f6ffd1f0,  free 
> space=1012k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native 
> code)
> V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+-1763873616
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+0
> j  
> org.apache.ignite.internal.util.IgniteUtils.writeVersion([BJLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;)J+135
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapEntryImpl.marshal()[B+128
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapManager.write(Lorg/apache/ignite/internal/processors/cache/KeyCacheObject;Ljava/nio/ByteBuffer;BLorg/apache/
> ignite/internal/processors/cache/version/GridCacheVersion;JJLorg/apache/ignite/lang/IgniteUuid;Lorg/apache/ignite/lang/IgniteUuid;)V+86
> j  org.apache.ignite.internal.processors.cache.GridCacheMapEntry.swap()V+333
> j  
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.evictInternal(ZLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignit
> e/internal/processors/cache/CacheEntryPredicate;)Z+122
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.evict0(Lorg/apache/ignite/internal/processors/cache/GridCacheAdapter;Lorg/apache/ignite/internal
> /processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignite/internal/processors/cache/CacheEntryPredica
> te;Z)Z+117
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(Lorg/apache/ignite/internal/processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/
> processors/affinity/AffinityTopologyVersion;)V+123
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(Ljava/util/Collection;Lorg/apache/ignite/internal/processors/affi
> nity/AffinityTopologyVersion;)V+331
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/
> cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+1023
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/c
> ache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+33
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapSingle(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/cache/
> distributed/dht/atomic/GridNearAtomicUpdateRequest;)V+28
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$1200(Lorg/apache/ignite/internal/processors/cache/distributed/dh
> t/atomic/GridNearAtomicUpdateFuture;Ljava/util/UUID;Lorg/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;)V+3
> j  
> 

[jira] [Comment Edited] (IGNITE-2080) JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c

[Andrey Gura (JIRA)]

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

Andrey Gura edited comment on IGNITE-2080 at 12/24/15 2:26 AM:
---

`GridUnsafeMap` is fixed. But the following tests fail under Solaris:

  * {{GridCacheMemoryModeBinarySelfTest.testOffheapSwap}}
  * {{GridCacheMemoryModeBinarySelfTest.testTiered}}
  * {{GridCacheP2PUndeploySelfTest.testOffHeapP2PReplicated}} and other offheap 
related tests
  * {{GridUnsafeMemorySelfTest}}
  * {{GridUnsafeMapSelfTest}}
  * {{GridUnsafePartitionedMapSelfTest}}
  * {{OptimizedObjectStreamSelfTest}}
  * {{OffHeapTieredTransactionSelfTest}}
  * {{GridEmbeddedFutureSelfTest}}
  * {{SocketStreamerSelfTest}}
  * {{GridCacheAbstractReduceFieldsQuerySelfTest.testIncludeBackups}}
  * {{GridCacheSwapScanQuerySelfTest}}

Failures don't related with JVM crash. Need to investigate.


was (Author: agura):
`GridUnsafeMap` is fixed. But the following tests fail under Solaris:

  * {{GridUnsafeMemorySelfTest}}
  * {{GridUnsafeMapSelfTest}}
  * {{GridUnsafePartitionedMapSelfTest}}
  * {{OptimizedObjectStreamSelfTest}}
  * {{OffHeapTieredTransactionSelfTest}}
  * {{GridEmbeddedFutureSelfTest}}
  * {{SocketStreamerSelfTest}}
  * {{GridCacheAbstractReduceFieldsQuerySelfTest.testIncludeBackups}}
  * {{GridCacheSwapScanQuerySelfTest}}

Failures don't related with JVM crash. Need to investigate.

> JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438]  
> Unsafe_SetInt+0x14c
> -
>
> Key: IGNITE-2080
> URL: https://issues.apache.org/jira/browse/IGNITE-2080
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5, 1.4
> Environment: SunOS 5.11, JDK 7
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 1.6
>
> Attachments: 054424_0_localhost.log, benchmark-offheap.properties, 
> hs_err_pid10523.log
>
>
> JVM crashes on SunOS 5.11 with the following message:
> {noformat}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGBUS (0xa) at pc=0x76a7c438, pid=10523, tid=652
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 
> 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode 
> solaris-sparc )
> # Problematic frame:
> # V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> {noformat}
> Stack trace:
> {noformat}
> Stack: [0xfff0f6f0,0xfff0f700],  sp=0xfff0f6ffd1f0,  free 
> space=1012k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native 
> code)
> V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+-1763873616
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+0
> j  
> org.apache.ignite.internal.util.IgniteUtils.writeVersion([BJLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;)J+135
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapEntryImpl.marshal()[B+128
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapManager.write(Lorg/apache/ignite/internal/processors/cache/KeyCacheObject;Ljava/nio/ByteBuffer;BLorg/apache/
> ignite/internal/processors/cache/version/GridCacheVersion;JJLorg/apache/ignite/lang/IgniteUuid;Lorg/apache/ignite/lang/IgniteUuid;)V+86
> j  org.apache.ignite.internal.processors.cache.GridCacheMapEntry.swap()V+333
> j  
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.evictInternal(ZLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignit
> e/internal/processors/cache/CacheEntryPredicate;)Z+122
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.evict0(Lorg/apache/ignite/internal/processors/cache/GridCacheAdapter;Lorg/apache/ignite/internal
> /processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignite/internal/processors/cache/CacheEntryPredica
> te;Z)Z+117
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(Lorg/apache/ignite/internal/processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/
> processors/affinity/AffinityTopologyVersion;)V+123
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(Ljava/util/Collection;Lorg/apache/ignite/internal/processors/affi
> nity/AffinityTopologyVersion;)V+331
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/
> cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+1023
> j  
> 

[jira] [Created] (IGNITE-2254) Need append nodeId for sql-query command in REST API

[Andrey Novikov (JIRA)]

Andrey Novikov created IGNITE-2254:
--

 Summary: Need append nodeId for sql-query command in REST API
 Key: IGNITE-2254
 URL: https://issues.apache.org/jira/browse/IGNITE-2254
 Project: Ignite
  Issue Type: Bug
  Components: clients
Reporter: Andrey Novikov
Assignee: Semen Boikov
 Fix For: 1.6


Query execute command should return nodeId for node where QueryCursor stored in 
nodeLocal
https://apacheignite.readme.io/v1.6/docs/rest-api#sql-query-execute

Query fetch command should resend job to node with nodeId
https://apacheignite.readme.io/v1.6/docs/rest-api#sql-query-fetch



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

[jira] [Commented] (IGNITE-2252) Add support for cache sql schema in REST topology command

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2252:


GitHub user nva opened a pull request:

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

IGNITE-2252 Add support for cache sql schema in REST topology command



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

$ git pull https://github.com/nva/ignite ignite-2252

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

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


commit 97c9c0c115e2381bfd759b4fcf6712cfcd475e1f
Author: Andrey 
Date:   2015-12-24T06:04:56Z

IGNITE-2252 Added support for cache sql schema in REST topology command




> Add support for cache sql schema in REST topology command
> -
>
> Key: IGNITE-2252
> URL: https://issues.apache.org/jira/browse/IGNITE-2252
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 1.5
>Reporter: Alexey Kuznetsov
>Assignee: Andrey Novikov
>Priority: Blocker
> Fix For: 1.5
>
>




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

[jira] [Resolved] (IGNITE-2252) Add support for cache sql schema in REST topology command

[Andrey Novikov (JIRA)]

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

Andrey Novikov resolved IGNITE-2252.

Resolution: Fixed
  Assignee: Semen Boikov  (was: Andrey Novikov)

Fixed. Semen, please review.

> Add support for cache sql schema in REST topology command
> -
>
> Key: IGNITE-2252
> URL: https://issues.apache.org/jira/browse/IGNITE-2252
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 1.5
>Reporter: Alexey Kuznetsov
>Assignee: Semen Boikov
>Priority: Blocker
> Fix For: 1.5
>
>




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

[jira] [Commented] (IGNITE-2016) Update KafkaStreamer to fit new features introduced in Kafka 0.9

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-2016:
-

What do you mean under the exactly-once delivery? Is it related to 
IgniteDataStreamer's implementation somehow?

> Update KafkaStreamer to fit new features introduced in Kafka 0.9
> 
>
> Key: IGNITE-2016
> URL: https://issues.apache.org/jira/browse/IGNITE-2016
> Project: Ignite
>  Issue Type: New Feature
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> Particularly,
> - new consumer
> - Kafka Connect (Copycat)
> http://www.confluent.io/blog/apache-kafka-0.9-is-released
> This can be a a different integration task or a complete re-write of the 
> current implementation, considering the fact that Kafka Connect is a new 
> standard way for "large-scale, real-time data import and export for Kafka."



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

[jira] [Commented] (IGNITE-2032) Filters passed to ScanQuery are not redeployed when originating from a client node

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2032:


GitHub user VladimirErshov opened a pull request:

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

Ignite 2032

IGNITE-2032 Filters passed to ScanQuery are not redeployed when originating 
from a client node
added undeploy for client nodes.

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

$ git pull https://github.com/VladimirErshov/ignite ignite-2032

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

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


commit 717dab259e3f0287046ffcefa28cf9214ab65ff7
Author: sboikov 
Date:   2015-12-14T07:00:57Z

ignite-1.5 Fixed TcpDiscoveryMulticastIpFinder to request address on each 
getRegisteredAddresses call

commit 6d96bb6a3219255b62af826e6806b1aa564bb005
Author: vozerov-gridgain 
Date:   2015-12-14T07:08:00Z

Fix to GridBinaryWildcardsSelfTest.

commit 4ae6292cface325f21237db5d18ce77dee380072
Author: vozerov-gridgain 
Date:   2015-12-14T07:08:29Z

Fixed failure in BinaryObjectBuilderSelfTest.testCopyFromInnerObject.

commit ed27fbdab9d8307b4db427866ed1094526c117c8
Author: vozerov-gridgain 
Date:   2015-12-14T07:08:47Z

Merge remote-tracking branch 'origin/ignite-1.5' into ignite-1.5

commit 3db14482091d01e96e1ae40a15cb903c3adcddbd
Author: vozerov-gridgain 
Date:   2015-12-14T07:19:24Z

Fixed failure in BinaryObjectBuilderSelfTest.testSetBinaryObject.

commit acb57c5eb95d11ebde5557618226d80f25ac610c
Author: sboikov 
Date:   2015-12-14T07:40:57Z

ignite-1.5 Fixed NPE in IgniteKernal.dumpDebugInfo.

commit ec2a64714c176f3a5aca60a058686d3354dc6a76
Author: sboikov 
Date:   2015-12-14T07:41:18Z

Merge remote-tracking branch 'origin/ignite-1.5' into ignite-1.5

commit 484a3afd05b9ad5a524a28c517ddc0a6b9dffcbc
Author: sboikov 
Date:   2015-12-14T07:58:57Z

ignite-1.5 Added waitForCondition in tests with TTL.

commit 47f1ced214b4176b13293386c1e2042c9cc20b32
Author: sboikov 
Date:   2015-12-14T08:09:17Z

ignite-1.5 Fixed test to override correct 'getConfiguration' method.

commit 4d086734833d96b7e2403ce4f17f763a1c75caab
Author: sboikov 
Date:   2015-12-14T08:27:33Z

ignite-1.5 Use TcpDiscoveryVmIpFinder in test.

commit de0b1badbf34538e04e7cf4be5378ef929fb6201
Author: Alexey Kuznetsov 
Date:   2015-12-14T08:33:09Z

ignite-1.5 Updated classnames.properties

commit beb64c34c271b7eac1388179b11f042b34fa0d60
Author: sboikov 
Date:   2015-12-14T08:34:07Z

ignite-1.5 Increased test timeouts.

commit 72e5b9adfdcfcad4b0002bbfc1cf20fd3a0ed149
Author: sboikov 
Date:   2015-12-14T08:34:32Z

Merge remote-tracking branch 'origin/ignite-1.5' into ignite-1.5

commit 4291edca326be4eafde331001238a9181333fbfc
Author: sboikov 
Date:   2015-12-14T09:01:51Z

ignite-1.5 Fixed CacheContinuousQueryFailoverAbstractSelfTest to do not 
hang in case of errors.

commit 345fc27d90f8ae28697fc021d55c7b7a015faeee
Author: sboikov 
Date:   2015-12-14T09:18:16Z

ignite-1.5 Fixed test for offheap mode.

commit fdea7cfaf6ea26834d2694cbfc9634de8d24209b
Author: vozerov-gridgain 
Date:   2015-12-14T09:21:17Z

IGNITE-2150: Fixed invalid test scenario.

commit f3cc98b189dd4c4a4ad6325e6b9a6fa6db795099
Author: vozerov-gridgain 
Date:   2015-12-14T09:21:38Z

Merge remote-tracking branch 'origin/ignite-1.5' into ignite-1.5

commit f87b80f7bf6e38b3ebd21088d4e8aa11a505ed59
Author: vozerov-gridgain 
Date:   2015-12-14T09:40:22Z

IGNITE-2152: .NET: Intro text is added.

commit 6bf716afc490a3bec987e788d795fd979edbdd23
Author: sboikov 
Date:   2015-12-14T09:42:41Z

ignite-1.5 More info in GridPartitionedSingleGetFuture.toString.

commit 68d317952485dd0a4e09844a9cdbb3a0f23ae399
Author: sboikov 
Date:   2015-12-14T09:43:14Z

Merge remote-tracking branch 'origin/ignite-1.5' into ignite-1.5

commit 1224658fe0d4b572b9980fa5de65bbb043646377
Author: sboikov 
Date:   2015-12-14T10:17:06Z

ignite-1.5 Fixed NPE in GridPartitionedSingleGetFuture.

commit 3d9be34c104cc2e89e2422e4f9c3f126449c8162
Author: sboikov 
Date:   2015-12-14T10:31:40Z

ignite-1.5 Less unnecessary logging in test.

commit d6b46115147704f13c36aa59f307f77baf954e3f

[jira] [Resolved] (IGNITE-2033) Refactoring summary page

[Dmitriyff (JIRA)]

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

Dmitriyff resolved IGNITE-2033.
---
Resolution: Fixed
  Assignee: Andrey Novikov  (was: Dmitriyff)

> Refactoring summary page
> 
>
> Key: IGNITE-2033
> URL: https://issues.apache.org/jira/browse/IGNITE-2033
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Dmitriyff
>Assignee: Andrey Novikov
> Fix For: 1.6
>
>




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

[jira] [Resolved] (IGNITE-2149) Build Apache Ignite failed for Java8

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov resolved IGNITE-2149.
---
Assignee: Sergey Kozlov

It fixed

> Build Apache Ignite failed for Java8
> 
>
> Key: IGNITE-2149
> URL: https://issues.apache.org/jira/browse/IGNITE-2149
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Blocker
> Fix For: 1.5
>
>
> {noformat}
> [19:20:12] :   [exec] [WARNING] 
> COMPILATION WARNING : 
> [19:20:12] :   [exec] [INFO] 
> -
> [19:20:12] :   [exec] [WARNING] 
> /home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/ttl/CacheTtlAbstractSelfTest.java:
>  Some input files use unchecked or unsafe operations.
> [19:20:12] :   [exec] [WARNING] 
> /home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/ttl/CacheTtlAbstractSelfTest.java:
>  Recompile with -Xlint:unchecked for details.
> [19:20:12] :   [exec] [INFO] 2 
> warnings 
> [19:20:12] :   [exec] [INFO] 
> -
> [19:20:12] :   [exec] [INFO] 
> -
> [19:20:12] :   [exec] [ERROR] 
> COMPILATION ERROR : 
> [19:20:12] :   [exec] [INFO] 
> -
> [19:20:12] :   [exec] [ERROR] 
> /home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/IgniteBinaryObjectFieldsQuerySelfTest.java:[213,17]
>  reference to assertEquals is ambiguous
> [19:20:12] :   [exec]   both method 
> assertEquals(java.lang.Object,java.lang.Object) in junit.framework.TestCase 
> and method assertEquals(int,int) in junit.framework.TestCase match
> [19:20:12] :   [exec] [INFO] 1 error
> [19:20:12] :   [exec] [INFO] 
> -
> [19:20:12] :   [exec] [INFO] 
> 
> [19:20:12] :   [exec] [INFO] Reactor 
> Summary:
> [19:20:12] :   [exec] [INFO] 
> [19:20:12] :   [exec] [INFO] 
> ignite-apache-license-gen . SUCCESS [1.177s]
> [19:20:12] :   [exec] [INFO] 
> ignite-tools .. SUCCESS [6.047s]
> [19:20:12] :   [exec] [INFO] 
> ignite-core ... SUCCESS [1:11.104s]
> [19:20:12] :   [exec] [INFO] 
> ignite-log4j .. SUCCESS [1.929s]
> [19:20:12] :   [exec] [INFO] 
> ignite-urideploy .. SUCCESS [2.380s]
> [19:20:12] :   [exec] [INFO] 
> ignite-spring . SUCCESS [2.634s]
> [19:20:12] :   [exec] [INFO] 
> ignite-hadoop . SUCCESS [5.968s]
> [19:20:12] :   [exec] [INFO] 
> ignite-extdata-p2p  SUCCESS [2.085s]
> [19:20:12] :   [exec] [INFO] 
> ignite-extdata-uri-dep  SUCCESS [1.272s]
> [19:20:12] :   [exec] [INFO] 
> ignite-extdata-uri  SUCCESS [0.388s]
> [19:20:12] :   [exec] [INFO] 
> ignite-indexing ... FAILURE [1.375s]
> [19:20:12] :   [exec] [INFO] 
> ignite-rest-http .. SKIPPED
> [19:20:12] :   [exec] [INFO] 
> ignite-clients  SKIPPED
> 

[jira] [Created] (IGNITE-2252) Add support for cache sql schema in REST topology command

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-2252:


 Summary: Add support for cache sql schema in REST topology command
 Key: IGNITE-2252
 URL: https://issues.apache.org/jira/browse/IGNITE-2252
 Project: Ignite
  Issue Type: Task
Affects Versions: 1.5
Reporter: Alexey Kuznetsov
Assignee: Andrey Novikov
Priority: Blocker
 Fix For: 1.5






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

[jira] [Created] (IGNITE-2253) Refactoring fields on cluster page

[Dmitriyff (JIRA)]

Dmitriyff created IGNITE-2253:
-

 Summary: Refactoring fields on cluster page
 Key: IGNITE-2253
 URL: https://issues.apache.org/jira/browse/IGNITE-2253
 Project: Ignite
  Issue Type: Sub-task
Reporter: Dmitriyff
Assignee: Dmitriyff






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

[jira] [Commented] (IGNITE-2149) Build Apache Ignite failed for Java8

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov commented on IGNITE-2149:
---

{noformat}
[10:12:35] : [exec] [ERROR] 
COMPILATION ERROR : 
[10:12:35] : [exec] [INFO] 
-
[10:12:35] : [exec] [ERROR] 
/home/teamcity/BuildAgent/work/4b78de95608af2b1/apache-ignite/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/IgniteCacheAbstractQuerySelfTest.java:[478,13]
 reference to assertEquals is ambiguous
[10:12:35] : [exec]   both method 
assertEquals(java.lang.Object,java.lang.Object) in junit.framework.TestCase and 
method assertEquals(long,long) in junit.framework.TestCase match
{noformat}

> Build Apache Ignite failed for Java8
> 
>
> Key: IGNITE-2149
> URL: https://issues.apache.org/jira/browse/IGNITE-2149
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Priority: Blocker
> Fix For: 1.5
>
>
> {noformat}
> [19:20:12] :   [exec] [WARNING] 
> COMPILATION WARNING : 
> [19:20:12] :   [exec] [INFO] 
> -
> [19:20:12] :   [exec] [WARNING] 
> /home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/ttl/CacheTtlAbstractSelfTest.java:
>  Some input files use unchecked or unsafe operations.
> [19:20:12] :   [exec] [WARNING] 
> /home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/ttl/CacheTtlAbstractSelfTest.java:
>  Recompile with -Xlint:unchecked for details.
> [19:20:12] :   [exec] [INFO] 2 
> warnings 
> [19:20:12] :   [exec] [INFO] 
> -
> [19:20:12] :   [exec] [INFO] 
> -
> [19:20:12] :   [exec] [ERROR] 
> COMPILATION ERROR : 
> [19:20:12] :   [exec] [INFO] 
> -
> [19:20:12] :   [exec] [ERROR] 
> /home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/IgniteBinaryObjectFieldsQuerySelfTest.java:[213,17]
>  reference to assertEquals is ambiguous
> [19:20:12] :   [exec]   both method 
> assertEquals(java.lang.Object,java.lang.Object) in junit.framework.TestCase 
> and method assertEquals(int,int) in junit.framework.TestCase match
> [19:20:12] :   [exec] [INFO] 1 error
> [19:20:12] :   [exec] [INFO] 
> -
> [19:20:12] :   [exec] [INFO] 
> 
> [19:20:12] :   [exec] [INFO] Reactor 
> Summary:
> [19:20:12] :   [exec] [INFO] 
> [19:20:12] :   [exec] [INFO] 
> ignite-apache-license-gen . SUCCESS [1.177s]
> [19:20:12] :   [exec] [INFO] 
> ignite-tools .. SUCCESS [6.047s]
> [19:20:12] :   [exec] [INFO] 
> ignite-core ... SUCCESS [1:11.104s]
> [19:20:12] :   [exec] [INFO] 
> ignite-log4j .. SUCCESS [1.929s]
> [19:20:12] :   [exec] [INFO] 
> ignite-urideploy .. SUCCESS [2.380s]
> [19:20:12] :   [exec] [INFO] 
> ignite-spring . SUCCESS [2.634s]
> [19:20:12] :   [exec] [INFO] 
> ignite-hadoop . SUCCESS [5.968s]
> [19:20:12] :   [exec] [INFO] 
> ignite-extdata-p2p 

[jira] [Commented] (IGNITE-2032) Filters passed to ScanQuery are not redeployed when originating from a client node

[Vladimir Ershov (JIRA)]

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

Vladimir Ershov commented on IGNITE-2032:
-

As found: during GridDeploymentPerVersionStore#onEvent clsLoader that should be 
cleaned from IgniteUtils.classCache is GridDeploymentClassLoader, but actual 
classes registered under CacheClassLoader. I'm going to discuss possible 
modification for that mechanism since it looks broken. As for server mode, it 
is working cos for server node we do unwind->onDeploy before deployment which 
is also strange.

> Filters passed to ScanQuery are not redeployed when originating from a client 
> node
> --
>
> Key: IGNITE-2032
> URL: https://issues.apache.org/jira/browse/IGNITE-2032
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Vladimir Ershov
>Priority: Critical
> Fix For: 1.6
>
> Attachments: ScanQueryFailure.java, test-config.xml
>
>
> The following case doesn't work:
> - start a standalone server node with peer class loading enabled;
> - start a client node, populate a cache with data, perform a scan query using 
> a filter;
> - since the server doesn't have the filter in its classpath it will load it 
> from the client. Everything works fine here;
> - stop the client, the server will undeploy the filter. No issue here so far;
> - modify the filter a bit and start the client one more time. The server 
> won't deploy the new version of the filter and will be using the old 
> regardless of the fact that it was undeployed before according to the logs.
> The server can be started using ignite.bat and test-config.xml (attached).
> The source of the client is located in attached ScanQueryFailure.java.
> BTW, everything works fine if to use the server mode instead of the client 
> one.



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

[jira] [Comment Edited] (IGNITE-2032) Filters passed to ScanQuery are not redeployed when originating from a client node

[Vladimir Ershov (JIRA)]

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

Vladimir Ershov edited comment on IGNITE-2032 at 12/23/15 9:06 AM:
---

As found: during GridDeploymentPerVersionStore#onEvent clsLoader that should be 
cleaned from IgniteUtils.classCache is GridDeploymentClassLoader, but actual 
classes registered under CacheClassLoader. That cause 
GridDeploymentPerVersionStore#createNewDeployment to not be invoked for 
reregistration of clientNodes. I'm going to discuss possible modification for 
that mechanism since it looks broken. As for server mode, it is working cos for 
server node we do unwind->onDeploy before deployment which is also strange.


was (Author: vershov):
As found: during GridDeploymentPerVersionStore#onEvent clsLoader that should be 
cleaned from IgniteUtils.classCache is GridDeploymentClassLoader, but actual 
classes registered under CacheClassLoader. I'm going to discuss possible 
modification for that mechanism since it looks broken. As for server mode, it 
is working cos for server node we do unwind->onDeploy before deployment which 
is also strange.

> Filters passed to ScanQuery are not redeployed when originating from a client 
> node
> --
>
> Key: IGNITE-2032
> URL: https://issues.apache.org/jira/browse/IGNITE-2032
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Vladimir Ershov
>Priority: Critical
> Fix For: 1.6
>
> Attachments: ScanQueryFailure.java, test-config.xml
>
>
> The following case doesn't work:
> - start a standalone server node with peer class loading enabled;
> - start a client node, populate a cache with data, perform a scan query using 
> a filter;
> - since the server doesn't have the filter in its classpath it will load it 
> from the client. Everything works fine here;
> - stop the client, the server will undeploy the filter. No issue here so far;
> - modify the filter a bit and start the client one more time. The server 
> won't deploy the new version of the filter and will be using the old 
> regardless of the fact that it was undeployed before according to the logs.
> The server can be started using ignite.bat and test-config.xml (attached).
> The source of the client is located in attached ScanQueryFailure.java.
> BTW, everything works fine if to use the server mode instead of the client 
> one.



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

[jira] [Commented] (IGNITE-2250) Client section on Summary contains ServerConfigurationFactory java class

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2250:


GitHub user Dmitriyff opened a pull request:

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

IGNITE-2250 added ability to set default value for config if directive has 
attribute



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

$ git pull https://github.com/Dmitriyff/ignite ignite-2250

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

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


commit 84aedd9a146ed0ff0e6d879f77ab5bfa74d4905d
Author: Dmitriyff 
Date:   2015-12-23T09:05:18Z

IGNITE-2250 added ability to set default value




> Client section on Summary contains ServerConfigurationFactory java class
> 
>
> Key: IGNITE-2250
> URL: https://issues.apache.org/jira/browse/IGNITE-2250
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Dmitriyff
> Fix For: 1.6
>
>
> Should contain ClientConfigurationFactory



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

[jira] [Resolved] (IGNITE-2250) Client section on Summary contains ServerConfigurationFactory java class

[Dmitriyff (JIRA)]

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

Dmitriyff resolved IGNITE-2250.
---
Resolution: Fixed
  Assignee: Andrey Novikov  (was: Dmitriyff)

> Client section on Summary contains ServerConfigurationFactory java class
> 
>
> Key: IGNITE-2250
> URL: https://issues.apache.org/jira/browse/IGNITE-2250
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Andrey Novikov
> Fix For: 1.6
>
>
> Should contain ClientConfigurationFactory



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

[jira] [Commented] (IGNITE-2200) CacheQueryExample failes after CacheClientBinaryQueryExample and vice versa

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2200:


GitHub user agoncharuk opened a pull request:

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

IGNITE-2200 - Fixed deployment and added a test.



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

$ git pull https://github.com/agoncharuk/ignite ignite-2200

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

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


commit 24953d0b62db9cf036a9400fdb955815b6d09fa0
Author: Alexey Goncharuk 
Date:   2015-12-23T09:09:08Z

IGNITE-2200 - Fixed deployment and added a test.




> CacheQueryExample failes after CacheClientBinaryQueryExample and vice versa
> ---
>
> Key: IGNITE-2200
> URL: https://issues.apache.org/jira/browse/IGNITE-2200
> Project: Ignite
>  Issue Type: Bug
>Reporter: Sergey Kozlov
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 1.5
>
>
> 1. Start remote node with config examples/config/example-ignite.xml
> 2. Run CacheClientBinaryQueryExample. It passed
> 3. Run CacheQueryExample. It failes:
> {noformat}
> >>> Cache query example started.
> Exception in thread "main" javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Type ID collision detected 
> [id=1178922291, clsName1=org.apache.ignite.examples.model.Organization, 
> clsName2=org.apache.ignite.examples.model.binary.Organization]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1618)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1078)
>   at 
> org.apache.ignite.examples.datagrid.CacheQueryExample.initialize(CacheQueryExample.java:276)
>   at 
> org.apache.ignite.examples.datagrid.CacheQueryExample.main(CacheQueryExample.java:97)
>   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)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: class org.apache.ignite.IgniteCheckedException: Type ID collision 
> detected [id=1178922291, 
> clsName1=org.apache.ignite.examples.model.Organization, 
> clsName2=org.apache.ignite.examples.model.binary.Organization]
>   at 
> org.apache.ignite.internal.MarshallerContextImpl.registerClassName(MarshallerContextImpl.java:116)
>   at 
> org.apache.ignite.internal.MarshallerContextAdapter.registerClass(MarshallerContextAdapter.java:157)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:576)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:555)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForClass(BinaryContext.java:457)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:145)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:132)
>   at 
> org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:225)
>   at 
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.marshalToBinary(CacheObjectBinaryProcessorImpl.java:438)
>   at 
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toBinary(CacheObjectBinaryProcessorImpl.java:777)
>   at 
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toCacheObject(CacheObjectBinaryProcessorImpl.java:724)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheContext.toCacheObject(GridCacheContext.java:1798)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.mapSingleUpdate(GridNearAtomicUpdateFuture.java:1137)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(GridNearAtomicUpdateFuture.java:868)
>   at 
> 

[jira] [Resolved] (IGNITE-2220) upgrade gulp tasks

[Dmitriyff (JIRA)]

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

Dmitriyff resolved IGNITE-2220.
---
Resolution: Fixed
  Assignee: Andrey Novikov  (was: Dmitriyff)

> upgrade gulp tasks
> --
>
> Key: IGNITE-2220
> URL: https://issues.apache.org/jira/browse/IGNITE-2220
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 1.6
>Reporter: Dmitriyff
>Assignee: Andrey Novikov
> Fix For: 1.6
>
>




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

[jira] [Assigned] (IGNITE-2219) ClassCastException from NodeIdMessage to AffinityTopologyVersion

[Semen Boikov (JIRA)]

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

Semen Boikov reassigned IGNITE-2219:


Assignee: Semen Boikov

> ClassCastException from NodeIdMessage to AffinityTopologyVersion
> 
>
> Key: IGNITE-2219
> URL: https://issues.apache.org/jira/browse/IGNITE-2219
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
> Environment: Ubuntu 12.04 64 bit
> java version "1.8.0_60"
> Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
> Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
> Ignite 1.4.0
>Reporter: Avihai Berkovitz
>Assignee: Semen Boikov
> Attachments: message-hex.txt
>
>
> We had a cluster up and running for a couple of days. Without doing anything 
> new, we got the following error in one of the nodes:
> {noformat}
> Caught unhandled exception in NIO worker thread (restart the node). 
> java.lang.ClassCastException: 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$NodeIdMessage 
> cannot be cast to 
> org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsFullMessage.readFrom(GridDhtPartitionsFullMessage.java:176)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.direct.DirectByteBufferStream.readMessage(DirectByteBufferStream.java:963)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.direct.DirectMessageReader.readMessage(DirectMessageReader.java:252)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:249)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:79)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:104)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:78)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:2124)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:173)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:898)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeys(GridNioServer.java:1437)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1379)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1263)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
> [ignite-core-1.4.0.jar:1.4.0]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
> {noformat}
> It happened only once so far, but killed the communication from this node.



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

[jira] [Commented] (IGNITE-2219) ClassCastException from NodeIdMessage to AffinityTopologyVersion

[Semen Boikov (JIRA)]

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

Semen Boikov commented on IGNITE-2219:
--

Looks like this issue with GridDhtPartitionsFullMessage.prepareMarshal is 
already fixed in ignite-1.5 and 'parts' is marshalled only once of first 
message send. Need to check others message for similar issue.

> ClassCastException from NodeIdMessage to AffinityTopologyVersion
> 
>
> Key: IGNITE-2219
> URL: https://issues.apache.org/jira/browse/IGNITE-2219
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
> Environment: Ubuntu 12.04 64 bit
> java version "1.8.0_60"
> Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
> Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
> Ignite 1.4.0
>Reporter: Avihai Berkovitz
>Assignee: Semen Boikov
> Attachments: message-hex.txt
>
>
> We had a cluster up and running for a couple of days. Without doing anything 
> new, we got the following error in one of the nodes:
> {noformat}
> Caught unhandled exception in NIO worker thread (restart the node). 
> java.lang.ClassCastException: 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$NodeIdMessage 
> cannot be cast to 
> org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsFullMessage.readFrom(GridDhtPartitionsFullMessage.java:176)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.direct.DirectByteBufferStream.readMessage(DirectByteBufferStream.java:963)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.direct.DirectMessageReader.readMessage(DirectMessageReader.java:252)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:249)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:79)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:104)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:78)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:2124)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:173)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:898)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeys(GridNioServer.java:1437)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1379)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1263)
>  ~[ignite-core-1.4.0.jar:1.4.0]
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
> [ignite-core-1.4.0.jar:1.4.0]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
> {noformat}
> It happened only once so far, but killed the communication from this node.



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

[jira] [Commented] (IGNITE-2016) Update KafkaStreamer to fit new features introduced in Kafka 0.9

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-2016:
-

Roman, thanks for the clarification. Please give me some time to investigate 
the difference between Kafka Connect & Flume VS other streamers.

Sorry for the delay.

> Update KafkaStreamer to fit new features introduced in Kafka 0.9
> 
>
> Key: IGNITE-2016
> URL: https://issues.apache.org/jira/browse/IGNITE-2016
> Project: Ignite
>  Issue Type: New Feature
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> Particularly,
> - new consumer
> - Kafka Connect (Copycat)
> http://www.confluent.io/blog/apache-kafka-0.9-is-released
> This can be a a different integration task or a complete re-write of the 
> current implementation, considering the fact that Kafka Connect is a new 
> standard way for "large-scale, real-time data import and export for Kafka."



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

[jira] [Updated] (IGNITE-2174) Error with overwrite dialog on loading metadata from DB

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2174:
-
Description: 
To reproduce just try to load the same metadata twice.
UI just hang, but should show confirm override dialog instead.

  was:To reproduce just try to load the same metadata twice.


> Error with overwrite dialog on loading metadata from DB
> ---
>
> Key: IGNITE-2174
> URL: https://issues.apache.org/jira/browse/IGNITE-2174
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
>
> To reproduce just try to load the same metadata twice.
> UI just hang, but should show confirm override dialog instead.



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

[jira] [Resolved] (IGNITE-2174) Error with overwrite dialog on loading metadata from DB

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov resolved IGNITE-2174.
--
Resolution: Fixed
  Assignee: Pavel Konstantinov

> Error with overwrite dialog on loading metadata from DB
> ---
>
> Key: IGNITE-2174
> URL: https://issues.apache.org/jira/browse/IGNITE-2174
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
>
> To reproduce just try to load the same metadata twice.



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

[jira] [Commented] (IGNITE-647) org.apache.ignite.IgniteCacheAffinitySelfTest.testAffinity() hangs

[Semen Boikov (JIRA)]

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

Semen Boikov commented on IGNITE-647:
-

There is one more race here:
- node 1 starts, exchange is finished
- node 2 starts, exchange is finished
- node 2 starts cache with fair affinity function, starts exchange and sends 
GridDhtAffinityAssignmentRequest to node1. At this point node1 started exchange 
process, but did start cache yet and did not register required message handler 
so message will be ignored.

So any dynamic cache start with fair affinity initiated from non-oldest node 
can easily hang.

> org.apache.ignite.IgniteCacheAffinitySelfTest.testAffinity() hangs
> --
>
> Key: IGNITE-647
> URL: https://issues.apache.org/jira/browse/IGNITE-647
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Yakov Zhdanov
>Assignee: Alexey Goncharuk
>Priority: Blocker
>  Labels: Muted_test
> Attachments: FairAffinityDynamicCacheSelfTest.testStartStopCache.txt, 
> threaddump.txt
>
>
> 1-2 runs out of ~10 local runs hanged for me



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