[jira] [Commented] (IGNITE-2065) Need to get rid of 'Portable' word in internals

[Semen Boikov (JIRA)]

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

Semen Boikov commented on IGNITE-2065:
--

Artem, please take a look, I think we should not have word 'portable' in ignite 
(need also check javadoc).

> Need to get rid of 'Portable' word in internals
> ---
>
> Key: IGNITE-2065
> URL: https://issues.apache.org/jira/browse/IGNITE-2065
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Alexey Goncharuk
>Assignee: Artem Shutak
> Fix For: 1.5
>
>
> Currently there is a bunch of objects that were kept from Portable objects 
> migration, such as PortableContext and portable package. Need to rename them 
> to Binary*.



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

[jira] [Resolved] (IGNITE-2008) Abandoned locks are not released when nodes leave the grid

[Semen Boikov (JIRA)]

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

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

There was an issue with callback called to release locks aquired by left node 
(GridCacheMvcc.removeExplicitNodeCandidates): it was erroneously called after 
partitionReleaseFuture is done, so deadlock was possible.  
Fixed it to call removeExplicitNodeCandidates after topology version was 
changed, but before partitionReleaseFuture  (in ignite-1.5 , commit baab3d2).

> Abandoned locks are not released when nodes leave the grid
> --
>
> Key: IGNITE-2008
> URL: https://issues.apache.org/jira/browse/IGNITE-2008
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
> Environment: Ubuntu 12.04, Ignite 1.4, Java 1.8.0_40-b26 (HotSpot 
> 64-Bit)
>Reporter: Noam Liran
>Assignee: Semen Boikov
> Fix For: 1.5
>
>
> Hi,
> We're starting to use Ignite in one of our environments and we've encountered 
> some strange behaviour in one of our test cases.
> # Start two nodes at the same time.
> # Each nodes should initialize a cache with the following parameters:
> ## Cache mode: REPLICATED / PARTITIONED
> ## Atomicity mode: TRANSACTIONAL
> # Both nodes run the following code:
> {code}
> System.out.println("Sleeping before..");
> Thread.sleep(5000);
> List locks = new ArrayList<>();
> System.out.println("Acquiring...");
> for (int lockId = 0; lockId < 4; lockId++) {
> String lockName = "LOCK_" + lockId;
> Lock lock = cache.lock(lockName);
> locks.add(lock);
> lock.lock();
> }
> System.out.println("Acquired!");
> Thread.sleep(2);
> System.out.println("Done");
> {code}
> # Node 1 acquires all the relevant locks and waits a while.
> # Node 2 tries to acquire the locks and is blocked.
> # Node 1 eventually quits while holding the locks.
> # Node 2 never gains control of the locks even though they're abandoned.
> When we try the same with a looped tryLock everything seems to work.
> Our Ignite configuration is pretty straightforward:
> # Regular TCP discovery
> # No checkpointing SPI
> # No collision SPI
> # Always failover SPI
> # CONTINUOUS deployment mode



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

[jira] [Closed] (IGNITE-2008) Abandoned locks are not released when nodes leave the grid

[Semen Boikov (JIRA)]

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

Semen Boikov closed IGNITE-2008.

Assignee: (was: Semen Boikov)

> Abandoned locks are not released when nodes leave the grid
> --
>
> Key: IGNITE-2008
> URL: https://issues.apache.org/jira/browse/IGNITE-2008
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
> Environment: Ubuntu 12.04, Ignite 1.4, Java 1.8.0_40-b26 (HotSpot 
> 64-Bit)
>Reporter: Noam Liran
> Fix For: 1.5
>
>
> Hi,
> We're starting to use Ignite in one of our environments and we've encountered 
> some strange behaviour in one of our test cases.
> # Start two nodes at the same time.
> # Each nodes should initialize a cache with the following parameters:
> ## Cache mode: REPLICATED / PARTITIONED
> ## Atomicity mode: TRANSACTIONAL
> # Both nodes run the following code:
> {code}
> System.out.println("Sleeping before..");
> Thread.sleep(5000);
> List locks = new ArrayList<>();
> System.out.println("Acquiring...");
> for (int lockId = 0; lockId < 4; lockId++) {
> String lockName = "LOCK_" + lockId;
> Lock lock = cache.lock(lockName);
> locks.add(lock);
> lock.lock();
> }
> System.out.println("Acquired!");
> Thread.sleep(2);
> System.out.println("Done");
> {code}
> # Node 1 acquires all the relevant locks and waits a while.
> # Node 2 tries to acquire the locks and is blocked.
> # Node 1 eventually quits while holding the locks.
> # Node 2 never gains control of the locks even though they're abandoned.
> When we try the same with a looped tryLock everything seems to work.
> Our Ignite configuration is pretty straightforward:
> # Regular TCP discovery
> # No checkpointing SPI
> # No collision SPI
> # Always failover SPI
> # CONTINUOUS deployment mode



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

[jira] [Updated] (IGNITE-2072) Chart settings doesn't contain fields with UUID type

[Andrey Novikov (JIRA)]

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

Andrey Novikov updated IGNITE-2072:
---
Fix Version/s: (was: 1.5)
   1.6

> Chart settings doesn't contain fields with UUID type
> 
>
> Key: IGNITE-2072
> URL: https://issues.apache.org/jira/browse/IGNITE-2072
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Andrey Novikov
> Fix For: 1.6
>
>
> Start tester
> select * from Person



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

[jira] [Updated] (IGNITE-2072) Chart settings doesn't contain fields with UUID type

[Andrey Novikov (JIRA)]

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

Andrey Novikov updated IGNITE-2072:
---
Assignee: Pavel Konstantinov  (was: Andrey Novikov)

> Chart settings doesn't contain fields with UUID type
> 
>
> Key: IGNITE-2072
> URL: https://issues.apache.org/jira/browse/IGNITE-2072
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
>
> Start tester
> select * from Person



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

[jira] [Updated] (IGNITE-1979) Support case insensitive nonquoted cache names in SQL queries

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-1979:

Assignee: (was: Denis Magda)

> Support case insensitive nonquoted cache names in SQL queries
> -
>
> Key: IGNITE-1979
> URL: https://issues.apache.org/jira/browse/IGNITE-1979
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Priority: Critical
> Fix For: 1.6
>
>
> According to SQL ANSI-99 standard the schema name (corresponds to a cache 
> name in Ignite) is case insensitive.
> However Ignite has the requirement to put a cache name into the quotation 
> marks. This violates the standard.
> The main reasons of that is because a cache name in Ignite is case sensitive 
> and can contain all kind of symbols that are not supported by underlying H2 
> engine.
> Proposed to introduce a new configuration property to {{CacheConfiguration}} 
> that will let the end user use a cache name in case insensitive manner 
> without quoted identifiers in SQL queries.



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

[jira] [Commented] (IGNITE-2019) schema import utility failed to start on Mac OS X EI Capitan

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2019:


GitHub user nva opened a pull request:

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

IGNITE-2019 Fixed schema import on Mac OSX El Capitan.



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

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

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

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


commit 30126a0046263dcd5d8027cc2e44654b90c316f3
Author: Andrey 
Date:   2015-12-04T05:02:55Z

IGNITE-2019 Fixed schema import on Mac OSX El Capitan.




> schema import utility failed to start on Mac OS X EI Capitan
> 
>
> Key: IGNITE-2019
> URL: https://issues.apache.org/jira/browse/IGNITE-2019
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Andrey Novikov
>Priority: Critical
> Fix For: 1.5
>
> Attachments: screenshot.png
>
>
> {code}
> /Users/kope/Downloads/gridgain-enterprise-fabric-7.5.0/bin/ignite-schema-import.sh
>  ; exit;
> kope-mac:~ kope$ 
> /Users/kope/Downloads/gridgain-enterprise-fabric-7.5.0/bin/ignite-schema-import.sh
>  ; exit;
> Exception in Application start method
> Exception in Application stop method
> Exception in thread "main" java.lang.RuntimeException: Exception in 
> Application start method
>   at 
> com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:403)
>   at 
> com.sun.javafx.application.LauncherImpl.access$000(LauncherImpl.java:47)
>   at com.sun.javafx.application.LauncherImpl$1.run(LauncherImpl.java:115)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ExceptionInInitializerError
>   at javafx.scene.control.TableColumn.impl_setWidth(TableColumn.java:1259)
>   at javafx.scene.control.TableColumn$7.invalidated(TableColumn.java:763)
>   at 
> javafx.beans.property.DoublePropertyBase.markInvalid(DoublePropertyBase.java:129)
>   at 
> javafx.beans.property.DoublePropertyBase.set(DoublePropertyBase.java:163)
>   at javafx.scene.control.TableColumn.setMinWidth(TableColumn.java:749)
>   at org.apache.ignite.schema.ui.Controls.tableColumn(Controls.java:437)
>   at org.apache.ignite.schema.ui.Controls.customColumn(Controls.java:472)
>   at 
> org.apache.ignite.schema.ui.SchemaImportApp.createGeneratePane(SchemaImportApp.java:1033)
>   at 
> org.apache.ignite.schema.ui.SchemaImportApp.start(SchemaImportApp.java:1590)
>   at com.sun.javafx.application.LauncherImpl$5.run(LauncherImpl.java:319)
>   at com.sun.javafx.application.PlatformImpl$5.run(PlatformImpl.java:219)
>   at 
> com.sun.javafx.application.PlatformImpl$4$1.run(PlatformImpl.java:182)
>   at 
> com.sun.javafx.application.PlatformImpl$4$1.run(PlatformImpl.java:179)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at com.sun.javafx.application.PlatformImpl$4.run(PlatformImpl.java:179)
>   at 
> com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:76)
> Caused by: java.lang.NullPointerException
>   at 
> com.sun.t2k.MacFontFinder.initPSFontNameToPathMap(MacFontFinder.java:339)
>   at 
> com.sun.t2k.MacFontFinder.getFontNamesOfFontFamily(MacFontFinder.java:390)
>   at com.sun.t2k.T2KFontFactory.getFontResource(T2KFontFactory.java:233)
>   at com.sun.t2k.LogicalFont.getSlot0Resource(LogicalFont.java:184)
>   at com.sun.t2k.LogicalFont.getSlotResource(LogicalFont.java:228)
>   at com.sun.t2k.CompositeStrike.getStrikeSlot(CompositeStrike.java:86)
>   at com.sun.t2k.CompositeStrike.getMetrics(CompositeStrike.java:132)
>   at 
> com.sun.javafx.font.PrismFontUtils.getFontMetrics(PrismFontUtils.java:31)
>   at 
> com.sun.javafx.font.PrismFontLoader.getFontMetrics(PrismFontLoader.java:466)
>   at javafx.scene.text.Text.(Text.java:153)
>   at com.sun.javafx.scene.control.skin.Utils.(Utils.java:52)
>   ... 16 more
> {code}
> {code}
> kope-mac:~ kope$ java -version
> java version "1.7.0_67"
> Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
> Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
> {code}



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

[jira] [Updated] (IGNITE-2083) EntryProcessor is called twice on primary node in transactional cache

[Semen Boikov (JIRA)]

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

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

> EntryProcessor is called twice on primary node in transactional cache
> -
>
> Key: IGNITE-2083
> URL: https://issues.apache.org/jira/browse/IGNITE-2083
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: 1.5
>
>
> Issue is described in details here: 
> http://apache-ignite-developers.2346864.n4.nabble.com/EntryProcessor-invoked-twice-td5494.html
> Looks like that this can be optimized, at least for {{REPEATABLE_READ}} 
> transactions.



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

[jira] [Assigned] (IGNITE-2083) EntryProcessor is called twice on primary node in transactional cache

[Semen Boikov (JIRA)]

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

Semen Boikov reassigned IGNITE-2083:


Assignee: Semen Boikov

> EntryProcessor is called twice on primary node in transactional cache
> -
>
> Key: IGNITE-2083
> URL: https://issues.apache.org/jira/browse/IGNITE-2083
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: 1.5
>
>
> Issue is described in details here: 
> http://apache-ignite-developers.2346864.n4.nabble.com/EntryProcessor-invoked-twice-td5494.html
> Looks like that this can be optimized, at least for {{REPEATABLE_READ}} 
> transactions.



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

[jira] [Commented] (IGNITE-2072) Chart settings doesn't contain fields with UUID type

[Andrey Novikov (JIRA)]

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

Andrey Novikov commented on IGNITE-2072:


For UUID columns 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager#sqlMetadata
 return UUID, but when execute query and columns metadata  from 
org.apache.ignite.internal.processors.cache.QueryCursorImpl#fieldsMeta() return 
[B] type.

> Chart settings doesn't contain fields with UUID type
> 
>
> Key: IGNITE-2072
> URL: https://issues.apache.org/jira/browse/IGNITE-2072
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Andrey Novikov
> Fix For: 1.5
>
>
> Start tester
> select * from Person



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

[jira] [Updated] (IGNITE-2008) Abandoned locks are not released when nodes leave the grid

[Semen Boikov (JIRA)]

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

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

> Abandoned locks are not released when nodes leave the grid
> --
>
> Key: IGNITE-2008
> URL: https://issues.apache.org/jira/browse/IGNITE-2008
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
> Environment: Ubuntu 12.04, Ignite 1.4, Java 1.8.0_40-b26 (HotSpot 
> 64-Bit)
>Reporter: Noam Liran
>Assignee: Semen Boikov
> Fix For: 1.5
>
>
> Hi,
> We're starting to use Ignite in one of our environments and we've encountered 
> some strange behaviour in one of our test cases.
> # Start two nodes at the same time.
> # Each nodes should initialize a cache with the following parameters:
> ## Cache mode: REPLICATED / PARTITIONED
> ## Atomicity mode: TRANSACTIONAL
> # Both nodes run the following code:
> {code}
> System.out.println("Sleeping before..");
> Thread.sleep(5000);
> List locks = new ArrayList<>();
> System.out.println("Acquiring...");
> for (int lockId = 0; lockId < 4; lockId++) {
> String lockName = "LOCK_" + lockId;
> Lock lock = cache.lock(lockName);
> locks.add(lock);
> lock.lock();
> }
> System.out.println("Acquired!");
> Thread.sleep(2);
> System.out.println("Done");
> {code}
> # Node 1 acquires all the relevant locks and waits a while.
> # Node 2 tries to acquire the locks and is blocked.
> # Node 1 eventually quits while holding the locks.
> # Node 2 never gains control of the locks even though they're abandoned.
> When we try the same with a looped tryLock everything seems to work.
> Our Ignite configuration is pretty straightforward:
> # Regular TCP discovery
> # No checkpointing SPI
> # No collision SPI
> # Always failover SPI
> # CONTINUOUS deployment mode



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

[jira] [Closed] (IGNITE-2036) Reset password link in the email doesn't redirect to reset password page

[Pavel Konstantinov (JIRA)]

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

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

Tested.

> Reset password link in the email doesn't redirect to reset password page
> 
>
> Key: IGNITE-2036
> URL: https://issues.apache.org/jira/browse/IGNITE-2036
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.6
>
>




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

[jira] [Closed] (IGNITE-2051) First (or newly created query) query doesn't opens on notebook page

[Pavel Konstantinov (JIRA)]

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

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

Tested.

> First (or newly created query) query doesn't opens on notebook page
> ---
>
> Key: IGNITE-2051
> URL: https://issues.apache.org/jira/browse/IGNITE-2051
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.6
>
>




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

[jira] [Created] (IGNITE-2077) .Net: Create builds on TeamCity

[Pavel Tupitsyn (JIRA)]

Pavel  Tupitsyn created IGNITE-2077:
---

 Summary: .Net: Create builds on TeamCity
 Key: IGNITE-2077
 URL: https://issues.apache.org/jira/browse/IGNITE-2077
 Project: Ignite
  Issue Type: Task
  Components: interop
Affects Versions: 1.5
Reporter: Pavel  Tupitsyn
Assignee: Pavel  Tupitsyn
 Fix For: 1.5


http://204.14.53.153/project.html?projectId=IgniteTests=projectOverview



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

[jira] [Updated] (IGNITE-2077) .Net: Create builds on TeamCity

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn updated IGNITE-2077:

Description: 
http://204.14.53.153/project.html?projectId=IgniteTests=projectOverview

* Platform .NET
* Platform .NET Long Running

  
was:http://204.14.53.153/project.html?projectId=IgniteTests=projectOverview


> .Net: Create builds on TeamCity
> ---
>
> Key: IGNITE-2077
> URL: https://issues.apache.org/jira/browse/IGNITE-2077
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.5
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: 1.5
>
>
> http://204.14.53.153/project.html?projectId=IgniteTests=projectOverview
> * Platform .NET
> * Platform .NET Long Running



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

[jira] [Commented] (IGNITE-1393) AssertionError when stop node executing transaction

[Semen Boikov (JIRA)]

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

Semen Boikov commented on IGNITE-1393:
--

Also need to add locks in the GridCacheStopSelfTest (something like simple 
lock/unlock in GridCacheStopSelfTest.cacheOperations).

> AssertionError when stop node executing transaction
> ---
>
> Key: IGNITE-1393
> URL: https://issues.apache.org/jira/browse/IGNITE-1393
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Semen Boikov
>  Labels: Muted_test
>
> I fixed GridCacheStopSelfTest which was disabled for long time, now it fails 
> because of asserts:
> {noformat}
> [10:53:02,362][ERROR][async-runner-1][GridNearTxLocal] Heuristic transaction 
> failure.
> class 
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException: 
> Failed to locally write to cache (all transaction entries will be 
> invalidated, however there was a window when entries for this transaction 
> were visible to others): GridNearTxLocal [nearLocallyMapped=false, 
> colocatedLocallyMapped=true, hasRemoteLocks=false, 
> mappings=[009f5238-db3d-426f-b787-9a4a156e8000], super=GridDhtTxLocalAdapter 
> [dhtThreadId=101, needsCompletedVers=false, nearNodes=[], dhtNodes=[], 
> explicitLock=false, super=IgniteTxLocalAdapter [txMap={IgniteTxKey 
> [key=KeyCacheObjectImpl [val=22, hasValBytes=true], cacheId=1]=IgniteTxEntry 
> [key=KeyCacheObjectImpl [val=22, hasValBytes=true], cacheId=1, 
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=22, hasValBytes=true], 
> cacheId=1], val=[op=CREATE, val=UserCacheObjectImpl [val=22, 
> hasValBytes=true]], prevVal=[op=CREATE, val=UserCacheObjectImpl [val=22, 
> hasValBytes=true]], entryProcessorsCol=null, entryProcessorCalcVal=null, 
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null, 
> dhtVer=GridCacheVersion [topVer=53261582, nodeOrderDrId=1, 
> globalTime=1441781582327, order=1441781581691], filters=[], 
> filtersPassed=false, filtersSet=true, entry=GridDhtColocatedCacheEntry 
> [super=GridDhtCacheEntry [rdrs=[], locPart=GridDhtLocalPartition [id=22, 
> mapPubSize=1, rmvQueue=GridCircularBuffer [sizeMask=31, idxGen=0], 
> state=OWNING, reservations=0, empty=false, createTime=09/09/2015 10:53:02, 
> mapPubSize=1], super=GridDistributedCacheEntry [super=GridCacheMapEntry 
> [key=KeyCacheObjectImpl [val=22, hasValBytes=true], val=CacheObjectImpl 
> [val=22, hasValBytes=true], startVer=1441781581658, ver=GridCacheVersion 
> [topVer=53261582, nodeOrderDrId=1, globalTime=1441781582327, 
> order=1441781581691], hash=2018242870, extras=null, flags=2, 
> prepared=false, locked=true, nodeId=009f5238-db3d-426f-b787-9a4a156e8000, 
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0, 
> xidVer=GridCacheVersion [topVer=53261582, nodeOrderDrId=1, 
> globalTime=1441781582217, order=1441781581591]]}, completedBase=null, 
> sndTransformedVals=false, super=IgniteTxAdapter [xidVer=GridCacheVersion 
> [topVer=53261582, nodeOrderDrId=1, globalTime=1441781582217, 
> order=1441781581591], writeVer=GridCacheVersion [topVer=53261582, 
> nodeOrderDrId=1, globalTime=1441781582327, order=1441781581691], 
> implicit=false, implicitSingle=false, loc=true, threadId=101, 
> startTime=1441781582212, nodeId=009f5238-db3d-426f-b787-9a4a156e8000, 
> startVer=GridCacheVersion [topVer=53261582, nodeOrderDrId=1, 
> globalTime=1441781582218, order=1441781581611], endVer=GridCacheVersion 
> [topVer=53261582, nodeOrderDrId=1, globalTime=1441781582336, 
> order=1441781581738], isolation=REPEATABLE_READ, concurrency=PESSIMISTIC, 
> timeout=0, sysInvalidate=false, sys=false, plc=2, commitVer=GridCacheVersion 
> [topVer=53261582, nodeOrderDrId=1, globalTime=1441781582217, 
> order=1441781581591], finalizing=NONE, preparing=false, state=COMMITTED, 
> timedOut=false, topVer=AffinityTopologyVersion [topVer=1, minorTopVer=0], 
> duration=138ms, onePhaseCommit=true], size=1]]]
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:1036)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.finish(GridNearTxLocal.java:654)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$3.apply(GridNearTxLocal.java:749)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$3.apply(GridNearTxLocal.java:741)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:262)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:225)
>   at 
> 

[jira] [Assigned] (IGNITE-1611) [Test Failed] GridNearCacheTxNodeFailureSelfTest.testPrimaryNodeFailureBackupCommitImplicit

[Semen Boikov (JIRA)]

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

Semen Boikov reassigned IGNITE-1611:


Assignee: Semen Boikov

> [Test Failed] 
> GridNearCacheTxNodeFailureSelfTest.testPrimaryNodeFailureBackupCommitImplicit
> ---
>
> Key: IGNITE-1611
> URL: https://issues.apache.org/jira/browse/IGNITE-1611
> Project: Ignite
>  Issue Type: Test
>Affects Versions: 1.5
>Reporter: Anton Vinogradov
>Assignee: Semen Boikov
>Priority: Blocker
>  Labels: Muted_test
> Fix For: 1.5
>
>
> There is no guarantee that test failure will be produced each test run, 
> please analyze logs in case of reproduction problem:
> {noformat}
> junit.framework.AssertionFailedError: near=GridNearCacheEntry [topVer=4, 
> dhtVer=GridCacheVersion [topVer=55263880, nodeOrderDrId=1, 
> globalTime=1443783881869, order=1443783876675], part=2, 
> super=GridDistributedCacheEntry [super=GridCacheMapEntry 
> [key=KeyCacheObjectImpl [val=2, hasValBytes=true], val=CacheObjectImpl 
> [val=2, hasValBytes=true], startVer=1443783876676, ver=GridCacheVersion 
> [topVer=55263880, nodeOrderDrId=1, globalTime=1443783881869, 
> order=1443783876675], hash=821347078, extras=null, flags=0]]]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNull(Assert.java:277)
> at junit.framework.TestCase.assertNull(TestCase.java:447)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheTxNodeFailureSelfTest.dataCheck(GridCacheTxNodeFailureSelfTest.java:342)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheTxNodeFailureSelfTest.checkPrimaryNodeFailureBackupCommit(GridCacheTxNodeFailureSelfTest.java:302)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheTxNodeFailureSelfTest.testPrimaryNodeFailureBackupCommitImplicit(GridCacheTxNodeFailureSelfTest.java:161)
> 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:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> --- Stdout: ---
> [14:04:36,650][INFO ][main][root] >>> Starting test: 
> testPrimaryNodeFailureBackupCommitImplicit <<<
> [14:04:36,661][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] 
> >>>__    
> >>>   /  _/ ___/ |/ /  _/_  __/ __/  
> >>>  _/ // (7 7// /  / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/   
> >>> 
> >>> ver. 1.5.0-SNAPSHOT#19700101-sha1:DEV
> >>> 2015 Copyright(C) Apache Software Foundation
> >>> 
> >>> Ignite documentation: http://ignite.apache.org
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] 
> Config URL: n/a
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] 
> Daemon mode: off
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] OS: 
> Linux 2.6.32-38-generic amd64
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] OS 
> user: teamcity
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] 
> Language runtime: Java Platform API Specification ver. 1.7
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] VM 
> information: Java(TM) SE Runtime Environment 1.7.0_80-b15 Oracle Corporation 
> Java HotSpot(TM) 64-Bit Server VM 24.80-b11
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] VM 
> total memory: 2.7GB
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] 
> Remote Management [restart: off, REST: off, JMX (remote: off)]
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] 
> IGNITE_HOME=/usr/local/TeamCityAgent/work/871ff4a46e450b13
> [14:04:36,664][INFO ][test-runner][GridNearCacheTxNodeFailureSelfTest0] VM 
> arguments: [-DJAVA_HOME=/usr/lib/jvm/java-7-oracle, -DMCAST_GRP=229.13.1.2, 
> -Dagent.home.dir=/usr/local/TeamCityAgent, -Dagent.name=teamcity-3, 
> -Dagent.ownPort=9090, -Dagent.work.dir=/usr/local/TeamCityAgent/work, 
> -Dbuild.number=3390, 
> -Dbuild.vcs.number=7b54cbd7499cd498b04e821dfa3b572bd94debec, 
> 

[jira] [Updated] (IGNITE-2064) Correct p2p deployment logic/tests for binary marshaller

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-2064:
-
Assignee: Anton Vinogradov

> Correct p2p deployment logic/tests for binary marshaller
> 
>
> Key: IGNITE-2064
> URL: https://issues.apache.org/jira/browse/IGNITE-2064
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Alexey Goncharuk
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.5
>
>
> In current implementation p2p deployment is disabled for cache when binary 
> marshaller is used. It pursues an ability to use peer-deployed compute tasks 
> and not to clear cache when deployment owner leaves the grid.
> Thus, existing tests should be disabled/corrected for the binary marshaller 
> and new tests that use BinaryObject API should be added.
> Also, there are TODOs in the code related to IGNITE-1272 ticket, which has 
> been closed. Need to revisit and fix those todos, if needed.



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

[jira] [Commented] (IGNITE-2050) NPE: Failed to reinitialize local partitions (preloading will be stopped)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2050:


GitHub user agoncharuk opened a pull request:

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

IGNITE-2050 - Remove duplicates from the configuration.



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

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

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

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


commit 2bc901bc3dcf54c88cfdbf8bc1131ef9b4bafe85
Author: Alexey Goncharuk 
Date:   2015-12-03T12:13:38Z

IGNITE-2050 - Remove duplicates from the configuration.




> NPE: Failed to reinitialize local partitions (preloading will be stopped)
> -
>
> Key: IGNITE-2050
> URL: https://issues.apache.org/jira/browse/IGNITE-2050
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Artem Shutak
> Fix For: 1.5
>
>
> I was testing using my own tester and catched NPE:
> {code}
> [10:42:43,151][SEVERE][exchange-worker-#52%tester%][GridDhtPartitionsExchangeFuture]
>  Failed to reinitialize local partitions (preloading will be stopped): 
> GridDhtPartitionExchangeId [topVer=AffinityTo
> pologyVersion [topVer=3, minorTopVer=1], nodeId=97e00c67, 
> evt=DISCOVERY_CUSTOM_EVT]
> class org.apache.ignite.IgniteCheckedException: Type with name 'FSFMRule' 
> already indexed in cache 'bank_FSFMRule'.
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.addTypeByName(GridQueryProcessor.java:345)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:255)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:382)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1021)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1630)
> 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)
> [10:42:43,155][SEVERE][exchange-worker-#52%tester%][GridCachePartitionExchangeManager]
>  Runtime error caught during grid runnable execution: GridWorker 
> [name=partition-exchanger, gridName=tester, finis
> hed=false, isCancelled=false, hashCode=364597628, interrupted=false, 
> runner=exchange-worker-#52%tester%]
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onExchangeDone(GridCacheProcessor.java:1705)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:1098)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:87)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:334)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:861)
> 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)
> {code}



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

[jira] [Created] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case

[Anton Vinogradov (JIRA)]

Anton Vinogradov created IGNITE-2079:


 Summary: GridCacheIoManager eats exception trail if it falls into 
the directed case
 Key: IGNITE-2079
 URL: https://issues.apache.org/jira/browse/IGNITE-2079
 Project: Ignite
  Issue Type: Bug
Reporter: Anton Vinogradov
Assignee: Anton Vinogradov


During a recent test I have run into an issue where a storage disabled client 
of a Fabric that has services deployed for which the client does not have the 
fabric in the class path failed with the following exception:

com.workday.fabric.HelloWorldTest STANDARD_ERROR
Nov 08, 2015 6:15:20 PM org.apache.ignite.logger.java.JavaLogger error
SEVERE: Failed to process message 
[senderId=30775397-457a-400f-a6c9-077c9e762d61, messageType=class 
o.a.i.i.processors.cache.query.GridCacheQueryResponse]
class org.apache.ignite.IgniteCheckedException: Failed to send response to 
node. Unsupported direct type [message=GridCacheQueryResponse [finished=true, 
reqId=5, err=null, fields=false, metadata=null]]
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:546)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:272)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:77)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1078)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2302)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:992)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:106)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:961)
 at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
 at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 at java.lang.Thread.run(Thread.java:745)

This unfortunately gives me 0 information to work on to resolve the issue, as 
the original unmarshalling exception (from the JdkMarshaller) was eaten as this 
is the code for the default process failed message:

default:
throw new IgniteCheckedException("Failed to send response to node. Unsupported 
direct type [message="
+ msg + "]");
}

you should also include the original stack from msg.getError() in the newly 
thrown IgniteCheckedException



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

[jira] [Assigned] (IGNITE-2074) Platforms C++ files have 1.5.0-EA version

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn reassigned IGNITE-2074:
---

Assignee: Pavel  Tupitsyn

> Platforms C++ files have 1.5.0-EA version
> -
>
> Key: IGNITE-2074
> URL: https://issues.apache.org/jira/browse/IGNITE-2074
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Pavel  Tupitsyn
>Priority: Minor
> Fix For: 1.5
>
>
> We decided to use -bN suffixes for beta versions but files below still have 
> -EA:
> platforms/cpp/common/configure.ac
> platforms/cpp/core/configure.ac
> platforms/cpp/examples/configure.ac



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

[jira] [Updated] (IGNITE-2074) Platforms C++ files have 1.5.0-EA version

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov updated IGNITE-2074:
--
Summary: Platforms C++ files have 1.5.0-EA version  (was: Platforms C++ 
files hasve 1.5.0-EA version)

> Platforms C++ files have 1.5.0-EA version
> -
>
> Key: IGNITE-2074
> URL: https://issues.apache.org/jira/browse/IGNITE-2074
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Priority: Minor
> Fix For: 1.5
>
>
> We decided to use -bN suffixes for beta versions but files below still have 
> -EA:
> platforms/cpp/common/configure.ac
> platforms/cpp/core/configure.ac
> platforms/cpp/examples/configure.ac



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

[jira] [Created] (IGNITE-2074) Platforms C++ files hasve 1.5.0-EA version

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-2074:
-

 Summary: Platforms C++ files hasve 1.5.0-EA version
 Key: IGNITE-2074
 URL: https://issues.apache.org/jira/browse/IGNITE-2074
 Project: Ignite
  Issue Type: Bug
  Components: interop
Affects Versions: 1.5
Reporter: Sergey Kozlov
Priority: Minor
 Fix For: 1.5


We decided to use -bN suffixes for beta versions but files below still have -EA:
platforms/cpp/common/configure.ac
platforms/cpp/core/configure.ac
platforms/cpp/examples/configure.ac




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

[jira] [Updated] (IGNITE-2050) NPE: Failed to reinitialize local partitions (preloading will be stopped)

[Artem Shutak (JIRA)]

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

Artem Shutak updated IGNITE-2050:
-
Fix Version/s: 1.5

> NPE: Failed to reinitialize local partitions (preloading will be stopped)
> -
>
> Key: IGNITE-2050
> URL: https://issues.apache.org/jira/browse/IGNITE-2050
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
>
> I was testing using my own tester and catched NPE:
> {code}
> [10:42:43,151][SEVERE][exchange-worker-#52%tester%][GridDhtPartitionsExchangeFuture]
>  Failed to reinitialize local partitions (preloading will be stopped): 
> GridDhtPartitionExchangeId [topVer=AffinityTo
> pologyVersion [topVer=3, minorTopVer=1], nodeId=97e00c67, 
> evt=DISCOVERY_CUSTOM_EVT]
> class org.apache.ignite.IgniteCheckedException: Type with name 'FSFMRule' 
> already indexed in cache 'bank_FSFMRule'.
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.addTypeByName(GridQueryProcessor.java:345)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:255)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:382)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1021)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1630)
> 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)
> [10:42:43,155][SEVERE][exchange-worker-#52%tester%][GridCachePartitionExchangeManager]
>  Runtime error caught during grid runnable execution: GridWorker 
> [name=partition-exchanger, gridName=tester, finis
> hed=false, isCancelled=false, hashCode=364597628, interrupted=false, 
> runner=exchange-worker-#52%tester%]
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onExchangeDone(GridCacheProcessor.java:1705)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:1098)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:87)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:334)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:861)
> 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)
> {code}



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

[jira] [Comment Edited] (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=15035809#comment-15035809
 ] 

Artem Shutak edited comment on IGNITE-1864 at 12/3/15 10:08 AM:


The following points should be discussed in process of review:
# {{CacheJndiTmFactory}}
#* Should we have {{setInitialContextEnvironment}} or not? Map vs Hashtable. 
See http://docs.oracle.com/javase/jndi/tutorial/basics/prepare/initial.html
#* jndiNames - single or plurale jndi name(s)
# {{CacheReflectionTmFactory}}. I think there is no need to have that factory 
at all.
# Where out-of-the-box factories should be listed? Currently they described in 
javadoc to {TransactionConfiguration.setTxManagerFactory()}.
# Can {{Factory.create()}} returns {{null}} value or not? In current 
implementation exception will be thrown.
# Is it okey to call {{Factory.create()}} on node start? It means that user 
TransactionManager have to be already initiated.


was (Author: ashutak):
The following points should be discussed in process of review:
# {{CacheJndiTmFactory}}
#* Should we have {{setInitialContextEnvironment}} or not? Map vs Hashtable. 
See http://docs.oracle.com/javase/jndi/tutorial/basics/prepare/initial.html
#* jndiNames - single or plurale jndi name(s)
# {{CacheReflectionTmFactory}}. I think there is no need to have that factory 
at all.
# Where out-of-the-box factories should be listed? Currently they described in 
javadoc to {TransactionConfiguration.setTxManagerFactory()}.
# Can {{Factory.create()}} returns {{null}} value or not? In current 
implementation exception will be thrown.
# Is it okey to call {{Factory.create()}} on node start?

> 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.6
>
>
> 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] [Closed] (IGNITE-2014) Incorrect behavior on Refresh (F5 in browser) in corner case

[Pavel Konstantinov (JIRA)]

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

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

Tested.

> Incorrect behavior on Refresh (F5 in browser) in corner case
> 
>
> Key: IGNITE-2014
> URL: https://issues.apache.org/jira/browse/IGNITE-2014
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
>
> To reproduce:
> 1)Open cluster page for existing cluster
> 2)Click on Add link on Caches list
> 3)Set some name for newly created cache
> 4)Save cache
> 5)Refresh the cache page
> Observed: you will get another new empty cache
> Expected: list of caches should be refreshed and last created cache should be 
> as active item



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

[jira] [Created] (IGNITE-2072) Chart settings doesn't contain fields with UUID type

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2072:
--

 Summary: Chart settings doesn't contain fields with UUID type
 Key: IGNITE-2072
 URL: https://issues.apache.org/jira/browse/IGNITE-2072
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov


Start tester
select * from Person



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

[jira] [Commented] (IGNITE-2074) Platforms C++ files have 1.5.0-EA version

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2074:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-2074 Platforms C++ files have 1.5.0-EA version



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

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

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

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


commit e5cc4e3ed47de1ddcd01042b80b4ad575fd22451
Author: Pavel Tupitsyn 
Date:   2015-12-03T09:45:29Z

IGNITE-2074 Platforms C++ files have 1.5.0-EA version




> Platforms C++ files have 1.5.0-EA version
> -
>
> Key: IGNITE-2074
> URL: https://issues.apache.org/jira/browse/IGNITE-2074
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Pavel  Tupitsyn
>Priority: Minor
> Fix For: 1.5
>
>
> We decided to use -bN suffixes for beta versions but files below still have 
> -EA:
> platforms/cpp/common/configure.ac
> platforms/cpp/core/configure.ac
> platforms/cpp/examples/configure.ac



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

[jira] [Commented] (IGNITE-1371) Key-Value store (like Cassandra) as CacheStore

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov commented on IGNITE-1371:
--

Igor, 
I do second review.
All my changes in ignite-1371-review2 branch.
Take a look.

> Key-Value store (like Cassandra) as CacheStore
> --
>
> Key: IGNITE-1371
> URL: https://issues.apache.org/jira/browse/IGNITE-1371
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Alexandre Boudnik
>Assignee: Igor Rudyak
> Attachments: master_02b59e4_ignite-1371.patch
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> It will provide ability to map particular cache holding POJOs to Cassandra 
> table. Later it would be generalized to support eventually any any Key-Value 
> store.



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

[jira] [Commented] (IGNITE-2008) Abandoned locks are not released when nodes leave the grid

[Semen Boikov (JIRA)]

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

Semen Boikov commented on IGNITE-2008:
--

Roy,

As a workaround you can use PESSIMISTIC/REPEATABLE_READ transactions for 
disributed locks (in PESSIMISTIC mode a lock is acquired for all cache 
operations):
{code}
IgniteCache cache = ignite.cache("cache");

try (Transaction tx = ignite.transactions().txStart(PESSIMISTIC, 
REPEATABLE_READ)) {
cache.get(key); // Lock is acquired.

tx.commit(); // Lock is released.
}
{code}

> Abandoned locks are not released when nodes leave the grid
> --
>
> Key: IGNITE-2008
> URL: https://issues.apache.org/jira/browse/IGNITE-2008
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
> Environment: Ubuntu 12.04, Ignite 1.4, Java 1.8.0_40-b26 (HotSpot 
> 64-Bit)
>Reporter: Noam Liran
>Assignee: Semen Boikov
> Fix For: 1.6
>
>
> Hi,
> We're starting to use Ignite in one of our environments and we've encountered 
> some strange behaviour in one of our test cases.
> # Start two nodes at the same time.
> # Each nodes should initialize a cache with the following parameters:
> ## Cache mode: REPLICATED / PARTITIONED
> ## Atomicity mode: TRANSACTIONAL
> # Both nodes run the following code:
> {code}
> System.out.println("Sleeping before..");
> Thread.sleep(5000);
> List locks = new ArrayList<>();
> System.out.println("Acquiring...");
> for (int lockId = 0; lockId < 4; lockId++) {
> String lockName = "LOCK_" + lockId;
> Lock lock = cache.lock(lockName);
> locks.add(lock);
> lock.lock();
> }
> System.out.println("Acquired!");
> Thread.sleep(2);
> System.out.println("Done");
> {code}
> # Node 1 acquires all the relevant locks and waits a while.
> # Node 2 tries to acquire the locks and is blocked.
> # Node 1 eventually quits while holding the locks.
> # Node 2 never gains control of the locks even though they're abandoned.
> When we try the same with a looped tryLock everything seems to work.
> Our Ignite configuration is pretty straightforward:
> # Regular TCP discovery
> # No checkpointing SPI
> # No collision SPI
> # Always failover SPI
> # CONTINUOUS deployment mode



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

[jira] [Created] (IGNITE-2073) GridLocalAtomicCache cannot be cast to GridDhtCacheAdapter

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2073:
--

 Summary: GridLocalAtomicCache cannot be cast to GridDhtCacheAdapter
 Key: IGNITE-2073
 URL: https://issues.apache.org/jira/browse/IGNITE-2073
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov


I have such cache configuration
{code}







java.util.UUID
org.my.tester.sql.Car



{code}
When I'm doing SQL "select * from Car" via REST I'm got:
{code}
Error: 
org.apache.ignite.internal.processors.cache.local.atomic.GridLocalAtomicCache 
cannot be cast to 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter
{code}



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

[jira] [Created] (IGNITE-2075) We must deny access to admin page to unauthorized users

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2075:
--

 Summary: We must deny access to admin page to unauthorized users
 Key: IGNITE-2075
 URL: https://issues.apache.org/jira/browse/IGNITE-2075
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov






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

[jira] [Created] (IGNITE-2076) Failed to send time request to remote node

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2076:
--

 Summary: Failed to send time request to remote node
 Key: IGNITE-2076
 URL: https://issues.apache.org/jira/browse/IGNITE-2076
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov
Priority: Minor


I'm started to server nodes.

I getting such warning in case if I explicitly  set .

If I commenting this option then no warnings in the log.
{code}
[16:40:28,538][WARNING][grid-time-coordinator-#50%tester%][GridClockSyncProcessor]
 Failed to send time request to remote node 
[rmtNodeId=3e38be9c-eeae-46d8-9bd8-cbcb06ad4b0b, addr=0.0.0.0/0.0.0.0, 
port=31100]
[16:40:29,539][WARNING][grid-time-coordinator-#50%tester%][GridClockSyncProcessor]
 Failed to send time request to remote node 
[rmtNodeId=3e38be9c-eeae-46d8-9bd8-cbcb06ad4b0b, addr=0.0.0.0/0.0.0.0, 
port=31100]
[16:40:30,539][WARNING][grid-time-coordinator-#50%tester%][GridClockSyncProcessor]
 Failed to send time request to remote node 
[rmtNodeId=3e38be9c-eeae-46d8-9bd8-cbcb06ad4b0b, addr=0.0.0.0/0.0.0.0, 
port=31100]
[16:40:31,539][WARNING][grid-time-coordinator-#50%tester%][GridClockSyncProcessor]
 Failed to send time request to remote node 
[rmtNodeId=3e38be9c-eeae-46d8-9bd8-cbcb06ad4b0b, addr=0.0.0.0/0.0.0.0, 
port=31100]
[16:40:32,540][WARNING][grid-time-coordinator-#50%tester%][GridClockSyncProcessor]
 Failed to send time request to remote node 
[rmtNodeId=3e38be9c-eeae-46d8-9bd8-cbcb06ad4b0b, addr=0.0.0.0/0.0.0.0, 
port=31100]
{code}



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

[jira] [Commented] (IGNITE-1692) [Test] DataStreamProcessorSelfTest.testReplicated fails sometimes.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-1692:


Github user ilantukh closed the pull request at:

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


> [Test] DataStreamProcessorSelfTest.testReplicated fails sometimes.
> --
>
> Key: IGNITE-1692
> URL: https://issues.apache.org/jira/browse/IGNITE-1692
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ivan Veselovsky
>Assignee: Ilya Lantukh
>
> DataStreamProcessorSelfTest.testReplicated fails with ~7% probability with 
> the following error:
> {code}
> org.apache.ignite.IgniteCheckedException: Failed to find server node for 
> cache (all affinity nodes have left the grid or cache was stopped): null
> at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6979)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
> at 
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:311)
> at 
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:302)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:262)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListeners(GridFutureAdapter.java:250)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:380)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:346)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:334)
> at 
> org.apache.ignite.testframework.GridTestUtils$5.run(GridTestUtils.java:675)
> at 
> org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:966)
> at 
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> Caused by: org.apache.ignite.cache.CacheServerNotFoundException: Failed to 
> find server node for cache (all affinity nodes have left the grid or cache 
> was stopped): null
> at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1604)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheFutureImpl.convertException(IgniteCacheFutureImpl.java:56)
> at 
> org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:122)
> at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessorSelfTest$1.call(DataStreamProcessorSelfTest.java:232)
> at 
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> Caused by: 
> org.apache.ignite.internal.cluster.ClusterTopologyServerNotFoundException: 
> Failed to find server node for cache (all affinity nodes have left the grid 
> or cache was stopped): null
> at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.nodes(DataStreamerImpl.java:772)
> at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.load0(DataStreamerImpl.java:638)
> at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addDataInternal(DataStreamerImpl.java:547)
> at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addData(DataStreamerImpl.java:583)
> at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessorSelfTest$1.call(DataStreamProcessorSelfTest.java:226)
> at 
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {code}



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

ASF GitHub Bot commented on IGNITE-1864:


GitHub user ashutakGG opened a pull request:

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

IGNITE-1864 Custom TX manager configuration

https://issues.apache.org/jira/browse/IGNITE-1864

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

$ git pull https://github.com/ashutakGG/incubator-ignite 
ignite-1864-tx-manager

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

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


commit 7587b8b992968b71737185792fac305ac8b947f2
Author: ashutak 
Date:   2015-12-02T10:37:15Z

API

commit 935580686ba850e876a2556b044fd7d7b7d7e8c6
Author: ashutak 
Date:   2015-12-02T13:27:41Z

initial implementation

commit 75d575e997cf81f01b88f55bee1242ee9088bace
Author: ashutak 
Date:   2015-12-02T16:11:05Z

add tests on jta

commit 2e2f77aec15be230893530cc881cd2460bbd9529
Author: ashutak 
Date:   2015-12-02T16:11:24Z

clean up

commit 57abcfcc53a6e2b00900433750a5d18398c5b241
Author: ashutak 
Date:   2015-12-02T17:22:45Z

GridJtaLifecycleAwareSelfTest

commit 155ba5d60feb531c23dbe1e8583aabd86a9617dc
Author: ashutak 
Date:   2015-12-02T18:15:57Z

minor

commit d0c549c9e9b9582ab730ed1e40f4672cff848a8b
Author: ashutak 
Date:   2015-12-03T10:10:14Z

cfg validation




> 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.6
>
>
> 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-2050) NPE: Failed to reinitialize local partitions (preloading will be stopped)

[Artem Shutak (JIRA)]

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

Artem Shutak reassigned IGNITE-2050:


Assignee: Artem Shutak

> NPE: Failed to reinitialize local partitions (preloading will be stopped)
> -
>
> Key: IGNITE-2050
> URL: https://issues.apache.org/jira/browse/IGNITE-2050
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Artem Shutak
> Fix For: 1.5
>
>
> I was testing using my own tester and catched NPE:
> {code}
> [10:42:43,151][SEVERE][exchange-worker-#52%tester%][GridDhtPartitionsExchangeFuture]
>  Failed to reinitialize local partitions (preloading will be stopped): 
> GridDhtPartitionExchangeId [topVer=AffinityTo
> pologyVersion [topVer=3, minorTopVer=1], nodeId=97e00c67, 
> evt=DISCOVERY_CUSTOM_EVT]
> class org.apache.ignite.IgniteCheckedException: Type with name 'FSFMRule' 
> already indexed in cache 'bank_FSFMRule'.
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.addTypeByName(GridQueryProcessor.java:345)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:255)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:382)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1021)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1630)
> 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)
> [10:42:43,155][SEVERE][exchange-worker-#52%tester%][GridCachePartitionExchangeManager]
>  Runtime error caught during grid runnable execution: GridWorker 
> [name=partition-exchanger, gridName=tester, finis
> hed=false, isCancelled=false, hashCode=364597628, interrupted=false, 
> runner=exchange-worker-#52%tester%]
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onExchangeDone(GridCacheProcessor.java:1705)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:1098)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:87)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:334)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:861)
> 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)
> {code}



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

[jira] [Updated] (IGNITE-2075) We must deny access to admin page to unauthorized users

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-2075:
---
Description: Currently user may open this page using direct link and see 
table header  (was: Currently user may open this page and see table header)

> We must deny access to admin page to unauthorized users
> ---
>
> Key: IGNITE-2075
> URL: https://issues.apache.org/jira/browse/IGNITE-2075
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.6
>
>
> Currently user may open this page using direct link and see table header



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

[jira] [Updated] (IGNITE-2075) We must deny access to admin page to unauthorized users

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-2075:
---
Description: Currently user may see table header

> We must deny access to admin page to unauthorized users
> ---
>
> Key: IGNITE-2075
> URL: https://issues.apache.org/jira/browse/IGNITE-2075
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.6
>
>
> Currently user may see table header



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

[jira] [Updated] (IGNITE-2075) We must deny access to admin page to unauthorized users

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-2075:
---
Description: Currently user may open this page and see table header  (was: 
Currently user may see table header)

> We must deny access to admin page to unauthorized users
> ---
>
> Key: IGNITE-2075
> URL: https://issues.apache.org/jira/browse/IGNITE-2075
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.6
>
>
> Currently user may open this page and see table header



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

[jira] [Updated] (IGNITE-2072) Chart settings doesn't contain fields with UUID type

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-2072:
---
Issue Type: Bug  (was: Sub-task)
Parent: (was: IGNITE-843)

> Chart settings doesn't contain fields with UUID type
> 
>
> Key: IGNITE-2072
> URL: https://issues.apache.org/jira/browse/IGNITE-2072
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
>
> Start tester
> select * from Person



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

[jira] [Updated] (IGNITE-2072) Chart settings doesn't contain fields with UUID type

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-2072:
---
Issue Type: Sub-task  (was: Bug)
Parent: IGNITE-2047

> Chart settings doesn't contain fields with UUID type
> 
>
> Key: IGNITE-2072
> URL: https://issues.apache.org/jira/browse/IGNITE-2072
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
>
> Start tester
> select * from Person



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

[jira] [Comment Edited] (IGNITE-1270) Basic OSGi support for Ignite

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov edited comment on IGNITE-1270 at 12/3/15 1:16 PM:


mvn test -Dtest=IgniteOsgiTestSuite -DfailIfNoTests=false

See logs in attachment.


was (Author: yzhdanov):
mvn test -Dtest=IgniteOsgiTestSuite -DfailIfNoTests=false

{noformat}

---
 T E S T S
---
Running org.apache.ignite.osgi.IgniteOsgiTestSuite
SLF4J: The requested version 1.6 by your slf4j binding is not compatible with 
[1.5.5, 1.5.6, 1.5.7, 1.5.8, 1.5.9, 1.5.10, 1.5.11]
SLF4J: See http://www.slf4j.org/codes.html#version_mismatch for further details.
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in 
[jar:file:/Users/yzhdanov/.m2/repository/org/apache/karaf/org.apache.karaf.client/4.0.2/org.apache.karaf.client-4.0.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in 
[jar:file:/Users/yzhdanov/.m2/repository/org/ops4j/pax/logging/pax-logging-api/1.8.4/pax-logging-api-1.8.4.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2015-12-03 17:09:37,658 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
org.ops4j.pax.url.mvn.cfg
2015-12-03 17:09:37,663 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
org.apache.karaf.jaas.cfg
2015-12-03 17:09:37,668 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
profile.cfg
2015-12-03 17:09:37,672 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
org.apache.karaf.kar.cfg
2015-12-03 17:09:37,676 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
org.apache.karaf.shell.cfg
2015-12-03 17:09:37,680 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
org.apache.felix.fileinstall-deploy.cfg
2015-12-03 17:09:40,969 | WARN  | pool-7-thread-1  | AetherBasedResolver
  | 1 - org.ops4j.pax.logging.pax-logging-api - 1.8.4 | Error resolving 
artifactorg.apache.ignite:ignite-osgi-karaf:xml:features:1.5.0-SNAPSHOT:Could 
not find artifact 
org.apache.ignite:ignite-osgi-karaf:xml:features:1.5.0-SNAPSHOT in apache 
(http://repository.apache.org/content/groups/snapshots-group/)
shaded.org.eclipse.aether.resolution.ArtifactResolutionException: Could not 
find artifact org.apache.ignite:ignite-osgi-karaf:xml:features:1.5.0-SNAPSHOT 
in apache (http://repository.apache.org/content/groups/snapshots-group/)
at 
shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
shaded.org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:573)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:528)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:506)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:481)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:123)[7:org.ops4j.pax.url.mvn:2.4.3]
at java.net.URL.openStream(URL.java:1037)[:1.7.0_40]
at 
org.apache.karaf.features.internal.service.RepositoryImpl.load(RepositoryImpl.java:80)[8:org.apache.karaf.features.core:4.0.2]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.loadRepository(FeaturesServiceImpl.java:391)[8:org.apache.karaf.features.core:4.0.2]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.addRepository(FeaturesServiceImpl.java:411)[8:org.apache.karaf.features.core:4.0.2]
at 

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

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-1270:
--
Attachment: osgi-tests.log

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



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

[jira] [Updated] (IGNITE-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:all-tabpanel
 ]

Andrey Gura updated IGNITE-2080:

Description: 
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}

In order ot reproduce it need to do following:
# Copy {{benchmark-offheap.properties}} file into {{modules/yardstick/config}} 
directory.
# Build yardstick {{mvn -B clean package -Prelease -DskipTests -pl 
modules/yardstick -am}}
# Run benchmark {{./bin/benchmark-drivers-start.sh 
config/benchmark-offheap.properties}} (do it from {{yardstick}} module 
directory)

The problem isn't related with JIT (reproduces with -Xint option).

Also see attached files (core dump and logs).

  was:
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}

In order ot reproduce it need to do following:
# Copy {{benchmark-offheap.properties}} file into {{modules/yardstick/config}} 
directory.
# Build yardstick {{mvn -B clean package -Prelease -DskipTests -pl 
modules/yardstick -am}}
# Run benchmark {{./bin/benchmark-drivers-start.sh 
config/benchmark-offheap.properties}} (do it from {{yardstick}} module 
directory)

The problem isn't related with JIT (reproduces with -Xint option).

Also see attached files (core dump and logs).


> 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
>
> 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}
> In order ot reproduce it need to do following:
> # Copy {{benchmark-offheap.properties}} file into 
> {{modules/yardstick/config}} directory.
> # Build yardstick {{mvn -B clean package -Prelease -DskipTests -pl 
> modules/yardstick -am}}
> # Run benchmark {{./bin/benchmark-drivers-start.sh 
> config/benchmark-offheap.properties}} (do it from {{yardstick}} module 
> directory)
> The problem isn't related with JIT (reproduces with -Xint option).
> Also see attached files (core dump and logs).



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

[jira] [Updated] (IGNITE-1810) Upgrade ignite-aws dependencies (HttpClient and AWS SDK)

[JIRA]

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

Raúl Kripalani updated IGNITE-1810:
---
Fix Version/s: (was: 1.6)
   1.5

> Upgrade ignite-aws dependencies (HttpClient and AWS SDK)
> 
>
> Key: IGNITE-1810
> URL: https://issues.apache.org/jira/browse/IGNITE-1810
> Project: Ignite
>  Issue Type: Improvement
>  Components: aws, osgi
>Reporter: Raúl Kripalani
>Assignee: Raúl Kripalani
> Fix For: 1.5
>
>
> We need to upgrade the HttpClient and AWS SDK dependencies in ignite-aws. 
> They are very old:
> * AWS SDK 1.3.21.1 => 1.10.29
> * HttpClient 4.2.3 => 4.5.1
> * HttpCore 4.2.3 => 4.4.3
> These upgrades are needed by the OSGi integration.



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

[jira] [Closed] (IGNITE-2077) .Net: Create builds on TeamCity

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn closed IGNITE-2077.
---

> .Net: Create builds on TeamCity
> ---
>
> Key: IGNITE-2077
> URL: https://issues.apache.org/jira/browse/IGNITE-2077
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.5
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: 1.5
>
>
> http://204.14.53.153/project.html?projectId=IgniteTests=projectOverview
> * Platform .NET
> * Platform .NET Long Running



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

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

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov commented on IGNITE-1270:
---

mvn test -Dtest=IgniteOsgiTestSuite -DfailIfNoTests=false

{noformat}

---
 T E S T S
---
Running org.apache.ignite.osgi.IgniteOsgiTestSuite
SLF4J: The requested version 1.6 by your slf4j binding is not compatible with 
[1.5.5, 1.5.6, 1.5.7, 1.5.8, 1.5.9, 1.5.10, 1.5.11]
SLF4J: See http://www.slf4j.org/codes.html#version_mismatch for further details.
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in 
[jar:file:/Users/yzhdanov/.m2/repository/org/apache/karaf/org.apache.karaf.client/4.0.2/org.apache.karaf.client-4.0.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in 
[jar:file:/Users/yzhdanov/.m2/repository/org/ops4j/pax/logging/pax-logging-api/1.8.4/pax-logging-api-1.8.4.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2015-12-03 17:02:12,301 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
jmx.acl.cfg
2015-12-03 17:02:12,308 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
org.apache.karaf.features.cfg
2015-12-03 17:02:12,312 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
org.apache.karaf.shell.cfg
2015-12-03 17:02:12,317 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
org.ops4j.pax.url.mvn.cfg
2015-12-03 17:02:12,321 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
org.apache.karaf.log.cfg
2015-12-03 17:02:12,325 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
org.apache.karaf.jaas.cfg
2015-12-03 17:02:12,331 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
org.apache.karaf.features.repos.cfg
2015-12-03 17:02:12,337 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
profile.cfg
2015-12-03 17:02:12,342 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
org.apache.felix.fileinstall-deploy.cfg
2015-12-03 17:02:17,686 | WARN  | pool-7-thread-1  | AetherBasedResolver
  | 1 - org.ops4j.pax.logging.pax-logging-api - 1.8.4 | Error resolving 
artifactorg.apache.ignite:ignite-osgi-karaf:xml:features:1.5.0-SNAPSHOT:Could 
not find artifact 
org.apache.ignite:ignite-osgi-karaf:xml:features:1.5.0-SNAPSHOT in apache 
(http://repository.apache.org/content/groups/snapshots-group/)
shaded.org.eclipse.aether.resolution.ArtifactResolutionException: Could not 
find artifact org.apache.ignite:ignite-osgi-karaf:xml:features:1.5.0-SNAPSHOT 
in apache (http://repository.apache.org/content/groups/snapshots-group/)
at 
shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
shaded.org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:573)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:528)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:506)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:481)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:123)[7:org.ops4j.pax.url.mvn:2.4.3]
at java.net.URL.openStream(URL.java:1037)[:1.7.0_40]
at 
org.apache.karaf.features.internal.service.RepositoryImpl.load(RepositoryImpl.java:80)[8:org.apache.karaf.features.core:4.0.2]
at 

[jira] [Resolved] (IGNITE-2042) Collocated mode is broken for IgniteSet with BinaryMarshaller

[Semen Boikov (JIRA)]

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

Semen Boikov resolved IGNITE-2042.
--
   Resolution: Fixed
Fix Version/s: 1.5

Fixed in 1.5 (commit 50f6c01).

> Collocated mode is broken for IgniteSet with BinaryMarshaller
> -
>
> Key: IGNITE-2042
> URL: https://issues.apache.org/jira/browse/IGNITE-2042
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 1.5
>Reporter: Semen Boikov
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: 1.5
>
>
> If BinaryMarshaller is used then 'collocated' mode does not work for 
> IgniteSet. To reproduce run 
> GridCachePartitionedAtomicSetSelfTest.testIteratorCollocated.
> Looks like the same issue exists for IgniteQueue, need to check if there are 
> test verifying this.



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

[jira] [Assigned] (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:all-tabpanel
 ]

Andrey Gura reassigned IGNITE-2080:
---

Assignee: Andrey Gura

> 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
>
> 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}
> In order ot reproduce it need to do following:
> # Copy {{benchmark-offheap.properties}} file into 
> {{modules/yardstick/config}} directory.
> # Build yardstick {{mvn -B clean package -Prelease-DskipTests -pl 
> modules/yardstick -am}}
> # Run benchmark {{./bin/benchmark-drivers-start.sh 
> config/benchmark-offheap.properties}} (do it from {{yardstick}} module 
> directory)
> Also see attached files (core dump and logs).



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

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

[JIRA]

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

Raúl Kripalani updated IGNITE-1270:
---
Fix Version/s: (was: 1.6)
   1.5

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



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

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

[JIRA]

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

Raúl Kripalani updated IGNITE-1527:
---
Fix Version/s: (was: 1.6)
   1.5

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



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

[jira] [Closed] (IGNITE-2042) Collocated mode is broken for IgniteSet with BinaryMarshaller

[Semen Boikov (JIRA)]

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

Semen Boikov closed IGNITE-2042.

Assignee: (was: Semen Boikov)

> Collocated mode is broken for IgniteSet with BinaryMarshaller
> -
>
> Key: IGNITE-2042
> URL: https://issues.apache.org/jira/browse/IGNITE-2042
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 1.5
>Reporter: Semen Boikov
>Priority: Critical
> Fix For: 1.5
>
>
> If BinaryMarshaller is used then 'collocated' mode does not work for 
> IgniteSet. To reproduce run 
> GridCachePartitionedAtomicSetSelfTest.testIteratorCollocated.
> Looks like the same issue exists for IgniteQueue, need to check if there are 
> test verifying this.



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

[jira] [Updated] (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:all-tabpanel
 ]

Andrey Gura updated IGNITE-2080:

Description: 
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  
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$18.apply()Lorg/apache/ignite/internal/IgniteInternalFuture;+4
j  
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$18.apply()Ljava/lang/Object;+1
j  
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(Lorg/apache/ignite/internal/util/typedef/CO;)Lorg/apache/ignite/internal/IgniteInternalFuture;+86
j  
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsync0(Ljava/util/Map;Ljava/util/Map;[Ljava/lang/Object;Ljava/util/Map;Ljava/util/Map;ZZ[Lorg/apache/ignite/internal/processors/cache/CacheEntryPredicate;Z)Lorg/apache/ignite/internal/IgniteInternalFuture;+331
j  

[jira] [Comment Edited] (IGNITE-2077) .Net: Create builds on TeamCity

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn edited comment on IGNITE-2077 at 12/3/15 1:01 PM:
--

Projects created: 
http://204.14.53.153/viewType.html?buildTypeId=IgniteTests_IgnitePlatformNet
http://204.14.53.153/viewType.html?buildTypeId=IgniteTests_IgnitePlatformNetLongRunnin


was (Author: ptupitsyn):
Project created: 
http://204.14.53.153/viewType.html?buildTypeId=IgniteTests_IgnitePlatformNet

> .Net: Create builds on TeamCity
> ---
>
> Key: IGNITE-2077
> URL: https://issues.apache.org/jira/browse/IGNITE-2077
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.5
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: 1.5
>
>
> http://204.14.53.153/project.html?projectId=IgniteTests=projectOverview
> * Platform .NET
> * Platform .NET Long Running



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

[jira] [Resolved] (IGNITE-2077) .Net: Create builds on TeamCity

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn resolved IGNITE-2077.
-
Resolution: Done

> .Net: Create builds on TeamCity
> ---
>
> Key: IGNITE-2077
> URL: https://issues.apache.org/jira/browse/IGNITE-2077
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.5
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: 1.5
>
>
> http://204.14.53.153/project.html?projectId=IgniteTests=projectOverview
> * Platform .NET
> * Platform .NET Long Running



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

[jira] [Updated] (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:all-tabpanel
 ]

Andrey Gura updated IGNITE-2080:

Description: 
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}

In order ot reproduce it need to do following:
# Copy {{benchmark-offheap.properties}} file into {{modules/yardstick/config}} 
directory.
# Build yardstick {{mvn -B clean package -Prelease -DskipTests -pl 
modules/yardstick -am}}
# Run benchmark {{./bin/benchmark-drivers-start.sh 
config/benchmark-offheap.properties}} (do it from {{yardstick}} module 
directory)

Also see attached files (core dump and logs).

  was:
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}

In order ot reproduce it need to do following:
# Copy {{benchmark-offheap.properties}} file into {{modules/yardstick/config}} 
directory.
# Build yardstick {{mvn -B clean package -Prelease-DskipTests -pl 
modules/yardstick -am}}
# Run benchmark {{./bin/benchmark-drivers-start.sh 
config/benchmark-offheap.properties}} (do it from {{yardstick}} module 
directory)

Also see attached files (core dump and logs).


> 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
>
> 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}
> In order ot reproduce it need to do following:
> # Copy {{benchmark-offheap.properties}} file into 
> {{modules/yardstick/config}} directory.
> # Build yardstick {{mvn -B clean package -Prelease -DskipTests -pl 
> modules/yardstick -am}}
> # Run benchmark {{./bin/benchmark-drivers-start.sh 
> config/benchmark-offheap.properties}} (do it from {{yardstick}} module 
> directory)
> Also see attached files (core dump and logs).



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

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

[Andrey Gura (JIRA)]

Andrey Gura created IGNITE-2080:
---

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


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}

In order ot reproduce it need to do following:
# Copy {{benchmark-offheap.properties}} file into {{modules/yardstick/config}} 
directory.
# Build yardstick {{mvn -B clean package -Prelease-DskipTests -pl 
modules/yardstick -am}}
# Run benchmark {{./bin/benchmark-drivers-start.sh 
config/benchmark-offheap.properties}} (do it from {{yardstick}} module 
directory)

Also see attached files (core dump and logs).



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

[jira] [Updated] (IGNITE-1529) Support server mode with Ignite OSGi without Peer Classloading

[JIRA]

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

Raúl Kripalani updated IGNITE-1529:
---
Fix Version/s: (was: 1.6)
   1.5

> Support server mode with Ignite OSGi without Peer Classloading
> --
>
> Key: IGNITE-1529
> URL: https://issues.apache.org/jira/browse/IGNITE-1529
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Reporter: Raúl Kripalani
>Assignee: Raúl Kripalani
> Fix For: 1.5
>
>
> Server mode means replication of user classes. Design a way for allow user 
> bundles to contribute classes to ignite-core, without using 
> DynamicImport-Package: *



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

[jira] [Updated] (IGNITE-1877) Make Ignite classloading OSGi-friendly & provide different classloading strategies

[JIRA]

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

Raúl Kripalani updated IGNITE-1877:
---
Fix Version/s: (was: 1.6)
   1.5

> Make Ignite classloading OSGi-friendly & provide different classloading 
> strategies
> --
>
> Key: IGNITE-1877
> URL: https://issues.apache.org/jira/browse/IGNITE-1877
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general, osgi
>Reporter: Dmitriy Setrakyan
>Assignee: Raúl Kripalani
> Fix For: 1.5
>
>
> The design is described here: 
> https://cwiki.apache.org/confluence/display/IGNITE/OSGI+Compatibility



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

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

[JIRA]

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

Raúl Kripalani resolved IGNITE-1528.

Resolution: Fixed

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




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

[jira] [Comment Edited] (IGNITE-1270) Basic OSGi support for Ignite

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov edited comment on IGNITE-1270 at 12/3/15 1:12 PM:


mvn test -Dtest=IgniteOsgiTestSuite -DfailIfNoTests=false

{noformat}

---
 T E S T S
---
Running org.apache.ignite.osgi.IgniteOsgiTestSuite
SLF4J: The requested version 1.6 by your slf4j binding is not compatible with 
[1.5.5, 1.5.6, 1.5.7, 1.5.8, 1.5.9, 1.5.10, 1.5.11]
SLF4J: See http://www.slf4j.org/codes.html#version_mismatch for further details.
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in 
[jar:file:/Users/yzhdanov/.m2/repository/org/apache/karaf/org.apache.karaf.client/4.0.2/org.apache.karaf.client-4.0.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in 
[jar:file:/Users/yzhdanov/.m2/repository/org/ops4j/pax/logging/pax-logging-api/1.8.4/pax-logging-api-1.8.4.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2015-12-03 17:09:37,658 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
org.ops4j.pax.url.mvn.cfg
2015-12-03 17:09:37,663 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
org.apache.karaf.jaas.cfg
2015-12-03 17:09:37,668 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
profile.cfg
2015-12-03 17:09:37,672 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
org.apache.karaf.kar.cfg
2015-12-03 17:09:37,676 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
org.apache.karaf.shell.cfg
2015-12-03 17:09:37,680 | INFO  | FelixStartLevel  | fileinstall
  | 4 - org.apache.felix.fileinstall - 3.5.0 | Creating configuration from 
org.apache.felix.fileinstall-deploy.cfg
2015-12-03 17:09:40,969 | WARN  | pool-7-thread-1  | AetherBasedResolver
  | 1 - org.ops4j.pax.logging.pax-logging-api - 1.8.4 | Error resolving 
artifactorg.apache.ignite:ignite-osgi-karaf:xml:features:1.5.0-SNAPSHOT:Could 
not find artifact 
org.apache.ignite:ignite-osgi-karaf:xml:features:1.5.0-SNAPSHOT in apache 
(http://repository.apache.org/content/groups/snapshots-group/)
shaded.org.eclipse.aether.resolution.ArtifactResolutionException: Could not 
find artifact org.apache.ignite:ignite-osgi-karaf:xml:features:1.5.0-SNAPSHOT 
in apache (http://repository.apache.org/content/groups/snapshots-group/)
at 
shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
shaded.org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:573)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:528)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:506)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:481)[7:org.ops4j.pax.url.mvn:2.4.3]
at 
org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:123)[7:org.ops4j.pax.url.mvn:2.4.3]
at java.net.URL.openStream(URL.java:1037)[:1.7.0_40]
at 
org.apache.karaf.features.internal.service.RepositoryImpl.load(RepositoryImpl.java:80)[8:org.apache.karaf.features.core:4.0.2]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.loadRepository(FeaturesServiceImpl.java:391)[8:org.apache.karaf.features.core:4.0.2]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.addRepository(FeaturesServiceImpl.java:411)[8:org.apache.karaf.features.core:4.0.2]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.addRepository(FeaturesServiceImpl.java:402)[8:org.apache.karaf.features.core:4.0.2]
at 

[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-2079:
--

Hotfix applied. 

Left: add GridCacheQueryResponse unmarshalled fail handling 
& test on GridCacheQueryResponse & GridCacheQueryRequest 

> GridCacheIoManager eats exception trail if it falls into the directed case
> --
>
> Key: IGNITE-2079
> URL: https://issues.apache.org/jira/browse/IGNITE-2079
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>
> During a recent test I have run into an issue where a storage disabled client 
> of a Fabric that has services deployed for which the client does not have the 
> fabric in the class path failed with the following exception:
> com.workday.fabric.HelloWorldTest STANDARD_ERROR
> Nov 08, 2015 6:15:20 PM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Failed to process message 
> [senderId=30775397-457a-400f-a6c9-077c9e762d61, messageType=class 
> o.a.i.i.processors.cache.query.GridCacheQueryResponse]
> class org.apache.ignite.IgniteCheckedException: Failed to send response to 
> node. Unsupported direct type [message=GridCacheQueryResponse [finished=true, 
> reqId=5, err=null, fields=false, metadata=null]]
>  at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:546)
>  at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:272)
>  at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:77)
>  at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1078)
>  at 
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2302)
>  at 
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:992)
>  at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:106)
>  at 
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:961)
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  at java.lang.Thread.run(Thread.java:745)
> This unfortunately gives me 0 information to work on to resolve the issue, as 
> the original unmarshalling exception (from the JdkMarshaller) was eaten as 
> this is the code for the default process failed message:
> default:
> throw new IgniteCheckedException("Failed to send response to node. 
> Unsupported direct type [message="
> + msg + "]");
> }
> you should also include the original stack from msg.getError() in the newly 
> thrown IgniteCheckedException



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

[jira] [Updated] (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:all-tabpanel
 ]

Andrey Gura updated IGNITE-2080:

Description: 
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}

In order ot reproduce it need to do following:
# Copy {{benchmark-offheap.properties}} file into {{modules/yardstick/config}} 
directory.
# Build yardstick {{mvn -B clean package -Prelease -DskipTests -pl 
modules/yardstick -am}}
# Run benchmark {{./bin/benchmark-drivers-start.sh 
config/benchmark-offheap.properties}} (do it from {{yardstick}} module 
directory)

The problem isn't related with JIT (reproduces with -Xint option).

Also see attached files (core dump and logs).

  was:
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}

In order ot reproduce it need to do following:
# Copy {{benchmark-offheap.properties}} file into {{modules/yardstick/config}} 
directory.
# Build yardstick {{mvn -B clean package -Prelease -DskipTests -pl 
modules/yardstick -am}}
# Run benchmark {{./bin/benchmark-drivers-start.sh 
config/benchmark-offheap.properties}} (do it from {{yardstick}} module 
directory)

Also see attached files (core dump and logs).


> 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
>
> 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}
> In order ot reproduce it need to do following:
> # Copy {{benchmark-offheap.properties}} file into 
> {{modules/yardstick/config}} directory.
> # Build yardstick {{mvn -B clean package -Prelease -DskipTests -pl 
> modules/yardstick -am}}
> # Run benchmark {{./bin/benchmark-drivers-start.sh 
> config/benchmark-offheap.properties}} (do it from {{yardstick}} module 
> directory)
> The problem isn't related with JIT (reproduces with -Xint option).
> Also see attached files (core dump and logs).



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

[jira] [Resolved] (IGNITE-1877) Make Ignite classloading OSGi-friendly & provide different classloading strategies

[JIRA]

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

Raúl Kripalani resolved IGNITE-1877.

Resolution: Fixed

> Make Ignite classloading OSGi-friendly & provide different classloading 
> strategies
> --
>
> Key: IGNITE-1877
> URL: https://issues.apache.org/jira/browse/IGNITE-1877
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general, osgi
>Reporter: Dmitriy Setrakyan
>Assignee: Raúl Kripalani
> Fix For: 1.5
>
>
> The design is described here: 
> https://cwiki.apache.org/confluence/display/IGNITE/OSGI+Compatibility



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

[jira] [Updated] (IGNITE-2042) Collocated mode is broken for IgniteSet with BinaryMarshaller

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-2042:
-
Summary: Collocated mode is broken for IgniteSet with BinaryMarshaller  
(was: Collocated mode is broken for IgniteSet witn BinaryMarshaller)

> Collocated mode is broken for IgniteSet with BinaryMarshaller
> -
>
> Key: IGNITE-2042
> URL: https://issues.apache.org/jira/browse/IGNITE-2042
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 1.5
>Reporter: Semen Boikov
>Assignee: Semen Boikov
>Priority: Critical
>
> If BinaryMarshaller is used then 'collocated' mode does not work for 
> IgniteSet. To reproduce run 
> GridCachePartitionedAtomicSetSelfTest.testIteratorCollocated.
> Looks like the same issue exists for IgniteQueue, need to check if there are 
> test verifying this.



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

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

[JIRA]

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

Raúl Kripalani updated IGNITE-1528:
---
Fix Version/s: (was: 1.6)
   1.5

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




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

[jira] [Resolved] (IGNITE-1527) Add OSGi manifest headers to all ignite-core + basic bundles and Karaf features

[JIRA]

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

Raúl Kripalani resolved IGNITE-1527.

Resolution: Fixed

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



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

[jira] [Resolved] (IGNITE-1529) Support server mode with Ignite OSGi without Peer Classloading

[JIRA]

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

Raúl Kripalani resolved IGNITE-1529.

Resolution: Fixed

> Support server mode with Ignite OSGi without Peer Classloading
> --
>
> Key: IGNITE-1529
> URL: https://issues.apache.org/jira/browse/IGNITE-1529
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Reporter: Raúl Kripalani
>Assignee: Raúl Kripalani
> Fix For: 1.5
>
>
> Server mode means replication of user classes. Design a way for allow user 
> bundles to contribute classes to ignite-core, without using 
> DynamicImport-Package: *



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

[jira] [Updated] (IGNITE-2070) "Back to Clusters" link doesn't work on Security page

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2070:
-
Fix Version/s: (was: 1.6)
   1.5

> "Back to Clusters" link doesn't work on Security page
> -
>
> Key: IGNITE-2070
> URL: https://issues.apache.org/jira/browse/IGNITE-2070
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
>
> Nothing happens when I clicking on it.



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

[jira] [Updated] (IGNITE-2040) Please generate java classes for all metadata linked with caches

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2040:
-
Fix Version/s: (was: 1.5)
   1.6

> Please generate java classes for all metadata linked with caches
> 
>
> Key: IGNITE-2040
> URL: https://issues.apache.org/jira/browse/IGNITE-2040
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 1.6
>
>
> Currently we generates java classes only if cache has store settings. Will be 
> much useful  to generate them always if they are linked to cluster cache.



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

[jira] [Updated] (IGNITE-2073) GridLocalAtomicCache cannot be cast to GridDhtCacheAdapter

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2073:
-
Fix Version/s: 1.5

> GridLocalAtomicCache cannot be cast to GridDhtCacheAdapter
> --
>
> Key: IGNITE-2073
> URL: https://issues.apache.org/jira/browse/IGNITE-2073
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
>
> I have such cache configuration
> {code}
> 
> 
> 
> 
> 
> 
> java.util.UUID
> org.my.tester.sql.Car
> 
> 
> 
> {code}
> When I'm doing SQL "select * from Car" via REST I'm got:
> {code}
> Error: 
> org.apache.ignite.internal.processors.cache.local.atomic.GridLocalAtomicCache 
> cannot be cast to 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter
> {code}



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

[jira] [Updated] (IGNITE-2075) We must deny access to admin page to unauthorized users

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2075:
-
Fix Version/s: (was: 1.6)
   1.5

> We must deny access to admin page to unauthorized users
> ---
>
> Key: IGNITE-2075
> URL: https://issues.apache.org/jira/browse/IGNITE-2075
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
>
> Currently user may open this page using direct link and see table header



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

[jira] [Updated] (IGNITE-2073) GridLocalAtomicCache cannot be cast to GridDhtCacheAdapter

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-2073:
-
Affects Version/s: 1.5

> GridLocalAtomicCache cannot be cast to GridDhtCacheAdapter
> --
>
> Key: IGNITE-2073
> URL: https://issues.apache.org/jira/browse/IGNITE-2073
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
>
> I have such cache configuration
> {code}
> 
> 
> 
> 
> 
> 
> java.util.UUID
> org.my.tester.sql.Car
> 
> 
> 
> {code}
> When I'm doing SQL "select * from Car" via REST I'm got:
> {code}
> Error: 
> org.apache.ignite.internal.processors.cache.local.atomic.GridLocalAtomicCache 
> cannot be cast to 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter
> {code}



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

[jira] [Updated] (IGNITE-1830) May be place check mark at the left from text in dropdown?

[Alexey Kuznetsov (JIRA)]

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

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

> May be place check mark at the left from text in dropdown?
> --
>
> Key: IGNITE-1830
> URL: https://issues.apache.org/jira/browse/IGNITE-1830
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
> Attachments: ig-1830.png
>
>
> Currently if item text is longer then the width of dropdown then ellipsis 
> ('...') printed at the right side of the item and check mark crosses it. 
> Looks a bit ugly.
> Please see attachment.



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

[jira] [Updated] (IGNITE-1830) May be place check mark at the left from text in dropdown?

[Alexey Kuznetsov (JIRA)]

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

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

> May be place check mark at the left from text in dropdown?
> --
>
> Key: IGNITE-1830
> URL: https://issues.apache.org/jira/browse/IGNITE-1830
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
> Attachments: ig-1830.png
>
>
> Currently if item text is longer then the width of dropdown then ellipsis 
> ('...') printed at the right side of the item and check mark crosses it. 
> Looks a bit ugly.
> Please see attachment.



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

[jira] [Updated] (IGNITE-1869) Generate separate cache for each metadata loaded from DB

[Alexey Kuznetsov (JIRA)]

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

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

> Generate separate cache for each metadata loaded from DB
> 
>
> Key: IGNITE-1869
> URL: https://issues.apache.org/jira/browse/IGNITE-1869
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Alexey Kuznetsov
> Fix For: 1.5
>
>
> It think will be useful to generate separate cache for each metadata loaded 
> from DB.
> In this case web console will generate a cache + metadata linked to it.
> User could point already created cache as a template for generation.
> We could have some checkbox for it.



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

[jira] [Updated] (IGNITE-1829) We must use short name for packages in metadata dropdown list

[Alexey Kuznetsov (JIRA)]

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

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

> We must use short name for packages in metadata dropdown list
> -
>
> Key: IGNITE-1829
> URL: https://issues.apache.org/jira/browse/IGNITE-1829
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Critical
> Fix For: 1.6
>
> Attachments: ig-1829.png
>
>
> Current view is uncomfortable because user don't see class name.
> Please see attachment.



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

[jira] [Updated] (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:all-tabpanel
 ]

Andrey Gura updated IGNITE-2080:

Description: 
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  
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$18.apply()Lorg/apache/ignite/internal/IgniteInternalFuture;+4
j  
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$18.apply()Ljava/lang/Object;+1
j  
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(Lorg/apache/ignite/internal/util/typedef/CO;)Lorg/apache/ignite/internal/IgniteInternalFuture;+86
j  
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsync0(Ljava/util/Map;Ljava/util/Map;[Ljava/lang/Object;Ljava/util/Map;Ljava/util/Map;ZZ[Lorg/apache/ignite/internal/processors/cache/CacheEntryPredicate;Z)Lorg/apache/ignite/internal/IgniteInternalFuture;+331
j  

[jira] [Updated] (IGNITE-1623) We need handle crashing of agent on every step of loading metadata from DB

[Alexey Kuznetsov (JIRA)]

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

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

> We need handle crashing of agent on every step of loading metadata from DB
> --
>
> Key: IGNITE-1623
> URL: https://issues.apache.org/jira/browse/IGNITE-1623
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.6
>
>
> We need to verify connection state on every step including fetching info 
> about scheme and tables.



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

[jira] [Updated] (IGNITE-1919) Blinking on Prev in load metadata dialog

[Alexey Kuznetsov (JIRA)]

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

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

> Blinking on Prev in load metadata dialog
> 
>
> Key: IGNITE-1919
> URL: https://issues.apache.org/jira/browse/IGNITE-1919
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
>
> To reproduce please do Prev in Load metadata dialog.



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

[jira] [Resolved] (IGNITE-1928) Area chart shows incorrect graph on first page in special case

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov resolved IGNITE-1928.
--
Resolution: Incomplete
  Assignee: Pavel Konstantinov

Actually chart is correct or I do not understand what is wrong.
Please add more details what is wrong.

> Area chart shows incorrect graph on first page in special case
> --
>
> Key: IGNITE-1928
> URL: https://issues.apache.org/jira/browse/IGNITE-1928
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
> Attachments: ig-1928.png
>
>
> I'm tested area chart with this query
> {code}
> select _key, _val, random() from car
> {code}
> Please see the result in attachment



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

[jira] [Updated] (IGNITE-1842) Add dropdown list of existing fields for setting it in index

[Alexey Kuznetsov (JIRA)]

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

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

> Add dropdown list of existing fields for setting it in index
> 
>
> Key: IGNITE-1842
> URL: https://issues.apache.org/jira/browse/IGNITE-1842
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
>
> If user already set field list will be useful to select existing field from 
> dropdown list for index.



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

[jira] [Updated] (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:all-tabpanel
 ]

Andrey Gura updated IGNITE-2080:

Description: 
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  
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$18.apply()Lorg/apache/ignite/internal/IgniteInternalFuture;+4
j  
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$18.apply()Ljava/lang/Object;+1
j  
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(Lorg/apache/ignite/internal/util/typedef/CO;)Lorg/apache/ignite/internal/IgniteInternalFuture;+86
j  
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsync0(Ljava/util/Map;Ljava/util/Map;[Ljava/lang/Object;Ljava/util/Map;Ljava/util/Map;ZZ[Lorg/apache/ignite/internal/processors/cache/CacheEntryPredicate;Z)Lorg/apache/ignite/internal/IgniteInternalFuture;+331
j  

[jira] [Updated] (IGNITE-1842) Add dropdown list of existing fields for setting it in index

[Alexey Kuznetsov (JIRA)]

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

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

> Add dropdown list of existing fields for setting it in index
> 
>
> Key: IGNITE-1842
> URL: https://issues.apache.org/jira/browse/IGNITE-1842
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
>
> If user already set field list will be useful to select existing field from 
> dropdown list for index.



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

[jira] [Updated] (IGNITE-1842) Add dropdown list of existing fields for setting it in index

[Alexey Kuznetsov (JIRA)]

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

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

> Add dropdown list of existing fields for setting it in index
> 
>
> Key: IGNITE-1842
> URL: https://issues.apache.org/jira/browse/IGNITE-1842
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
>
> If user already set field list will be useful to select existing field from 
> dropdown list for index.



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

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

Artem Shutak commented on IGNITE-1864:
--

Finished with an implementation. Waiting for TC.

> 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.6
>
>
> 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-2081) Javadoc: org.apache.ignite.yarn.utils has no description in overview-summary.html

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-2081:
-

 Summary: Javadoc: org.apache.ignite.yarn.utils has no description 
in overview-summary.html
 Key: IGNITE-2081
 URL: https://issues.apache.org/jira/browse/IGNITE-2081
 Project: Ignite
  Issue Type: Bug
  Components: documentation
Affects Versions: 1.5
Reporter: Sergey Kozlov
Assignee: Yakov Zhdanov
Priority: Trivial
 Fix For: 1.5


Open overview-summary.html and take a look on Yarn integration section:
org.apache.ignite.yarn.utils has no description



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

[jira] [Updated] (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:all-tabpanel
 ]

Andrey Gura updated IGNITE-2080:

Attachment: hs_err_pid10523.log
054424_0_localhost.log

> 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, 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] [Updated] (IGNITE-1805) Implement 'Reset' button for 'Load metadata from database' popup

[Alexey Kuznetsov (JIRA)]

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

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

> Implement 'Reset' button for 'Load metadata from database' popup
> 
>
> Key: IGNITE-1805
> URL: https://issues.apache.org/jira/browse/IGNITE-1805
> Project: Ignite
>  Issue Type: Bug
>  Components: UI
>Reporter: Prachi Garg
> Fix For: 1.5
>
>
> When trying to load the metadata from database, the fields in the popup 
> contain values that were previously used to load the metadata. We should 
> either have a reset button to clear the previous values, or the popup should 
> come up with clear fields every time it is launched.



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

[jira] [Updated] (IGNITE-1805) Implement 'Reset' button for 'Load metadata from database' popup

[Alexey Kuznetsov (JIRA)]

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

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

> Implement 'Reset' button for 'Load metadata from database' popup
> 
>
> Key: IGNITE-1805
> URL: https://issues.apache.org/jira/browse/IGNITE-1805
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Prachi Garg
> Fix For: 1.5
>
>
> When trying to load the metadata from database, the fields in the popup 
> contain values that were previously used to load the metadata. We should 
> either have a reset button to clear the previous values, or the popup should 
> come up with clear fields every time it is launched.



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

[jira] [Updated] (IGNITE-1201) Create tests for Web Console Agent

[Alexey Kuznetsov (JIRA)]

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

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

> Create tests for Web Console Agent
> --
>
> Key: IGNITE-1201
> URL: https://issues.apache.org/jira/browse/IGNITE-1201
> Project: Ignite
>  Issue Type: Bug
>Reporter: Sergey Evdokimov
>Assignee: Alexey Kuznetsov
> Attachments: ignite-843_4abc9f1_ignite-1201.patch
>
>
> Need tests for Web Control Center Agent. 
> Tests should simulate Web Control Center requests.



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

[jira] [Updated] (IGNITE-1869) Generate separate cache for each metadata loaded from DB

[Alexey Kuznetsov (JIRA)]

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

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

> Generate separate cache for each metadata loaded from DB
> 
>
> Key: IGNITE-1869
> URL: https://issues.apache.org/jira/browse/IGNITE-1869
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Alexey Kuznetsov
> Fix For: 1.5
>
>
> It think will be useful to generate separate cache for each metadata loaded 
> from DB.
> In this case web console will generate a cache + metadata linked to it.
> User could point already created cache as a template for generation.
> We could have some checkbox for it.



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

[jira] [Updated] (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:all-tabpanel
 ]

Andrey Gura updated IGNITE-2080:

Attachment: benchmark-offheap.properties

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

[jira] [Updated] (IGNITE-1623) We need handle crashing of agent on every step of loading metadata from DB

[Alexey Kuznetsov (JIRA)]

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

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

> We need handle crashing of agent on every step of loading metadata from DB
> --
>
> Key: IGNITE-1623
> URL: https://issues.apache.org/jira/browse/IGNITE-1623
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.6
>
>
> We need to verify connection state on every step including fetching info 
> about scheme and tables.



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

[jira] [Updated] (IGNITE-1919) Blinking on Prev in load metadata dialog

[Alexey Kuznetsov (JIRA)]

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

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

> Blinking on Prev in load metadata dialog
> 
>
> Key: IGNITE-1919
> URL: https://issues.apache.org/jira/browse/IGNITE-1919
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
>
> To reproduce please do Prev in Load metadata dialog.



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

[jira] [Updated] (IGNITE-1379) Need send error with stacktrace from web control center to webmaster email.

[Alexey Kuznetsov (JIRA)]

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

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

> Need send error with stacktrace from web control center to webmaster email.
> ---
>
> Key: IGNITE-1379
> URL: https://issues.apache.org/jira/browse/IGNITE-1379
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Andrey Novikov
>




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

[jira] [Updated] (IGNITE-1842) Add dropdown list of existing fields for setting it in index

[Alexey Kuznetsov (JIRA)]

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

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

> Add dropdown list of existing fields for setting it in index
> 
>
> Key: IGNITE-1842
> URL: https://issues.apache.org/jira/browse/IGNITE-1842
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
>
> If user already set field list will be useful to select existing field from 
> dropdown list for index.



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

[jira] [Updated] (IGNITE-1379) Need send error with stacktrace from web control center to webmaster email.

[Alexey Kuznetsov (JIRA)]

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

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

> Need send error with stacktrace from web control center to webmaster email.
> ---
>
> Key: IGNITE-1379
> URL: https://issues.apache.org/jira/browse/IGNITE-1379
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Andrey Novikov
>




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

[jira] [Updated] (IGNITE-1201) Create tests for Web Console Agent

[Alexey Kuznetsov (JIRA)]

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

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

> Create tests for Web Console Agent
> --
>
> Key: IGNITE-1201
> URL: https://issues.apache.org/jira/browse/IGNITE-1201
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Sergey Evdokimov
>Assignee: Alexey Kuznetsov
> Attachments: ignite-843_4abc9f1_ignite-1201.patch
>
>
> Need tests for Web Control Center Agent. 
> Tests should simulate Web Control Center requests.



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

[jira] [Updated] (IGNITE-1829) We must use short name for packages in metadata dropdown list

[Alexey Kuznetsov (JIRA)]

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

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

> We must use short name for packages in metadata dropdown list
> -
>
> Key: IGNITE-1829
> URL: https://issues.apache.org/jira/browse/IGNITE-1829
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Critical
> Fix For: 1.6
>
> Attachments: ig-1829.png
>
>
> Current view is uncomfortable because user don't see class name.
> Please see attachment.



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