[jira] [Closed] (IGNITE-1864) Cannot configure jndiNames for CacheJndiTmLookup

[Artem Shutak (JIRA)]

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

Artem Shutak closed IGNITE-1864.


> Cannot configure jndiNames for CacheJndiTmLookup 
> -
>
> Key: IGNITE-1864
> URL: https://issues.apache.org/jira/browse/IGNITE-1864
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Yakov Zhdanov
>Assignee: Artem Shutak
>Priority: Critical
> Fix For: 1.5
>
>
> Since user have an ability to configure only lookup class name via 
> org.apache.ignite.configuration.TransactionConfiguration#getTxManagerLookupClassName,
>  he lacks ability to properly configure all of its properties.
> This seems to be a general problem for this approach



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

[jira] [Updated] (IGNITE-1871) Fix the color of column in chart settings

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1871:
-
Issue Type: Bug  (was: Sub-task)
Parent: (was: IGNITE-843)

> Fix the color of column in chart settings
> -
>
> Key: IGNITE-1871
> URL: https://issues.apache.org/jira/browse/IGNITE-1871
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
>
> Now if user set two columns on Y-axis each has its unique color.
> After that if user remove the first column then the second column change it 
> color - this is a bit confuses.



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

[jira] [Updated] (IGNITE-1918) Incorrect EXPORT ALL file content for EXPLAIN

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1918:
-
Issue Type: Bug  (was: Sub-task)
Parent: (was: IGNITE-843)

> Incorrect EXPORT ALL file content for EXPLAIN
> -
>
> Key: IGNITE-1918
> URL: https://issues.apache.org/jira/browse/IGNITE-1918
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
>
> 1) Execute any correct query
> 2) Do EXPLAIN
> 3) Do Export All
> I'm expected to see explain text, but see prev query result. I'm right?



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

[jira] [Updated] (IGNITE-1929) Add code snippets for C++ and C#.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1929:
-
Issue Type: Bug  (was: Sub-task)
Parent: (was: IGNITE-843)

> Add code snippets for C++ and C#.
> -
>
> Key: IGNITE-1929
> URL: https://issues.apache.org/jira/browse/IGNITE-1929
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Alexey Kuznetsov
>Priority: Minor
> Fix For: 1.5
>
>
> We need to generate code for C++ and C# the same way we do for Java.



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

[jira] [Updated] (IGNITE-2068) Generation of separate metod for each metadata

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko updated IGNITE-2068:
--
Description: 
# Also do not generate QueryEntity when SQL query fields is not configured.
# Generation of caches in separate methods.

  was:Also do not generate QueryEntity when SQL query fields is not configured.


> Generation of separate metod for each metadata 
> ---
>
> Key: IGNITE-2068
> URL: https://issues.apache.org/jira/browse/IGNITE-2068
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
>Priority: Minor
> Fix For: 1.5
>
>
> # Also do not generate QueryEntity when SQL query fields is not configured.
> # Generation of caches in separate methods.



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

[jira] [Commented] (IGNITE-2088) EntryProcessor invoke might not run in CLOCK write order

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-2088:
--

Dmitriy, Noam described the situation correctly. Entry processor invocations 
may be dropped on affinity node because the version is assigned on client nodes.
Setting ignoreTime to true if op == TRANSFORM will not work because it will 
lead to an inconsistent version comparison when concurrent put/invoke 
operations are running.

My preference is that ignite throw an exception on invoke() in CLOCK mode.

> EntryProcessor invoke might not run in CLOCK write order
> 
>
> Key: IGNITE-2088
> URL: https://issues.apache.org/jira/browse/IGNITE-2088
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
> Environment: Windows 8.1 64 bit
> java version "1.8.0_51"
> Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
> Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
> Ignite 1.4.0
>Reporter: Avihai Berkovitz
>
> I have a program that runs several threads at the same time, all of them 
> executing an invoke() on the same cache key to update it. I found that the 
> EntryProcessor is not always executed, and in this case invoke() returns 
> null. This happens when the cache is configured with CLOCK 
> CacheAtomicWriteOrderMode, but not when using PRIMARY.
> After some debugging I found out that it happens when the cache gets the 
> invocations out of order, and dismisses the older ones, returning the result 
> from GridCacheMapEntry line 1855.
> As I understand it, this mechanism is in place to protect against 
> out-of-order updates. Invokes, however, are a special case as they execute 
> client code with unknown side effects that should not be discarded. If you 
> believe the current behavior is correct, it should at least be documented.
> Here is a sample program to illustrate the problem. Notice that "IN INVOKE" 
> is printed less than 10 times (usually):
> {code}
> IgniteConfiguration igniteConfiguration = new IgniteConfiguration()
>   .setFailoverSpi(new AlwaysFailoverSpi())
>   .setGridLogger(new Slf4jLogger())
>   .setPeerClassLoadingEnabled(false)
>   .setDeploymentMode(DeploymentMode.CONTINUOUS);
> Ignite ignite = Ignition.start(igniteConfiguration);
> CacheConfiguration cacheConfiguration = new 
> CacheConfiguration()
>   .setName("test")
>   .setCacheMode(CacheMode.PARTITIONED)
>   .setAtomicityMode(CacheAtomicityMode.ATOMIC)
>   
> .setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);
> IgniteCache cache = ignite.getOrCreateCache(cacheConfiguration);
> Thread[] threads = new Thread[10];
> for (int i = 0; i < threads.length; i++) {
>   threads[i] = new Thread() {
>   @Override
>   public void run() {
>   System.out.println(String.format("Thread %s running", 
> getId()));
>   Long result = cache.invoke("key", (entry, arguments) -> 
> {
>   Long value = entry.getValue();
>   System.out.println(String.format("IN INVOKE: 
> thread ID:%s exists:%s value:%s", getId(), entry.exists(), value));
>   if (!entry.exists()) {
>   entry.setValue(getId());
>   }
>   return value;
>   });
>   System.out.println(String.format("Thread %s got invoke 
> result %s", getId(), result));
>   }
>   };
> }
> for (Thread thread : threads) {
>   thread.start();
> }
> Thread.sleep(2_000);
> for (Thread thread : threads) {
>   thread.interrupt();
> }
> for (Thread thread : threads) {
>   thread.join();
> }
> System.out.println("Done");
> {code}
> Output sample:
> {noformat}
> [13:51:41]__   
> [13:51:41]   /  _/ ___/ |/ /  _/_  __/ __/ 
> [13:51:41]  _/ // (7 7// /  / / / _/   
> [13:51:41] /___/\___/_/|_/___/ /_/ /___/  
> [13:51:41] 
> [13:51:41] ver. 1.4.0#20150924-sha1:c2def5f6
> [13:51:41] 2015 Copyright(C) Apache Software Foundation
> [13:51:41] 
> [13:51:41] Ignite documentation: http://ignite.apache.org
> [13:51:41] 
> [13:51:41] Quiet mode.
> [13:51:41]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
> "-v" to ignite.{sh|bat}
> [13:51:41] 
> [13:51:41] Initial heap size is 256MB (should be no less than 512MB, use 
> -Xms512m -Xmx512m).
> [13:51:43] Configured plugins:
> [13:51:43]   ^-- None
> [13:51:43] 
> [13:52:04] Security status [authentication=off, communication encryption=off]
> [13:52:10] To start Console 

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

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-2080:
-

I can answer for "Platforms" - definitely not safe. Changes must be applied 
there as well.

> 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
> 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  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(Lorg/apache/ignite/internal/processors/affinity/Affinit
> yTopologyVersion;)V+595
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology()V+253
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map()V+60

[jira] [Assigned] (IGNITE-1861) We should not save metadata if it contains incompleted index

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-1861:


Assignee: Vasiliy Sisko

> We should not save metadata if it contains incompleted index
> 
>
> Key: IGNITE-1861
> URL: https://issues.apache.org/jira/browse/IGNITE-1861
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
> Fix For: 1.5
>
>
> 1)Add new metadata
> 2)Add index but not add the fields in it
> 3)Save
> Observed - successfully saved
> Expected - error that index is incomplete



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

[jira] [Updated] (IGNITE-1860) SQL: Do not export system columns if they are OFF (invisible)

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1860:
-
Issue Type: Sub-task  (was: Bug)
Parent: IGNITE-2047

> SQL: Do not export system columns if they are OFF (invisible)
> -
>
> Key: IGNITE-1860
> URL: https://issues.apache.org/jira/browse/IGNITE-1860
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
>
> Export only visible columns



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

[jira] [Comment Edited] (IGNITE-1864) Cannot configure jndiNames for CacheJndiTmLookup

[Semen Boikov (JIRA)]

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

Semen Boikov edited comment on IGNITE-1864 at 12/9/15 8:25 AM:
---

I have minor comments: CacheJndiTmLookup.getTm should throw exception if failed 
to find tm, also please fix CacheJndiTmLookup test to restore modified system 
properties.


was (Author: sboikov):
I have minor comments: CacheJndiTmLookup.getTm should throw exception if failed 
to find tm, also please fix CacheJndiTmLookup test to resotore modified system 
properties.

> Cannot configure jndiNames for CacheJndiTmLookup 
> -
>
> Key: IGNITE-1864
> URL: https://issues.apache.org/jira/browse/IGNITE-1864
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Yakov Zhdanov
>Assignee: Artem Shutak
>Priority: Critical
> Fix For: 1.5
>
>
> Since user have an ability to configure only lookup class name via 
> org.apache.ignite.configuration.TransactionConfiguration#getTxManagerLookupClassName,
>  he lacks ability to properly configure all of its properties.
> This seems to be a general problem for this approach



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

[jira] [Commented] (IGNITE-1864) Cannot configure jndiNames for CacheJndiTmLookup

[Semen Boikov (JIRA)]

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

Semen Boikov commented on IGNITE-1864:
--

I have minor comments: CacheJndiTmLookup.getTm should throw exception if failed 
to find tm, also please fix CacheJndiTmLookup test to resotore modified system 
properties.

> Cannot configure jndiNames for CacheJndiTmLookup 
> -
>
> Key: IGNITE-1864
> URL: https://issues.apache.org/jira/browse/IGNITE-1864
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Yakov Zhdanov
>Assignee: Artem Shutak
>Priority: Critical
> Fix For: 1.5
>
>
> Since user have an ability to configure only lookup class name via 
> org.apache.ignite.configuration.TransactionConfiguration#getTxManagerLookupClassName,
>  he lacks ability to properly configure all of its properties.
> This seems to be a general problem for this approach



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

[jira] [Assigned] (IGNITE-2099) Binary marshaller writes any map as a HashMap

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-2099:
---

Assignee: Vladimir Ozerov

> Binary marshaller writes any map as a HashMap
> -
>
> Key: IGNITE-2099
> URL: https://issues.apache.org/jira/browse/IGNITE-2099
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Valentin Kulichenko
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>
> Bug is described and discussed in this user@ thread: 
> http://apache-ignite-users.70518.x6.nabble.com/Serialization-issue-with-Ignite-1-5-built-from-master-357d791-td2149.html
> In general, we need to make sure that binary marshaller fully supports Java 
> serialization and behaves consistently with optimized marshaller.



--
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=15048450#comment-15048450
 ] 

Andrey Gura commented on IGNITE-2080:
-

It requires some clarification.

{{Unsafe}} contains two group of methods: the first for memory access by 
address pointer and the second one for memroy access by object field offset.

For the first group methods {{GridUnsafe}} wrappers always take in account 
information about aligment. For the second group of methods there are two 
different cases of memory access^

#. Access to the object field by offset always aligned, so we can always use 
one {{int}}, {{long}}, etc. operation insted of {{ByByte}}-version.
#. Exception form the previous case is read/write operation upon byte arrays. 
This operations should be aligment aware. For this cases added {{Aligned}} 
methods family.

May be I use not the best naming this methos. So you are welcome with any ideas 
about it.

> 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
> 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  
> 

[jira] [Updated] (IGNITE-1874) Adjust initial placement and size of metadada popup on SQL

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1874:
-
Issue Type: Sub-task  (was: Bug)
Parent: IGNITE-2047

> Adjust initial placement and size of metadada popup on SQL
> --
>
> Key: IGNITE-1874
> URL: https://issues.apache.org/jira/browse/IGNITE-1874
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
> Attachments: ig-1874.png
>
>
> Currently if user opens two metadata popups then they will cross each other 
> (please see attachment).
> Because of that I suggest:
> 1) change initial position - align with top of query be vertical
> 2) change initial height - the same as initial query height



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

[jira] [Updated] (IGNITE-1879) Add platforms configurations

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1879:
-
Issue Type: Bug  (was: Sub-task)
Parent: (was: IGNITE-843)

> Add platforms configurations
> 
>
> Key: IGNITE-1879
> URL: https://issues.apache.org/jira/browse/IGNITE-1879
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Alexey Kuznetsov
> Fix For: 1.5
>
>




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

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

[Semen Boikov (JIRA)]

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

Semen Boikov edited comment on IGNITE-2080 at 12/9/15 8:11 AM:
---

Andrey,

I still see suspicious unsafe usages in following places:
- GridCacheOffheapSwapEntry
- IgniteUtils.readVersion(long ptr, boolean verEx)
- PlatformMemoryUtils
- PlatformOutputStreamImpl/PlatformInputStreamImpl
- PortableOffheapInputStream/PortableOffheapOutputStream
- BinaryObjectOffheapImpl

Are you sure 'it is safe to not use 'aligned' get/put in these places.

Please also fix javadoc warnings in GridUnsafe: 'return' is missed in many 
places.


was (Author: sboikov):
Andrey,

I still see suspicious unsafe usages in following places:
- GridCacheOffheapSwapEntry
- IgniteUtils.readVersion(long ptr, boolean verEx)
- PlatformMemoryUtils
- PlatformOutputStreamImpl/PlatformInputStreamImpl
- PortableOffheapInputStream/PortableOffheapOutputStream

Are you sure 'it is safe to not use 'aligned' get/put in these places.

Please also fix javadoc warnings in GridUnsafe: 'return' is missed in many 
places.

> 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
> 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  
> 

[jira] [Updated] (IGNITE-1860) SQL: Do not export system columns if they are OFF (invisible)

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1860:
-
Issue Type: Bug  (was: Sub-task)
Parent: (was: IGNITE-843)

> SQL: Do not export system columns if they are OFF (invisible)
> -
>
> Key: IGNITE-1860
> URL: https://issues.apache.org/jira/browse/IGNITE-1860
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
>
> Export only visible columns



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

[jira] [Updated] (IGNITE-1836) Automatically select the first item if current is not in filtered list

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1836:
-
Issue Type: Bug  (was: Sub-task)
Parent: (was: IGNITE-843)

> Automatically select the first item if current is not in filtered list
> --
>
> Key: IGNITE-1836
> URL: https://issues.apache.org/jira/browse/IGNITE-1836
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Critical
> Fix For: 1.5
>
>
> 1) select valid metadata item
> 2) switch to invalid or set filter - current active item is not in the new 
> list
> 3) try to remove item - you will be remove item which was active before 
> filtration



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

[jira] [Commented] (IGNITE-1864) Cannot configure jndiNames for CacheJndiTmLookup

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-1864:


Github user ashutakGG closed the pull request at:

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


> Cannot configure jndiNames for CacheJndiTmLookup 
> -
>
> Key: IGNITE-1864
> URL: https://issues.apache.org/jira/browse/IGNITE-1864
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Yakov Zhdanov
>Assignee: Artem Shutak
>Priority: Critical
> Fix For: 1.5
>
>
> Since user have an ability to configure only lookup class name via 
> org.apache.ignite.configuration.TransactionConfiguration#getTxManagerLookupClassName,
>  he lacks ability to properly configure all of its properties.
> This seems to be a general problem for this approach



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

[jira] [Updated] (IGNITE-1918) Incorrect EXPORT ALL file content for EXPLAIN

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-1918:
-
Issue Type: Sub-task  (was: Bug)
Parent: IGNITE-2047

> Incorrect EXPORT ALL file content for EXPLAIN
> -
>
> Key: IGNITE-1918
> URL: https://issues.apache.org/jira/browse/IGNITE-1918
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
>
> 1) Execute any correct query
> 2) Do EXPLAIN
> 3) Do Export All
> I'm expected to see explain text, but see prev query result. I'm right?



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

[jira] [Commented] (IGNITE-2111) .Net: Create a build script

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2111:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-2111 .Net: Create a build script



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

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

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

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


commit 163cdac9d035e5fe73d23b3b2eb52f102b8d881b
Author: Pavel Tupitsyn 
Date:   2015-12-08T15:43:28Z

Include XML documentation

commit a5b8cd8f9e7ffd13d68c8d168b869100fca2c9bd
Author: Pavel Tupitsyn 
Date:   2015-12-08T16:30:48Z

Update examples HintPaths

commit 665dd80b0ab15c30c38d5018870d321b0846af6d
Author: Pavel Tupitsyn 
Date:   2015-12-08T16:41:24Z

Fix HintPath conditions

commit c2e40f737da8b80b3c8d13424c0e96f23bf9966b
Author: Pavel Tupitsyn 
Date:   2015-12-09T09:19:26Z

Fix HintPath typo

commit f12c7cab4a2915351c6f1bd595f35ed91cdff665
Author: Pavel Tupitsyn 
Date:   2015-12-09T09:54:54Z

wip dxg

commit 90ff07f8db21f84b07c14aeab7ef5285ddd34da3
Author: Pavel Tupitsyn 
Date:   2015-12-09T10:01:06Z

wip dxg

commit 8abf95aa50d1daf2c3738043224c4defca93affc
Author: Pavel Tupitsyn 
Date:   2015-12-09T10:26:56Z

wip dxg

commit 4767eb210e35cb8e0f0c818ff7598d580667ab73
Author: Pavel Tupitsyn 
Date:   2015-12-09T11:51:52Z

wip dxg

commit 57159066bd10714222e0647ec4e670da2d1ff40e
Author: Pavel Tupitsyn 
Date:   2015-12-09T12:08:35Z

wip dxg

commit 2f6136127bd0d3faf1fd9bd86770a448b23e44dc
Author: Pavel Tupitsyn 
Date:   2015-12-09T12:12:14Z

Update release fabric

commit c7922f6014362513f531299620321a4c785a5103
Author: Pavel Tupitsyn 
Date:   2015-12-09T12:14:59Z

cleanup




> .Net: Create a build script
> ---
>
> Key: IGNITE-2111
> URL: https://issues.apache.org/jira/browse/IGNITE-2111
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 1.5
>
>
> * Create a build script (batch file) to produce x86/x64 binaries
> * Change examples reference paths to use produced binaries (to simplify 
> example running)
> * Add doxygen documentation template



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

[jira] [Updated] (IGNITE-2099) Binary marshaller writes any map as a HashMap

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2099:

Component/s: interop

> Binary marshaller writes any map as a HashMap
> -
>
> Key: IGNITE-2099
> URL: https://issues.apache.org/jira/browse/IGNITE-2099
> Project: Ignite
>  Issue Type: Bug
>  Components: general, interop
>Reporter: Valentin Kulichenko
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>
> Bug is described and discussed in this user@ thread: 
> http://apache-ignite-users.70518.x6.nabble.com/Serialization-issue-with-Ignite-1-5-built-from-master-357d791-td2149.html
> In general, we need to make sure that binary marshaller fully supports Java 
> serialization and behaves consistently with optimized marshaller.



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

[jira] [Updated] (IGNITE-2100) Queries do not work with binary marshaller and Externalizable objects

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2100:

Component/s: interop

> Queries do not work with binary marshaller and Externalizable objects
> -
>
> Key: IGNITE-2100
> URL: https://issues.apache.org/jira/browse/IGNITE-2100
> Project: Ignite
>  Issue Type: Bug
>  Components: general, interop
>Reporter: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.5
>
>
> If new binary marshaller is used and model classes implement 
> {{Externalizable}} (which is often the case when user migrates from 1.4 to 
> 1.5), queries stop working and return nulls instead of all field values.
> At least, we need to properly document it and throw an exception so that user 
> is aware about the issue.



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

[jira] [Assigned] (IGNITE-2030) ignite.bat file does not work when JAVA_HOME contains parethensis

[Vladimir Ershov (JIRA)]

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

Vladimir Ershov reassigned IGNITE-2030:
---

Assignee: Sergey Kozlov  (was: Semen Boikov)

Fixed and checked. PR merged by Semen. Please, tes.

> ignite.bat file does not work when JAVA_HOME contains parethensis
> -
>
> Key: IGNITE-2030
> URL: https://issues.apache.org/jira/browse/IGNITE-2030
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Sergey Kozlov
> Fix For: 1.5
>
>
> When starting ignite.bat with a folder which contains parenthesis, the 
> launcher will fail:
> For example, JAVA_HOME=C:\Program Files (x86)\jdk1.7.0_76\
> Program Files (x86)
> Error (happens @ parseargs.bat script): 
> \Java\jre1.8.0_25\bin\java.exe" -cp 
> C:\ignite\gridgain-enterprise-fabric-7.5.0\g
> ridgain-enterprise-fabric-7.5.0\libs\*;C:\ignite\gridgain-enterprise-fabric-7.5.
> 0\gridgain-enterprise-fabric-7.5.0\libs\ignite-indexing\*;C:\ignite\gridgain-ent
> erprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\ignite-spring\*;C:\ig
> nite\gridgain-enterprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\lice
> nses\* org.apache.ignite.startup.cmdline.CommandLineTransformer "`) was 
> unexpect
> ed at this time.



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

[jira] [Commented] (IGNITE-2059) CPP: Implement basic support of the params for the ODBC driver.

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-2059:
-

Merged to parent development branch.

> CPP: Implement basic support of the params for the ODBC driver.
> ---
>
> Key: IGNITE-2059
> URL: https://issues.apache.org/jira/browse/IGNITE-2059
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> We need to provide basic API for parameters binding.
> Here is the list of functions that need to be supported:
> - {{SQLBindParameter}}
> - {{SQLNumParams}}



--
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=15048599#comment-15048599
 ] 

Andrey Gura commented on IGNITE-2080:
-

See my reply to Vladimnir below.

Javadoc fixed. PR updated.

> 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.5
>
> 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  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(Lorg/apache/ignite/internal/processors/affinity/Affinit
> yTopologyVersion;)V+595
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology()V+253
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map()V+60
> j  
> 

[jira] [Created] (IGNITE-2116) ignite-osgi-karaf has only readme and license files

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-2116:
-

 Summary: ignite-osgi-karaf has only readme and license files
 Key: IGNITE-2116
 URL: https://issues.apache.org/jira/browse/IGNITE-2116
 Project: Ignite
  Issue Type: Bug
  Components: build
Affects Versions: 1.5
Reporter: Sergey Kozlov
Assignee: Yakov Zhdanov
Priority: Critical
 Fix For: 1.5


{noformat}
C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
...
08.12.2015  12:34  .
08.12.2015  12:34  ..
08.12.2015  12:34  licenses
08.12.2015  12:34   735 README.txt
...
C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir 
licenses
...
08.12.2015  12:34  .
08.12.2015  12:34  ..
08.12.2015  12:3411 358 apache-2.0.txt
08.12.2015  12:34   289 ignite-osgi-karaf-licenses.txt
...
{noformat}



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

[jira] [Created] (IGNITE-2118) CacheBinaryAutoStore Example output depend on number of runs

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-2118:
-

 Summary: CacheBinaryAutoStore Example output depend on number of 
runs
 Key: IGNITE-2118
 URL: https://issues.apache.org/jira/browse/IGNITE-2118
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.5
Reporter: Sergey Kozlov
Assignee: Yakov Zhdanov
 Fix For: 1.5


1. Start H2 server
2. Start ignite node
3. Start CacheBinaryAutoStore a few times. Each time "Loaded cache entries" 
incremented by one.

{noformat}
>>> Cache auto store example started.
Read value: null
Overwrote old value: null
Read value: Person [firstName=Isaac, lastName=Newton, id=5980051555829975513, 
orgId=null, resume=null, salary=0.0]
Read value after commit: Person [firstName=Isaac, lastName=Newton, 
id=5980051555829975513, orgId=null, resume=null, salary=0.0]
>>> --
>>> Load data to cache from DB with custom SQL...
Loaded cache entries: 3
>>> Load ALL data to cache from DB...
Loaded cache entries: 7
{noformat}

{noformat}

>>> Cache auto store example started.
Read value: null
Overwrote old value: null
Read value: Person [firstName=Isaac, lastName=Newton, id=5677607654468819582, 
orgId=null, resume=null, salary=0.0]
Read value after commit: Person [firstName=Isaac, lastName=Newton, 
id=5677607654468819582, orgId=null, resume=null, salary=0.0]
>>> --
>>> Load data to cache from DB with custom SQL...
Loaded cache entries: 3
>>> Load ALL data to cache from DB...
Loaded cache entries: 8
{noformat}

{noformat}
>>> Cache auto store example started.
Read value: null
Overwrote old value: null
Read value: Person [firstName=Isaac, lastName=Newton, id=5702655301354862064, 
orgId=null, resume=null, salary=0.0]
Read value after commit: Person [firstName=Isaac, lastName=Newton, 
id=5702655301354862064, orgId=null, resume=null, salary=0.0]
>>> --
>>> Load data to cache from DB with custom SQL...
Loaded cache entries: 3
>>> Load ALL data to cache from DB...
Loaded cache entries: 9
{noformat}





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

[jira] [Assigned] (IGNITE-2022) CPP: Add local tests for ODBC driver.

[Igor Sapego (JIRA)]

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

Igor Sapego reassigned IGNITE-2022:
---

Assignee: Igor Sapego  (was: Vladimir Ozerov)

> CPP: Add local tests for ODBC driver.
> -
>
> Key: IGNITE-2022
> URL: https://issues.apache.org/jira/browse/IGNITE-2022
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> Need to add tests for the components that can be tested locally, without 
> establishing connection to a node. Here is the list of such a components:
> 1. Configuration.
> 2. ConnectionInfo.
> 3. Parser.
> 5. ApplicationDataBuffer.
> 4. Row.
> 6. Cursor.
> 7. Utility.



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

[jira] [Assigned] (IGNITE-2021) CPP: Create test project for ODBC driver.

[Igor Sapego (JIRA)]

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

Igor Sapego reassigned IGNITE-2021:
---

Assignee: Igor Sapego  (was: Vladimir Ozerov)

> CPP: Create test project for ODBC driver.
> -
>
> Key: IGNITE-2021
> URL: https://issues.apache.org/jira/browse/IGNITE-2021
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> Need to implement tests sub-project for ODBC driver.



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

[jira] [Created] (IGNITE-2115) Improve "peerClassLoadingEnabled=true" handling in Hadoop module.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2115:
---

 Summary: Improve "peerClassLoadingEnabled=true" handling in Hadoop 
module.
 Key: IGNITE-2115
 URL: https://issues.apache.org/jira/browse/IGNITE-2115
 Project: Ignite
  Issue Type: Task
  Components: hadoop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
 Fix For: 1.6


We have very subtle logic for Hadoop module loading. Even if it is in 
classpath, if "peerClassloadingEnabledFlag" is set, module is not loaded. No 
warning or errors appear. 

We should:
1) Print warning if this flag prevents loading of Hadoop module;
2) Remove "peerClassLoadingEnabled=true" from IGFS example.



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

[jira] [Comment Edited] (IGNITE-2030) ignite.bat file does not work when JAVA_HOME contains parethensis

[Vladimir Ershov (JIRA)]

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

Vladimir Ershov edited comment on IGNITE-2030 at 12/9/15 12:11 PM:
---

Fixed and checked. PR merged by Semen. Please, test.


was (Author: vershov):
Fixed and checked. PR merged by Semen. Please, tes.

> ignite.bat file does not work when JAVA_HOME contains parethensis
> -
>
> Key: IGNITE-2030
> URL: https://issues.apache.org/jira/browse/IGNITE-2030
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Sergey Kozlov
> Fix For: 1.5
>
>
> When starting ignite.bat with a folder which contains parenthesis, the 
> launcher will fail:
> For example, JAVA_HOME=C:\Program Files (x86)\jdk1.7.0_76\
> Program Files (x86)
> Error (happens @ parseargs.bat script): 
> \Java\jre1.8.0_25\bin\java.exe" -cp 
> C:\ignite\gridgain-enterprise-fabric-7.5.0\g
> ridgain-enterprise-fabric-7.5.0\libs\*;C:\ignite\gridgain-enterprise-fabric-7.5.
> 0\gridgain-enterprise-fabric-7.5.0\libs\ignite-indexing\*;C:\ignite\gridgain-ent
> erprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\ignite-spring\*;C:\ig
> nite\gridgain-enterprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\lice
> nses\* org.apache.ignite.startup.cmdline.CommandLineTransformer "`) was 
> unexpect
> ed at this time.



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

[jira] [Assigned] (IGNITE-2108) CacheJdbcPojoStoreFactory is not fully initialized when deserialized on a remote node

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-2108:


Assignee: Alexey Kuznetsov

> CacheJdbcPojoStoreFactory is not fully initialized when deserialized on a 
> remote node
> -
>
> Key: IGNITE-2108
> URL: https://issues.apache.org/jira/browse/IGNITE-2108
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Denis Magda
>Assignee: Alexey Kuznetsov
>Priority: Blocker
> Fix For: 1.5
>
>
> When a cache is started dynamically and has an implementation of 
> {{CacheJdbcPojoStoreFactory}} in its configuration then the cache startup 
> procedure will fail on a remote node with the following exception:
> {noformat}
> [16:14:10,014][ERROR][exchange-worker-#49%null%][GridDhtPartitionsExchangeFuture]
>  Failed to reinitialize local partitions (preloading will be stopped): 
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=2, 
> minorTopVer=1], nodeId=a7a1f89a, evt=DISCOVERY_CUSTOM_EVT]
> class org.apache.ignite.IgniteCheckedException: Failed to start component: 
> class org.apache.ignite.IgniteException: Failed to initialize cache store 
> (data source is not provided).
>   at 
> org.apache.ignite.internal.util.IgniteUtils.startLifecycleAware(IgniteUtils.java:8385)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCache(GridCacheProcessor.java:1251)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1620)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCachesStart(GridCacheProcessor.java:1545)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.startCaches(GridDhtPartitionsExchangeFuture.java:944)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:511)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1297)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteException: Failed to initialize 
> cache store (data source is not provided).
>   at 
> org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore.start(CacheAbstractJdbcStore.java:297)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.startLifecycleAware(IgniteUtils.java:8381)
>   ... 8 more
> {noformat}
> The reason is that in version 1.5 {{CacheJdbcPojoStoreFactory}} was reworked 
> significantly and presently it has field {{private transient DataSource 
> dataSrc}} that must be initiated somehow after deserialization.
> The issue is easily to reproduce with schema-import example:
> 1) complete all the steps described in the demo tutorial
> https://apacheignite.readme.io/docs/automatic-persistence#example
> 2) Start a remote node using {{DemoNode}}
> 3) Start {{Demo}}
> 4) The node started with {{DemoNode}} won't be able to start a cache because 
> of the issue with the storage described above



--
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

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-2080:
-

I see several problems with this implementation.
1) Big endianees are handled incorrectly. 

2) Some suspicious places in PR. E.g. 
- PlatformMemoryUtils,
- "puts" in PortableOffheapOutputStream,
etc.

These errors are very subtle and hard to find until another crash is reported 
by user. Can we get rid of paired "aligned"/"not aligned" methods and always 
use aligned variants? Something like this:

{code}
void putShort(@Nullable Object obj, long offset, short val) {
if (ALIGNED) {
if (LITTLE_ENDIAN) {
UNSAFE.putByte(obj, offset, val & 0xFF);
UNSAFE.putByte(obj, offset + 1, (val >> 8) & 0xFF);
}
else {
UNSAFE.putByte(obj, offset, (val >> 8) & 0xFF);
UNSAFE.putByte(obj, offset + 1, val & 0xFF);
}
}
else
UNSAFE.putShort(obj, offset, val);
}
{code}
With this approach there will be no way to make any mistake.

3) "Volatile" access are not protected with the same logic.

> 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
> Fix For: 1.5
>
> 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  
> 

[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=15048647#comment-15048647
 ] 

Andrey Gura commented on IGNITE-2080:
-

1) All methods of {{GridUnsafe}} use bigendian byte order. Client code is 
reposonsible for correct endianness handling. 

2) Of course, we can always uses aligned aware methods. But why we need do it 
in cases where we sure that pointer/offset already aligned?

3) I can be wrong but volatile access always requires aligned access. 

> 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
> Fix For: 1.5
>
> 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  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(Lorg/apache/ignite/internal/processors/affinity/Affinit
> yTopologyVersion;)V+595
> j  
> 

[jira] [Updated] (IGNITE-2111) .Net: Create a build script

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2111:
---
Description: 
* Create a build script (batch file) to produce x86/x64 binaries
* Change examples reference paths to use produced binaries (to simplify example 
running)
* Add doxygen documentation template


  was:
* Create a build script (batch file) to easily produce x86/x64 debug/release 
binaries
* Change examples reference paths to use produced binaries (to simplify example 
running)
* Add a Maven step to generate Doxygen documentation



> .Net: Create a build script
> ---
>
> Key: IGNITE-2111
> URL: https://issues.apache.org/jira/browse/IGNITE-2111
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 1.5
>
>
> * Create a build script (batch file) to produce x86/x64 binaries
> * Change examples reference paths to use produced binaries (to simplify 
> example running)
> * Add doxygen documentation template



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

[jira] [Assigned] (IGNITE-2111) .Net: Create a build script

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-2111:
---

Assignee: Vladimir Ozerov  (was: Pavel Tupitsyn)

> .Net: Create a build script
> ---
>
> Key: IGNITE-2111
> URL: https://issues.apache.org/jira/browse/IGNITE-2111
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Vladimir Ozerov
> Fix For: 1.5
>
>
> * Create a build script (batch file) to produce x86/x64 binaries
> * Change examples reference paths to use produced binaries (to simplify 
> example running)
> * Add doxygen documentation template



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

[jira] [Created] (IGNITE-2117) Javadoc: osgi packages have no description

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-2117:
-

 Summary: Javadoc: osgi packages have no description
 Key: IGNITE-2117
 URL: https://issues.apache.org/jira/browse/IGNITE-2117
 Project: Ignite
  Issue Type: Bug
  Components: documentation
Affects Versions: 1.5
Reporter: Sergey Kozlov
Assignee: Yakov Zhdanov
 Fix For: 1.5


Take a look on summary-overview.hml. following packages have no description:
org.apache.ignite.osgi   
org.apache.ignite.osgi.classloaders



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

[jira] [Resolved] (IGNITE-2111) .Net: Create a build script

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-2111.
-
Resolution: Fixed

> .Net: Create a build script
> ---
>
> Key: IGNITE-2111
> URL: https://issues.apache.org/jira/browse/IGNITE-2111
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Vladimir Ozerov
> Fix For: 1.5
>
>
> * Create a build script (batch file) to produce x86/x64 binaries
> * Change examples reference paths to use produced binaries (to simplify 
> example running)
> * Add doxygen documentation template



--
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=15048674#comment-15048674
 ] 

Andrey Gura commented on IGNITE-2080:
-

1) Need use native byte order in {{GridUnsafe}}

2) Current implementation is ok. But should be used carefully.

3) Need use alignment memory access in order to avoid failures.

> 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
> Fix For: 1.5
>
> 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  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(Lorg/apache/ignite/internal/processors/affinity/Affinit
> yTopologyVersion;)V+595
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology()V+253
> j  
> 

[jira] [Updated] (IGNITE-2118) CacheBinaryAutoStore Example output depends on number of runs

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov updated IGNITE-2118:
--
Summary: CacheBinaryAutoStore Example output depends on number of runs  
(was: CacheBinaryAutoStore Example output depend on number of runs)

> CacheBinaryAutoStore Example output depends on number of runs
> -
>
> Key: IGNITE-2118
> URL: https://issues.apache.org/jira/browse/IGNITE-2118
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Yakov Zhdanov
> Fix For: 1.5
>
>
> 1. Start H2 server
> 2. Start ignite node
> 3. Start CacheBinaryAutoStore a few times. Each time "Loaded cache entries" 
> incremented by one.
> {noformat}
> >>> Cache auto store example started.
> Read value: null
> Overwrote old value: null
> Read value: Person [firstName=Isaac, lastName=Newton, id=5980051555829975513, 
> orgId=null, resume=null, salary=0.0]
> Read value after commit: Person [firstName=Isaac, lastName=Newton, 
> id=5980051555829975513, orgId=null, resume=null, salary=0.0]
> >>> --
> >>> Load data to cache from DB with custom SQL...
> Loaded cache entries: 3
> >>> Load ALL data to cache from DB...
> Loaded cache entries: 7
> {noformat}
> {noformat}
> >>> Cache auto store example started.
> Read value: null
> Overwrote old value: null
> Read value: Person [firstName=Isaac, lastName=Newton, id=5677607654468819582, 
> orgId=null, resume=null, salary=0.0]
> Read value after commit: Person [firstName=Isaac, lastName=Newton, 
> id=5677607654468819582, orgId=null, resume=null, salary=0.0]
> >>> --
> >>> Load data to cache from DB with custom SQL...
> Loaded cache entries: 3
> >>> Load ALL data to cache from DB...
> Loaded cache entries: 8
> {noformat}
> {noformat}
> >>> Cache auto store example started.
> Read value: null
> Overwrote old value: null
> Read value: Person [firstName=Isaac, lastName=Newton, id=5702655301354862064, 
> orgId=null, resume=null, salary=0.0]
> Read value after commit: Person [firstName=Isaac, lastName=Newton, 
> id=5702655301354862064, orgId=null, resume=null, salary=0.0]
> >>> --
> >>> Load data to cache from DB with custom SQL...
> Loaded cache entries: 3
> >>> Load ALL data to cache from DB...
> Loaded cache entries: 9
> {noformat}



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

[jira] [Created] (IGNITE-2122) .NET: Add generic Read/WriteCollection and Read/WriteDictionary methods.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2122:
---

 Summary: .NET: Add generic Read/WriteCollection and 
Read/WriteDictionary methods.
 Key: IGNITE-2122
 URL: https://issues.apache.org/jira/browse/IGNITE-2122
 Project: Ignite
  Issue Type: Task
  Components: general, interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: 1.5






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

[jira] [Commented] (IGNITE-1789) Data Snapshots for Ignite caches

[Michael Griggs (JIRA)]

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

Michael Griggs commented on IGNITE-1789:


For my use-case, I would prefer to have the option to copy all in-memory 
objects and give them new keys that have the snapshot name added in some way, 
but remain in the same cache.  So for example, Country:GB would get snapshotted 
and copied to Country:GB:snapshot1.0, and both Country:GB and 
Country:GB:snapshot1.0 would be stored in memory.

> Data Snapshots for Ignite caches
> 
>
> Key: IGNITE-1789
> URL: https://issues.apache.org/jira/browse/IGNITE-1789
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Reporter: Raúl Kripalani
>
> There was a discussion in the dev forum about Data Snapshots in Ignite as a 
> way to obtain a consistent and "frozen" view of one or multiple caches in 
> order to execute a set of SQL queries, distributed closures, map reduce, etc. 
> without having to worry about data slippage (or moving data).
> The discussion is here: 
> http://apache-ignite-developers.2346864.n4.nabble.com/Data-Snapshots-in-Ignite-td4183.html
>  and we still need to mature the idea, but several users chimed in and 
> considered it interesting.



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

[jira] [Updated] (IGNITE-2119) Tasks can get stuck in case of communication error

[Avihai Berkovitz (JIRA)]

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

Avihai Berkovitz updated IGNITE-2119:
-
Attachment: worker2stacks.txt

> Tasks can get stuck in case of communication error
> --
>
> Key: IGNITE-2119
> URL: https://issues.apache.org/jira/browse/IGNITE-2119
> 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
> Attachments: worker2stacks.txt
>
>
> After running a cluster of 20 nodes for a couple of hours under heavy load 
> (hundreds of tasks per minute) we have a problem with one of the nodes. The 
> public thread pool is completely full, and all the threads are stuck here:
> {noformat}
>  - sun.misc.Unsafe.park(boolean, long) @bci=0 (Compiled frame; information 
> may be imprecise)
>  - java.util.concurrent.locks.LockSupport.park(java.lang.Object) @bci=14, 
> line=175 (Compiled frame)
>  - 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt() 
> @bci=1, line=836 (Compiled frame)
>  - 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(int)
>  @bci=72, line=997 (Compiled frame)
>  - 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(int)
>  @bci=24, line=1304 (Compiled frame)
>  - org.apache.ignite.internal.util.future.GridFutureAdapter.get0(boolean) 
> @bci=23, line=157 (Compiled frame)
>  - org.apache.ignite.internal.util.future.GridFutureAdapter.get() @bci=5, 
> line=115 (Compiled frame)
>  - 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(org.apache.ignite.cluster.ClusterNode)
>  @bci=413, line=2017 (Compiled frame)
>  - 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(org.apache.ignite.cluster.ClusterNode,
>  org.apache.ignite.plugin.extensions.communication.Message, 
> org.apache.ignite.lang.IgniteInClosure) @bci=185, line=1914 (Compiled frame)
>  - 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(org.apache.ignite.cluster.ClusterNode,
>  org.apache.ignite.plugin.extensions.communication.Message, 
> org.apache.ignite.lang.IgniteInClosure) @bci=4, line=1880 (Compiled frame)
>  - 
> org.apache.ignite.internal.managers.communication.GridIoManager.send(org.apache.ignite.cluster.ClusterNode,
>  java.lang.Object, int, 
> org.apache.ignite.plugin.extensions.communication.Message, byte, boolean, 
> long, boolean, org.apache.ignite.lang.IgniteInClosure) @bci=227, line=1066 
> (Compiled frame)
>  - 
> org.apache.ignite.internal.managers.communication.GridIoManager.send(org.apache.ignite.cluster.ClusterNode,
>  org.apache.ignite.internal.GridTopic, 
> org.apache.ignite.plugin.extensions.communication.Message, byte) @bci=14, 
> line=1214 (Compiled frame)
>  - 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(org.apache.ignite.cluster.ClusterNode,
>  org.apache.ignite.internal.processors.cache.GridCacheMessage, byte) 
> @bci=123, line=652 (Compiled frame)
>  - 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(java.util.UUID,
>  org.apache.ignite.internal.processors.cache.GridCacheMessage, byte) @bci=64, 
> line=801 (Compiled frame)
>  - 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapSingle(java.util.UUID,
>  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateRequest)
>  @bci=108, line=474 (Compiled frame)
>  - 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$1200(org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture,
>  java.util.UUID, 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateRequest)
>  @bci=3, line=73 (Compiled frame)
>  - 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion)
>  @bci=560, line=880 (Compiled frame)
>  - 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology()
>  @bci=253, line=422 (Compiled frame)
>  - 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map()
>  @bci=60, line=291 (Compiled frame)
>  - 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$14.apply()
>  @bci=4, line=844 (Compiled frame)
>  - 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$14.apply()
>  

[jira] [Commented] (IGNITE-1864) Cannot configure jndiNames for CacheJndiTmLookup

[Artem Shutak (JIRA)]

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

Artem Shutak commented on IGNITE-1864:
--

Documentation updated: 
http://apacheignite.gridgain.org/v1.5/docs/transactions#integration-with-jta.

> Cannot configure jndiNames for CacheJndiTmLookup 
> -
>
> Key: IGNITE-1864
> URL: https://issues.apache.org/jira/browse/IGNITE-1864
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Yakov Zhdanov
>Assignee: Artem Shutak
>Priority: Critical
> Fix For: 1.5
>
>
> Since user have an ability to configure only lookup class name via 
> org.apache.ignite.configuration.TransactionConfiguration#getTxManagerLookupClassName,
>  he lacks ability to properly configure all of its properties.
> This seems to be a general problem for this approach



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

[jira] [Created] (IGNITE-2121) .NET: Port correct collections handling logic.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2121:
---

 Summary: .NET: Port correct collections handling logic.
 Key: IGNITE-2121
 URL: https://issues.apache.org/jira/browse/IGNITE-2121
 Project: Ignite
  Issue Type: Sub-task
  Components: interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: 1.5






--
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=15048722#comment-15048722
 ] 

Andrey Gura commented on IGNITE-2080:
-

PR updated.

> 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
> Fix For: 1.5
>
> 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  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(Lorg/apache/ignite/internal/processors/affinity/Affinit
> yTopologyVersion;)V+595
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology()V+253
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map()V+60
> j  
> 

[jira] [Created] (IGNITE-2119) Tasks can get stuck in case of communication error

[Avihai Berkovitz (JIRA)]

Avihai Berkovitz created IGNITE-2119:


 Summary: Tasks can get stuck in case of communication error
 Key: IGNITE-2119
 URL: https://issues.apache.org/jira/browse/IGNITE-2119
 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


After running a cluster of 20 nodes for a couple of hours under heavy load 
(hundreds of tasks per minute) we have a problem with one of the nodes. The 
public thread pool is completely full, and all the threads are stuck here:
{noformat}
 - sun.misc.Unsafe.park(boolean, long) @bci=0 (Compiled frame; information may 
be imprecise)
 - java.util.concurrent.locks.LockSupport.park(java.lang.Object) @bci=14, 
line=175 (Compiled frame)
 - 
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt() 
@bci=1, line=836 (Compiled frame)
 - 
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(int)
 @bci=72, line=997 (Compiled frame)
 - 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(int)
 @bci=24, line=1304 (Compiled frame)
 - org.apache.ignite.internal.util.future.GridFutureAdapter.get0(boolean) 
@bci=23, line=157 (Compiled frame)
 - org.apache.ignite.internal.util.future.GridFutureAdapter.get() @bci=5, 
line=115 (Compiled frame)
 - 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(org.apache.ignite.cluster.ClusterNode)
 @bci=413, line=2017 (Compiled frame)
 - 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(org.apache.ignite.cluster.ClusterNode,
 org.apache.ignite.plugin.extensions.communication.Message, 
org.apache.ignite.lang.IgniteInClosure) @bci=185, line=1914 (Compiled frame)
 - 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(org.apache.ignite.cluster.ClusterNode,
 org.apache.ignite.plugin.extensions.communication.Message, 
org.apache.ignite.lang.IgniteInClosure) @bci=4, line=1880 (Compiled frame)
 - 
org.apache.ignite.internal.managers.communication.GridIoManager.send(org.apache.ignite.cluster.ClusterNode,
 java.lang.Object, int, 
org.apache.ignite.plugin.extensions.communication.Message, byte, boolean, long, 
boolean, org.apache.ignite.lang.IgniteInClosure) @bci=227, line=1066 (Compiled 
frame)
 - 
org.apache.ignite.internal.managers.communication.GridIoManager.send(org.apache.ignite.cluster.ClusterNode,
 org.apache.ignite.internal.GridTopic, 
org.apache.ignite.plugin.extensions.communication.Message, byte) @bci=14, 
line=1214 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(org.apache.ignite.cluster.ClusterNode,
 org.apache.ignite.internal.processors.cache.GridCacheMessage, byte) @bci=123, 
line=652 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(java.util.UUID,
 org.apache.ignite.internal.processors.cache.GridCacheMessage, byte) @bci=64, 
line=801 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapSingle(java.util.UUID,
 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateRequest)
 @bci=108, line=474 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$1200(org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture,
 java.util.UUID, 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateRequest)
 @bci=3, line=73 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion)
 @bci=560, line=880 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology()
 @bci=253, line=422 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map()
 @bci=60, line=291 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$14.apply()
 @bci=4, line=844 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$14.apply()
 @bci=1, line=842 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(org.apache.ignite.internal.util.typedef.CO)
 @bci=86, line=648 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsync0(java.util.Map,
 java.util.Map, java.lang.Object[], java.util.Map, java.util.Map, 

[jira] [Created] (IGNITE-2120) Rename Binarylizable -> Binarizable

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2120:
---

 Summary: Rename Binarylizable -> Binarizable
 Key: IGNITE-2120
 URL: https://issues.apache.org/jira/browse/IGNITE-2120
 Project: Ignite
  Issue Type: Task
  Components: general, interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: 1.5






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

[jira] [Commented] (IGNITE-1433) .Net: Add IgniteException.JavaStackTrace

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-1433:


* JavaStackTrace removed from some things like ClusterTopologyException
* NPE and other Java exceptions without .NET mapping: we convert these to 
IgniteException, so the stack trace is preserved. Double-checked this with 
actual recent NPE in Services tests
* Bad classpath (class or method not found): message contains all required 
information (class/method name), no need for stack trace.

> .Net: Add IgniteException.JavaStackTrace
> 
>
> Key: IGNITE-1433
> URL: https://issues.apache.org/jira/browse/IGNITE-1433
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
> Fix For: 1.6
>
>
> Propagate java stack trace as a string in ExceptionUtils.GetException and 
> write it to a new field in IgniteException class.
> This will simplify debugging for us both locally and when getting error 
> reports from clients.



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

[jira] [Commented] (IGNITE-1993) JDBC discovery uses non-standard SQL when creating table (not compatible with Oracle)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-1993:


GitHub user westbury opened a pull request:

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

IGNITE-1993 remove non-standard SQL clause so table for JDBC discovery…

Note that the tests do not run locally.  They fail because portable/test1 
and portable/test2 are not available (see IGNITE-1462).  However I note that 
the instructions at 
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute instruct 
to use -DskipTests so I did that.

This pull request supercedes the patch as per Denis Magda's comment.

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

$ git pull https://github.com/westbury/ignite ignite-1993

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

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


commit e8088e92e409eff80c6622cda55201c6719abe4e
Author: Nigel Westbury 
Date:   2015-12-09T14:49:36Z

IGNITE1993 remove non-standard SQL clause so table for JDBC discovery works 
in Oracle




> JDBC discovery uses non-standard SQL when creating table (not compatible with 
> Oracle)
> -
>
> Key: IGNITE-1993
> URL: https://issues.apache.org/jira/browse/IGNITE-1993
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: ignite-1.4
> Environment: Oracle database
>Reporter: Nigel Westbury
>  Labels: easyfix, patch
> Fix For: 1.4
>
> Attachments: IGNITE1993.patch
>
>
> The SQL used by TcpDiscoveryJdbcIpFinder to create the table (defined by 
> CREATE_ADDRS_TABLE_QRY) uses 'if not exists' clause.  However this clause is 
> not supported by Oracle and causes SQLSyntaxErrorException: "ORA-00922: 
> missing or invalid option" to be thrown.  This prevents JDBC discovery from 
> being used with an Oracle database.



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

[jira] [Created] (IGNITE-2123) Need to add EntryProcessorExample to cache examples

[Yakov Zhdanov (JIRA)]

Yakov Zhdanov created IGNITE-2123:
-

 Summary: Need to add EntryProcessorExample to cache examples
 Key: IGNITE-2123
 URL: https://issues.apache.org/jira/browse/IGNITE-2123
 Project: Ignite
  Issue Type: Task
Reporter: Yakov Zhdanov


One can take {{CacheAffinityExample}} as an example.

# call entry processors in a loop, if entry is null then create it in entry 
processor
# do gets in a loop and show that entries are in cache
# call entry processors in a loop and modify existing entries
# do gets in a loop and show the results of modification



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

[jira] [Commented] (IGNITE-2012) Add support for ConcurrentLinkedQueue type in .NET/C++

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2012:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-2012 Add support for ConcurrentLinkedQueue type in .NET/C++



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

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

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

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


commit b9f14ad2f173677d430b293224a3785d68b4458c
Author: Pavel Tupitsyn 
Date:   2015-12-09T16:23:35Z

IGNITE-2012 Add support for ConcurrentLinkedQueue type in .NET/C++




> Add support for ConcurrentLinkedQueue type in .NET/C++
> --
>
> Key: IGNITE-2012
> URL: https://issues.apache.org/jira/browse/IGNITE-2012
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Alexey Goncharuk
>Assignee: Pavel Tupitsyn
> Fix For: 1.6
>
>
> I added support for a new collection type ConcurrentLinkedQueue in portable 
> context to enable run of continuous mapper example.
> Need to add support of this collection type to other platforms.



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

[jira] [Closed] (IGNITE-10) Fix ignite components [de]serialization

[Vladimir Ershov (JIRA)]

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

Vladimir Ershov closed IGNITE-10.
-

> Fix ignite components [de]serialization
> ---
>
> Key: IGNITE-10
> URL: https://issues.apache.org/jira/browse/IGNITE-10
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Yakov Zhdanov
>Assignee: Vladimir Ershov
>  Labels: Muted_test
> Fix For: 1.6
>
>
> Current solution: serialize grid name, then find comp by name on peer.
> Current solution not working: in our internal unit tests, in distributed 
> topology when user gives different names to nodes 
> New solution: each grid thread should know its node. So, on deserialization 
> we cast thread to e.g. IgniteThread and take its holding component from it. 
> If it is not IgniteThread then exception should be thrown since it is anyway 
> impossible to deserialize component outside of context.
> Suggestion from IGNITE-553:
> As we moving to java8 lambdas, it is impossible to use 
> @IgniteInstanceResource in lambdas. As a result, single-jvm ping-pong test 
> does not work.
> Suggested fix:
> Introduce a static thread-local field which will be set before processing a 
> message and will be nullified after message is processed. IgniteKernal should 
> check this thread-local in readResolve and return this instance.



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

[jira] [Resolved] (IGNITE-10) Fix ignite components [de]serialization

[Vladimir Ershov (JIRA)]

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

Vladimir Ershov resolved IGNITE-10.
---
Resolution: Fixed
  Assignee: Vladimir Ershov  (was: Yakov Zhdanov)

Fix implemented through readResolve and ThreadIgnite holds gridName. New method 
Ignition.localIgnite() introduced. JD fixed, review and TC is ok.

> Fix ignite components [de]serialization
> ---
>
> Key: IGNITE-10
> URL: https://issues.apache.org/jira/browse/IGNITE-10
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Yakov Zhdanov
>Assignee: Vladimir Ershov
>  Labels: Muted_test
> Fix For: 1.6
>
>
> Current solution: serialize grid name, then find comp by name on peer.
> Current solution not working: in our internal unit tests, in distributed 
> topology when user gives different names to nodes 
> New solution: each grid thread should know its node. So, on deserialization 
> we cast thread to e.g. IgniteThread and take its holding component from it. 
> If it is not IgniteThread then exception should be thrown since it is anyway 
> impossible to deserialize component outside of context.
> Suggestion from IGNITE-553:
> As we moving to java8 lambdas, it is impossible to use 
> @IgniteInstanceResource in lambdas. As a result, single-jvm ping-pong test 
> does not work.
> Suggested fix:
> Introduce a static thread-local field which will be set before processing a 
> message and will be nullified after message is processed. IgniteKernal should 
> check this thread-local in readResolve and return this instance.



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

[jira] [Commented] (IGNITE-2124) Deserialization of a BinaryObject key on a remote node

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-2124:
-

Tested using the latest sources from 1.5 branch.

> Deserialization of a BinaryObject key on a remote node
> --
>
> Key: IGNITE-2124
> URL: https://issues.apache.org/jira/browse/IGNITE-2124
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
> Environment: Windows 7
>Reporter: Denis Magda
>Priority: Blocker
> Fix For: 1.5
>
>
> BinaryObject key gets deserialized on a remote node. In my understanding this 
> mustn't happen when {{BinaryMarshaller}} is enabled.
> Steps to reproduce:
> - start a remote node using ignite.bat/sh;
> - launch {{CacheClientBinaryQueryExample}};
> The example will fail with the following stack trace:
> {noformat}
> Exception in thread "main" 
> org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys 
> (retry update if possible).: [EmployeeKey [id=4, organizationId=2]]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1620)
>   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.binary.datagrid.CacheClientBinaryQueryExample.populateCache(CacheClientBinaryQueryExample.java:301)
>   at 
> org.apache.ignite.examples.binary.datagrid.CacheClientBinaryQueryExample.main(CacheClientBinaryQueryExample.java:98)
>   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.internal.processors.cache.CachePartialUpdateCheckedException:
>  Failed to update keys (retry update if possible).: [EmployeeKey [id=4, 
> organizationId=2]]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.addFailedKeys(GridNearAtomicUpdateFuture.java:1189)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.onResult(GridNearAtomicUpdateFuture.java:658)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.onResult(GridNearAtomicUpdateFuture.java:352)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateResponse(GridDhtAtomicCache.java:2617)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$700(GridDhtAtomicCache.java:127)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:262)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:260)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:579)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:277)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:201)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:80)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:163)
>   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)
>   Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to 
> update keys on primary node.
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKeys(GridNearAtomicUpdateResponse.java:368)
>   at 
> 

[jira] [Created] (IGNITE-2124) Deserialization of a BinaryObject key on a remote node

[Denis Magda (JIRA)]

Denis Magda created IGNITE-2124:
---

 Summary: Deserialization of a BinaryObject key on a remote node
 Key: IGNITE-2124
 URL: https://issues.apache.org/jira/browse/IGNITE-2124
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.5
 Environment: Windows 7
Reporter: Denis Magda
Priority: Blocker
 Fix For: 1.5


BinaryObject key gets deserialized on a remote node. In my understanding this 
mustn't happen when {{BinaryMarshaller}} is enabled.

Steps to reproduce:
- start a remote node using ignite.bat/sh;
- launch {{CacheClientBinaryQueryExample}};

The example will fail with the following stack trace:

{noformat}
Exception in thread "main" org.apache.ignite.cache.CachePartialUpdateException: 
Failed to update keys (retry update if possible).: [EmployeeKey [id=4, 
organizationId=2]]
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1620)
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.binary.datagrid.CacheClientBinaryQueryExample.populateCache(CacheClientBinaryQueryExample.java:301)
at 
org.apache.ignite.examples.binary.datagrid.CacheClientBinaryQueryExample.main(CacheClientBinaryQueryExample.java:98)
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.internal.processors.cache.CachePartialUpdateCheckedException: 
Failed to update keys (retry update if possible).: [EmployeeKey [id=4, 
organizationId=2]]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.addFailedKeys(GridNearAtomicUpdateFuture.java:1189)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.onResult(GridNearAtomicUpdateFuture.java:658)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.onResult(GridNearAtomicUpdateFuture.java:352)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateResponse(GridDhtAtomicCache.java:2617)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$700(GridDhtAtomicCache.java:127)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:262)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:260)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:579)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:277)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:201)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:80)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:163)
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)
Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to 
update keys on primary node.
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKeys(GridNearAtomicUpdateResponse.java:368)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1384)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1193)
at 

[jira] [Closed] (IGNITE-2031) Add the possibility to adress local ignite instance inside lambda.

[Vladimir Ershov (JIRA)]

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

Vladimir Ershov closed IGNITE-2031.
---

> Add the possibility to adress local ignite instance inside lambda.
> --
>
> Key: IGNITE-2031
> URL: https://issues.apache.org/jira/browse/IGNITE-2031
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 1.6
>Reporter: Vladimir Ershov
>Assignee: Vladimir Ershov
>Priority: Minor
>  Labels: newbie
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Ignition.currentIgnite method is needed for case, when there is no Ignite 
> instance available around the closure. 
> So, this ticket is aimed to support syntax like this:
> {code:java}
> cfg.setLifecycleBeans((LifecycleEventType evt)  -> {
> if (evt == LifecycleEventType.AFTER_NODE_START) {
> log.info("Load cache: " + 
> Ignition.currentIgnite().name());
> Ignition.currentIgnite().cache(null).loadCache(null, 0);
> log.info("Cache loaded: " + 
> Ignition.currentIgnite().name());
> }
> });
> {code}
> Plus tests.



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

[jira] [Commented] (IGNITE-2094) building the project with 'install' crashes on Mesos module

[Konstantin Boudnik (JIRA)]

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

Konstantin Boudnik commented on IGNITE-2094:


I have exactly the same result on the clean m2. Which is actually irrelevant, 
because the failure happens _before_ it gets to the point of installing 
anything. 
I know from another user, that the build fails similarly on different modules 
sometimes. 

It seems though, that's the problem is in the combination of {{package 
install}} targets. If either is specified alone - everything works fine. Two 
together is not go. That evidently a build issue, but is a minor one, because I 
can simply skip {{package}} part and be done with it. Please feel free to close 
the ticket as "Won't Fix" if no one feels like working on it ;) Thanks!

> building the project with 'install' crashes on Mesos module
> ---
>
> Key: IGNITE-2094
> URL: https://issues.apache.org/jira/browse/IGNITE-2094
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Affects Versions: 1.5
>Reporter: Konstantin Boudnik
>Assignee: Anton Vinogradov
> Fix For: 1.5
>
>
> Attempting to do {{mvn install...}} on the latest {{-b1}} release and the 
> build crashed on the Mesos module.



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

[jira] [Updated] (IGNITE-1666) Fallback for full scan query does not work

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-1666:
-
Fix Version/s: (was: 1.5)
   1.6

> Fallback for full scan query does not work
> --
>
> Key: IGNITE-1666
> URL: https://issues.apache.org/jira/browse/IGNITE-1666
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 1.6
>
>
> Fallback for full scan query doesn't work.
> Steps to reproduce (all in one thread):
> 1. Start N nodes, create cache and populate some entries to cache.
> 2. Stop some node.
> 3. Get iterator on the cache and fetch all entries one by one.
> 4. Repeat from step 2.
> On some iteration scan query fails with exception: 
> {noformat}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
> Query execution failed: GridCacheQueryBean [qry=GridCacheQueryAdapter 
> [type=SCAN, clsName=null, clause=null, filter=null, 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=false, incBackups=false, dedup=false, prj=null, keepPortable=false, 
> subjId=3026635f-2a79-4a59-83cb-9db427f45003, taskHash=0], rdc=null, 
> trans=null]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1614)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:181)
>   at 
> org.apache.ignite.internal.processors.cache.CacheWeakQueryIteratorsHolder$WeakQueryFutureIterator.init(CacheWeakQueryIteratorsHolder.java:228)
>   at 
> org.apache.ignite.internal.processors.cache.CacheWeakQueryIteratorsHolder$WeakQueryFutureIterator.onHasNext(CacheWeakQueryIteratorsHolder.java:180)
>   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.internal.processors.cache.distributed.CacheIteratorWhileRemovalSelfTest.doTest(CacheIteratorWhileRemovalSelfTest.java:135)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.CacheIteratorWhileRemovalSelfTest.testFullScanIterator(CacheIteratorWhileRemovalSelfTest.java:91)
>   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 junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1658)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:112)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1596)
> Caused by: class org.apache.ignite.IgniteCheckedException: Query execution 
> failed: GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN, 
> clsName=null, clause=null, filter=null, 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=false, incBackups=false, dedup=false, prj=null, keepPortable=false, 
> subjId=3026635f-2a79-4a59-83cb-9db427f45003, 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:276)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:171)
>   ... 14 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=null, 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=false, incBackups=false, dedup=false, prj=null, keepPortable=false, 
> subjId=3026635f-2a79-4a59-83cb-9db427f45003, taskHash=0], rdc=null, 
> trans=null], nodeId=203d0a36-8587-4a32-aa51-3332d126d002]
>   at 
> 

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

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-1149:
-
Fix Version/s: (was: 1.5)
   1.6

> Failed to send time request to remote node
> --
>
> Key: IGNITE-1149
> URL: https://issues.apache.org/jira/browse/IGNITE-1149
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-8
> Environment: jdk 1.7
> host - OS X 10.10.3
> vm - ubuntu 14.04
>Reporter: Ilya Suntsov
>Assignee: Nikolay Tikhonov
> Fix For: 1.6
>
> Attachments: node01vm.log, node02host.txt
>
>
> Steps for reproduce:
> 1. Start two nodes with examle-ignite.xml config on different hosts in 
> verbose mode
> Result:
> The following message in log of one of nodes:
> {noformat}
> 
> [16:19:01,155][WARNING][grid-time-coordinator-#49%null%][GridClockSyncProcessor]
>  Failed to send time request to remote node 
> [rmtNodeId=1b25492a-2d17-4557-8322-6eed54f602b6, addr=/192.168.3.18, 
> port=31100]
> [16:19:02,160][WARNING][grid-time-coordinator-#49%null%][GridClockSyncProcessor]
>  Failed to send time request to remote node 
> [rmtNodeId=1b25492a-2d17-4557-8322-6eed54f602b6, addr=/192.168.3.18, 
> port=31100]
> [16:19:03,165][WARNING][grid-time-coordinator-#49%null%][GridClockSyncProcessor]
>  Failed to send time request to remote node 
> [rmtNodeId=1b25492a-2d17-4557-8322-6eed54f602b6, addr=/192.168.3.18, 
> port=31100]
> [16:19:04,170][WARNING][grid-time-coordinator-#49%null%][GridClockSyncProcessor]
>  Failed to send time request to remote node 
> [rmtNodeId=1b25492a-2d17-4557-8322-6eed54f602b6, addr=/192.168.3.18, 
> port=31100]
> ..
> {noformat}
> Full logs in attachment.



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

[jira] [Updated] (IGNITE-842) Do full run of Ignite tests under open JDK.

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-842:

Fix Version/s: (was: 1.5)
   1.6

> Do full run of Ignite tests under open JDK.
> ---
>
> Key: IGNITE-842
> URL: https://issues.apache.org/jira/browse/IGNITE-842
> Project: Ignite
>  Issue Type: Task
>Reporter: Artem Shutak
>Assignee: Artem Shutak
> Fix For: 1.6
>
>
> Do full run of Ignite tests under open JDK. Configure TC for it.



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

[jira] [Updated] (IGNITE-1291) Bad link on https://ignite.incubator.apache.org

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-1291:
-
Fix Version/s: (was: 1.5)
   1.6

> Bad link on https://ignite.incubator.apache.org
> ---
>
> Key: IGNITE-1291
> URL: https://issues.apache.org/jira/browse/IGNITE-1291
> Project: Ignite
>  Issue Type: Bug
>  Components: website
>Affects Versions: ignite-1.4
>Reporter: Ilya Suntsov
>Assignee: Nikolay Tikhonov
>Priority: Critical
> Fix For: 1.6
>
>
> Bad link:
> https://storage.googleapis.com/ignite-media/ignite-google-image.tar.gz
> Appears on:
> https://ignite.incubator.apache.org/download.html



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

[jira] [Updated] (IGNITE-1202) Provide ARM template for running Ignite on Microsoft Azure infra.

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-1202:
-
Fix Version/s: (was: 1.5)
   1.6

> Provide ARM template for running Ignite on Microsoft Azure infra.
> -
>
> Key: IGNITE-1202
> URL: https://issues.apache.org/jira/browse/IGNITE-1202
> Project: Ignite
>  Issue Type: Task
>  Components: build, general
>Affects Versions: 1.1.4
>Reporter: Nikita Ivanov
>Assignee: Nikolay Tikhonov
> Fix For: 1.6
>
> Attachments: Introduction to ARM Quickstart Templates.pptx
>
>
> Basically, it would be great to have Ignite be natively runnable on Azure 
> infra. 
> It looks like all we need is a VM and an install script. If that is the case 
> then fastest way to get started ARM is through  QuickStart templates (see 
> https://github.com/azure/azure-quickstart-templates), specifically 
> https://github.com/Azure/azure-quickstart-templates/tree/master/lamp-app 
> (which uses a script to configure the machine appropriately).
>  
> Since we already have Docker container we can it them instead of shell 
> scripts.
> I'm also attaching slide deck with more information on Azure ARM. 



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

[jira] [Updated] (IGNITE-1521) Exception when running sql benchmark on AWS

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-1521:
-
Fix Version/s: (was: 1.5)
   1.6

> Exception when running sql benchmark on AWS
> ---
>
> Key: IGNITE-1521
> URL: https://issues.apache.org/jira/browse/IGNITE-1521
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: ignite-1.4
>Reporter: Ilya Suntsov
>Assignee: Nikolay Tikhonov
>Priority: Blocker
> Fix For: 1.6
>
>
> 1. I fork this repo: https://github.com/apacheignite/yardstick-ignite
> 2. Clone it
> 3. Used the following docs for start SQL benchmarks on AWS:
> https://github.com/yardstick-benchmarks/yardstick-docker
> And got the following exception:
> {noformat}
> ERROR: Shutting down benchmark driver to unexpected exception.
> Type '--help' for usage.
> java.lang.NoSuchMethodError: 
> org.apache.ignite.internal.processors.cache.query.GridCacheTwoStepQuery.(Ljava/util/Set;Ljava/lang/String;[Ljava/lang/Object;)V
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.split(GridSqlQuerySplitter.java:216)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:859)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:807)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:662)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:660)
>   at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1492)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:660)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:618)
>   at 
> org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.executeQuery(IgniteSqlQueryBenchmark.java:85)
>   at 
> org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.test(IgniteSqlQueryBenchmark.java:61)
>   at 
> org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:165)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}



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

[jira] [Updated] (IGNITE-499) Implement client communication SPI

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-499:

Fix Version/s: (was: 1.5)

> Implement client communication SPI
> --
>
> Key: IGNITE-499
> URL: https://issues.apache.org/jira/browse/IGNITE-499
> Project: Ignite
>  Issue Type: Task
>Reporter: Yakov Zhdanov
>Assignee: Nikolay Tikhonov
>Priority: Blocker
>
> Add ability to communication SPI on client node to communicate with nodes 
> through its driver node.



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

[jira] [Resolved] (IGNITE-2121) .NET: Port correct collections handling logic.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-2121.
-
Resolution: Won't Fix

> .NET: Port correct collections handling logic.
> --
>
> Key: IGNITE-2121
> URL: https://issues.apache.org/jira/browse/IGNITE-2121
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>




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

[jira] [Updated] (IGNITE-1849) cache.size() method causes three TASK_* events

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-1849:
-
Fix Version/s: (was: 1.5)
   1.6

> cache.size() method causes three TASK_* events
> --
>
> Key: IGNITE-1849
> URL: https://issues.apache.org/jira/browse/IGNITE-1849
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Artem Shutak
> Fix For: 1.6
>
>
> cache.size() causes following events:
> TASK_STARTED
> TASK_REDUCED
> TASK_FINISHED



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

[jira] [Resolved] (IGNITE-1684) NPE in GridCacheProcessor.processClientReconnectData on client left

[Semen Boikov (JIRA)]

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

Semen Boikov resolved IGNITE-1684.
--
Resolution: Fixed

> NPE in GridCacheProcessor.processClientReconnectData on client left
> ---
>
> Key: IGNITE-1684
> URL: https://issues.apache.org/jira/browse/IGNITE-1684
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>Assignee: Artem Shutak
> Fix For: 1.5
>
>
> I've got NPE on server node in next scenario:
> - 4 servers and 2 clients (on one physical machine)
> - one server node has been killed
> - 1 client "Failed to reconnect" and leave 
> {{[22:24:52,382][ERROR][tcp-client-disco-reconnector-#9%null][TcpDiscoverySpi]
>  Failed to reconnect}}
> - At the same time (see timing) got NPE (see below)
> - started one new servers, which couldn't connect to cluster (may be after 
> NPE)
> See "trans-write-invoke" logs.
> {noformat}
> [22:24:53,079][ERROR][tcp-disco-msg-worker-#2%null][TcpDiscoverySpi] Runtime 
> error caught during grid runnable execution: IgniteSpiThread 
> [name=tcp-disco-msg-worker-#2%null]
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.processClientReconnectData(GridCacheProcessor.java:2011)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onDiscoveryDataReceived(GridCacheProcessor.java:1904)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$6.onExchange(GridDiscoveryManager.java:659)
>   at 
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1706)
>   at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddedMessage(ServerImpl.java:3310)
>   at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processJoinRequestMessage(ServerImpl.java:3002)
>   at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2095)
>   at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5382)
>   at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {noformat}
> In additional, after it (left 3 server node + 1 client)
> - one more server has been killed
> - the last client said  "Failed to reconnect"
> - and another server node got the same NPE



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

[jira] [Closed] (IGNITE-1684) NPE in GridCacheProcessor.processClientReconnectData on client left

[Semen Boikov (JIRA)]

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

Semen Boikov closed IGNITE-1684.

Assignee: (was: Artem Shutak)

> NPE in GridCacheProcessor.processClientReconnectData on client left
> ---
>
> Key: IGNITE-1684
> URL: https://issues.apache.org/jira/browse/IGNITE-1684
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
> Fix For: 1.5
>
>
> I've got NPE on server node in next scenario:
> - 4 servers and 2 clients (on one physical machine)
> - one server node has been killed
> - 1 client "Failed to reconnect" and leave 
> {{[22:24:52,382][ERROR][tcp-client-disco-reconnector-#9%null][TcpDiscoverySpi]
>  Failed to reconnect}}
> - At the same time (see timing) got NPE (see below)
> - started one new servers, which couldn't connect to cluster (may be after 
> NPE)
> See "trans-write-invoke" logs.
> {noformat}
> [22:24:53,079][ERROR][tcp-disco-msg-worker-#2%null][TcpDiscoverySpi] Runtime 
> error caught during grid runnable execution: IgniteSpiThread 
> [name=tcp-disco-msg-worker-#2%null]
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.processClientReconnectData(GridCacheProcessor.java:2011)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onDiscoveryDataReceived(GridCacheProcessor.java:1904)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$6.onExchange(GridDiscoveryManager.java:659)
>   at 
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1706)
>   at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddedMessage(ServerImpl.java:3310)
>   at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processJoinRequestMessage(ServerImpl.java:3002)
>   at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2095)
>   at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5382)
>   at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {noformat}
> In additional, after it (left 3 server node + 1 client)
> - one more server has been killed
> - the last client said  "Failed to reconnect"
> - and another server node got the same NPE



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

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

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-1099:
-
Fix Version/s: (was: 1.5)
   1.6

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



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

[jira] [Created] (IGNITE-2125) Refactoring popup more-info on configuration pages

[Dmitriyff (JIRA)]

Dmitriyff created IGNITE-2125:
-

 Summary: Refactoring popup more-info on configuration pages
 Key: IGNITE-2125
 URL: https://issues.apache.org/jira/browse/IGNITE-2125
 Project: Ignite
  Issue Type: Sub-task
Reporter: Dmitriyff






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

[jira] [Updated] (IGNITE-870) Need to add more information on Ignite Contribute page

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-870:

Fix Version/s: (was: 1.5)
   1.6

> Need to add more information on Ignite Contribute page 
> ---
>
> Key: IGNITE-870
> URL: https://issues.apache.org/jira/browse/IGNITE-870
> Project: Ignite
>  Issue Type: Task
>Reporter: Artem Shutak
>Assignee: Artem Shutak
> Fix For: 1.6
>
>
> Add information about:
> - AL2 header
> - it'd be nice to have an explanation how one can contribute to
> the website, documentation, etc. After all, the project doesn't consist of
> code only. In fact, user facing part of it isn't the code at all.



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

[jira] [Updated] (IGNITE-1260) S3 IP finder should have an option to use a subfolder instead of bucket root

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-1260:
-
Fix Version/s: (was: 1.5)
   1.6

> S3 IP finder should have an option to use a subfolder instead of bucket root
> 
>
> Key: IGNITE-1260
> URL: https://issues.apache.org/jira/browse/IGNITE-1260
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>Assignee: Artem Shutak
>  Labels: usability, user-request
> Fix For: 1.6
>
>
> Current implementation forces user to use the bucket root which is not always 
> possible. Need to provide a configuration parameter that allows to provide a 
> path in addition to the bucket name.
> Corresponding user@ thread: 
> http://apache-ignite-users.70518.x6.nabble.com/AWS-Integration-td495.html



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

[jira] [Updated] (IGNITE-1126) Make sure REST is covered with tests

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-1126:
-
Fix Version/s: (was: 1.5)
   1.6

> Make sure REST is covered with tests
> 
>
> Key: IGNITE-1126
> URL: https://issues.apache.org/jira/browse/IGNITE-1126
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Alexey Goncharuk
>Assignee: Artem Shutak
> Fix For: 1.6
>
>
> Need to make sure all REST commands are covered with tests.



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

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

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-1450:
-
Fix Version/s: (was: 1.5)
   1.6

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



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

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

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-1125:
-
Fix Version/s: (was: 1.5)
   1.6

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



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

[jira] [Assigned] (IGNITE-2125) Refactoring popup more-info on configuration pages

[Dmitriyff (JIRA)]

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

Dmitriyff reassigned IGNITE-2125:
-

Assignee: Dmitriyff

> Refactoring popup more-info on configuration pages
> --
>
> Key: IGNITE-2125
> URL: https://issues.apache.org/jira/browse/IGNITE-2125
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Dmitriyff
>Assignee: Dmitriyff
> Fix For: 1.6
>
>




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

[jira] [Resolved] (IGNITE-2108) CacheJdbcPojoStoreFactory is not fully initialized when deserialized on a remote node

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov resolved IGNITE-2108.
--
Resolution: Fixed
  Assignee: Sergey Kozlov  (was: Alexey Kuznetsov)

Fixed in ignite-1.5 branch.
Examples with cache auto store updated.

To test: 
1) Run with several nodes started: CacheBinaryAutoStoreExample, 
CacheAutoStoreExample examples.

2) Run examples\schema-import demo.

3) Check updated documentation (in 1.5 version): 
https://apacheignite.readme.io/docs/automatic-persistence

> CacheJdbcPojoStoreFactory is not fully initialized when deserialized on a 
> remote node
> -
>
> Key: IGNITE-2108
> URL: https://issues.apache.org/jira/browse/IGNITE-2108
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Denis Magda
>Assignee: Sergey Kozlov
>Priority: Blocker
> Fix For: 1.5
>
>
> When a cache is started dynamically and has an implementation of 
> {{CacheJdbcPojoStoreFactory}} in its configuration then the cache startup 
> procedure will fail on a remote node with the following exception:
> {noformat}
> [16:14:10,014][ERROR][exchange-worker-#49%null%][GridDhtPartitionsExchangeFuture]
>  Failed to reinitialize local partitions (preloading will be stopped): 
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=2, 
> minorTopVer=1], nodeId=a7a1f89a, evt=DISCOVERY_CUSTOM_EVT]
> class org.apache.ignite.IgniteCheckedException: Failed to start component: 
> class org.apache.ignite.IgniteException: Failed to initialize cache store 
> (data source is not provided).
>   at 
> org.apache.ignite.internal.util.IgniteUtils.startLifecycleAware(IgniteUtils.java:8385)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCache(GridCacheProcessor.java:1251)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1620)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCachesStart(GridCacheProcessor.java:1545)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.startCaches(GridDhtPartitionsExchangeFuture.java:944)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:511)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1297)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteException: Failed to initialize 
> cache store (data source is not provided).
>   at 
> org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore.start(CacheAbstractJdbcStore.java:297)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.startLifecycleAware(IgniteUtils.java:8381)
>   ... 8 more
> {noformat}
> The reason is that in version 1.5 {{CacheJdbcPojoStoreFactory}} was reworked 
> significantly and presently it has field {{private transient DataSource 
> dataSrc}} that must be initiated somehow after deserialization.
> The issue is easily to reproduce with schema-import example:
> 1) complete all the steps described in the demo tutorial
> https://apacheignite.readme.io/docs/automatic-persistence#example
> 2) Start a remote node using {{DemoNode}}
> 3) Start {{Demo}}
> 4) The node started with {{DemoNode}} won't be able to start a cache because 
> of the issue with the storage described above



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

[jira] [Assigned] (IGNITE-2120) Rename Binarylizable -> Binarizable

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-2120:
---

Assignee: Vladimir Ozerov

> Rename Binarylizable -> Binarizable
> ---
>
> Key: IGNITE-2120
> URL: https://issues.apache.org/jira/browse/IGNITE-2120
> Project: Ignite
>  Issue Type: Task
>  Components: general, 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] [Updated] (IGNITE-2120) Rename Binarylizable -> Binarizable

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2120:

Assignee: (was: Vladimir Ozerov)

> Rename Binarylizable -> Binarizable
> ---
>
> Key: IGNITE-2120
> URL: https://issues.apache.org/jira/browse/IGNITE-2120
> Project: Ignite
>  Issue Type: Task
>  Components: general, interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>




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

[jira] [Resolved] (IGNITE-2120) Rename Binarylizable -> Binarizable

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-2120.
-
Resolution: Won't Fix

It is hard to pronounce "Binarizable". Let's stick with existing name.

> Rename Binarylizable -> Binarizable
> ---
>
> Key: IGNITE-2120
> URL: https://issues.apache.org/jira/browse/IGNITE-2120
> Project: Ignite
>  Issue Type: Task
>  Components: general, interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>




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

[jira] [Closed] (IGNITE-2120) Rename Binarylizable -> Binarizable

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-2120.
---

> Rename Binarylizable -> Binarizable
> ---
>
> Key: IGNITE-2120
> URL: https://issues.apache.org/jira/browse/IGNITE-2120
> Project: Ignite
>  Issue Type: Task
>  Components: general, interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>




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

[jira] [Assigned] (IGNITE-2105) DirectMessageWriter cannot write nested collections.

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko reassigned IGNITE-2105:
---

Assignee: Valentin Kulichenko

> DirectMessageWriter cannot write nested collections.
> 
>
> Key: IGNITE-2105
> URL: https://issues.apache.org/jira/browse/IGNITE-2105
> Project: Ignite
>  Issue Type: Bug
>  Components: 1.4
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.5
>
>
> Steps to reproduce:
> 1) Run GridMessageCollectionTest in ignite-1.5 branch
> 2) Observe class-cast exception.
> The problem is caused by DirectByteBufferStreamImplV2 which is re-used across 
> all nested objects. 
> This class is stateful. When nested collection is written, instead of writing 
> collection element it writes element of another collection which is upper in 
> call stack.
> Looks pretty critical for me.



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

[jira] [Closed] (IGNITE-2094) building the project with 'install' crashes on Mesos module

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov closed IGNITE-2094.


> building the project with 'install' crashes on Mesos module
> ---
>
> Key: IGNITE-2094
> URL: https://issues.apache.org/jira/browse/IGNITE-2094
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Affects Versions: 1.5
>Reporter: Konstantin Boudnik
>Assignee: Anton Vinogradov
> Fix For: 1.5
>
>
> Attempting to do {{mvn install...}} on the latest {{-b1}} release and the 
> build crashed on the Mesos module.



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

[jira] [Resolved] (IGNITE-2094) building the project with 'install' crashes on Mesos module

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov resolved IGNITE-2094.
--
Resolution: Won't Fix

> building the project with 'install' crashes on Mesos module
> ---
>
> Key: IGNITE-2094
> URL: https://issues.apache.org/jira/browse/IGNITE-2094
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Affects Versions: 1.5
>Reporter: Konstantin Boudnik
>Assignee: Anton Vinogradov
> Fix For: 1.5
>
>
> Attempting to do {{mvn install...}} on the latest {{-b1}} release and the 
> build crashed on the Mesos module.



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

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

[Semen Boikov (JIRA)]

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

Semen Boikov commented on IGNITE-1355:
--

Changes look good, but I see minor issues in GridAffinityProcessor:
- line 894: '@Nullable private AffinityInfo cache() throws 
IgniteCheckedException {' - please remove '@Nullable' here
- line 895: unnesessary call 'ctx.discovery().topologyVersionEx();', please 
remove

> Potential NPE in CacheAffinityProxy
> ---
>
> Key: IGNITE-1355
> URL: https://issues.apache.org/jira/browse/IGNITE-1355
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Semen Boikov
>Assignee: Artem Shutak
>Priority: Critical
> Fix For: 1.6
>
>
> NPE was observed on TC:
> {noformat}
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor$AffinityInfo.access$1800(GridAffinityProcessor.java:537)
> at 
> org.apache.ignite.internal.processors.affinity.GridAffinityProcessor$CacheAffinityProxy.mapPartitionToPrimaryAndBackups(GridAffinityProcessor.java:879)
> at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:423)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteCacheCrossCacheTxFailoverTest.crossCacheTxFailover(IgniteCacheCrossCacheTxFailoverTest.java:355)
> {noformat}
> As I see method CacheAffinityProxy.cache() can return null, but there are no 
> checks for null.



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

[jira] [Commented] (IGNITE-2100) Queries do not work with binary marshaller and Externalizable objects

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2100:


GitHub user agoncharuk opened a pull request:

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

IGNITE-2100 - Fixes for Externalizable classes and queries.



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

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

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

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


commit e84b268f8c3ff85a8e2af8c763b10b41a3659a18
Author: Alexey Goncharuk 
Date:   2015-12-09T17:29:12Z

IGNITE-2100 - Fixes for Externalizable classes and queries.




> Queries do not work with binary marshaller and Externalizable objects
> -
>
> Key: IGNITE-2100
> URL: https://issues.apache.org/jira/browse/IGNITE-2100
> Project: Ignite
>  Issue Type: Bug
>  Components: general, interop
>Reporter: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.5
>
>
> If new binary marshaller is used and model classes implement 
> {{Externalizable}} (which is often the case when user migrates from 1.4 to 
> 1.5), queries stop working and return nulls instead of all field values.
> At least, we need to properly document it and throw an exception so that user 
> is aware about the issue.



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