[jira] [Updated] (IGNITE-1765) Insufficient height for label of Y-axis in case of several Y-values

[Alexey Kuznetsov (JIRA)]

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

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

> Insufficient height for label of Y-axis in case of several Y-values
> ---
>
> Key: IGNITE-1765
> URL: https://issues.apache.org/jira/browse/IGNITE-1765
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
> Attachments: ig-1765.png
>
>
> Please see attachment



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

[jira] [Updated] (IGNITE-1766) Zooming of charts

[Alexey Kuznetsov (JIRA)]

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

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

> Zooming of charts
> -
>
> Key: IGNITE-1766
> URL: https://issues.apache.org/jira/browse/IGNITE-1766
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
> Attachments: ig-1766.png
>
>
> Currently the minimum results page size is 50, but in case of several values 
> on Y-axis viewing for example bar chart becomes uncomfortable (see attachment)



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

[jira] [Updated] (IGNITE-1765) Insufficient height for label of Y-axis in case of several Y-values

[Alexey Kuznetsov (JIRA)]

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

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

> Insufficient height for label of Y-axis in case of several Y-values
> ---
>
> Key: IGNITE-1765
> URL: https://issues.apache.org/jira/browse/IGNITE-1765
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
> Attachments: ig-1765.png
>
>
> Please see attachment



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

[jira] [Commented] (IGNITE-2063) Enable 4 windows agents on TC

[Artem Shutak (JIRA)]

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

Artem Shutak commented on IGNITE-2063:
--

Some builds fail with "Execution timeout". Will just disable windows agents for 
the builds.

Ignite Cache, w_231_63,  
http://ci.ignite.apache.org/viewLog.html?buildId=82321=buildResultsDiv=Ignite_IgniteDataGrid
Ignite Data Structures, w_231_64, 
http://ci.ignite.apache.org/viewLog.html?buildId=82409=buildResultsDiv=Ignite_IgniteDataStrucutures
Java CLient, w_231_62, 
http://ci.ignite.apache.org/viewLog.html?buildId=82319=buildResultsDiv=Ignite_IgniteJavaClient
JDBC Driver, w_231_64, 
http://ci.ignite.apache.org/viewLog.html?buildId=82320=buildResultsDiv=Ignite_IgniteJdbcDriver
Queries, w_231_61, 
http://ci.ignite.apache.org/viewLog.html?buildId=82323=buildResultsDiv=Ignite_IgniteQueries

> Enable 4 windows agents on TC
> -
>
> Key: IGNITE-2063
> URL: https://issues.apache.org/jira/browse/IGNITE-2063
> Project: Ignite
>  Issue Type: Task
>Reporter: Artem Shutak
>Assignee: Artem Shutak
>
> Need to enable 4 windows agents on TC.



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

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

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-2064:


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



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

[jira] [Resolved] (IGNITE-2029) .Net: Readme.io documentation

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn resolved IGNITE-2029.
-
Resolution: Fixed

Done: https://apacheignite-net.readme.io/

> .Net: Readme.io documentation
> -
>
> Key: IGNITE-2029
> URL: https://issues.apache.org/jira/browse/IGNITE-2029
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: 1.6
>
>
> Adapt Java docs from https://apacheignite.readme.io/ for .NET API: 
> https://apacheignite-net.readme.io/



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

[jira] [Closed] (IGNITE-2029) .Net: Readme.io documentation

[Pavel Tupitsyn (JIRA)]

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

Pavel  Tupitsyn closed IGNITE-2029.
---

> .Net: Readme.io documentation
> -
>
> Key: IGNITE-2029
> URL: https://issues.apache.org/jira/browse/IGNITE-2029
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: 1.6
>
>
> Adapt Java docs from https://apacheignite.readme.io/ for .NET API: 
> https://apacheignite-net.readme.io/



--
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/2/15 6:13 PM:
---

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.


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()}.

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

Artem Shutak commented on IGNITE-1864:
--

Finished with an implementation. Working on tests.

> 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] [Commented] (IGNITE-2008) Abandoned locks are not released when nodes leave the grid

[Roy Reznik (JIRA)]

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

Roy Reznik commented on IGNITE-2008:


[~agura] - This is a very common use-case, when a node disconnects from the 
cluster while holding a lock. 
Is this bug something new to 1.4?
Currently it may cause the entire cluster to hang.
Why aim only for 1.6? Any workaround?

Thanks.

> 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.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] [Updated] (IGNITE-2041) CacheAutoStoreExample: Failed to find class with given class loader for unmarshalling

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-2041:
--
Assignee: Alexey Kuznetsov  (was: Yakov Zhdanov)

> CacheAutoStoreExample: Failed to find class with given class loader for 
> unmarshalling
> -
>
> Key: IGNITE-2041
> URL: https://issues.apache.org/jira/browse/IGNITE-2041
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5
>Reporter: Ilya Suntsov
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Fix For: 1.5
>
>
> Steps for reproduce:
> 1. Start
> examples/src/main/java/org/apache/ignite/examples/datagrid/store/auto/DbH2ServerStartup.java
> 2. Start 1 node from IDEA and 1 from terminal (with 
> examples/config/example-ignite.xml)
> 3. Run CacheAutoStoreExample
> Result:
> Node in terminal:
> {noformat}
> mpb:bin gridgain$ ./ignite.sh ../examples/config/example-ignite.xml -v
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; 
> support was removed in 8.0
> Ignite Command Line Startup, ver. 1.5.1-EA#20151130-sha1:4f1d55cc
> 2015 Copyright(C) Apache Software Foundation
> [15:26:14,676][INFO][main][IgniteKernal] 
> >>>__    
> >>>   /  _/ ___/ |/ /  _/_  __/ __/  
> >>>  _/ // (7 7// /  / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/   
> >>> 
> >>> ver. 1.5.1-EA#20151130-sha1:4f1d55cc
> >>> 2015 Copyright(C) Apache Software Foundation
> >>> 
> >>> Ignite documentation: http://ignite.apache.org
> [15:26:14,677][INFO][main][IgniteKernal] Config URL: 
> file:/Users/gridgain/Downloads/gridgain-enterprise-fabric-7.5.1-EA/bin/../examples/config/example-ignite.xml
> [15:26:14,677][INFO][main][IgniteKernal] Daemon mode: off
> [15:26:14,677][INFO][main][IgniteKernal] OS: Mac OS X 10.10.3 x86_64
> [15:26:14,677][INFO][main][IgniteKernal] OS user: gridgain
> [15:26:14,677][INFO][main][IgniteKernal] Language runtime: Java Platform API 
> Specification ver. 1.8
> [15:26:14,678][INFO][main][IgniteKernal] VM information: Java(TM) SE Runtime 
> Environment 1.8.0_45-b14 Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 
> 25.45-b02
> [15:26:14,679][INFO][main][IgniteKernal] VM total memory: 0.96GB
> [15:26:14,679][INFO][main][IgniteKernal] Remote Management [restart: on, 
> REST: on, JMX (remote: on, port: 49113, auth: off, ssl: off)]
> [15:26:14,679][INFO][main][IgniteKernal] 
> IGNITE_HOME=/Users/gridgain/Downloads/gridgain-enterprise-fabric-7.5.1-EA
> [15:26:14,680][INFO][main][IgniteKernal] VM arguments: [-Xms1g, -Xmx1g, 
> -XX:+AggressiveOpts, -XX:MaxPermSize=256m, -DIGNITE_QUIET=false, 
> -DIGNITE_SUCCESS_FILE=/Users/gridgain/Downloads/gridgain-enterprise-fabric-7.5.1-EA/work/ignite_success_6cde77f0-d8a7-44f7-8e33-ad553102eb52,
>  -Dcom.sun.management.jmxremote, -Dcom.sun.management.jmxremote.port=49113, 
> -Dcom.sun.management.jmxremote.authenticate=false, 
> -Dcom.sun.management.jmxremote.ssl=false, 
> -DIGNITE_HOME=/Users/gridgain/Downloads/gridgain-enterprise-fabric-7.5.1-EA, 
> -DIGNITE_PROG_NAME=./ignite.sh]
> [15:26:14,680][INFO][main][IgniteKernal] Configured caches 
> ['ignite-marshaller-sys-cache', 'ignite-sys-cache', 
> 'ignite-atomics-sys-cache']
> [15:26:14,680][WARNING][main][IgniteKernal] Peer class loading is enabled 
> (disable it in production for performance and deployment consistency reasons)
> [15:26:14,683][INFO][main][IgniteKernal] 3-rd party licenses can be found at: 
> /Users/gridgain/Downloads/gridgain-enterprise-fabric-7.5.1-EA/libs/licenses
> [15:26:14,741][INFO][main][IgniteKernal] Non-loopback local IPs: 
> 192.168.1.113, fe80:0:0:0:3e07:54ff:fe6b:6c35%en0
> [15:26:14,741][INFO][main][IgniteKernal] Enabled local MACs: 3C07546B6C35
> [15:26:14,752][INFO][main][IgnitePluginProcessor] Configured plugins:
> [15:26:14,752][INFO][main][IgnitePluginProcessor]   ^-- GridGain 
> 7.5.1-EA#20151130-sha1:7528584b
> [15:26:14,752][INFO][main][IgnitePluginProcessor]   ^-- 2015 Copyright(C) 
> GridGain Systems
> [15:26:14,753][INFO][main][IgnitePluginProcessor] 
> [15:26:14,815][INFO][main][TcpCommunicationSpi] IPC shared memory server 
> endpoint started [port=48101, 
> tokDir=/Users/gridgain/Downloads/gridgain-enterprise-fabric-7.5.1-EA/work/ipc/shmem/358d6354-ed8f-4806-8da3-3d19971fa90b-703]
> [15:26:14,815][INFO][main][TcpCommunicationSpi] Successfully bound shared 
> memory communication to TCP port [port=48101, locHost=0.0.0.0/0.0.0.0]
> [15:26:14,841][INFO][main][TcpCommunicationSpi] Successfully bound to TCP 
> port [port=47101, locHost=0.0.0.0/0.0.0.0]
> [15:26:14,861][WARNING][main][NoopCheckpointSpi] Checkpoints are disabled (to 
> enable configure any GridCheckpointSpi implementation)
> [15:26:14,884][WARNING][main][GridCollisionManager] Collision resolution 

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

[Alexey Kuznetsov (JIRA)]

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

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

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




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

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-2019:


I've tried with JDK-8 update 66, but unsuccessful.

> 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: Pavel Konstantinov
>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-2019) schema import utility failed to start on Mac OS X EI Capitan

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-2019:
---
Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> 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: Alexey Kuznetsov
>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] [Commented] (IGNITE-2041) CacheAutoStoreExample: Failed to find class with given class loader for unmarshalling

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov commented on IGNITE-2041:
---

Alexey, can you see if javadoc in example is valid? As far as I know deployment 
is not supported on Discovery level, so remote node can be started only from 
examples project with the same classpath.

> CacheAutoStoreExample: Failed to find class with given class loader for 
> unmarshalling
> -
>
> Key: IGNITE-2041
> URL: https://issues.apache.org/jira/browse/IGNITE-2041
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5
>Reporter: Ilya Suntsov
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Fix For: 1.5
>
>
> Steps for reproduce:
> 1. Start
> examples/src/main/java/org/apache/ignite/examples/datagrid/store/auto/DbH2ServerStartup.java
> 2. Start 1 node from IDEA and 1 from terminal (with 
> examples/config/example-ignite.xml)
> 3. Run CacheAutoStoreExample
> Result:
> Node in terminal:
> {noformat}
> mpb:bin gridgain$ ./ignite.sh ../examples/config/example-ignite.xml -v
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; 
> support was removed in 8.0
> Ignite Command Line Startup, ver. 1.5.1-EA#20151130-sha1:4f1d55cc
> 2015 Copyright(C) Apache Software Foundation
> [15:26:14,676][INFO][main][IgniteKernal] 
> >>>__    
> >>>   /  _/ ___/ |/ /  _/_  __/ __/  
> >>>  _/ // (7 7// /  / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/   
> >>> 
> >>> ver. 1.5.1-EA#20151130-sha1:4f1d55cc
> >>> 2015 Copyright(C) Apache Software Foundation
> >>> 
> >>> Ignite documentation: http://ignite.apache.org
> [15:26:14,677][INFO][main][IgniteKernal] Config URL: 
> file:/Users/gridgain/Downloads/gridgain-enterprise-fabric-7.5.1-EA/bin/../examples/config/example-ignite.xml
> [15:26:14,677][INFO][main][IgniteKernal] Daemon mode: off
> [15:26:14,677][INFO][main][IgniteKernal] OS: Mac OS X 10.10.3 x86_64
> [15:26:14,677][INFO][main][IgniteKernal] OS user: gridgain
> [15:26:14,677][INFO][main][IgniteKernal] Language runtime: Java Platform API 
> Specification ver. 1.8
> [15:26:14,678][INFO][main][IgniteKernal] VM information: Java(TM) SE Runtime 
> Environment 1.8.0_45-b14 Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 
> 25.45-b02
> [15:26:14,679][INFO][main][IgniteKernal] VM total memory: 0.96GB
> [15:26:14,679][INFO][main][IgniteKernal] Remote Management [restart: on, 
> REST: on, JMX (remote: on, port: 49113, auth: off, ssl: off)]
> [15:26:14,679][INFO][main][IgniteKernal] 
> IGNITE_HOME=/Users/gridgain/Downloads/gridgain-enterprise-fabric-7.5.1-EA
> [15:26:14,680][INFO][main][IgniteKernal] VM arguments: [-Xms1g, -Xmx1g, 
> -XX:+AggressiveOpts, -XX:MaxPermSize=256m, -DIGNITE_QUIET=false, 
> -DIGNITE_SUCCESS_FILE=/Users/gridgain/Downloads/gridgain-enterprise-fabric-7.5.1-EA/work/ignite_success_6cde77f0-d8a7-44f7-8e33-ad553102eb52,
>  -Dcom.sun.management.jmxremote, -Dcom.sun.management.jmxremote.port=49113, 
> -Dcom.sun.management.jmxremote.authenticate=false, 
> -Dcom.sun.management.jmxremote.ssl=false, 
> -DIGNITE_HOME=/Users/gridgain/Downloads/gridgain-enterprise-fabric-7.5.1-EA, 
> -DIGNITE_PROG_NAME=./ignite.sh]
> [15:26:14,680][INFO][main][IgniteKernal] Configured caches 
> ['ignite-marshaller-sys-cache', 'ignite-sys-cache', 
> 'ignite-atomics-sys-cache']
> [15:26:14,680][WARNING][main][IgniteKernal] Peer class loading is enabled 
> (disable it in production for performance and deployment consistency reasons)
> [15:26:14,683][INFO][main][IgniteKernal] 3-rd party licenses can be found at: 
> /Users/gridgain/Downloads/gridgain-enterprise-fabric-7.5.1-EA/libs/licenses
> [15:26:14,741][INFO][main][IgniteKernal] Non-loopback local IPs: 
> 192.168.1.113, fe80:0:0:0:3e07:54ff:fe6b:6c35%en0
> [15:26:14,741][INFO][main][IgniteKernal] Enabled local MACs: 3C07546B6C35
> [15:26:14,752][INFO][main][IgnitePluginProcessor] Configured plugins:
> [15:26:14,752][INFO][main][IgnitePluginProcessor]   ^-- GridGain 
> 7.5.1-EA#20151130-sha1:7528584b
> [15:26:14,752][INFO][main][IgnitePluginProcessor]   ^-- 2015 Copyright(C) 
> GridGain Systems
> [15:26:14,753][INFO][main][IgnitePluginProcessor] 
> [15:26:14,815][INFO][main][TcpCommunicationSpi] IPC shared memory server 
> endpoint started [port=48101, 
> tokDir=/Users/gridgain/Downloads/gridgain-enterprise-fabric-7.5.1-EA/work/ipc/shmem/358d6354-ed8f-4806-8da3-3d19971fa90b-703]
> [15:26:14,815][INFO][main][TcpCommunicationSpi] Successfully bound shared 
> memory communication to TCP port [port=48101, locHost=0.0.0.0/0.0.0.0]
> [15:26:14,841][INFO][main][TcpCommunicationSpi] Successfully bound to TCP 
> port [port=47101, locHost=0.0.0.0/0.0.0.0]
> 

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

[Dmitriyff (JIRA)]

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

Dmitriyff updated IGNITE-2033:
--
Issue Type: Bug  (was: Sub-task)
Parent: (was: IGNITE-843)

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




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

[jira] [Created] (IGNITE-2052) Need move $generatorXml to services

[Dmitriyff (JIRA)]

Dmitriyff created IGNITE-2052:
-

 Summary: Need move $generatorXml to services
 Key: IGNITE-2052
 URL: https://issues.apache.org/jira/browse/IGNITE-2052
 Project: Ignite
  Issue Type: Sub-task
Reporter: Dmitriyff






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

[jira] [Assigned] (IGNITE-2052) Need move $generatorXml to services

[Dmitriyff (JIRA)]

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

Dmitriyff reassigned IGNITE-2052:
-

Assignee: Dmitriyff

> Need move $generatorXml to services
> ---
>
> Key: IGNITE-2052
> URL: https://issues.apache.org/jira/browse/IGNITE-2052
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Dmitriyff
>Assignee: Dmitriyff
> Fix For: 1.6
>
>




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

[jira] [Created] (IGNITE-2054) need move $generatorJava to services

[Dmitriyff (JIRA)]

Dmitriyff created IGNITE-2054:
-

 Summary: need move $generatorJava to services
 Key: IGNITE-2054
 URL: https://issues.apache.org/jira/browse/IGNITE-2054
 Project: Ignite
  Issue Type: Sub-task
Reporter: Dmitriyff
Assignee: Dmitriyff






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

[jira] [Created] (IGNITE-2053) need move $generatorPom to services

[Dmitriyff (JIRA)]

Dmitriyff created IGNITE-2053:
-

 Summary: need move $generatorPom to services
 Key: IGNITE-2053
 URL: https://issues.apache.org/jira/browse/IGNITE-2053
 Project: Ignite
  Issue Type: Sub-task
Reporter: Dmitriyff
Assignee: Dmitriyff






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

[jira] [Commented] (IGNITE-686) HadoopClientProtocolEmbeddedSelfTest.testJobCounters failed.

[Neeraj Sabharwal (JIRA)]

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

Neeraj Sabharwal commented on IGNITE-686:
-

I am getting the same issue in setup HDP 2.3.2 
hadoop jar 
/usr/hdp/2.3.4.0-3276/hadoop-mapreduce/hadoop-mapreduce-examples-2.7.1.2.3.4.0-3276.jar
 wordcount /input /output
WARNING: Use "yarn jar" to launch YARN applications.
Dec 02, 2015 2:01:33 PM org.apache.ignite.internal.client.impl.GridClientImpl 

WARNING: Failed to initialize topology on client start. Will retry in 
background.
Dec 02, 2015 2:01:33 PM org.apache.ignite.internal.client.impl.GridClientImpl 

INFO: Client started [id=6bf4d4ff-4afb-4cdf-821f-2e2b7d4b1467, protocol=TCP]
java.io.IOException: Failed to get new job ID.
at 
org.apache.ignite.internal.processors.hadoop.proto.HadoopClientProtocol.getNewJobID(HadoopClientProtocol.java:109)
at 
org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:153)
at org.apache.hadoop.mapreduce.Job$10.run(Job.java:1290)
at org.apache.hadoop.mapreduce.Job$10.run(Job.java:1287)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
at org.apache.hadoop.mapreduce.Job.submit(Job.java:1287)
at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1308)
at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
Caused by: class 
org.apache.ignite.internal.client.GridClientDisconnectedException: Latest 
topology update failed.
at 
org.apache.ignite.internal.client.impl.connection.GridClientTopology.nodes(GridClientTopology.java:335)
at 
org.apache.ignite.internal.client.impl.GridClientAbstractProjection.projectionNodes(GridClientAbstractProjection.java:312)
at 
org.apache.ignite.internal.client.impl.GridClientAbstractProjection.balancedNode(GridClientAbstractProjection.java:352)
at 
org.apache.ignite.internal.client.impl.GridClientAbstractProjection.withReconnectHandling(GridClientAbstractProjection.java:109)
at 
org.apache.ignite.internal.client.impl.GridClientComputeImpl.executeAsync(GridClientComputeImpl.java:132)
at 
org.apache.ignite.internal.client.impl.GridClientComputeImpl.execute(GridClientComputeImpl.java:121)
at 
org.apache.ignite.internal.processors.hadoop.proto.HadoopClientProtocol.getNewJobID(HadoopClientProtocol.java:102)
... 22 more
Caused by: class 
org.apache.ignite.internal.client.GridServerUnreachableException: Failed to 
connect to any of the servers in list: [/127.0.0.1:11211]
at 
org.apache.ignite.internal.client.impl.connection.GridClientConnectionManagerAdapter.connect(GridClientConnectionManagerAdapter.java:414)
at 
org.apache.ignite.internal.client.impl.connection.GridClientConnectionManagerAdapter.init(GridClientConne

> HadoopClientProtocolEmbeddedSelfTest.testJobCounters failed.
> 
>
> Key: IGNITE-686
> URL: https://issues.apache.org/jira/browse/IGNITE-686
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: sprint-2
>Reporter: Vladimir Ozerov
>Assignee: Ivan Veselovsky
> Fix For: 1.5
>
>
> java.io.IOException: Failed to get new job ID.
> at 
> org.apache.ignite.internal.processors.hadoop.proto.HadoopClientProtocol.getNewJobID(HadoopClientProtocol.java:90)
> at 
> org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:357)
> at org.apache.hadoop.mapreduce.Job$10.run(Job.java:1285)
> at org.apache.hadoop.mapreduce.Job$10.run(Job.java:1282)
> at 

[jira] [Commented] (IGNITE-843) Web console development

[Prachi Garg (JIRA)]

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

Prachi Garg commented on IGNITE-843:


I've noticed two issues:
# The load time of clusters page 
(https://console.gridgain.com/configuration/clusters) is more than 4 sec. The 
blue and the green background on the first half of the page loads quickly. But 
the text in it   and the configuration part takes really long. On my laptop, it 
takes approximately 4.5s to load the page.

# After downloading the configuration, I tried to import the project in IDEA. 
But most of the types in ClientConfigurationFactory.java and 
ServerConfigurationFactory.java are not recognized. Looks like these files are 
missing some imports.


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



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

[jira] [Resolved] (IGNITE-2067) fix minimize build version

[Dmitriyff (JIRA)]

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

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

> fix minimize build version
> --
>
> Key: IGNITE-2067
> URL: https://issues.apache.org/jira/browse/IGNITE-2067
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Dmitriyff
>Assignee: Andrey Novikov
> Fix For: 1.5
>
>
> fix logout ability 



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

[jira] [Closed] (IGNITE-2066) Clean build process, add needed comments

[Andrey Novikov (JIRA)]

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

Andrey Novikov closed IGNITE-2066.
--
Assignee: (was: Andrey Novikov)

Review. Merged.

> Clean build process, add needed comments
> 
>
> Key: IGNITE-2066
> URL: https://issues.apache.org/jira/browse/IGNITE-2066
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Dmitriyff
> Fix For: 1.5
>
>
> rename "gulp concat" task
> add description to run process to devnotes
> add license comment to serve.js



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

[jira] [Resolved] (IGNITE-2014) Incorrect behavior on Refresh (F5 in browser) in corner case

[Andrey Novikov (JIRA)]

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

Andrey Novikov resolved IGNITE-2014.

Resolution: Fixed

Fixed. Pavel. please retest

> 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
>Assignee: Andrey Novikov
>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] [Updated] (IGNITE-2068) Generation of separate metod for each metadata

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko updated IGNITE-2068:
--
Description: Also do not generate QueryEntity when SQL query fields is not 
configured.  (was: Also do not generate QueryIndex when SQL query fields is not 
configured.)

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



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

[jira] [Closed] (IGNITE-1980) Download button is available on empty Summary page

[Pavel Konstantinov (JIRA)]

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

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

Tested.

> Download button is available on empty Summary page
> --
>
> Key: IGNITE-1980
> URL: https://issues.apache.org/jira/browse/IGNITE-1980
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
>
> Download button should be unavailable if no one clusters are created.
> Currently user will get:
> {code}
> 16:52:49.086 Error: cluster is undefined
> $generatorProperties.sslProperties@https://console.gridgain.com/generator/generator-properties.js:82:1
> $scope.downloadConfiguration@https://console.gridgain.com/summary-controller.js:209:23
> anonymous/fn@https://console.gridgain.com/app.min.js line 52794 > 
> Function:2:251
> ngEventHandler/https://console.gridgain.com/app.min.js:56475:21
> $RootScopeProvider/this.$gethttps://console.gridgain.com/app.min.js:54398:22
> $RootScopeProvider/this.$gethttps://console.gridgain.com/app.min.js:54421:26
> ngEventHandler/<@https://console.gridgain.com/app.min.js:56480:21
> jQuery.event.dispatch@https://console.gridgain.com/app.min.js:90093:25
> jQuery.event.add/elemData.handle@https://console.gridgain.com/app.min.js:89879:92
> 1 app.min.js:52000:24
> consoleLog/<() app.min.js:52000
> $ExceptionHandlerProvider/this.$get $RootScopeProvider/this.$get ngEventHandler/<() app.min.js:56480
> jQuery.event.dispatch() app.min.js:90093
> jQuery.event.add/elemData.handle() app.min.js:89879
> {code}



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

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

Pavel Konstantinov edited comment on IGNITE-2051 at 12/3/15 5:23 AM:
-

Still doesn't works for already existing notebooks:
1) create notebook
2) create and execute 2 query
3) switch to another notebook
4) switch back


was (Author: pkonstantinov):
Still doesn't works for already existing notebooks

> 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
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
>




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

[jira] [Reopened] (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 reopened IGNITE-2051:

  Assignee: Andrey Novikov  (was: Pavel Konstantinov)

> 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
>Assignee: Andrey Novikov
> Fix For: 1.6
>
>




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

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-2070:
---
Description: Nothing happens when I clicking on it.

> "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.6
>
>
> Nothing happens when I clicking on it.



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

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

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2070:
--

 Summary: "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
Reporter: Pavel Konstantinov






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

[jira] [Updated] (IGNITE-2014) Incorrect behavior on Refresh (F5 in browser) in corner case

[Andrey Novikov (JIRA)]

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

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

> 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
>Assignee: 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-2068) Generation of separate metod for each metadata

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-2068:
-

 Summary: Generation of separate metod for each metadata 
 Key: IGNITE-2068
 URL: https://issues.apache.org/jira/browse/IGNITE-2068
 Project: Ignite
  Issue Type: Sub-task
Affects Versions: 1.5
Reporter: Vasiliy Sisko
Assignee: Vasiliy Sisko
Priority: Minor
 Fix For: 1.5


Also do not generate QueryIndex when SQL query fields is not configured.



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

[jira] [Closed] (IGNITE-2048) Secondary file system (SFS) is not mandatory in IGFS settings

[Pavel Konstantinov (JIRA)]

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

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

Tested.

> Secondary file system (SFS) is not mandatory in IGFS settings
> -
>
> Key: IGNITE-2048
> URL: https://issues.apache.org/jira/browse/IGNITE-2048
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
>
> Current javadoc says that if SFS is not configured then IGFS will work in 
> Primary mode. We need to add confirmation about that moment on IGFS save and 
> allow to user to save IGFS without SFS.



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

[jira] [Reopened] (IGNITE-2039) Please generate two 'NodeStartup' classes - NodeStartupServer and NodeStartupClient for each mode: XML- and Java- ways

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reopened IGNITE-2039:

  Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Please generate two 'NodeStartup' classes - NodeStartupServer and 
> NodeStartupClient for each mode: XML- and Java- ways 
> ---
>
> Key: IGNITE-2039
> URL: https://issues.apache.org/jira/browse/IGNITE-2039
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 1.5
>
>
> I was playing a bit with generated code and suggest to generate four 
> NodeStartup classes:
> NodeStartupServerXml, NodeStartupServerJava, NodeStartupClientXml, 
> NodeStartupClientJava



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

[jira] [Commented] (IGNITE-2039) Please generate two 'NodeStartup' classes - NodeStartupServer and NodeStartupClient for each mode: XML- and Java- ways

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-2039:


{code}
Information:java: Errors occurred while compiling module 
'ignite-generated-model'
Information:03.12.2015 12:33 - Compilation completed with 4 errors and 0 
warnings in 2s 568ms
S:\work\111-configuration\src\main\java\startup\ClientNodeCodeStartup.java
Error:(18, 33) java: ';' expected
S:\work\111-configuration\src\main\java\startup\ClientNodeSpringStartup.java
Error:(16, 26) java: ';' expected
S:\work\111-configuration\src\main\java\startup\ServerNodeSpringStartup.java
Error:(16, 26) java: ';' expected
S:\work\111-configuration\src\main\java\startup\ServerNodeCodeStartup.java
Error:(17, 26) java: ';' expected
{code}

> Please generate two 'NodeStartup' classes - NodeStartupServer and 
> NodeStartupClient for each mode: XML- and Java- ways 
> ---
>
> Key: IGNITE-2039
> URL: https://issues.apache.org/jira/browse/IGNITE-2039
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
>
> I was playing a bit with generated code and suggest to generate four 
> NodeStartup classes:
> NodeStartupServerXml, NodeStartupServerJava, NodeStartupClientXml, 
> NodeStartupClientJava



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

[jira] [Comment Edited] (IGNITE-2039) Please generate two 'NodeStartup' classes - NodeStartupServer and NodeStartupClient for each mode: XML- and Java- ways

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov edited comment on IGNITE-2039 at 12/3/15 5:35 AM:
-

Did you try to download and build in Idea?
{code}
Information:java: Errors occurred while compiling module 
'ignite-generated-model'
Information:03.12.2015 12:33 - Compilation completed with 4 errors and 0 
warnings in 2s 568ms
S:\work\111-configuration\src\main\java\startup\ClientNodeCodeStartup.java
Error:(18, 33) java: ';' expected
S:\work\111-configuration\src\main\java\startup\ClientNodeSpringStartup.java
Error:(16, 26) java: ';' expected
S:\work\111-configuration\src\main\java\startup\ServerNodeSpringStartup.java
Error:(16, 26) java: ';' expected
S:\work\111-configuration\src\main\java\startup\ServerNodeCodeStartup.java
Error:(17, 26) java: ';' expected
{code}


was (Author: pkonstantinov):
{code}
Information:java: Errors occurred while compiling module 
'ignite-generated-model'
Information:03.12.2015 12:33 - Compilation completed with 4 errors and 0 
warnings in 2s 568ms
S:\work\111-configuration\src\main\java\startup\ClientNodeCodeStartup.java
Error:(18, 33) java: ';' expected
S:\work\111-configuration\src\main\java\startup\ClientNodeSpringStartup.java
Error:(16, 26) java: ';' expected
S:\work\111-configuration\src\main\java\startup\ServerNodeSpringStartup.java
Error:(16, 26) java: ';' expected
S:\work\111-configuration\src\main\java\startup\ServerNodeCodeStartup.java
Error:(17, 26) java: ';' expected
{code}

> Please generate two 'NodeStartup' classes - NodeStartupServer and 
> NodeStartupClient for each mode: XML- and Java- ways 
> ---
>
> Key: IGNITE-2039
> URL: https://issues.apache.org/jira/browse/IGNITE-2039
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
>
> I was playing a bit with generated code and suggest to generate four 
> NodeStartup classes:
> NodeStartupServerXml, NodeStartupServerJava, NodeStartupClientXml, 
> NodeStartupClientJava



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

[jira] [Updated] (IGNITE-2069) Top menu has no Gridgain item and sub-items

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-2069:
---
Description: Also please pay attention that GridGain sub-items not looks  
like a sub-items, they are looks like items without numbers on the first level.

> Top menu has no Gridgain item and sub-items
> ---
>
> Key: IGNITE-2069
> URL: https://issues.apache.org/jira/browse/IGNITE-2069
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.6
>
>
> Also please pay attention that GridGain sub-items not looks  like a 
> sub-items, they are looks like items without numbers on the first level.



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

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

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-2040:


SQL fields in most cases are the Value Type fields. So we could generate all 
SQL fields as members of Value Type java-class.

> 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.5
>
>
> 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] [Commented] (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:comment-tabpanel=15037281#comment-15037281
 ] 

Pavel Konstantinov commented on IGNITE-2051:


Still doesn't works for already existing notebooks

> 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
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
>




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

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-2040:
---
Issue Type: Improvement  (was: Sub-task)
Parent: (was: IGNITE-843)

> 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: Improvement
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 1.5
>
>
> 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] [Created] (IGNITE-2071) Download button on sammary page placed into wrong block

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2071:
--

 Summary: Download button on sammary page placed into wrong block
 Key: IGNITE-2071
 URL: https://issues.apache.org/jira/browse/IGNITE-2071
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov


Try to scroll summary page and will see what I'm talking about.



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

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-2040:
---
Issue Type: Sub-task  (was: Improvement)
Parent: IGNITE-2047

> 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.5
>
>
> 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] [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=15037390#comment-15037390
 ] 

Semen Boikov commented on IGNITE-2008:
--

Added test reproducing issue: CacheLockReleaseNodeLeaveTest.

> 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] [Assigned] (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 reassigned IGNITE-2008:


Assignee: 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
>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-2067) fix minimize build version

[Dmitriyff (JIRA)]

Dmitriyff created IGNITE-2067:
-

 Summary: fix minimize build version
 Key: IGNITE-2067
 URL: https://issues.apache.org/jira/browse/IGNITE-2067
 Project: Ignite
  Issue Type: Sub-task
Reporter: Dmitriyff
Assignee: Dmitriyff


fix logout ability 



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

[jira] [Closed] (IGNITE-2056) Chart settings does not open by clicking on button with arrow

[Pavel Konstantinov (JIRA)]

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

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

Tested.

> Chart settings does not open by clicking on button with arrow
> -
>
> Key: IGNITE-2056
> URL: https://issues.apache.org/jira/browse/IGNITE-2056
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
>
> In all other places it works.



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

[jira] [Updated] (IGNITE-2039) Please generate two 'NodeStartup' classes - NodeStartupServer and NodeStartupClient for each mode: XML- and Java- ways

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-2039:
---
Attachment: 111-configuration.zip

> Please generate two 'NodeStartup' classes - NodeStartupServer and 
> NodeStartupClient for each mode: XML- and Java- ways 
> ---
>
> Key: IGNITE-2039
> URL: https://issues.apache.org/jira/browse/IGNITE-2039
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 1.5
>
> Attachments: 111-configuration.zip
>
>
> I was playing a bit with generated code and suggest to generate four 
> NodeStartup classes:
> NodeStartupServerXml, NodeStartupServerJava, NodeStartupClientXml, 
> NodeStartupClientJava



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

[jira] [Resolved] (IGNITE-2039) Please generate two 'NodeStartup' classes - NodeStartupServer and NodeStartupClient for each mode: XML- and Java- ways

[Alexey Kuznetsov (JIRA)]

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

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

Fixed code generation typo.

> Please generate two 'NodeStartup' classes - NodeStartupServer and 
> NodeStartupClient for each mode: XML- and Java- ways 
> ---
>
> Key: IGNITE-2039
> URL: https://issues.apache.org/jira/browse/IGNITE-2039
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
> Attachments: 111-configuration.zip
>
>
> I was playing a bit with generated code and suggest to generate four 
> NodeStartup classes:
> NodeStartupServerXml, NodeStartupServerJava, NodeStartupClientXml, 
> NodeStartupClientJava



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

[jira] [Closed] (IGNITE-2015) Improve Marshaller section on Cluster page

[Pavel Konstantinov (JIRA)]

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

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

Tested.

> Improve Marshaller section on Cluster page
> --
>
> Key: IGNITE-2015
> URL: https://issues.apache.org/jira/browse/IGNITE-2015
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
>
> 1) add the case "Not set"
> 2) fix tooltip - add info about default BinaryMarshaller



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

[jira] [Closed] (IGNITE-1027) Possible data loss in replicated cache on unstable topology.

[Semen Boikov (JIRA)]

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

Semen Boikov closed IGNITE-1027.

Assignee: (was: Semen Boikov)

> Possible data loss in replicated cache on unstable topology.
> 
>
> Key: IGNITE-1027
> URL: https://issues.apache.org/jira/browse/IGNITE-1027
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Sergi Vladykin
> Fix For: 1.5
>
>
> In test IgniteCacheClientQueryReplicatedNodeRestartSelfTest we have 4 data 
> nodes with replicated caches and single client-only node, which runs SQL 
> queries against those data nodes. Background threads restarting data nodes. 
> When we restart 2 of 4 data nodes everything is fine, when 3 of 4 then 
> eventually query returns inconsistent result and cache size returns smaller 
> values than expected. Since we use rebalance mode SYNC, such a data loss 
> should not happen.



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

[jira] [Resolved] (IGNITE-1027) Possible data loss in replicated cache on unstable topology.

[Semen Boikov (JIRA)]

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

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

Issue with early sync rebalance future completion was fixed in 1.5 (commit 
ad9e4db).

> Possible data loss in replicated cache on unstable topology.
> 
>
> Key: IGNITE-1027
> URL: https://issues.apache.org/jira/browse/IGNITE-1027
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Sergi Vladykin
>Assignee: Semen Boikov
> Fix For: 1.5
>
>
> In test IgniteCacheClientQueryReplicatedNodeRestartSelfTest we have 4 data 
> nodes with replicated caches and single client-only node, which runs SQL 
> queries against those data nodes. Background threads restarting data nodes. 
> When we restart 2 of 4 data nodes everything is fine, when 3 of 4 then 
> eventually query returns inconsistent result and cache size returns smaller 
> values than expected. Since we use rebalance mode SYNC, such a data loss 
> should not happen.



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

[jira] [Commented] (IGNITE-2067) fix minimize build version

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2067:


GitHub user Dmitriyff opened a pull request:

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

IGNITE-2067 fixed minimize version, logout method



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

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

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

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


commit cb42765e429958d7aee3d14740d2f841d252e29e
Author: Alexey Kuznetsov 
Date:   2015-10-26T03:13:28Z

Merge remote-tracking branch 'origin/ignite-843-rc1' into ignite-843-rc1

commit 952dcd9fe6ed5de676d2e51b27a0316ec3eb294a
Author: Andrey 
Date:   2015-10-26T04:06:02Z

IGNITE-1781 Fixed long query name.

commit 336d8a1e30c4e2ff5d663aef576d8c53f303f5d0
Author: Andrey 
Date:   2015-10-26T05:32:24Z

IGNITE-1769 Close the current query on server-side when user start new one

commit 591e0c551f8e786e41fcd30a8869482d8b484658
Author: vsisko 
Date:   2015-10-26T09:04:09Z

IGNITE-1200 WIP IGFS: added code generation for IGFS caches + refactoring 
of JS "for()" to "_.forEach()".

commit 0c3a8960de32188bd0da7a474377ab153b42af94
Author: vsisko 
Date:   2015-10-26T10:27:33Z

IGNITE-1750 WIP: Fixed some placeholders and code generation with default 
values.

commit 31c502b04281017772e9544f1cbb6342c7abff8a
Author: AKuznetsov 
Date:   2015-10-26T13:03:42Z

IGNITE-843 Update dependencies.

commit 8b9a57148c94375bf442f6293e4c147c1b26f4dd
Author: Andrey 
Date:   2015-10-27T04:13:40Z

IGNITE-1781 Fixed css

commit ccbb34ad546faf1d2648e43e688f004cc1dcecf9
Author: vsisko 
Date:   2015-10-27T04:18:14Z

IGNITE-1200 Code generation of IGFS caches.

commit 0ebd7a5676af1aa7d977c87271a1c95636c247a0
Author: Alexey Kuznetsov 
Date:   2015-10-27T04:18:33Z

Merge remote-tracking branch 'origin/ignite-843-rc1' into ignite-843-rc1

commit b5daaf1e618da9bf537565a420174c3430a46be2
Author: vsisko 
Date:   2015-10-27T09:08:33Z

IGNITE-1200 IGFS preview fixes + placeholders.

commit 302d62f8445acbe8fc0aeac322b31b976c1ed021
Author: vsisko 
Date:   2015-10-27T10:06:53Z

IGNITE-1485 Fixed check agent connected.

commit d8fc3990d5c775a5e83756e8237b8031bc916dcd
Author: vsisko 
Date:   2015-10-27T10:39:45Z

IGNITE-1715 Reset button.

commit 0d8c5e311defc826752cd7f8719651cf6c16b26d
Author: vsisko 
Date:   2015-10-28T02:55:59Z

IGNITE-1715 Reset button.

commit 91aab57bb666f64df2879b17cdcfe68faf588279
Author: vsisko 
Date:   2015-10-28T04:29:30Z

IGNITE-1799 Fixed not needed highlighting in special case.

commit e8216ed3a938c82bc5a289b0b74aac840258042c
Author: vsisko 
Date:   2015-10-28T04:45:01Z

IGNITE-1767 Fixed JDBC driver class selection.

commit fd1dc0b315e8aff95246777e2d193d8a9f2b68a1
Author: vsisko 
Date:   2015-10-28T08:28:02Z

IGNITE-1749 Fixed code generation: read secret props from file.

commit ec266e3cdb32ae3aaa188ee5712c482ec031d0aa
Author: Andrey 
Date:   2015-10-28T09:11:30Z

Merge branches 'ignite-843-rc1' and 'master' of 
https://git-wip-us.apache.org/repos/asf/ignite into ignite-843-rc1

commit db3548eba2e708f629f63d8557b5de69fcbb04fb
Author: Vasiliy Sisko 
Date:   2015-10-28T09:40:15Z

IGNITE-1749 Close input stream.

commit 6a35c4c95ff9300585303c9b99ecb1dd0f11ab98
Author: Vasiliy Sisko 
Date:   2015-10-28T09:41:39Z

IGNITE-1729 Hiding of showed element details by filtration.

commit f4ece6e44a00a39d9ab4281411cf66e4be0cafc1
Author: Andrey 
Date:   2015-10-29T02:35:01Z

IGNITE-843 Minor fix

commit 775e5e378648125cb87d23a0939fe1aea564478d
Author: Alexey Kuznetsov 
Date:   2015-10-29T02:41:59Z

IGNITE-843 Fixed several typos.

commit 96ef0ff0cd49fd414148d966a4ec2cf1dc815e2e
Author: vsisko 
Date:   2015-10-30T03:01:23Z

IGNITE-1703 Show original query.

commit 63e9ffdc0117a70f52f09281c4efb18cb575e3fc
Author: Andrey 
Date:   2015-10-30T06:06:51Z

IGNITE-843 One download button on summary page.

commit f87dd3a84d50eb8424f589bc7885ae55fc00d7e8
Author: Andrey 
Date:   2015-10-30T06:07:11Z

Merge remote-tracking branch 

[jira] [Resolved] (IGNITE-1980) Download button is available on empty Summary page

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko resolved IGNITE-1980.
---
Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

Implemented hiding of download button

> Download button is available on empty Summary page
> --
>
> Key: IGNITE-1980
> URL: https://issues.apache.org/jira/browse/IGNITE-1980
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.5
>
>
> Download button should be unavailable if no one clusters are created.
> Currently user will get:
> {code}
> 16:52:49.086 Error: cluster is undefined
> $generatorProperties.sslProperties@https://console.gridgain.com/generator/generator-properties.js:82:1
> $scope.downloadConfiguration@https://console.gridgain.com/summary-controller.js:209:23
> anonymous/fn@https://console.gridgain.com/app.min.js line 52794 > 
> Function:2:251
> ngEventHandler/https://console.gridgain.com/app.min.js:56475:21
> $RootScopeProvider/this.$gethttps://console.gridgain.com/app.min.js:54398:22
> $RootScopeProvider/this.$gethttps://console.gridgain.com/app.min.js:54421:26
> ngEventHandler/<@https://console.gridgain.com/app.min.js:56480:21
> jQuery.event.dispatch@https://console.gridgain.com/app.min.js:90093:25
> jQuery.event.add/elemData.handle@https://console.gridgain.com/app.min.js:89879:92
> 1 app.min.js:52000:24
> consoleLog/<() app.min.js:52000
> $ExceptionHandlerProvider/this.$get $RootScopeProvider/this.$get ngEventHandler/<() app.min.js:56480
> jQuery.event.dispatch() app.min.js:90093
> jQuery.event.add/elemData.handle() app.min.js:89879
> {code}



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

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

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-2040:


Perhaps you worked with the old console, but on staging I don't see anything 
you are talking about.

> 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: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
>
> 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] [Reopened] (IGNITE-2040) Please generate java classes for all metadata linked with caches

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reopened IGNITE-2040:


> 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.5
>
>
> 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-2040) Please generate java classes for all metadata linked with caches

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-2040:
---
Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> 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.5
>
>
> 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] [Created] (IGNITE-2069) Top menu has no Gridgain item and sub-items

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2069:
--

 Summary: Top menu has no Gridgain item and sub-items
 Key: IGNITE-2069
 URL: https://issues.apache.org/jira/browse/IGNITE-2069
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov






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

[jira] [Created] (IGNITE-2056) Chart settings does not open by clicking on button with arrow

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2056:
--

 Summary: Chart settings does not open by clicking on button with 
arrow
 Key: IGNITE-2056
 URL: https://issues.apache.org/jira/browse/IGNITE-2056
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Priority: Minor






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

[jira] [Updated] (IGNITE-2056) Chart settings does not open by clicking on button with arrow

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-2056:
---
Description: In all others places it works.

> Chart settings does not open by clicking on button with arrow
> -
>
> Key: IGNITE-2056
> URL: https://issues.apache.org/jira/browse/IGNITE-2056
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
>
> In all others places it works.



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

[jira] [Updated] (IGNITE-1761) Load metadata from DB: add possibility to set JDBC driver jar file from local folder

[Alexey Kuznetsov (JIRA)]

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

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

> Load metadata from DB: add possibility to set JDBC driver jar file from local 
> folder
> 
>
> Key: IGNITE-1761
> URL: https://issues.apache.org/jira/browse/IGNITE-1761
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
>
> Currently the list of available JDBC jar-files is configured only on 
> web-agent side by placing necessary files into 'jdbc-drivers' folder. In case 
> when user have not direct access to this folder he cannot place driver he 
> needed. So we need to give to user possibility to select needed JDBC driver 
> from local folder.



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

[jira] [Updated] (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 updated IGNITE-2051:
---
Summary: First (or newly created query) query doesn't opens on notebook 
page  (was: First query doesn't opens on notebook page)

> 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
>Assignee: Andrey Novikov
> Fix For: 1.6
>
>




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

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-2008:
-

Noam,

I reproduced it on current development branch (ignite-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
> 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] [Resolved] (IGNITE-2039) Please generate two 'NodeStartup' classes - NodeStartupServer and NodeStartupClient for each mode: XML- and Java- ways

[Alexey Kuznetsov (JIRA)]

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

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

Reworked generation in following way:
# subfolder "factory" with xxxConfigurationFactory.java files.
# subfolder "startup" with xxxNodeSpringStartup.java and 
xxxNodeCodeStartup.java files.

> Please generate two 'NodeStartup' classes - NodeStartupServer and 
> NodeStartupClient for each mode: XML- and Java- ways 
> ---
>
> Key: IGNITE-2039
> URL: https://issues.apache.org/jira/browse/IGNITE-2039
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
>
> I was playing a bit with generated code and suggest to generate four 
> NodeStartup classes:
> NodeStartupServerXml, NodeStartupServerJava, NodeStartupClientXml, 
> NodeStartupClientJava



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

[jira] [Assigned] (IGNITE-2056) Chart settings does not open by clicking on button with arrow

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-2056:
-

Assignee: Vasiliy Sisko

> Chart settings does not open by clicking on button with arrow
> -
>
> Key: IGNITE-2056
> URL: https://issues.apache.org/jira/browse/IGNITE-2056
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Minor
> Fix For: 1.5
>
>
> In all other places it works.



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

[jira] [Updated] (IGNITE-1212) Support different version of Ignite

[Alexey Kuznetsov (JIRA)]

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

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

> Support different version of Ignite
> ---
>
> Key: IGNITE-1212
> URL: https://issues.apache.org/jira/browse/IGNITE-1212
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: ignite-1.4
>Reporter: Alexey Kuznetsov
> Fix For: 1.6
>
>
> Ignite configuration could evolve over time. Some new properties added, some 
> deprecated. We should add a dropdown with Ignite version in web UI that will 
> adjust list of available properties to show.



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

[jira] [Updated] (IGNITE-1736) Configuration add scroll to group from sidebar

[Alexey Kuznetsov (JIRA)]

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

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

> Configuration add scroll to group from sidebar
> --
>
> Key: IGNITE-1736
> URL: https://issues.apache.org/jira/browse/IGNITE-1736
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Andrey Novikov
> Fix For: 1.5
>
>




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

[jira] [Updated] (IGNITE-1761) Load metadata from DB: add possibility to set JDBC driver jar file from local folder

[Alexey Kuznetsov (JIRA)]

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

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

> Load metadata from DB: add possibility to set JDBC driver jar file from local 
> folder
> 
>
> Key: IGNITE-1761
> URL: https://issues.apache.org/jira/browse/IGNITE-1761
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
>
> Currently the list of available JDBC jar-files is configured only on 
> web-agent side by placing necessary files into 'jdbc-drivers' folder. In case 
> when user have not direct access to this folder he cannot place driver he 
> needed. So we need to give to user possibility to select needed JDBC driver 
> from local folder.



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

[Noam Liran (JIRA)]

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

Noam Liran commented on IGNITE-2008:


Hi Andrey, 
Out of curiosity, did you happen to try and reproduce this on (soon to be) 
1.5.0 or on the current stable version?
Thanks,
Noam

> 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.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-2058) need move $generatorDocker to services

[Dmitriyff (JIRA)]

Dmitriyff created IGNITE-2058:
-

 Summary: need move $generatorDocker to services
 Key: IGNITE-2058
 URL: https://issues.apache.org/jira/browse/IGNITE-2058
 Project: Ignite
  Issue Type: Sub-task
Reporter: Dmitriyff
Assignee: Dmitriyff






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

[jira] [Resolved] (IGNITE-2057) 'show query' link throws the exception

[Andrey Novikov (JIRA)]

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

Andrey Novikov resolved IGNITE-2057.

Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Andrey Novikov)

Fixed. Pavel, please retest

> 'show query' link throws the exception
> --
>
> Key: IGNITE-2057
> URL: https://issues.apache.org/jira/browse/IGNITE-2057
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
>
> {code}
> 16:39:17.250 "Error: [$sce:itype] Attempted to trust a non-string value in a 
> content requiring a string: Context: html
> http://errors.angularjs.org/1.4.8/$sce/itype?p0=html
> minErr/<@https://staging-console.gridgain.com/app.min.js:50992:18
> trustAs@https://staging-console.gridgain.com/app.min.js:58930:1
> @https://staging-console.gridgain.com/app.min.js:59014:22
> ModalFactory/<@https://staging-console.gridgain.com/app.min.js:47236:30
> forEach@https://staging-console.gridgain.com/app.min.js:51053:17
> ModalFactory@https://staging-console.gridgain.com/app.min.js:47234:13
> $scope.showResultQuery@https://staging-console.gridgain.com/all.js:5029:13
> anonymous/fn@https://staging-console.gridgain.com/app.min.js line 56968 > 
> Function:2:341
> ngEventHandler/https://staging-console.gridgain.com/app.min.js:60659:21
> $RootScopeProvider/this.$gethttps://staging-console.gridgain.com/app.min.js:58582:22
> $RootScopeProvider/this.$gethttps://staging-console.gridgain.com/app.min.js:58605:26
> ngEventHandler/<@https://staging-console.gridgain.com/app.min.js:60664:21
> jQuery.event.dispatch@https://staging-console.gridgain.com/app.min.js:90683:25
> jQuery.event.add/elemData.handle@https://staging-console.gridgain.com/app.min.js:90469:92
> "1 app.min.js:56174:24
> consoleLog/<() app.min.js:56174
> $ExceptionHandlerProvider/this.$get $RootScopeProvider/this.$get ngEventHandler/<() app.min.js:60664
> jQuery.event.dispatch() app.min.js:90683
> jQuery.event.add/elemData.handle() app.min.js:90469
> {code}



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

[jira] [Assigned] (IGNITE-1980) Download button is available on empty Summary page

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-1980:


Assignee: Vasiliy Sisko

> Download button is available on empty Summary page
> --
>
> Key: IGNITE-1980
> URL: https://issues.apache.org/jira/browse/IGNITE-1980
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
> Fix For: 1.5
>
>
> Download button should be unavailable if no one clusters are created.
> Currently user will get:
> {code}
> 16:52:49.086 Error: cluster is undefined
> $generatorProperties.sslProperties@https://console.gridgain.com/generator/generator-properties.js:82:1
> $scope.downloadConfiguration@https://console.gridgain.com/summary-controller.js:209:23
> anonymous/fn@https://console.gridgain.com/app.min.js line 52794 > 
> Function:2:251
> ngEventHandler/https://console.gridgain.com/app.min.js:56475:21
> $RootScopeProvider/this.$gethttps://console.gridgain.com/app.min.js:54398:22
> $RootScopeProvider/this.$gethttps://console.gridgain.com/app.min.js:54421:26
> ngEventHandler/<@https://console.gridgain.com/app.min.js:56480:21
> jQuery.event.dispatch@https://console.gridgain.com/app.min.js:90093:25
> jQuery.event.add/elemData.handle@https://console.gridgain.com/app.min.js:89879:92
> 1 app.min.js:52000:24
> consoleLog/<() app.min.js:52000
> $ExceptionHandlerProvider/this.$get $RootScopeProvider/this.$get ngEventHandler/<() app.min.js:56480
> jQuery.event.dispatch() app.min.js:90093
> jQuery.event.add/elemData.handle() app.min.js:89879
> {code}



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

[jira] [Updated] (IGNITE-1736) Configuration add scroll to group from sidebar

[Alexey Kuznetsov (JIRA)]

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

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

> Configuration add scroll to group from sidebar
> --
>
> Key: IGNITE-1736
> URL: https://issues.apache.org/jira/browse/IGNITE-1736
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: 1.5
>Reporter: Andrey Novikov
> Fix For: 1.5
>
>




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

[jira] [Updated] (IGNITE-1212) Support different version of Ignite

[Alexey Kuznetsov (JIRA)]

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

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

> Support different version of Ignite
> ---
>
> Key: IGNITE-1212
> URL: https://issues.apache.org/jira/browse/IGNITE-1212
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Affects Versions: ignite-1.4
>Reporter: Alexey Kuznetsov
> Fix For: 1.6
>
>
> Ignite configuration could evolve over time. Some new properties added, some 
> deprecated. We should add a dropdown with Ignite version in web UI that will 
> adjust list of available properties to show.



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

[jira] [Created] (IGNITE-2055) Implement ability to select version

[Dmitriyff (JIRA)]

Dmitriyff created IGNITE-2055:
-

 Summary: Implement ability to select version 
 Key: IGNITE-2055
 URL: https://issues.apache.org/jira/browse/IGNITE-2055
 Project: Ignite
  Issue Type: Sub-task
Reporter: Dmitriyff
Assignee: Dmitriyff






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

[jira] [Updated] (IGNITE-2055) Implement ability to select version

[Dmitriyff (JIRA)]

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

Dmitriyff updated IGNITE-2055:
--
Attachment: 7vQf7r8.png

> Implement ability to select version 
> 
>
> Key: IGNITE-2055
> URL: https://issues.apache.org/jira/browse/IGNITE-2055
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Dmitriyff
>Assignee: Dmitriyff
> Fix For: 1.6
>
> Attachments: 7vQf7r8.png
>
>




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

[jira] [Updated] (IGNITE-2056) Chart settings does not open by clicking on button with arrow

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-2056:
---
Description: In all other places it works.  (was: In all others places it 
works.)

> Chart settings does not open by clicking on button with arrow
> -
>
> Key: IGNITE-2056
> URL: https://issues.apache.org/jira/browse/IGNITE-2056
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
>
> In all other places it works.



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

[jira] [Resolved] (IGNITE-2056) Chart settings does not open by clicking on button with arrow

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko resolved IGNITE-2056.
---
Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

Fixed link.

> Chart settings does not open by clicking on button with arrow
> -
>
> Key: IGNITE-2056
> URL: https://issues.apache.org/jira/browse/IGNITE-2056
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
>
> In all other places it works.



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

[jira] [Resolved] (IGNITE-2048) Secondary file system (SFS) is not mandatory in UGFS settings

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko resolved IGNITE-2048.
---
Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

Fixed validation. Message shows only on proxy mode.

> Secondary file system (SFS) is not mandatory in UGFS settings
> -
>
> Key: IGNITE-2048
> URL: https://issues.apache.org/jira/browse/IGNITE-2048
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.5
>
>
> Current javadoc says that if SFS is not configured then IGFS will work in 
> Primary mode. We need to add confirmation about that moment on IGFS save and 
> allow to user to save IGFS without SFS.



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

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

[Andrey Novikov (JIRA)]

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

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

> 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
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
>




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

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

[Andrey Novikov (JIRA)]

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

Andrey Novikov resolved IGNITE-2051.

Resolution: Fixed

Fixed. Pavel, please retest

> 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
>Assignee: Andrey Novikov
> Fix For: 1.6
>
>




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

[jira] [Commented] (IGNITE-843) Web console development

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-843:
---

GitHub user Dmitriyff opened a pull request:

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

IGNITE-843-rc2 update gulp tasks, chage documentation to run console



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

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

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

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


commit 819658208c79422a3ef6ac2b958b709cc699c013
Author: Dmitriyff 
Date:   2015-12-02T11:31:17Z

IGNITE-843-rc2 update tasks




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



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

[jira] [Commented] (IGNITE-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=15035708#comment-15035708
 ] 

ASF GitHub Bot commented on IGNITE-1692:


GitHub user ilantukh opened a pull request:

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

IGNITE-1692 Test Suite for DataStreamProcessorSelfTest.testReplicated.



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

$ git pull https://github.com/ilantukh/ignite 1692

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

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


commit 0ae52562db085e795b441a61a135ee30dd1815fb
Author: Ilya Lantukh 
Date:   2015-12-02T12:02:25Z

Test Suite for DataStreamProcessorSelfTest.testReplicated.




> [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
>
> 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] [Assigned] (IGNITE-2042) Collocated mode is broken for IgniteSet witn BinaryMarshaller

[Semen Boikov (JIRA)]

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

Semen Boikov reassigned IGNITE-2042:


Assignee: Semen Boikov  (was: Yakov Zhdanov)

> Collocated mode is broken for IgniteSet witn 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] [Assigned] (IGNITE-1692) [Test] DataStreamProcessorSelfTest.testReplicated fails sometimes.

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh reassigned IGNITE-1692:


Assignee: Ilya Lantukh

> [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] [Updated] (IGNITE-2046) CPP: Implement catalog ODBC API functions

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-2046:

Summary: CPP: Implement catalog ODBC API functions  (was: CPP: Implement 
SQLColumns ODBC API function)

> CPP: Implement catalog ODBC API functions
> -
>
> Key: IGNITE-2046
> URL: https://issues.apache.org/jira/browse/IGNITE-2046
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> {{SQLColumns}} API function is often used by the data analyzing software to 
> retrieve information about columns returned by the SQL query.



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

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

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-2059:
---

 Summary: CPP: Implement basic support of the params for the OSBC 
driver.
 Key: IGNITE-2059
 URL: https://issues.apache.org/jira/browse/IGNITE-2059
 Project: Ignite
  Issue Type: Sub-task
  Components: interop
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 1.6


We need to provide basic API for parameters binding.
Here is the list of functions that need to be supported:
- {{SQLBindParameter}}
- {{SQLNumParams}}



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

[jira] [Updated] (IGNITE-2046) CPP: Implement catalog ODBC API functions

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-2046:

Description: 
Such API functions is often used by the data analyzing software to retrieve 
information about columns, tables and supported data types.
Here is the list of functions that need to be supported:
- {{SQLColumns}} 
- {{SQLTables}} 
- {{SQLGetTypeInfo}} 
- {{SQLStatistics}} 

  was:
Such API function is often used by the data analyzing software to retrieve 
information about columns, tables and supported data types.
Here is the list of functions that need to be supported:
- {{SQLColumns}} 
- {{SQLTables}} 
- {{SQLGetTypeInfo}} 
- {{SQLStatistics}} 


> CPP: Implement catalog ODBC API functions
> -
>
> Key: IGNITE-2046
> URL: https://issues.apache.org/jira/browse/IGNITE-2046
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> Such API functions is often used by the data analyzing software to retrieve 
> information about columns, tables and supported data types.
> Here is the list of functions that need to be supported:
> - {{SQLColumns}} 
> - {{SQLTables}} 
> - {{SQLGetTypeInfo}} 
> - {{SQLStatistics}} 



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

[jira] [Created] (IGNITE-2060) CPP: Implement access to the metadata for result sets of the ODBC driver.

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-2060:
---

 Summary: CPP: Implement access to the metadata for result sets of 
the ODBC driver. 
 Key: IGNITE-2060
 URL: https://issues.apache.org/jira/browse/IGNITE-2060
 Project: Ignite
  Issue Type: Sub-task
  Components: interop
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 1.6


This type of API functions is often used by the data analyzing software to 
retrieve information about columns, tables and supported data types.
Here is the list of functions that need to be supported:
- {{SQLColAttribute}} 
- {{SQLDescribeCol}} 
- {{SQLRowCount}}



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

[jira] [Resolved] (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 resolved IGNITE-2040.
--
Resolution: Cannot Reproduce
  Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

I created cluster + cache + metadata.
Store was not specified.
Click download on *Summary* page - POJO classes generated.
Also on *Summary* page in *Client* section I see *POJO* tab with classes.
Please check on latest staging.

> 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: Pavel Konstantinov
>Priority: Minor
> Fix For: 1.5
>
>
> 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] [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=15035813#comment-15035813
 ] 

Artem Shutak commented on IGNITE-1864:
--

Will go with the following API (Dev list: 
https://mail-archives.apache.org/mod_mbox/ignite-dev/201512.mbox/browser):

{code}
public  void setTxManagerLookupFactory(Factory f) {

}

public  Factory getTxManagerLookupFactory() {
return ...;
}
{code}

> 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] [Updated] (IGNITE-2046) CPP: Implement catalog ODBC API functions

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-2046:

Description: 
Such API function is often used by the data analyzing software to retrieve 
information about columns, tables and supported data types.
Here is the list of functions that need to be supported:
- {{SQLColumns}} 
- {{SQLTables}} 
- {{SQLGetTypeInfo}} 
- {{SQLStatistics}} 

  was:{{SQLColumns}} API function is often used by the data analyzing software 
to retrieve information about columns returned by the SQL query.


> CPP: Implement catalog ODBC API functions
> -
>
> Key: IGNITE-2046
> URL: https://issues.apache.org/jira/browse/IGNITE-2046
> Project: Ignite
>  Issue Type: Sub-task
>  Components: interop
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> Such API function is often used by the data analyzing software to retrieve 
> information about columns, tables and supported data types.
> Here is the list of functions that need to be supported:
> - {{SQLColumns}} 
> - {{SQLTables}} 
> - {{SQLGetTypeInfo}} 
> - {{SQLStatistics}} 



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

[jira] [Created] (IGNITE-2061) CPP: Implement obtaining of diagnostic information for ODBC driver.

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-2061:
---

 Summary: CPP: Implement obtaining of diagnostic information for 
ODBC driver.
 Key: IGNITE-2061
 URL: https://issues.apache.org/jira/browse/IGNITE-2061
 Project: Ignite
  Issue Type: Sub-task
  Components: interop
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 1.6


These API functions used by user to retrieve diagnostic information, such as 
error or warning messages.
Here is the list of functions that need to be supported:
- {{SQLGetDiagField }}
- {{SQLGetDiagRec}}



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

[jira] [Created] (IGNITE-2062) CPP: Implement support of Linux OS family for the ODBC driver.

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-2062:
---

 Summary: CPP: Implement support of Linux OS family for the ODBC 
driver.
 Key: IGNITE-2062
 URL: https://issues.apache.org/jira/browse/IGNITE-2062
 Project: Ignite
  Issue Type: Sub-task
  Components: interop
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 1.6


ODBC driver should be buildable and usable on the Linux-based OS.



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

Artem Shutak commented on IGNITE-1864:
--

The following points should be discussed in process of review:
# {{CacheJndiTmFactory}}
#* Should we have {{setInitialContextEnvironment}} or not? Map vs Hashtable.
#* 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()}.

> 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] [Updated] (IGNITE-1484) Allow to store configuration in Google Datastore.

[Alexey Kuznetsov (JIRA)]

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

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

> Allow to store configuration in Google Datastore.
> -
>
> Key: IGNITE-1484
> URL: https://issues.apache.org/jira/browse/IGNITE-1484
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Nikita Ivanov
>
> It would be very convenient to store a configuration (e.g. in Google 
> Datastore) and come back to it later. We need to introduce a notion of new 
> configuration (with a name) and ability to "load" previously saved 
> configuration by name.
> We should store these outside of local database so that it would survive 
> restarts and DB updates. Google Datastore is good tech to use here.



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

[jira] [Updated] (IGNITE-1027) Possible data loss in replicated cache on unstable topology.

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-1027:
-
Fix Version/s: 1.5

> Possible data loss in replicated cache on unstable topology.
> 
>
> Key: IGNITE-1027
> URL: https://issues.apache.org/jira/browse/IGNITE-1027
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Sergi Vladykin
>Assignee: Semen Boikov
> Fix For: 1.5
>
>
> In test IgniteCacheClientQueryReplicatedNodeRestartSelfTest we have 4 data 
> nodes with replicated caches and single client-only node, which runs SQL 
> queries against those data nodes. Background threads restarting data nodes. 
> When we restart 2 of 4 data nodes everything is fine, when 3 of 4 then 
> eventually query returns inconsistent result and cache size returns smaller 
> values than expected. Since we use rebalance mode SYNC, such a data loss 
> should not happen.



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

[jira] [Updated] (IGNITE-1484) Allow to store configuration in Google Datastore.

[Alexey Kuznetsov (JIRA)]

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

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

> Allow to store configuration in Google Datastore.
> -
>
> Key: IGNITE-1484
> URL: https://issues.apache.org/jira/browse/IGNITE-1484
> Project: Ignite
>  Issue Type: Bug
>  Components: UI
>Reporter: Nikita Ivanov
>
> It would be very convenient to store a configuration (e.g. in Google 
> Datastore) and come back to it later. We need to introduce a notion of new 
> configuration (with a name) and ability to "load" previously saved 
> configuration by name.
> We should store these outside of local database so that it would survive 
> restarts and DB updates. Google Datastore is good tech to use here.



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

[jira] [Updated] (IGNITE-1483) Web console sign up via Google (i.e. via Google Identity Platform).

[Alexey Kuznetsov (JIRA)]

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

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

> Web console sign up via Google (i.e. via Google Identity Platform).
> ---
>
> Key: IGNITE-1483
> URL: https://issues.apache.org/jira/browse/IGNITE-1483
> Project: Ignite
>  Issue Type: Bug
>  Components: UI
>Reporter: Nikita Ivanov
>
> Basically, why do we ask people to supply email, keep password or security 
> tokens when 99% of them have Google account already. Let's use Google 
> Identity Platform - https://developers.google.com/identity/ - for sign ins.



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

[jira] [Updated] (IGNITE-1483) Web console sign up via Google (i.e. via Google Identity Platform).

[Alexey Kuznetsov (JIRA)]

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

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

> Web console sign up via Google (i.e. via Google Identity Platform).
> ---
>
> Key: IGNITE-1483
> URL: https://issues.apache.org/jira/browse/IGNITE-1483
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Nikita Ivanov
>
> Basically, why do we ask people to supply email, keep password or security 
> tokens when 99% of them have Google account already. Let's use Google 
> Identity Platform - https://developers.google.com/identity/ - for sign ins.



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