[jira] [Commented] (IGNITE-4287) DML: DELETE statement failed: Invalid number of query parameters. Cannot find 2 parameter.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-4287:
-

Will that fix work with OptimizedMarshaller?

> DML: DELETE statement failed: Invalid number of query parameters. Cannot find 
> 2 parameter.
> --
>
> Key: IGNITE-4287
> URL: https://issues.apache.org/jira/browse/IGNITE-4287
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
>Assignee: Sergi Vladykin
> Fix For: 1.8
>
>
> {code:title=test.java|borderStyle=solid}
>   IgniteCache orgCache = 
> Ignition.ignite().cache(ORG_CACHE);
> orgCache.clear();
> for (int z=100; z < 10; z++) {
> orgCache.query(new SqlFieldsQuery("insert into Organization 
> (_key, name) values (?, ?)").setArgs(z, "Org " + Integer.toString(z)));
> }
> for (int z=100; z < 10; z++) {
> if (z > 0 && z % 10 == 0)
> System.out.println("Delete " + z);
> orgCache.query(new SqlFieldsQuery("delete from Organization where 
> _key >= ?").setArgs(z));
> }
> {code}
> The code above failed with IgniteException
> {noformat}
> Exception in thread "main" javax.cache.CacheException: class 
> org.apache.ignite.IgniteException: Invalid number of query parameters. Cannot 
> find 2 parameter.
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:761)
>   at 
> org.apache.ignite.examples.datagrid.CacheQueryExample.initialize(CacheQueryExample.java:336)
>   at 
> org.apache.ignite.examples.datagrid.CacheQueryExample.main(CacheQueryExample.java:110)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: class org.apache.ignite.IgniteException: Invalid number of query 
> parameters. Cannot find 2 parameter.
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:818)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:749)
>   ... 7 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Invalid number of 
> query parameters. Cannot find 2 parameter.
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1789)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:811)
>   ... 8 more
> Caused by: class org.apache.ignite.IgniteException: Invalid number of query 
> parameters. Cannot find 2 parameter.
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.findParams(GridSqlQuerySplitter.java:634)
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.findParams(GridSqlQuerySplitter.java:650)
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.findParams(GridSqlQuerySplitter.java:650)
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.findParams(GridSqlQuerySplitter.java:604)
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.split(GridSqlQuerySplitter.java:403)
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.split(GridSqlQuerySplitter.java:184)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1277)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:226)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:134)
>   at 
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:160)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1266)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:813)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:811)
>   at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
>  

[jira] [Assigned] (IGNITE-3169) .NET: Provide better error messages when user assembly loading has failed

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-3169:
--

Assignee: Pavel Tupitsyn

> .NET: Provide better error messages when user assembly loading has failed
> -
>
> Key: IGNITE-3169
> URL: https://issues.apache.org/jira/browse/IGNITE-3169
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.9
>
>
> Make sure we do not ignore failed assembly load in Apache.Ignite.exe



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

[jira] [Updated] (IGNITE-3169) .NET: Provide better error messages when user assembly loading has failed

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3169:
---
Fix Version/s: (was: 2.0)
   1.9

> .NET: Provide better error messages when user assembly loading has failed
> -
>
> Key: IGNITE-3169
> URL: https://issues.apache.org/jira/browse/IGNITE-3169
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net
> Fix For: 1.9
>
>
> Make sure we do not ignore failed assembly load in Apache.Ignite.exe



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

[jira] [Resolved] (IGNITE-4094) .NET: NPE at org.apache.ignite.internal.processors.platform.services.PlatformAbstractService.execute while running ServicesExample

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-4094.

Resolution: Cannot Reproduce
  Assignee: (was: Pavel Tupitsyn)

> .NET: NPE at 
> org.apache.ignite.internal.processors.platform.services.PlatformAbstractService.execute
>  while running ServicesExample
> --
>
> Key: IGNITE-4094
> URL: https://issues.apache.org/jira/browse/IGNITE-4094
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.6
> Environment: version 1.6.10
>Reporter: Ksenia Rybakova
>  Labels: .NET
> Fix For: 1.9
>
>
> 1) Build examples according to 
> %IGNITE_HOME%\platforms\dotnet\examples\README.txt
> 2) Run 4 standalone Apache Ignite.NET nodes as it is described in 
> ServicesExample.cs
> 3) Run ServicesExample
> NPE occured at one of the nodes. Also it's strange that 
> initialized->started->cancelled happened twice.
> {noformat}
> [15:03:08] Topology snapshot [ver=41, servers=5, clients=0, CPUs=4, 
> heap=18.0GB]
> Service initialized: service
> Service started: service
> Service cancelled: service
> Service initialized: service
> Service cancelled: service
> [15:03:11,062][SEVERE][ignite-#374%null%][GridServiceProcessor] Service 
> execution stopped with error [name=service, 
> execId=e27cefac-31a8-46b7-bee9-b56d060d77b3]
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.platform.services.PlatformAbstractService.execute(PlatformAbstractService.java:119)
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor$2.run(GridServiceProcessor.java:1101)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> [15:03:11] Topology snapshot [ver=42, servers=4, clients=0, CPUs=4, 
> heap=14.0GB]
> {noformat}
> The 2nd node has two "initialized->started->cancelled" as well
> {noformat}
> [15:03:08] Topology snapshot [ver=41, servers=5, clients=0, CPUs=4, 
> heap=18.0GB]
> Service initialized: service
> Service started: service
> Service cancelled: service
> Service initialized: service
> Service started: service
> Service cancelled: service
> [15:03:11] Topology snapshot [ver=42, servers=4, clients=0, CPUs=4, 
> heap=14.0GB]
> {noformat}
> The 3rd and 4th nodes are ok:
> {noformat}
> [15:03:08] Topology snapshot [ver=41, servers=5, clients=0, CPUs=4, 
> heap=18.0GB]
> Service initialized: service
> Service started: service
> Service cancelled: service
> [15:03:11] Topology snapshot [ver=42, servers=4, clients=0, CPUs=4, 
> heap=14.0GB]
> {noformat}



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

[jira] [Commented] (IGNITE-4094) .NET: NPE at org.apache.ignite.internal.processors.platform.services.PlatformAbstractService.execute while running ServicesExample

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4094:


Could not reproduce in 1.6 and 1.7 with 3, 4, 5 standalone nodes (did around 10 
runs each time).

Is there anything else I should know? Did you run any other examples with same 
standalone nodes? Can you please re-check on 1.7?

> .NET: NPE at 
> org.apache.ignite.internal.processors.platform.services.PlatformAbstractService.execute
>  while running ServicesExample
> --
>
> Key: IGNITE-4094
> URL: https://issues.apache.org/jira/browse/IGNITE-4094
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.6
> Environment: version 1.6.10
>Reporter: Ksenia Rybakova
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 1.9
>
>
> 1) Build examples according to 
> %IGNITE_HOME%\platforms\dotnet\examples\README.txt
> 2) Run 4 standalone Apache Ignite.NET nodes as it is described in 
> ServicesExample.cs
> 3) Run ServicesExample
> NPE occured at one of the nodes. Also it's strange that 
> initialized->started->cancelled happened twice.
> {noformat}
> [15:03:08] Topology snapshot [ver=41, servers=5, clients=0, CPUs=4, 
> heap=18.0GB]
> Service initialized: service
> Service started: service
> Service cancelled: service
> Service initialized: service
> Service cancelled: service
> [15:03:11,062][SEVERE][ignite-#374%null%][GridServiceProcessor] Service 
> execution stopped with error [name=service, 
> execId=e27cefac-31a8-46b7-bee9-b56d060d77b3]
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.platform.services.PlatformAbstractService.execute(PlatformAbstractService.java:119)
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor$2.run(GridServiceProcessor.java:1101)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> [15:03:11] Topology snapshot [ver=42, servers=4, clients=0, CPUs=4, 
> heap=14.0GB]
> {noformat}
> The 2nd node has two "initialized->started->cancelled" as well
> {noformat}
> [15:03:08] Topology snapshot [ver=41, servers=5, clients=0, CPUs=4, 
> heap=18.0GB]
> Service initialized: service
> Service started: service
> Service cancelled: service
> Service initialized: service
> Service started: service
> Service cancelled: service
> [15:03:11] Topology snapshot [ver=42, servers=4, clients=0, CPUs=4, 
> heap=14.0GB]
> {noformat}
> The 3rd and 4th nodes are ok:
> {noformat}
> [15:03:08] Topology snapshot [ver=41, servers=5, clients=0, CPUs=4, 
> heap=18.0GB]
> Service initialized: service
> Service started: service
> Service cancelled: service
> [15:03:11] Topology snapshot [ver=42, servers=4, clients=0, CPUs=4, 
> heap=14.0GB]
> {noformat}



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

[jira] [Updated] (IGNITE-4026) BinaryObjectBuilder.build() can fail if one of the fields is Externalizable

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-4026:

Attachment: BuilderTest2.java

> BinaryObjectBuilder.build() can fail if one of the fields is Externalizable
> ---
>
> Key: IGNITE-4026
> URL: https://issues.apache.org/jira/browse/IGNITE-4026
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Dmitry Karachentsev
>Priority: Critical
> Fix For: 2.0
>
> Attachments: BuilderTest.java, BuilderTest2.java
>
>
> Test reproducing the issue is attached.
> Scenario is the following:
> # Create a binary object with an {{Externalizable}} field.
> # Create a builder from this object using {{toBuilder()}} method.
> # Do some modifications.
> # Call {{build()}}, get exception below.
> {noformat}
> Exception in thread "main" class 
> org.apache.ignite.binary.BinaryObjectException: Invalid flag value: -2
>   at 
> org.apache.ignite.internal.binary.builder.BinaryBuilderReader.parseValue(BinaryBuilderReader.java:761)
>   at 
> org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.serializeTo(BinaryObjectBuilderImpl.java:281)
>   at 
> org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.build(BinaryObjectBuilderImpl.java:183)
>   at BuilderTest.main(BuilderTest.java:16)
> {noformat}
> Similar issue exists with enums. An attempt to set enum field to builder with 
> a value which was read from a binary object fails with this exception:
> {noformat}
> Exception in thread "main" class 
> org.apache.ignite.binary.BinaryObjectException: Wrong value has been set 
> [typeName=MyType, fieldName=enum, fieldType=Enum, assignedValueType=Object]
>   at 
> org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.checkMetadata(BinaryObjectBuilderImpl.java:401)
>   at 
> org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.serializeTo(BinaryObjectBuilderImpl.java:316)
>   at 
> org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.build(BinaryObjectBuilderImpl.java:183)
>   at BuilderTest2.main(BuilderTest2.java:15)
> {noformat}
> The letter is reproduced in {{BinaryTest2.java}} (attached).



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

[jira] [Updated] (IGNITE-4026) BinaryObjectBuilder.build() can fail if one of the fields is Externalizable

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-4026:

Description: 
Test reproducing the issue is attached.

Scenario is the following:
# Create a binary object with an {{Externalizable}} field.
# Create a builder from this object using {{toBuilder()}} method.
# Do some modifications.
# Call {{build()}}, get exception below.

{noformat}
Exception in thread "main" class 
org.apache.ignite.binary.BinaryObjectException: Invalid flag value: -2
at 
org.apache.ignite.internal.binary.builder.BinaryBuilderReader.parseValue(BinaryBuilderReader.java:761)
at 
org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.serializeTo(BinaryObjectBuilderImpl.java:281)
at 
org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.build(BinaryObjectBuilderImpl.java:183)
at BuilderTest.main(BuilderTest.java:16)
{noformat}
Similar issue exists with enums. An attempt to set enum field to builder with a 
value which was read from a binary object fails with this exception:
{noformat}
Exception in thread "main" class 
org.apache.ignite.binary.BinaryObjectException: Wrong value has been set 
[typeName=MyType, fieldName=enum, fieldType=Enum, assignedValueType=Object]
at 
org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.checkMetadata(BinaryObjectBuilderImpl.java:401)
at 
org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.serializeTo(BinaryObjectBuilderImpl.java:316)
at 
org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.build(BinaryObjectBuilderImpl.java:183)
at BuilderTest2.main(BuilderTest2.java:15)
{noformat}
The letter is reproduced in {{BinaryTest2.java}} (attached).

  was:
Test reproducing the issue is attached.

Scenario is the following:
# Create a binary object with an {{Externalizable}} field.
# Create a builder from this object using {{toBuilder()}} method.
# Do some modifications.
# Call {{build()}}, get exception below.

{noformat}
Exception in thread "main" class 
org.apache.ignite.binary.BinaryObjectException: Invalid flag value: -2
at 
org.apache.ignite.internal.binary.builder.BinaryBuilderReader.parseValue(BinaryBuilderReader.java:761)
at 
org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.serializeTo(BinaryObjectBuilderImpl.java:281)
at 
org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.build(BinaryObjectBuilderImpl.java:183)
at BuilderTest.main(BuilderTest.java:16)
{noformat}


> BinaryObjectBuilder.build() can fail if one of the fields is Externalizable
> ---
>
> Key: IGNITE-4026
> URL: https://issues.apache.org/jira/browse/IGNITE-4026
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Dmitry Karachentsev
>Priority: Critical
> Fix For: 2.0
>
> Attachments: BuilderTest.java
>
>
> Test reproducing the issue is attached.
> Scenario is the following:
> # Create a binary object with an {{Externalizable}} field.
> # Create a builder from this object using {{toBuilder()}} method.
> # Do some modifications.
> # Call {{build()}}, get exception below.
> {noformat}
> Exception in thread "main" class 
> org.apache.ignite.binary.BinaryObjectException: Invalid flag value: -2
>   at 
> org.apache.ignite.internal.binary.builder.BinaryBuilderReader.parseValue(BinaryBuilderReader.java:761)
>   at 
> org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.serializeTo(BinaryObjectBuilderImpl.java:281)
>   at 
> org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.build(BinaryObjectBuilderImpl.java:183)
>   at BuilderTest.main(BuilderTest.java:16)
> {noformat}
> Similar issue exists with enums. An attempt to set enum field to builder with 
> a value which was read from a binary object fails with this exception:
> {noformat}
> Exception in thread "main" class 
> org.apache.ignite.binary.BinaryObjectException: Wrong value has been set 
> [typeName=MyType, fieldName=enum, fieldType=Enum, assignedValueType=Object]
>   at 
> org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.checkMetadata(BinaryObjectBuilderImpl.java:401)
>   at 
> org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.serializeTo(BinaryObjectBuilderImpl.java:316)
>   at 
> org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.build(BinaryObjectBuilderImpl.java:183)
>   at BuilderTest2.main(BuilderTest2.java:15)
> {noformat}
> The letter is reproduced in {{BinaryTest2.java}} (attached).



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

[jira] [Commented] (IGNITE-1656) Get rid of md5 and sha1 in favor of sha512

[Konstantin Boudnik (JIRA)]

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

Konstantin Boudnik commented on IGNITE-1656:


I stand against lowering the priority of this, because signing releases with a 
weak and proven insecure algorithm posses the risk of delivering malicious code 
to the users.

> Get rid of md5 and sha1 in favor of sha512
> --
>
> Key: IGNITE-1656
> URL: https://issues.apache.org/jira/browse/IGNITE-1656
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Ivan Veselovsky
> Fix For: 2.0
>
>
> Description of the problem wrt sha1 is there:   
> https://sites.google.com/site/itstheshappening/ .



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

[jira] [Updated] (IGNITE-1656) Get rid of md5 and sha1 in favor of sha512

[Konstantin Boudnik (JIRA)]

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

Konstantin Boudnik updated IGNITE-1656:
---
Priority: Major  (was: Minor)

> Get rid of md5 and sha1 in favor of sha512
> --
>
> Key: IGNITE-1656
> URL: https://issues.apache.org/jira/browse/IGNITE-1656
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Ivan Veselovsky
> Fix For: 2.0
>
>
> Description of the problem wrt sha1 is there:   
> https://sites.google.com/site/itstheshappening/ .



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

[jira] [Updated] (IGNITE-4304) ClusterTopologyCheckedException: Failed to send message because node left grid

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov updated IGNITE-4304:
--
Description: 
The server node prints out the following after execution of 
{{CacheClientBinaryPutGetExample}}:
{noformat}
[22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one phase 
commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
Failed to send message because node left grid 
[nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion [topVer=91496812, 
time=1480016812498, order=1480016808989, nodeOrder=1]], super=GridCacheMessage 
[msgId=-1, depInfo=null, err=null, skipPrepare=false, cacheId=0, cacheId=0]]]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1056)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6620)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:764)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}

  was:
The server node prints out the following after execution of some examples:
{noformat}
[22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one phase 
commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
Failed to send message because node left grid 
[nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion [topVer=91496812, 
time=1480016812498, order=1480016808989, nodeOrder=1]], super=GridCacheMessage 
[msgId=-1, depInfo=null, err=null, skipPrepare=false, cacheId=0, cacheId=0]]]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1056)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6620)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:764)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}


> ClusterTopologyCheckedException: Failed to send message because node left grid
> --
>
> Key: IGNITE-4304
> URL: https://issues.apache.org/jira/browse/IGNITE-4304
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
> Fix For: 1.8
>
>
> The server node prints out the following after execution of 
> {{CacheClientBinaryPutGetExample}}:
> {noformat}
> [22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one 
> phase commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
> class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
> Failed to send message because node left grid 
> [nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
> msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion 

[jira] [Updated] (IGNITE-4304) ClusterTopologyCheckedException: Failed to send message because node left grid

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov updated IGNITE-4304:
--
Description: 
The server node prints out the following exception after run  
{{CacheClientBinaryPutGetExample}}:
{noformat}
[22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one phase 
commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
Failed to send message because node left grid 
[nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion [topVer=91496812, 
time=1480016812498, order=1480016808989, nodeOrder=1]], super=GridCacheMessage 
[msgId=-1, depInfo=null, err=null, skipPrepare=false, cacheId=0, cacheId=0]]]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1056)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6620)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:764)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}

  was:
The server node prints out the following after run  
{{CacheClientBinaryPutGetExample}}:
{noformat}
[22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one phase 
commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
Failed to send message because node left grid 
[nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion [topVer=91496812, 
time=1480016812498, order=1480016808989, nodeOrder=1]], super=GridCacheMessage 
[msgId=-1, depInfo=null, err=null, skipPrepare=false, cacheId=0, cacheId=0]]]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1056)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6620)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:764)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}


> ClusterTopologyCheckedException: Failed to send message because node left grid
> --
>
> Key: IGNITE-4304
> URL: https://issues.apache.org/jira/browse/IGNITE-4304
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
> Fix For: 1.8
>
>
> The server node prints out the following exception after run  
> {{CacheClientBinaryPutGetExample}}:
> {noformat}
> [22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one 
> phase commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
> class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
> Failed to send message because node left grid 
> [nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
> msg=GridDhtTxOnePhaseCommitAckRequest 

[jira] [Updated] (IGNITE-4304) ClusterTopologyCheckedException: Failed to send message because node left grid

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov updated IGNITE-4304:
--
Description: 
The server node prints out the following after run  
{{CacheClientBinaryPutGetExample}}:
{noformat}
[22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one phase 
commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
Failed to send message because node left grid 
[nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion [topVer=91496812, 
time=1480016812498, order=1480016808989, nodeOrder=1]], super=GridCacheMessage 
[msgId=-1, depInfo=null, err=null, skipPrepare=false, cacheId=0, cacheId=0]]]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1056)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6620)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:764)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}

  was:
The server node prints out the following after execution of 
{{CacheClientBinaryPutGetExample}}:
{noformat}
[22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one phase 
commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
Failed to send message because node left grid 
[nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion [topVer=91496812, 
time=1480016812498, order=1480016808989, nodeOrder=1]], super=GridCacheMessage 
[msgId=-1, depInfo=null, err=null, skipPrepare=false, cacheId=0, cacheId=0]]]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1056)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6620)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:764)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}


> ClusterTopologyCheckedException: Failed to send message because node left grid
> --
>
> Key: IGNITE-4304
> URL: https://issues.apache.org/jira/browse/IGNITE-4304
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
> Fix For: 1.8
>
>
> The server node prints out the following after run  
> {{CacheClientBinaryPutGetExample}}:
> {noformat}
> [22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one 
> phase commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
> class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
> Failed to send message because node left grid 
> [nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
> msg=GridDhtTxOnePhaseCommitAckRequest 

[jira] [Updated] (IGNITE-4304) ClusterTopologyCheckedException: Failed to send message because node left grid

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov updated IGNITE-4304:
--
Summary: ClusterTopologyCheckedException: Failed to send message because 
node left grid  (was: CLONE - CacheClientBinaryQueryExample returns wrong 
result)

> ClusterTopologyCheckedException: Failed to send message because node left grid
> --
>
> Key: IGNITE-4304
> URL: https://issues.apache.org/jira/browse/IGNITE-4304
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
> Fix For: 1.8
>
>
> The server node print out following after execution of some examples:
> {noformat}
> [22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one 
> phase commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
> class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
> Failed to send message because node left grid 
> [nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
> msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion 
> [topVer=91496812, time=1480016812498, order=1480016808989, nodeOrder=1]], 
> super=GridCacheMessage [msgId=-1, depInfo=null, err=null, skipPrepare=false, 
> cacheId=0, cacheId=0]]]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1056)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
>   at 
> org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
>   at 
> org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
>   at 
> org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6620)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:764)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}



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

[jira] [Updated] (IGNITE-4304) ClusterTopologyCheckedException: Failed to send message because node left grid

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov updated IGNITE-4304:
--
Description: 
The server node prints out the following after execution of some examples:
{noformat}
[22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one phase 
commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
Failed to send message because node left grid 
[nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion [topVer=91496812, 
time=1480016812498, order=1480016808989, nodeOrder=1]], super=GridCacheMessage 
[msgId=-1, depInfo=null, err=null, skipPrepare=false, cacheId=0, cacheId=0]]]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1056)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6620)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:764)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}

  was:
The server node print out following after execution of some examples:
{noformat}
[22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one phase 
commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
Failed to send message because node left grid 
[nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion [topVer=91496812, 
time=1480016812498, order=1480016808989, nodeOrder=1]], super=GridCacheMessage 
[msgId=-1, depInfo=null, err=null, skipPrepare=false, cacheId=0, cacheId=0]]]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1056)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6620)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:764)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}


> ClusterTopologyCheckedException: Failed to send message because node left grid
> --
>
> Key: IGNITE-4304
> URL: https://issues.apache.org/jira/browse/IGNITE-4304
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
> Fix For: 1.8
>
>
> The server node prints out the following after execution of some examples:
> {noformat}
> [22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one 
> phase commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
> class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
> Failed to send message because node left grid 
> [nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
> msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion 
> [topVer=91496812, time=1480016812498, 

[jira] [Updated] (IGNITE-4304) CLONE - CacheClientBinaryQueryExample returns wrong result

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov updated IGNITE-4304:
--
Description: 
The server node print out following after execution of some examples:
{noformat}
[22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one phase 
commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
Failed to send message because node left grid 
[nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion [topVer=91496812, 
time=1480016812498, order=1480016808989, nodeOrder=1]], super=GridCacheMessage 
[msgId=-1, depInfo=null, err=null, skipPrepare=false, cacheId=0, cacheId=0]]]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1056)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6620)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:764)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}

  was:
CacheClientBinaryQueryExample returns wrong result: the list of GridGain 
employees must be not empty.

{noformat}
>>> Employees working for GridGain:

>>> Employee names and their salaries:
>>> [Name=Allison Mathis, salary=25300]
>>> [Name=Breana Robbin, salary=6500]
>>> [Name=Philip Horsley, salary=19800]
>>> [Name=Brian Peters, salary=10600]
>>> [Name=James Wilson, salary=12500]
>>> [Name=Daniel Adams, salary=11000]
>>> [Name=Cristian Moss, salary=12500]
{noformat}

Also the server node print out following:
{noformat}
[22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one phase 
commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
Failed to send message because node left grid 
[nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion [topVer=91496812, 
time=1480016812498, order=1480016808989, nodeOrder=1]], super=GridCacheMessage 
[msgId=-1, depInfo=null, err=null, skipPrepare=false, cacheId=0, cacheId=0]]]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1056)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6620)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:764)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}


> CLONE - CacheClientBinaryQueryExample returns wrong result
> --
>
> Key: IGNITE-4304
> URL: https://issues.apache.org/jira/browse/IGNITE-4304
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
> Fix For: 1.8
>
>
> The server node print out following after execution of some examples:
> {noformat}
> 

[jira] [Created] (IGNITE-4304) CLONE - CacheClientBinaryQueryExample returns wrong result

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-4304:
-

 Summary: CLONE - CacheClientBinaryQueryExample returns wrong result
 Key: IGNITE-4304
 URL: https://issues.apache.org/jira/browse/IGNITE-4304
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.8
Reporter: Sergey Kozlov
 Fix For: 1.8


CacheClientBinaryQueryExample returns wrong result: the list of GridGain 
employees must be not empty.

{noformat}
>>> Employees working for GridGain:

>>> Employee names and their salaries:
>>> [Name=Allison Mathis, salary=25300]
>>> [Name=Breana Robbin, salary=6500]
>>> [Name=Philip Horsley, salary=19800]
>>> [Name=Brian Peters, salary=10600]
>>> [Name=James Wilson, salary=12500]
>>> [Name=Daniel Adams, salary=11000]
>>> [Name=Cristian Moss, salary=12500]
{noformat}

Also the server node print out following:
{noformat}
[22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one phase 
commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
Failed to send message because node left grid 
[nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion [topVer=91496812, 
time=1480016812498, order=1480016808989, nodeOrder=1]], super=GridCacheMessage 
[msgId=-1, depInfo=null, err=null, skipPrepare=false, cacheId=0, cacheId=0]]]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1056)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6620)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:764)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}



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

[jira] [Created] (IGNITE-4303) CacheClientBinaryQueryExample returns wrong result

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-4303:
-

 Summary: CacheClientBinaryQueryExample returns wrong result
 Key: IGNITE-4303
 URL: https://issues.apache.org/jira/browse/IGNITE-4303
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.8
Reporter: Sergey Kozlov
 Fix For: 1.8


CacheClientBinaryQueryExample returns wrong result: the list of GridGain 
employees must be not empty.

{noformat}
>>> Employees working for GridGain:

>>> Employee names and their salaries:
>>> [Name=Allison Mathis, salary=25300]
>>> [Name=Breana Robbin, salary=6500]
>>> [Name=Philip Horsley, salary=19800]
>>> [Name=Brian Peters, salary=10600]
>>> [Name=James Wilson, salary=12500]
>>> [Name=Daniel Adams, salary=11000]
>>> [Name=Cristian Moss, salary=12500]
{noformat}

Also the server node print out following:
{noformat}
[22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one phase 
commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
Failed to send message because node left grid 
[nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion [topVer=91496812, 
time=1480016812498, order=1480016808989, nodeOrder=1]], super=GridCacheMessage 
[msgId=-1, depInfo=null, err=null, skipPrepare=false, cacheId=0, cacheId=0]]]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1056)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6620)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:764)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}



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

[jira] [Commented] (IGNITE-1443) CPP: Implement cache continuous queries.

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-1443:
-

Vladimir,

Here is my approach:

I've added special class {{ignite::Reference}} which can hold any kind of user 
reference. It can be used like that:
{code}
// Function that takes ignite::Reference as an argument.
void foo(ignite::Reference ref);

...
// User passes reference of their object like that:
SomeType obj1;

// Passing simple reference.
foo(ignite::PassReference(obj1);

// Passing object copy.
foo(ignite::PassCopy(obj1);

SomeType* obj2 = new SomeType;

// Passing ownership to the function. That means, object will be deleted,
// once Ignite does not need it anymore. User should not use pointer after
// they have passed it to Ignite.
foo(ignite::PassOwnership(obj2);

std::shared_ptr obj3 = std::make_shared();

// Passing smart pointer. In this case, Reference class behaves like 
// smart pointer of the type, user passes to it.
foo(ignite::PassSmartPointer(obj3);
{code}

You can take a closer look at the code on linked Upsource page. There are also 
tests with all kind of scenarios in file {{reference_test.cpp}}.
Please, review and tell me what do you think. Thanks.

> CPP: Implement cache continuous queries.
> 
>
> Key: IGNITE-1443
> URL: https://issues.apache.org/jira/browse/IGNITE-1443
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Igor Sapego
>  Labels: cpp, important, roadmap
> Fix For: 2.0
>
>




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

[jira] [Assigned] (IGNITE-4094) .NET: NPE at org.apache.ignite.internal.processors.platform.services.PlatformAbstractService.execute while running ServicesExample

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-4094:
--

Assignee: Pavel Tupitsyn

> .NET: NPE at 
> org.apache.ignite.internal.processors.platform.services.PlatformAbstractService.execute
>  while running ServicesExample
> --
>
> Key: IGNITE-4094
> URL: https://issues.apache.org/jira/browse/IGNITE-4094
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.6
> Environment: version 1.6.10
>Reporter: Ksenia Rybakova
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 1.9
>
>
> 1) Build examples according to 
> %IGNITE_HOME%\platforms\dotnet\examples\README.txt
> 2) Run 4 standalone Apache Ignite.NET nodes as it is described in 
> ServicesExample.cs
> 3) Run ServicesExample
> NPE occured at one of the nodes. Also it's strange that 
> initialized->started->cancelled happened twice.
> {noformat}
> [15:03:08] Topology snapshot [ver=41, servers=5, clients=0, CPUs=4, 
> heap=18.0GB]
> Service initialized: service
> Service started: service
> Service cancelled: service
> Service initialized: service
> Service cancelled: service
> [15:03:11,062][SEVERE][ignite-#374%null%][GridServiceProcessor] Service 
> execution stopped with error [name=service, 
> execId=e27cefac-31a8-46b7-bee9-b56d060d77b3]
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.platform.services.PlatformAbstractService.execute(PlatformAbstractService.java:119)
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor$2.run(GridServiceProcessor.java:1101)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> [15:03:11] Topology snapshot [ver=42, servers=4, clients=0, CPUs=4, 
> heap=14.0GB]
> {noformat}
> The 2nd node has two "initialized->started->cancelled" as well
> {noformat}
> [15:03:08] Topology snapshot [ver=41, servers=5, clients=0, CPUs=4, 
> heap=18.0GB]
> Service initialized: service
> Service started: service
> Service cancelled: service
> Service initialized: service
> Service started: service
> Service cancelled: service
> [15:03:11] Topology snapshot [ver=42, servers=4, clients=0, CPUs=4, 
> heap=14.0GB]
> {noformat}
> The 3rd and 4th nodes are ok:
> {noformat}
> [15:03:08] Topology snapshot [ver=41, servers=5, clients=0, CPUs=4, 
> heap=18.0GB]
> Service initialized: service
> Service started: service
> Service cancelled: service
> [15:03:11] Topology snapshot [ver=42, servers=4, clients=0, CPUs=4, 
> heap=14.0GB]
> {noformat}



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

[jira] [Updated] (IGNITE-3169) .NET: Provide better error messages when user assembly loading has failed

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3169:
---
Description: Make sure we do not ignore failed assembly load in 
Apache.Ignite.exe

> .NET: Provide better error messages when user assembly loading has failed
> -
>
> Key: IGNITE-3169
> URL: https://issues.apache.org/jira/browse/IGNITE-3169
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
> Fix For: 2.0
>
>
> Make sure we do not ignore failed assembly load in Apache.Ignite.exe



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

[jira] [Updated] (IGNITE-3886) .NET: Build script

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3886:
---
Description: 
Create a build script with powershell or cake http://cakebuild.net/.

Currently, we have our build completely automated on TeamCity. However, it 
should be possible to build everything (jars, dlls, NuGet) locally with a 
single command.

As a result, we should have:
* bin folder with all .NET-related files (DLL, XML, XSD, etc) and Libs folder 
with jar files
* nupkg folder with all NuGet packages

Investigate how to integrate this with Maven: IGNITE-2292


  was:
Create a build script with powershell or cake http://cakebuild.net/.

Currently, we have our build completely automated on TeamCity. However, it 
should be possible to build everything (jars, dlls, NuGet) locally with a 
single command.

As a result, we should have:
* bin folder with all .NET-related files (DLL, XML, XSD, etc) and Libs folder 
with jar files
* nupkg folder with all NuGet packages



> .NET: Build script
> --
>
> Key: IGNITE-3886
> URL: https://issues.apache.org/jira/browse/IGNITE-3886
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Create a build script with powershell or cake http://cakebuild.net/.
> Currently, we have our build completely automated on TeamCity. However, it 
> should be possible to build everything (jars, dlls, NuGet) locally with a 
> single command.
> As a result, we should have:
> * bin folder with all .NET-related files (DLL, XML, XSD, etc) and Libs folder 
> with jar files
> * nupkg folder with all NuGet packages
> Investigate how to integrate this with Maven: IGNITE-2292



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

[jira] [Assigned] (IGNITE-3886) .NET: Build script

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-3886:
--

Assignee: Pavel Tupitsyn

> .NET: Build script
> --
>
> Key: IGNITE-3886
> URL: https://issues.apache.org/jira/browse/IGNITE-3886
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Create a build script with powershell or cake http://cakebuild.net/.
> Currently, we have our build completely automated on TeamCity. However, it 
> should be possible to build everything (jars, dlls, NuGet) locally with a 
> single command.
> As a result, we should have:
> * bin folder with all .NET-related files (DLL, XML, XSD, etc) and Libs folder 
> with jar files
> * nupkg folder with all NuGet packages



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

[jira] [Updated] (IGNITE-2292) .NET: Add ability to build .NET platform from Maven

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2292:
---
Summary: .NET: Add ability to build .NET platform from Maven  (was: .NET: 
Add ability to build .NET platform from Maven.)

> .NET: Add ability to build .NET platform from Maven
> ---
>
> Key: IGNITE-2292
> URL: https://issues.apache.org/jira/browse/IGNITE-2292
> Project: Ignite
>  Issue Type: Task
>  Components: general, platforms
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>  Labels: .net
> Fix For: 2.0
>
>
> Currently build procedure looks as follows:
> 1) Java is built from Maven
> 2) .NET is built manually using modules/platforms/dotnet/mkbuild.cmd
> 3) Docs fo Java, .NET and CPP are built form Maven
> Looks like we should intergrate .NET buld into Maven process so that user can 
> build the whole product with a single command. E.g.:
> {code}mvn clean package [java_build_args] -Dignite.net.docs=true 
> -Dignite.net.build =true -Dignite.net.build.x86=true 
> -Dignite.net.build.x86.javaHome=[path to x86 JDK]{code}



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

[jira] [Updated] (IGNITE-3568) .NET: Start JVM externally

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-3568:
---
Summary: .NET: Start JVM externally  (was: .NET: Start JVM externally.)

> .NET: Start JVM externally
> --
>
> Key: IGNITE-3568
> URL: https://issues.apache.org/jira/browse/IGNITE-3568
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: .net
>
> Currently we start JVM inside .NET process. This is not good for several 
> reasons:
> 1) Broken isolation - only one JVM can exist per process. This way it is 
> impossible to start two Ignite instances with different JVM options.
> 2) JVM startup is expensive, cluster connection is expensive, and process 
> must host both Java and .NET heaps. Should we have external JVM to connect 
> to, we would allow for truly thin clients, when dozens thin processes will be 
> able to work with the same client. We already see growing demand for this 
> feature,



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

[jira] [Resolved] (IGNITE-4291) SQL: Multi-from join returns no results

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-4291.
-
Resolution: Duplicate

> SQL: Multi-from join returns no results
> ---
>
> Key: IGNITE-4291
> URL: https://issues.apache.org/jira/browse/IGNITE-4291
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>
> {code}
>  select _T0.Name, _T1.Name from "".Person as _T0 , "role_cache".Role as _T1 
> where (_T0._key < ?) and (_T0._key = _T1._foo)
> {code}
> This is CacheLinqTest.TestMultipleFrom in "Ignite Platform .NET" suite. Works 
> in master, does not work in ignite-1.8 after DML merge.
> Models:
> {code}
> CREATE MEMORY TABLE "".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ADDR_ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP,
> PERSON_ALIASTEST INT
> )
> CREATE MEMORY TABLE "role_cache".ROLE(
> _KEY OTHER NOT NULL,
> _VAL OTHER,
> _FOO INT,
> _BAR BIGINT,
> NAME VARCHAR,
> DATE TIMESTAMP
> )
> CREATE MEMORY TABLE "person_cache".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP
> )
> {code}



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

[jira] [Reopened] (IGNITE-4291) SQL: Multi-from join returns no results

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reopened IGNITE-4291:
-

> SQL: Multi-from join returns no results
> ---
>
> Key: IGNITE-4291
> URL: https://issues.apache.org/jira/browse/IGNITE-4291
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>
> {code}
>  select _T0.Name, _T1.Name from "".Person as _T0 , "role_cache".Role as _T1 
> where (_T0._key < ?) and (_T0._key = _T1._foo)
> {code}
> This is CacheLinqTest.TestMultipleFrom in "Ignite Platform .NET" suite. Works 
> in master, does not work in ignite-1.8 after DML merge.
> Models:
> {code}
> CREATE MEMORY TABLE "".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ADDR_ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP,
> PERSON_ALIASTEST INT
> )
> CREATE MEMORY TABLE "role_cache".ROLE(
> _KEY OTHER NOT NULL,
> _VAL OTHER,
> _FOO INT,
> _BAR BIGINT,
> NAME VARCHAR,
> DATE TIMESTAMP
> )
> CREATE MEMORY TABLE "person_cache".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP
> )
> {code}



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

[jira] [Resolved] (IGNITE-4290) SQL: Three-way join returns no results

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-4290.
-
Resolution: Duplicate

IGNITE-4280

> SQL: Three-way join returns no results
> --
>
> Key: IGNITE-4290
> URL: https://issues.apache.org/jira/browse/IGNITE-4290
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>
> Join three tables (two from the same cache) - no results returned.
> {code}
>  select _T0._key, _T0._val, _T1._key, _T1._val, _T2._key, _T2._val from 
> "role_cache".Role as _T2 inner join "".Person as _T1 on (_T1._key = _T2._foo) 
> inner join "".Organization as _T0 on (_T0.Id = _T1.OrganizationId)
> {code}
> This is CacheLinqTest.TestMulticacheJoin in "Ignite Platform .NET" suite. 
> Works in master, does not work in ignite-1.8 after DML merge.
> Models:
> {code}
> CREATE MEMORY TABLE "".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ADDR_ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP,
> PERSON_ALIASTEST INT
> )
> CREATE MEMORY TABLE "role_cache".ROLE(
> _KEY OTHER NOT NULL,
> _VAL OTHER,
> _FOO INT,
> _BAR BIGINT,
> NAME VARCHAR,
> DATE TIMESTAMP
> )
> CREATE MEMORY TABLE "person_cache".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP
> )
> {code}



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

[jira] [Resolved] (IGNITE-4289) SQL: Intersect with subquery returns no results

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-4289.
-
Resolution: Duplicate

IGNITE-4280

> SQL: Intersect with subquery returns no results
> ---
>
> Key: IGNITE-4289
> URL: https://issues.apache.org/jira/browse/IGNITE-4289
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>
> Whole entry intersect works:
> {code}
> select _T0._key, _T0._val from "".Person as _T0 intersect (select _T1._key, 
> _T1._val from "person_cache".Person as _T1)
> {code}
> but subquery intersect does not:
> {code}
> select _T0._key from "".Person as _T0 intersect (select _T1._foo from 
> "role_cache".Role as _T1)
> {code}
> This is CacheLinqTest.TestIntersect in "Ignite Platform .NET" suite. Works in 
> master, does not work in ignite-1.8 after DML merge.
> Models:
> {code}
> CREATE MEMORY TABLE "".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ADDR_ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP,
> PERSON_ALIASTEST INT
> )
> CREATE MEMORY TABLE "role_cache".ROLE(
> _KEY OTHER NOT NULL,
> _VAL OTHER,
> _FOO INT,
> _BAR BIGINT,
> NAME VARCHAR,
> DATE TIMESTAMP
> )
> CREATE MEMORY TABLE "person_cache".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP
> )
> {code}



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

[jira] [Resolved] (IGNITE-4292) SQL: Except returns incorrect results

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-4292.
-
Resolution: Duplicate

> SQL: Except returns incorrect results
> -
>
> Key: IGNITE-4292
> URL: https://issues.apache.org/jira/browse/IGNITE-4292
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>
> {code}
> select _T0._key from "".Person as _T0 except (select _T1._foo from 
> "role_cache".Role as _T1)
> {code}
> Returns all keys even though some are present in both tables.
> This is CacheLinqTest.TestExcept in "Ignite Platform .NET" suite. Works in 
> master, does not work in ignite-1.8 after DML merge.
> Models:
> {code}
> CREATE MEMORY TABLE "".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ADDR_ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP,
> PERSON_ALIASTEST INT
> )
> CREATE MEMORY TABLE "role_cache".ROLE(
> _KEY OTHER NOT NULL,
> _VAL OTHER,
> _FOO INT,
> _BAR BIGINT,
> NAME VARCHAR,
> DATE TIMESTAMP
> )
> CREATE MEMORY TABLE "person_cache".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP
> )
> {code}



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

[jira] [Resolved] (IGNITE-4291) SQL: Multi-from join returns no results

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-4291.
-
Resolution: Fixed

> SQL: Multi-from join returns no results
> ---
>
> Key: IGNITE-4291
> URL: https://issues.apache.org/jira/browse/IGNITE-4291
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>
> {code}
>  select _T0.Name, _T1.Name from "".Person as _T0 , "role_cache".Role as _T1 
> where (_T0._key < ?) and (_T0._key = _T1._foo)
> {code}
> This is CacheLinqTest.TestMultipleFrom in "Ignite Platform .NET" suite. Works 
> in master, does not work in ignite-1.8 after DML merge.
> Models:
> {code}
> CREATE MEMORY TABLE "".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ADDR_ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP,
> PERSON_ALIASTEST INT
> )
> CREATE MEMORY TABLE "role_cache".ROLE(
> _KEY OTHER NOT NULL,
> _VAL OTHER,
> _FOO INT,
> _BAR BIGINT,
> NAME VARCHAR,
> DATE TIMESTAMP
> )
> CREATE MEMORY TABLE "person_cache".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP
> )
> {code}



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

[jira] [Commented] (IGNITE-4287) DML: DELETE statement failed: Invalid number of query parameters. Cannot find 2 parameter.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4287:


GitHub user alexpaschenko opened a pull request:

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

IGNITE-4287 DmlStatementsProcessor logic fix



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

$ git pull https://github.com/gridgain/apache-ignite ignite-4287

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

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


commit 63a36224d30f3d7626770e6a35a9eac05e370290
Author: Alexander Paschenko 
Date:   2016-11-24T06:09:45Z

IGNITE-4287 DmlStatementsProcessor logic fix (always force keepBinary for 
SELECTs inside DML logic)




> DML: DELETE statement failed: Invalid number of query parameters. Cannot find 
> 2 parameter.
> --
>
> Key: IGNITE-4287
> URL: https://issues.apache.org/jira/browse/IGNITE-4287
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
>Assignee: Sergi Vladykin
> Fix For: 1.8
>
>
> {code:title=test.java|borderStyle=solid}
>   IgniteCache orgCache = 
> Ignition.ignite().cache(ORG_CACHE);
> orgCache.clear();
> for (int z=100; z < 10; z++) {
> orgCache.query(new SqlFieldsQuery("insert into Organization 
> (_key, name) values (?, ?)").setArgs(z, "Org " + Integer.toString(z)));
> }
> for (int z=100; z < 10; z++) {
> if (z > 0 && z % 10 == 0)
> System.out.println("Delete " + z);
> orgCache.query(new SqlFieldsQuery("delete from Organization where 
> _key >= ?").setArgs(z));
> }
> {code}
> The code above failed with IgniteException
> {noformat}
> Exception in thread "main" javax.cache.CacheException: class 
> org.apache.ignite.IgniteException: Invalid number of query parameters. Cannot 
> find 2 parameter.
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:761)
>   at 
> org.apache.ignite.examples.datagrid.CacheQueryExample.initialize(CacheQueryExample.java:336)
>   at 
> org.apache.ignite.examples.datagrid.CacheQueryExample.main(CacheQueryExample.java:110)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: class org.apache.ignite.IgniteException: Invalid number of query 
> parameters. Cannot find 2 parameter.
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:818)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:749)
>   ... 7 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Invalid number of 
> query parameters. Cannot find 2 parameter.
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1789)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:811)
>   ... 8 more
> Caused by: class org.apache.ignite.IgniteException: Invalid number of query 
> parameters. Cannot find 2 parameter.
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.findParams(GridSqlQuerySplitter.java:634)
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.findParams(GridSqlQuerySplitter.java:650)
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.findParams(GridSqlQuerySplitter.java:650)
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.findParams(GridSqlQuerySplitter.java:604)
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.split(GridSqlQuerySplitter.java:403)
>   at 
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.split(GridSqlQuerySplitter.java:184)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1277)
>   at 
> 

[jira] [Updated] (IGNITE-4157) Use discovery custom messages instead of marshaller cache

[Sergey Chugunov (JIRA)]

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

Sergey Chugunov updated IGNITE-4157:

Summary: Use discovery custom messages instead of marshaller cache  (was: 
Use discovery custom messages instead of marshaller and system cache)

> Use discovery custom messages instead of marshaller cache
> -
>
> Key: IGNITE-4157
> URL: https://issues.apache.org/jira/browse/IGNITE-4157
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Sergey Chugunov
> Fix For: 2.0
>
>
> Currently we use system caches for keeping classname to class ID mapping and 
> for storing binary metadata
> This has several serious disadvantages:
> 1) We need to introduce at least two additional thread pools for each of 
> these caches
> 2) Since cache operations require stable topology, registering a class ID or 
> updating metadata inside a transaction or another cache operation is tricky 
> and deadlock-prone.
> 3) It may be beneficial in some cases to have nodes with no caches at all, 
> currently this is impossible because system caches are always present.
> 4) Reading binary metadata leads to huge local contention, caching metadata 
> values in a local map doubles memory consumption
> I suggest we use discovery custom events for these purposes. Each node will 
> have a corresponding local map (state) which will be updated inside custom 
> event handler. From the first point of view, this should remove all the 
> disadvantages above.



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

[jira] [Commented] (IGNITE-4302) Use discovery custom messages instead of system cache

[Sergey Chugunov (JIRA)]

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

Sergey Chugunov commented on IGNITE-4302:
-

IGNITE-4157 was decided to be too large improvement to conveniently track 
progress of; part for binary metadata cache was moved to a separate ticket.

> Use discovery custom messages instead of system cache
> -
>
> Key: IGNITE-4302
> URL: https://issues.apache.org/jira/browse/IGNITE-4302
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
> Fix For: 2.0
>
>
> h4. Notes
> See [IGNITE-4157|https://issues.apache.org/jira/browse/IGNITE-4157] for more 
> details about context.
> h4. Acceptance Criteria
> # Binary metadata cache is deleted.
> # Binary metadata exchange is performed using *DiscoveryCustomMessage* events.



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

[jira] [Created] (IGNITE-4302) Use discovery custom messages instead of system cache

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-4302:
---

 Summary: Use discovery custom messages instead of system cache
 Key: IGNITE-4302
 URL: https://issues.apache.org/jira/browse/IGNITE-4302
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Reporter: Sergey Chugunov
Assignee: Sergey Chugunov
 Fix For: 2.0


h4. Notes
See [IGNITE-4157|https://issues.apache.org/jira/browse/IGNITE-4157] for more 
details about context.

h4. Acceptance Criteria
# Binary metadata cache is deleted.
# Binary metadata exchange is performed using *DiscoveryCustomMessage* events.






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

[jira] [Assigned] (IGNITE-4026) BinaryObjectBuilder.build() can fail if one of the fields is Externalizable

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev reassigned IGNITE-4026:
---

Assignee: Dmitry Karachentsev

> BinaryObjectBuilder.build() can fail if one of the fields is Externalizable
> ---
>
> Key: IGNITE-4026
> URL: https://issues.apache.org/jira/browse/IGNITE-4026
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Dmitry Karachentsev
>Priority: Critical
> Fix For: 2.0
>
> Attachments: BuilderTest.java
>
>
> Test reproducing the issue is attached.
> Scenario is the following:
> # Create a binary object with an {{Externalizable}} field.
> # Create a builder from this object using {{toBuilder()}} method.
> # Do some modifications.
> # Call {{build()}}, get exception below.
> {noformat}
> Exception in thread "main" class 
> org.apache.ignite.binary.BinaryObjectException: Invalid flag value: -2
>   at 
> org.apache.ignite.internal.binary.builder.BinaryBuilderReader.parseValue(BinaryBuilderReader.java:761)
>   at 
> org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.serializeTo(BinaryObjectBuilderImpl.java:281)
>   at 
> org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.build(BinaryObjectBuilderImpl.java:183)
>   at BuilderTest.main(BuilderTest.java:16)
> {noformat}



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

[jira] [Updated] (IGNITE-514) Need to lock entries in ATOMIC cache only when doing batch store update

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev updated IGNITE-514:
---
Assignee: (was: Dmitry Karachentsev)

> Need to lock entries in ATOMIC cache only when doing batch store update
> ---
>
> Key: IGNITE-514
> URL: https://issues.apache.org/jira/browse/IGNITE-514
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Andrey Gura
>
> 1. Lock all entries only if store enabled and batch update is true
> 2. Lock entries in natural order if keys are comparable, otherwise serialize 
> keys and sort serialized byte arrays.



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

[jira] [Updated] (IGNITE-514) Need to lock entries in ATOMIC cache only when doing batch store update

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev updated IGNITE-514:
---
Fix Version/s: (was: 2.0)

> Need to lock entries in ATOMIC cache only when doing batch store update
> ---
>
> Key: IGNITE-514
> URL: https://issues.apache.org/jira/browse/IGNITE-514
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Andrey Gura
>Assignee: Dmitry Karachentsev
>
> 1. Lock all entries only if store enabled and batch update is true
> 2. Lock entries in natural order if keys are comparable, otherwise serialize 
> keys and sort serialized byte arrays.



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

[jira] [Created] (IGNITE-4301) Hadoop: put shuffle ack to the top of send queue.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4301:
---

 Summary: Hadoop: put shuffle ack to the top of send queue.
 Key: IGNITE-4301
 URL: https://issues.apache.org/jira/browse/IGNITE-4301
 Project: Ignite
  Issue Type: Sub-task
  Components: general, hadoop
Affects Versions: 1.7, 1.8
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.0


This shuffle acks will be processed ASAP, hence minimizing wait during 
completion.



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

[jira] [Commented] (IGNITE-4300) Hadoop: get rid of shuffle job.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-4300:
-

1) Send messages from mappers synchronously.
2) Can we write them directly to shuffle message? Or may be we can send 
multimap as a whole?

> Hadoop: get rid of shuffle job.
> ---
>
> Key: IGNITE-4300
> URL: https://issues.apache.org/jira/browse/IGNITE-4300
> Project: Ignite
>  Issue Type: Sub-task
>  Components: hadoop
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>
> 1) When mapper detects that 



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

[jira] [Updated] (IGNITE-2662) .NET Standard support

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-2662:
---
Description: 
Ignite.NET should target .NET Standard so it is available on maximum number of 
platforms, see
https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introducing-net-standard/
https://weblog.west-wind.com/posts/2016/Nov/23/NET-Standard-20-Making-Sense-of-NET-Again

This will allow us to run on Windows, OSX, and Linux, and target .NET Core in 
additional to good old regular .NET.

Possible difficulties:
* JNI interop. Core has dllImport and it works on linux, and our C++ client 
works on linux, so it should be possible
* Reflection. We use it a lot, and API has changed.

  was:
Ignite.NET should target .NET Standard so it is available on maximum number of 
platforms, see
https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introducing-net-standard/

This will allow us to run on Windows, OSX, and Linux, and target .NET Core in 
additional to good old regular .NET.

Possible difficulties:
* JNI interop. Core has dllImport and it works on linux, and our C++ client 
works on linux, so it should be possible
* Reflection. We use it a lot, and API has changed.


> .NET Standard support
> -
>
> Key: IGNITE-2662
> URL: https://issues.apache.org/jira/browse/IGNITE-2662
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>  Labels: .net
>
> Ignite.NET should target .NET Standard so it is available on maximum number 
> of platforms, see
> https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introducing-net-standard/
> https://weblog.west-wind.com/posts/2016/Nov/23/NET-Standard-20-Making-Sense-of-NET-Again
> This will allow us to run on Windows, OSX, and Linux, and target .NET Core in 
> additional to good old regular .NET.
> Possible difficulties:
> * JNI interop. Core has dllImport and it works on linux, and our C++ client 
> works on linux, so it should be possible
> * Reflection. We use it a lot, and API has changed.



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

[jira] [Assigned] (IGNITE-3964) SQL: implement support for table alias

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov reassigned IGNITE-3964:


Assignee: Andrew Mashenkov

> SQL: implement support for table alias
> --
>
> Key: IGNITE-3964
> URL: https://issues.apache.org/jira/browse/IGNITE-3964
> Project: Ignite
>  Issue Type: Task
>  Components: SQL
>Affects Versions: 1.6
>Reporter: Alexey Kuznetsov
>Assignee: Andrew Mashenkov
> Fix For: 2.0
>
>
> We have ability to specify aliases for columns via 
> org.apache.ignite.cache.QueryEntity#getAliases.
> But how about alias for table name? This could be useful in case of moving 
> legacy application to Ignite with a lot of SQL statements.



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

[jira] [Resolved] (IGNITE-4297) .NET: Upgrading NuGet to new version does not clean up jar files in bin folder

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-4297.

Resolution: Fixed
  Assignee: (was: Pavel Tupitsyn)

> .NET: Upgrading NuGet to new version does not clean up jar files in bin folder
> --
>
> Key: IGNITE-4297
> URL: https://issues.apache.org/jira/browse/IGNITE-4297
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 1.8
>
>
> Apache.Ignite.Core NuGet package updates post-build step with a script to 
> copy jar files to the bin directory.
> However, this script does not remove old versions of jar files. This causes a 
> problem when upgrading to a new version of NuGet package: user gets an error 
> like
> {code}
> Failed to initialize JVM. ---> Apache.Ignite.Core.Common.IgniteException: 
> Java class method is not found (did you set IGNITE_HOME environment 
> variable?): binaryProcessor ---> Apache.Ignite.Core.Common.JavaException: 
> java.lang.NoSuchMethodError: binaryProcessor
> {code}



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

[jira] [Commented] (IGNITE-4297) .NET: Upgrading NuGet to new version does not clean up jar files in bin folder

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4297:


Github user ptupitsyn closed the pull request at:

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


> .NET: Upgrading NuGet to new version does not clean up jar files in bin folder
> --
>
> Key: IGNITE-4297
> URL: https://issues.apache.org/jira/browse/IGNITE-4297
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 1.8
>
>
> Apache.Ignite.Core NuGet package updates post-build step with a script to 
> copy jar files to the bin directory.
> However, this script does not remove old versions of jar files. This causes a 
> problem when upgrading to a new version of NuGet package: user gets an error 
> like
> {code}
> Failed to initialize JVM. ---> Apache.Ignite.Core.Common.IgniteException: 
> Java class method is not found (did you set IGNITE_HOME environment 
> variable?): binaryProcessor ---> Apache.Ignite.Core.Common.JavaException: 
> java.lang.NoSuchMethodError: binaryProcessor
> {code}



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

[jira] [Commented] (IGNITE-4297) .NET: Upgrading NuGet to new version does not clean up jar files in bin folder

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4297:


Merged to master and 1.8

> .NET: Upgrading NuGet to new version does not clean up jar files in bin folder
> --
>
> Key: IGNITE-4297
> URL: https://issues.apache.org/jira/browse/IGNITE-4297
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 1.8
>
>
> Apache.Ignite.Core NuGet package updates post-build step with a script to 
> copy jar files to the bin directory.
> However, this script does not remove old versions of jar files. This causes a 
> problem when upgrading to a new version of NuGet package: user gets an error 
> like
> {code}
> Failed to initialize JVM. ---> Apache.Ignite.Core.Common.IgniteException: 
> Java class method is not found (did you set IGNITE_HOME environment 
> variable?): binaryProcessor ---> Apache.Ignite.Core.Common.JavaException: 
> java.lang.NoSuchMethodError: binaryProcessor
> {code}



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

[jira] [Resolved] (IGNITE-1725) [Test] IgniteProjectionStartStopRestartSelfTest.testStopNodesByIdsC fails

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky resolved IGNITE-1725.
-
Resolution: Cannot Reproduce

> [Test] IgniteProjectionStartStopRestartSelfTest.testStopNodesByIdsC   fails
> -
>
> Key: IGNITE-1725
> URL: https://issues.apache.org/jira/browse/IGNITE-1725
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Ivan Veselovsky
>Priority: Critical
>  Labels: Muted_test
> Fix For: 2.0
>
>
> {code}
> java.lang.AssertionError: null
> at 
> org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.afterTest(IgniteProjectionStartStopRestartSelfTest.java:179)
> {code}



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

[jira] [Closed] (IGNITE-4179) ExampleNodeStartup fails with IllegalStateException: Cache stopped: CacheQueryExamplePersons for CacheQueryExample

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-4179.
-

> ExampleNodeStartup fails with IllegalStateException: Cache stopped: 
> CacheQueryExamplePersons for CacheQueryExample 
> ---
>
> Key: IGNITE-4179
> URL: https://issues.apache.org/jira/browse/IGNITE-4179
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
> Fix For: 1.8
>
>
> 1. Start two {{ExampleNodeStartup}}
> 2. Run {{CacheQueryExample}}
> 3. All server nodes threw the following exception:
> {noformat}
> java.lang.IllegalStateException: Cache stopped: CacheQueryExamplePersons
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheContext.topology(GridCacheContext.java:827)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionsReservation.release(GridDhtPartitionsReservation.java:207)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2QueryContext.clearContext(GridH2QueryContext.java:419)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2QueryContext.doClear(GridH2QueryContext.java:402)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2QueryContext.clearAfterDeadNode(GridH2QueryContext.java:437)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor$1.onEvent(GridMapQueryExecutor.java:156)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:770)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:755)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:295)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:2102)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:2310)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:2142)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}



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

[jira] [Resolved] (IGNITE-4179) ExampleNodeStartup fails with IllegalStateException: Cache stopped: CacheQueryExamplePersons for CacheQueryExample

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov resolved IGNITE-4179.
---
Resolution: Cannot Reproduce

> ExampleNodeStartup fails with IllegalStateException: Cache stopped: 
> CacheQueryExamplePersons for CacheQueryExample 
> ---
>
> Key: IGNITE-4179
> URL: https://issues.apache.org/jira/browse/IGNITE-4179
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
> Fix For: 1.8
>
>
> 1. Start two {{ExampleNodeStartup}}
> 2. Run {{CacheQueryExample}}
> 3. All server nodes threw the following exception:
> {noformat}
> java.lang.IllegalStateException: Cache stopped: CacheQueryExamplePersons
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheContext.topology(GridCacheContext.java:827)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionsReservation.release(GridDhtPartitionsReservation.java:207)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2QueryContext.clearContext(GridH2QueryContext.java:419)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2QueryContext.doClear(GridH2QueryContext.java:402)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2QueryContext.clearAfterDeadNode(GridH2QueryContext.java:437)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor$1.onEvent(GridMapQueryExecutor.java:156)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:770)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:755)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:295)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:2102)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:2310)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:2142)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}



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

[jira] [Commented] (IGNITE-4297) .NET: Upgrading NuGet to new version does not clean up jar files in bin folder

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4297:


Updated both install and uninstall script to clean up bin\libs folder in all 
build configurations

> .NET: Upgrading NuGet to new version does not clean up jar files in bin folder
> --
>
> Key: IGNITE-4297
> URL: https://issues.apache.org/jira/browse/IGNITE-4297
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 1.8
>
>
> Apache.Ignite.Core NuGet package updates post-build step with a script to 
> copy jar files to the bin directory.
> However, this script does not remove old versions of jar files. This causes a 
> problem when upgrading to a new version of NuGet package: user gets an error 
> like
> {code}
> Failed to initialize JVM. ---> Apache.Ignite.Core.Common.IgniteException: 
> Java class method is not found (did you set IGNITE_HOME environment 
> variable?): binaryProcessor ---> Apache.Ignite.Core.Common.JavaException: 
> java.lang.NoSuchMethodError: binaryProcessor
> {code}



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

[jira] [Commented] (IGNITE-4106) SQL: parallelize sql queries over cache local partitions

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov commented on IGNITE-4106:
--

I've done with splitting indices. There are some broken tests left, unresolved 
issue with distributed joins and issue with prepared statement cache.

Prepared statement cache is now broken due to H2 knows nothing about splitted 
indices and how they work. Reused statement can return same result on different 
segments, so I've just disabled this feature.

Serj, would you please review PR #1278 for if I go the right way.



> SQL: parallelize sql queries over cache local partitions
> 
>
> Key: IGNITE-4106
> URL: https://issues.apache.org/jira/browse/IGNITE-4106
> Project: Ignite
>  Issue Type: Improvement
>  Components: SQL
>Affects Versions: 1.6, 1.7
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>  Labels: performance
> Fix For: 2.0
>
> Attachments: 1node-4thread.jfr, 4node-1thread.jfr
>
>
> If we run SQL query on cache partitioned over several cluster nodes, it will 
> be split into several queries running in parallel. But really we will have 
> one thread per query on each node.
> So, for now, to improve SQL query performance we need to run more Ignite 
> instances or split caches manually.
> It seems to be better to split local SQL queries over cache partitions, so we 
> would be able to parallelize SQL query on every single node and utilize CPU 
> more efficiently.



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

[jira] [Commented] (IGNITE-4299) Remove useless cin.get() in query_example.cpp

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4299:


Looks good.

> Remove useless cin.get() in query_example.cpp
> -
>
> Key: IGNITE-4299
> URL: https://issues.apache.org/jira/browse/IGNITE-4299
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Ksenia Rybakova
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Fix For: 1.8
>
>
> Remove useless cin.get() in query_example.cpp:
> {noformat}
> std::cout << ">>> Ready" << std::endl;
> std::cout << std::endl;
> std::cin.get();
> {noformat}



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

[jira] [Assigned] (IGNITE-4299) Remove useless cin.get() in query_example.cpp

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-4299:
--

Assignee: Igor Sapego  (was: Pavel Tupitsyn)

> Remove useless cin.get() in query_example.cpp
> -
>
> Key: IGNITE-4299
> URL: https://issues.apache.org/jira/browse/IGNITE-4299
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Ksenia Rybakova
>Assignee: Igor Sapego
>Priority: Minor
> Fix For: 1.8
>
>
> Remove useless cin.get() in query_example.cpp:
> {noformat}
> std::cout << ">>> Ready" << std::endl;
> std::cout << std::endl;
> std::cin.get();
> {noformat}



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

[jira] [Resolved] (IGNITE-1724) [Test] IgniteProjectionStartStopRestartSelfTest.testStartOneNode fails

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky resolved IGNITE-1724.
-
Resolution: Cannot Reproduce

> [Test] IgniteProjectionStartStopRestartSelfTest.testStartOneNode fails
> --
>
> Key: IGNITE-1724
> URL: https://issues.apache.org/jira/browse/IGNITE-1724
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Ivan Veselovsky
>Priority: Critical
>  Labels: Muted_test
> Fix For: 2.0
>
>
> {code}
> org.apache.ignite.IgniteException: Default grid instance has already been 
> started.
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:952)
> at 
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:892)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:784)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:705)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:576)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:546)
> at org.apache.ignite.Ignition.start(Ignition.java:346)
> at 
> org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.beforeTest(IgniteProjectionStartStopRestartSelfTest.java:143)
> {code}



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

[jira] [Updated] (IGNITE-4179) ExampleNodeStartup fails with IllegalStateException: Cache stopped: CacheQueryExamplePersons for CacheQueryExample

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4179:

Assignee: Sergey Kozlov

> ExampleNodeStartup fails with IllegalStateException: Cache stopped: 
> CacheQueryExamplePersons for CacheQueryExample 
> ---
>
> Key: IGNITE-4179
> URL: https://issues.apache.org/jira/browse/IGNITE-4179
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
> Fix For: 1.8
>
>
> 1. Start two {{ExampleNodeStartup}}
> 2. Run {{CacheQueryExample}}
> 3. All server nodes threw the following exception:
> {noformat}
> java.lang.IllegalStateException: Cache stopped: CacheQueryExamplePersons
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheContext.topology(GridCacheContext.java:827)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionsReservation.release(GridDhtPartitionsReservation.java:207)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2QueryContext.clearContext(GridH2QueryContext.java:419)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2QueryContext.doClear(GridH2QueryContext.java:402)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2QueryContext.clearAfterDeadNode(GridH2QueryContext.java:437)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor$1.onEvent(GridMapQueryExecutor.java:156)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:770)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:755)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:295)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:2102)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:2310)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:2142)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}



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

[jira] [Commented] (IGNITE-4106) SQL: parallelize sql queries over cache local partitions

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4106:


GitHub user AMashenkov opened a pull request:

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

IGNITE-4106: SQL: parallelize sql queries over cache local partitions

Indexes splitted

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

$ git pull https://github.com/gridgain/apache-ignite ignite-4106-2

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

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


commit cede430c27f1bc73a3fd61a3569c164d16869816
Author: Andrey V. Mashenkov 
Date:   2016-11-18T12:19:33Z

Merged

commit e8329f93003c77d1070cf88be3cbaf19e7845656
Author: Andrey V. Mashenkov 
Date:   2016-11-18T12:47:05Z

index splitted

commit 4e88be252ce35482ac4b885e8e97b7fa16d3e53b
Author: Andrey V. Mashenkov 
Date:   2016-11-24T12:46:15Z

Merge remote-tracking branch 'apache/master' into ignite-4106-2

# Conflicts:
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/twostep/GridMergeIndex.java




> SQL: parallelize sql queries over cache local partitions
> 
>
> Key: IGNITE-4106
> URL: https://issues.apache.org/jira/browse/IGNITE-4106
> Project: Ignite
>  Issue Type: Improvement
>  Components: SQL
>Affects Versions: 1.6, 1.7
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>  Labels: performance
> Fix For: 2.0
>
> Attachments: 1node-4thread.jfr, 4node-1thread.jfr
>
>
> If we run SQL query on cache partitioned over several cluster nodes, it will 
> be split into several queries running in parallel. But really we will have 
> one thread per query on each node.
> So, for now, to improve SQL query performance we need to run more Ignite 
> instances or split caches manually.
> It seems to be better to split local SQL queries over cache partitions, so we 
> would be able to parallelize SQL query on every single node and utilize CPU 
> more efficiently.



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

[jira] [Resolved] (IGNITE-1723) [Test] 2 tests of "Scalar Examples" suite permanently fail due to missing "ignite-schedule" module

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky resolved IGNITE-1723.
-
Resolution: Cannot Reproduce

> [Test] 2 tests of "Scalar Examples" suite permanently fail due to missing 
> "ignite-schedule" module
> --
>
> Key: IGNITE-1723
> URL: https://issues.apache.org/jira/browse/IGNITE-1723
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ivan Veselovsky
>Priority: Critical
>  Labels: Muted_test
> Fix For: 2.0
>
>
> The following 2 tests fail:
>  ScalarExamplesMultiNodeSelfTest.testScalarScheduleCallableExample
>  ScalarExamplesSelfTest.testScalarScheduleCallableExample 
> {code}
> org.apache.ignite.IgniteException: Current Ignite configuration does not 
> support schedule functionality (consider adding ignite-schedule module to 
> classpath).
> at 
> org.apache.ignite.internal.processors.schedule.IgniteNoopScheduleProcessor.processorException(IgniteNoopScheduleProcessor.java:50)
> at 
> org.apache.ignite.internal.processors.schedule.IgniteNoopScheduleProcessor.schedule(IgniteNoopScheduleProcessor.java:43)
> at 
> org.apache.ignite.internal.IgniteSchedulerImpl.scheduleLocal(IgniteSchedulerImpl.java:105)
> at 
> org.apache.ignite.scalar.pimps.ScalarGridPimp.scheduleLocalCall(ScalarGridPimp.scala:76)
> at 
> org.apache.ignite.scalar.examples.ScalarScheduleExample$$anonfun$1.apply$mcV$sp(ScalarScheduleExample.scala:44)
> at 
> org.apache.ignite.scalar.examples.ScalarScheduleExample$$anonfun$1.apply(ScalarScheduleExample.scala:35)
> at 
> org.apache.ignite.scalar.examples.ScalarScheduleExample$$anonfun$1.apply(ScalarScheduleExample.scala:35)
> at org.apache.ignite.scalar.scalar$.init0(scalar.scala:181)
> at org.apache.ignite.scalar.scalar$.apply(scalar.scala:237)
> at 
> org.apache.ignite.scalar.examples.ScalarScheduleExample$.delayedEndpoint$org$apache$ignite$scalar$examples$ScalarScheduleExample$1(ScalarScheduleExample.scala:35)
> at 
> org.apache.ignite.scalar.examples.ScalarScheduleExample$delayedInit$body.apply(ScalarScheduleExample.scala:34)
> at scala.Function0$class.apply$mcV$sp(Function0.scala:40)
> at 
> scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12)
> at scala.App$$anonfun$main$1.apply(App.scala:76)
> at scala.App$$anonfun$main$1.apply(App.scala:76)
> at scala.collection.immutable.List.foreach(List.scala:381)
> at 
> scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:35)
> at scala.App$class.main(App.scala:76)
> at 
> org.apache.ignite.scalar.examples.ScalarScheduleExample$.main(ScalarScheduleExample.scala:34)
> at 
> org.apache.ignite.scalar.tests.examples.ScalarExamplesSelfTest.testScalarScheduleCallableExample(ScalarExamplesSelfTest.scala:81)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1658)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:112)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1596)
> {code}



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

[jira] [Closed] (IGNITE-4186) .NET: "Invalid session release request" exception in IgniteSessionStateStoreProvider.SetAndReleaseItemExclusive

[Ksenia Rybakova (JIRA)]

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

Ksenia Rybakova closed IGNITE-4186.
---

Verified

> .NET: "Invalid session release request" exception in 
> IgniteSessionStateStoreProvider.SetAndReleaseItemExclusive
> ---
>
> Key: IGNITE-4186
> URL: https://issues.apache.org/jira/browse/IGNITE-4186
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.7
> Environment: Windows 10
> MS VS 2015
> .NET Framework 4.0.30319
> ASP.NET 4.6.1586.0
>Reporter: Ksenia Rybakova
>Assignee: Ksenia Rybakova
> Fix For: 1.8
>
>
> Steps:
> - Create a new C# Web application in MS Visual Studio
> - Install Apache.Ignite.AspNet package via Tools->NuGet Package 
> ManagerPackage Manager Console
> - Open Web.config file, remove default sessionState section in  
> and add the following instead:
> {noformat}
> 
>   
>  type="Apache.Ignite.AspNet.IgniteSessionStateStoreProvider, 
> Apache.Ignite.AspNet" />
>   
> 
> {noformat}
> - Open Default.aspx.cs file and add the following to Page_Load method
> {noformat}
> Session["test"] = "abc";
> {noformat}
> - Run project
> - Use Incognito mode or clear the cookies and open the main page
> Result:
> {noformat}
> [IgniteException: Invalid session release request, expected lockId: 0, 
> actual: ]
>  
> Apache.Ignite.AspNet.IgniteSessionStateStoreProvider.SetAndReleaseItemExclusive(HttpContext
>  context, String id, SessionStateStoreData item, Object lockId, Boolean 
> newItem) +298
>System.Web.SessionState.SessionStateModule.OnReleaseState(Object source, 
> EventArgs eventArgs) +573
>
> System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
>  +141
>System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& 
> completedSynchronously) +69
> {noformat}



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

[jira] [Updated] (IGNITE-514) Need to lock entries in ATOMIC cache only when doing batch store update

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev updated IGNITE-514:
---
Component/s: cache

> Need to lock entries in ATOMIC cache only when doing batch store update
> ---
>
> Key: IGNITE-514
> URL: https://issues.apache.org/jira/browse/IGNITE-514
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Andrey Gura
>Assignee: Dmitry Karachentsev
> Fix For: 2.0
>
>
> 1. Lock all entries only if store enabled and batch update is true
> 2. Lock entries in natural order if keys are comparable, otherwise serialize 
> keys and sort serialized byte arrays.



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

[jira] [Updated] (IGNITE-514) Need to lock entries in ATOMIC cache only when doing batch store update

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev updated IGNITE-514:
---
Fix Version/s: 2.0

> Need to lock entries in ATOMIC cache only when doing batch store update
> ---
>
> Key: IGNITE-514
> URL: https://issues.apache.org/jira/browse/IGNITE-514
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Gura
>Assignee: Dmitry Karachentsev
> Fix For: 2.0
>
>
> 1. Lock all entries only if store enabled and batch update is true
> 2. Lock entries in natural order if keys are comparable, otherwise serialize 
> keys and sort serialized byte arrays.



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

[jira] [Commented] (IGNITE-4299) Remove useless cin.get() in query_example.cpp

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4299:


GitHub user isapego opened a pull request:

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

IGNITE-4299: Fixes for examples.



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

$ git pull https://github.com/isapego/ignite ignite-4299

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

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


commit 1403c6438d5d5263d98b3796d15cd65faff8845b
Author: Igor Sapego 
Date:   2016-11-24T12:37:32Z

IGNITE-4299: Fixes for examples.




> Remove useless cin.get() in query_example.cpp
> -
>
> Key: IGNITE-4299
> URL: https://issues.apache.org/jira/browse/IGNITE-4299
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Ksenia Rybakova
>Assignee: Igor Sapego
>Priority: Minor
> Fix For: 1.8
>
>
> Remove useless cin.get() in query_example.cpp:
> {noformat}
> std::cout << ">>> Ready" << std::endl;
> std::cout << std::endl;
> std::cin.get();
> {noformat}



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

[jira] [Assigned] (IGNITE-4299) Remove useless cin.get() in query_example.cpp

[Igor Sapego (JIRA)]

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

Igor Sapego reassigned IGNITE-4299:
---

Assignee: Igor Sapego

> Remove useless cin.get() in query_example.cpp
> -
>
> Key: IGNITE-4299
> URL: https://issues.apache.org/jira/browse/IGNITE-4299
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Ksenia Rybakova
>Assignee: Igor Sapego
>Priority: Minor
> Fix For: 1.8
>
>
> Remove useless cin.get() in query_example.cpp:
> {noformat}
> std::cout << ">>> Ready" << std::endl;
> std::cout << std::endl;
> std::cin.get();
> {noformat}



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

[jira] [Updated] (IGNITE-4299) Remove useless cin.get() in query_example.cpp

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-4299:

Affects Version/s: 1.7

> Remove useless cin.get() in query_example.cpp
> -
>
> Key: IGNITE-4299
> URL: https://issues.apache.org/jira/browse/IGNITE-4299
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Ksenia Rybakova
>Priority: Minor
> Fix For: 1.8
>
>
> Remove useless cin.get() in query_example.cpp:
> {noformat}
> std::cout << ">>> Ready" << std::endl;
> std::cout << std::endl;
> std::cin.get();
> {noformat}



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

[jira] [Updated] (IGNITE-4299) Remove useless cin.get() in query_example.cpp

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-4299:

Fix Version/s: 1.8

> Remove useless cin.get() in query_example.cpp
> -
>
> Key: IGNITE-4299
> URL: https://issues.apache.org/jira/browse/IGNITE-4299
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Ksenia Rybakova
>Priority: Minor
> Fix For: 1.8
>
>
> Remove useless cin.get() in query_example.cpp:
> {noformat}
> std::cout << ">>> Ready" << std::endl;
> std::cout << std::endl;
> std::cin.get();
> {noformat}



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

[jira] [Updated] (IGNITE-4299) Remove useless cin.get() in query_example.cpp

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-4299:

Affects Version/s: (was: 1.7)

> Remove useless cin.get() in query_example.cpp
> -
>
> Key: IGNITE-4299
> URL: https://issues.apache.org/jira/browse/IGNITE-4299
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Ksenia Rybakova
>Priority: Minor
> Fix For: 1.8
>
>
> Remove useless cin.get() in query_example.cpp:
> {noformat}
> std::cout << ">>> Ready" << std::endl;
> std::cout << std::endl;
> std::cin.get();
> {noformat}



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

[jira] [Created] (IGNITE-4299) Remove useless cin.get() in query_example.cpp

[Ksenia Rybakova (JIRA)]

Ksenia Rybakova created IGNITE-4299:
---

 Summary: Remove useless cin.get() in query_example.cpp
 Key: IGNITE-4299
 URL: https://issues.apache.org/jira/browse/IGNITE-4299
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Reporter: Ksenia Rybakova
Priority: Minor


Remove useless cin.get() in query_example.cpp:
{noformat}
std::cout << ">>> Ready" << std::endl;
std::cout << std::endl;
std::cin.get();
{noformat}



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

[jira] [Updated] (IGNITE-872) Scan query scans the whole cache before returning the first page in case of single node

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-872:

Priority: Critical  (was: Blocker)

> Scan query scans the whole cache before returning the first page in case of 
> single node
> ---
>
> Key: IGNITE-872
> URL: https://issues.apache.org/jira/browse/IGNITE-872
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Dmitriy Setrakyan
>Assignee: Sergi Vladykin
>Priority: Critical
>
> Dev list link:
> http://apache-ignite-developers.2346864.n4.nabble.com/Scan-query-with-page-size-should-return-as-first-page-available-td353.html



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

[jira] [Resolved] (IGNITE-1720) [Test] GridVersionSelfTest.testVersions fails

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky resolved IGNITE-1720.
-
Resolution: Cannot Reproduce

> [Test] GridVersionSelfTest.testVersions fails
> -
>
> Key: IGNITE-1720
> URL: https://issues.apache.org/jira/browse/IGNITE-1720
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ivan Veselovsky
>Priority: Critical
>  Labels: Muted_test
> Fix For: 2.0
>
>
> Test GridVersionSelfTest.testVersions fails:
> {code}
> junit.framework.AssertionFailedError: null
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNotNull(Assert.java:256)
> at junit.framework.Assert.assertNotNull(Assert.java:248)
> at junit.framework.TestCase.assertNotNull(TestCase.java:417)
> at 
> org.apache.ignite.internal.GridVersionSelfTest.testVersions(GridVersionSelfTest.java:54)
> {code}



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

[jira] [Commented] (IGNITE-4297) .NET: Upgrading NuGet to new version does not clean up jar files in bin folder

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4297:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-4297 .NET: Update NuGet uninstall script to clean up jars



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

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

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

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


commit 226278bd748b7598749732a9a4e424147ce98fef
Author: Pavel Tupitsyn 
Date:   2016-11-24T11:53:29Z

IGNITE-4297 .NET: Update uninstall script to clean up jars




> .NET: Upgrading NuGet to new version does not clean up jar files in bin folder
> --
>
> Key: IGNITE-4297
> URL: https://issues.apache.org/jira/browse/IGNITE-4297
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 1.8
>
>
> Apache.Ignite.Core NuGet package updates post-build step with a script to 
> copy jar files to the bin directory.
> However, this script does not remove old versions of jar files. This causes a 
> problem when upgrading to a new version of NuGet package: user gets an error 
> like
> {code}
> Failed to initialize JVM. ---> Apache.Ignite.Core.Common.IgniteException: 
> Java class method is not found (did you set IGNITE_HOME environment 
> variable?): binaryProcessor ---> Apache.Ignite.Core.Common.JavaException: 
> java.lang.NoSuchMethodError: binaryProcessor
> {code}



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

[jira] [Resolved] (IGNITE-1719) [Test] GridUpdateNotifierSelfTest.testNotifier fails

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky resolved IGNITE-1719.
-
Resolution: Cannot Reproduce

The test does not fail any more.

> [Test] GridUpdateNotifierSelfTest.testNotifier fails
> -
>
> Key: IGNITE-1719
> URL: https://issues.apache.org/jira/browse/IGNITE-1719
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ivan Veselovsky
>Priority: Critical
>  Labels: Muted_test
> Fix For: 2.0
>
>
> The test fails with timeout: 
> {code}
> java.util.concurrent.TimeoutException: Test has been timed out 
> [test=testNotifier, timeout=3]
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTest(GridAbstractTest.java:1630)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
>   at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
>   at 
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74)
>   at 
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211)
>   at 
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> {code}



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

[jira] [Updated] (IGNITE-4275) Hadoop: create separate property to avoid sorting of mapper output.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4275:

Issue Type: Bug  (was: Sub-task)
Parent: (was: IGNITE-4262)

> Hadoop: create separate property to avoid sorting of mapper output.
> ---
>
> Key: IGNITE-4275
> URL: https://issues.apache.org/jira/browse/IGNITE-4275
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>
> Currently it is "merged" with reducer sorting flag.



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

[jira] [Updated] (IGNITE-4275) Hadoop: create separate property to avoid sorting of mapper output.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4275:

Issue Type: Task  (was: Bug)

> Hadoop: create separate property to avoid sorting of mapper output.
> ---
>
> Key: IGNITE-4275
> URL: https://issues.apache.org/jira/browse/IGNITE-4275
> Project: Ignite
>  Issue Type: Task
>  Components: hadoop
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>
> Currently it is "merged" with reducer sorting flag.



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

[jira] [Closed] (IGNITE-4278) Hadoop: investigate why small array copying is slow on PPC.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-4278.
---

> Hadoop: investigate why small array copying is slow on PPC.
> ---
>
> Key: IGNITE-4278
> URL: https://issues.apache.org/jira/browse/IGNITE-4278
> Project: Ignite
>  Issue Type: Sub-task
>  Components: hadoop
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>




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

[jira] [Resolved] (IGNITE-4278) Hadoop: investigate why small array copying is slow on PPC.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-4278.
-
Resolution: Duplicate

> Hadoop: investigate why small array copying is slow on PPC.
> ---
>
> Key: IGNITE-4278
> URL: https://issues.apache.org/jira/browse/IGNITE-4278
> Project: Ignite
>  Issue Type: Sub-task
>  Components: hadoop
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>




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

[jira] [Resolved] (IGNITE-76) CME in tx map with optimistic txs

[Semen Boikov (JIRA)]

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

Semen Boikov resolved IGNITE-76.

   Resolution: Fixed
 Assignee: (was: Alexey Goncharuk)
Fix Version/s: 1.6

This issue does not reproduce now, verified that access to lockKeys in 
GridDhtTxPrepareFuture is properly sychronized.

> CME in tx map with optimistic txs
> -
>
> Key: IGNITE-76
> URL: https://issues.apache.org/jira/browse/IGNITE-76
> Project: Ignite
>  Issue Type: Bug
>Reporter: Yakov Zhdanov
>Priority: Critical
> Fix For: 1.6
>
>
> {code}
> public class GridGainBulkUpdateBenchmark extends 
> GridGainCacheAbstractBenchmark {
> /** */
> public static final int SHIFT = 1_000_000;
> /** {@inheritDoc} */
> @Override public void setUp(BenchmarkConfiguration cfg) throws Exception {
> super.setUp(cfg);
> println(cfg, "Populating data...");
> long start = System.nanoTime();
> try (GridDataLoader dataLdr = 
> grid().dataLoader(cache.name())) {
> for (int i = 0; i < args.range() && 
> !Thread.currentThread().isInterrupted(); i++) {
> dataLdr.addData(String.valueOf(SHIFT + i), 
> BigDecimal.valueOf(i));
> if (i % 10 == 0)
> println(cfg, "Populated cache: " + i);
> }
> }
> println(cfg, "Finished populating data in " + ((System.nanoTime() - 
> start) / 1_000_000) + " ms.");
> }
> /** {@inheritDoc} */
> @Override public boolean test(Map ctx) throws Exception {
> Map changesMap = generateBatch();
> try (GridCacheTx tx = cache().txStart()) {
> final Map oldVals = 
> cache().getAll(changesMap.keySet());
> final Map newVals = new 
> HashMap<>(oldVals.size());
> for (Map.Entry ent : oldVals.entrySet())
> newVals.put(ent.getKey(), 
> ent.getValue().add(changesMap.get(ent.getKey(;
> cache().putAll(newVals);
> tx.commit();
> }
> return true;
> }
> /**
>  * @return Batch.
>  */
> private Map generateBatch() {
> SortedMap batch = new TreeMap<>();
> while (batch.size() < args.batchSize()) {
> String key = String.valueOf(nextRandom(SHIFT, SHIFT + 
> args.range()));
> batch.put(key, BigDecimal.valueOf(nextRandom(1000)));
> }
> return batch;
> }
> /** {@inheritDoc} */
> @Override protected GridCache cache() {
> return grid().cache("tx");
> }
> }
> {code}
> {noformat}
> Dec 25, 2014 1:40:35 PM org.gridgain.grid.logger.java.GridJavaLogger error
> SEVERE:  Failed processing message 
> [senderId=432325aa-0f4c-4dad-bfeb-077c2fe0ab7e]
> java.util.ConcurrentModificationException
>   at 
> java.util.LinkedHashMap$LinkedHashIterator.nextNode(LinkedHashMap.java:711)
>   at 
> java.util.LinkedHashMap$LinkedEntryIterator.next(LinkedHashMap.java:744)
>   at 
> java.util.LinkedHashMap$LinkedEntryIterator.next(LinkedHashMap.java:742)
>   at 
> org.gridgain.grid.kernal.processors.cache.GridCacheTxMap$1$1.advance(GridCacheTxMap.java:133)
>   at 
> org.gridgain.grid.kernal.processors.cache.GridCacheTxMap$1$1.next(GridCacheTxMap.java:120)
>   at 
> org.gridgain.grid.kernal.processors.cache.GridCacheTxMap$1$1.next(GridCacheTxMap.java:100)
>   at java.util.AbstractMap$2$1.next(AbstractMap.java:396)
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.checkLocks(GridDhtTxPrepareFuture.java:224)
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:369)
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:569)
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtTxLocal.prepareAsync(GridDhtTxLocal.java:425)
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.prepareTx(GridDhtTransactionalCacheAdapter.java:244)
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processNearTxPrepareRequest(GridDhtTransactionalCacheAdapter.java:991)
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$100(GridDhtTransactionalCacheAdapter.java:53)
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$4.apply(GridDhtTransactionalCacheAdapter.java:109)
> 

[jira] [Closed] (IGNITE-76) CME in tx map with optimistic txs

[Semen Boikov (JIRA)]

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

Semen Boikov closed IGNITE-76.
--

> CME in tx map with optimistic txs
> -
>
> Key: IGNITE-76
> URL: https://issues.apache.org/jira/browse/IGNITE-76
> Project: Ignite
>  Issue Type: Bug
>Reporter: Yakov Zhdanov
>Priority: Critical
> Fix For: 1.6
>
>
> {code}
> public class GridGainBulkUpdateBenchmark extends 
> GridGainCacheAbstractBenchmark {
> /** */
> public static final int SHIFT = 1_000_000;
> /** {@inheritDoc} */
> @Override public void setUp(BenchmarkConfiguration cfg) throws Exception {
> super.setUp(cfg);
> println(cfg, "Populating data...");
> long start = System.nanoTime();
> try (GridDataLoader dataLdr = 
> grid().dataLoader(cache.name())) {
> for (int i = 0; i < args.range() && 
> !Thread.currentThread().isInterrupted(); i++) {
> dataLdr.addData(String.valueOf(SHIFT + i), 
> BigDecimal.valueOf(i));
> if (i % 10 == 0)
> println(cfg, "Populated cache: " + i);
> }
> }
> println(cfg, "Finished populating data in " + ((System.nanoTime() - 
> start) / 1_000_000) + " ms.");
> }
> /** {@inheritDoc} */
> @Override public boolean test(Map ctx) throws Exception {
> Map changesMap = generateBatch();
> try (GridCacheTx tx = cache().txStart()) {
> final Map oldVals = 
> cache().getAll(changesMap.keySet());
> final Map newVals = new 
> HashMap<>(oldVals.size());
> for (Map.Entry ent : oldVals.entrySet())
> newVals.put(ent.getKey(), 
> ent.getValue().add(changesMap.get(ent.getKey(;
> cache().putAll(newVals);
> tx.commit();
> }
> return true;
> }
> /**
>  * @return Batch.
>  */
> private Map generateBatch() {
> SortedMap batch = new TreeMap<>();
> while (batch.size() < args.batchSize()) {
> String key = String.valueOf(nextRandom(SHIFT, SHIFT + 
> args.range()));
> batch.put(key, BigDecimal.valueOf(nextRandom(1000)));
> }
> return batch;
> }
> /** {@inheritDoc} */
> @Override protected GridCache cache() {
> return grid().cache("tx");
> }
> }
> {code}
> {noformat}
> Dec 25, 2014 1:40:35 PM org.gridgain.grid.logger.java.GridJavaLogger error
> SEVERE:  Failed processing message 
> [senderId=432325aa-0f4c-4dad-bfeb-077c2fe0ab7e]
> java.util.ConcurrentModificationException
>   at 
> java.util.LinkedHashMap$LinkedHashIterator.nextNode(LinkedHashMap.java:711)
>   at 
> java.util.LinkedHashMap$LinkedEntryIterator.next(LinkedHashMap.java:744)
>   at 
> java.util.LinkedHashMap$LinkedEntryIterator.next(LinkedHashMap.java:742)
>   at 
> org.gridgain.grid.kernal.processors.cache.GridCacheTxMap$1$1.advance(GridCacheTxMap.java:133)
>   at 
> org.gridgain.grid.kernal.processors.cache.GridCacheTxMap$1$1.next(GridCacheTxMap.java:120)
>   at 
> org.gridgain.grid.kernal.processors.cache.GridCacheTxMap$1$1.next(GridCacheTxMap.java:100)
>   at java.util.AbstractMap$2$1.next(AbstractMap.java:396)
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.checkLocks(GridDhtTxPrepareFuture.java:224)
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:369)
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:569)
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtTxLocal.prepareAsync(GridDhtTxLocal.java:425)
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.prepareTx(GridDhtTransactionalCacheAdapter.java:244)
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processNearTxPrepareRequest(GridDhtTransactionalCacheAdapter.java:991)
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$100(GridDhtTransactionalCacheAdapter.java:53)
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$4.apply(GridDhtTransactionalCacheAdapter.java:109)
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$4.apply(GridDhtTransactionalCacheAdapter.java:107)
>   at 
> 

[jira] [Updated] (IGNITE-1656) Get rid of md5 and sha1 in favor of sha512

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky updated IGNITE-1656:

Priority: Minor  (was: Critical)

> Get rid of md5 and sha1 in favor of sha512
> --
>
> Key: IGNITE-1656
> URL: https://issues.apache.org/jira/browse/IGNITE-1656
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Ivan Veselovsky
>Priority: Minor
> Fix For: 2.0
>
>
> Description of the problem wrt sha1 is there:   
> https://sites.google.com/site/itstheshappening/ .



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

[jira] [Updated] (IGNITE-3141) IgnitePartitionedLockSelfTest fails on TC

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-3141:
-
Priority: Major  (was: Critical)

> IgnitePartitionedLockSelfTest fails on TC
> -
>
> Key: IGNITE-3141
> URL: https://issues.apache.org/jira/browse/IGNITE-3141
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Reporter: Semen Boikov
>Assignee: Yakov Zhdanov
> Fix For: 2.0
>
>
> IgnitePartitionedLockSelfTest fails from time to time on TC.
> Example of failed run:
> http://149.202.210.143:8111/viewLog.html?buildId=243004=buildResultsDiv=IgniteTests_IgniteBinaryObjectsDataStrucutures
> IgnitePartitionedLockSelfTest.testConditionAwaitUninterruptibly. Hang:
> {noformat}
> Thread 
> [name="test-runner-#116519%partitioned.IgnitePartitionedLockSelfTest%", 
> id=155625, state=WAITING, blockCnt=0, waitCnt=6]
> Lock [object=o.a.i.i.util.future.GridCompoundFuture@4b9dffc6, 
> ownerName=null, ownerId=-1]
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> at 
> o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:159)
> at 
> o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:117)
> at 
> o.a.i.i.processors.cache.datastructures.IgniteLockAbstractSelfTest.testConditionAwaitUninterruptibly(IgniteLockAbstractSelfTest.java:1233)
> at 
> o.a.i.i.processors.cache.datastructures.IgniteLockAbstractSelfTest.testConditionAwaitUninterruptibly(IgniteLockAbstractSelfTest.java:1158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> o.a.i.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1760)
> at 
> o.a.i.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
> at 
> o.a.i.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1698)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> IgnitePartitionedLockSelfTest.testConditionInterruptAwait
> {noformat}
> junit.framework.AssertionFailedError: null
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertFalse(Assert.java:39)
> at junit.framework.Assert.assertFalse(Assert.java:47)
> at junit.framework.TestCase.assertFalse(TestCase.java:219)
> at 
> org.apache.ignite.internal.processors.cache.datastructures.IgniteLockAbstractSelfTest.testConditionInterruptAwait(IgniteLockAbstractSelfTest.java:1260)
> at 
> org.apache.ignite.internal.processors.cache.datastructures.IgniteLockAbstractSelfTest.testConditionInterruptAwait(IgniteLockAbstractSelfTest.java:1247)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1760)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1698)
> {noformat}
> IgnitePartitionedLockSelfTest.testHasConditionQueuedThreads:
> {noformat}
> junit.framework.AssertionFailedError: null
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertFalse(Assert.java:39)
> at junit.framework.Assert.assertFalse(Assert.java:47)
> at junit.framework.TestCase.assertFalse(TestCase.java:219)
> at 
> org.apache.ignite.internal.processors.cache.datastructures.IgniteLockAbstractSelfTest.testHasConditionQueuedThreads(IgniteLockAbstractSelfTest.java:1416)
> at 
> 

[jira] [Commented] (IGNITE-4280) Fix failing tests in IgniteBinaryCacheQueryTestSuite

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4280:


GitHub user alexpaschenko opened a pull request:

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

IGNITE-4280 Test fix for IgniteBinaryCacheQueryTestSuite



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

$ git pull https://github.com/gridgain/apache-ignite ignite-4280

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

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


commit be73e8af6f2ef3e0c7ad06625d6c59a2054e877d
Author: Alexander Paschenko 
Date:   2016-11-24T10:35:48Z

IGNITE-4280 Test fix for IgniteBinaryCacheQueryTestSuite




> Fix failing tests in IgniteBinaryCacheQueryTestSuite
> 
>
> Key: IGNITE-4280
> URL: https://issues.apache.org/jira/browse/IGNITE-4280
> Project: Ignite
>  Issue Type: Test
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>
> Details: 
> https://issues.apache.org/jira/browse/IGNITE-2294?focusedCommentId=15683377



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

[jira] [Updated] (IGNITE-614) Race in preloading/unswapping

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-614:

Priority: Major  (was: Critical)

> Race in preloading/unswapping
> -
>
> Key: IGNITE-614
> URL: https://issues.apache.org/jira/browse/IGNITE-614
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Semen Boikov
>  Labels: Muted_test
> Fix For: 2.0
>
>
> During unswap entry is removed from swap then unswap listener is notified, 
> and this logic in preload supply worker:
> - register unswap listener
> - iterater over heap
> - iterate over swap
> - remove unswap listener
> - iterate over entries recorded by unswap listener
> There is a race: entry is removed from unswap, listener is not notified yet, 
> at this moment supply worker removes unswap listener.
> These tests fail from time to time because entry can be missed during 
> preloading:
> GridCacheSwapPreloadSelfTest.testSwapPartitionedMultithreaded
> GridCacheSwapPreloadSelfTest.testSwapReplicatedMultithreaded



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

[jira] [Commented] (IGNITE-4298) User exceptions cause IgniteException if Ignite services are deployed separately

[Ben (JIRA)]

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

Ben commented on IGNITE-4298:
-

Looks like this was already reported here: IGNITE-4235

> User exceptions cause IgniteException if Ignite services are deployed 
> separately
> 
>
> Key: IGNITE-4298
> URL: https://issues.apache.org/jira/browse/IGNITE-4298
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Ben
>
> 2 services, Service A and Service B, are deployed and restricted to 
> individual nodes. If A calls a method of B thru the service proxy and a user 
> exception is thrown inside that method, then an IgniteException is thrown due 
> to an InvocationTargetException. See code below for a reproducable example.
> {code:title=MyUserException.java|borderStyle=solid}
> package com.example.testing;
> public class MyUserException extends Throwable {}
> {code}
> {code:title=MyCounterService.java|borderStyle=solid}
> package com.example.testing;
> public interface MyCounterService {
> int increment() throws MyUserException;
> }
> {code}
> Note this error condition in the deployment of the two services: 
> {{ignite.cluster().forYoungest()}}
> {code:title=MyCounterServiceImpl.java|borderStyle=solid}
> package com.example.testing;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteServices;
> import org.apache.ignite.Ignition;
> import org.apache.ignite.resources.IgniteInstanceResource;
> import org.apache.ignite.services.Service;
> import org.apache.ignite.services.ServiceContext;
> public class MyCounterServiceImpl implements MyCounterService, Service {
> @IgniteInstanceResource
> private Ignite ignite;
> private int value = 0;
> public int increment() throws MyUserException {
> if ((value % 2) == 0) {
> throw new MyUserException();
> } else {
> value++;
> }
> return value;
> }
> public static void main(String [] args) {
> Ignite ignite = Ignition.start();
> IgniteServices svcs = ignite.services(ignite.cluster().forYoungest());
> svcs.deployNodeSingleton("MyCounterService", new 
> MyCounterServiceImpl());
> }
> @Override
> public void cancel(ServiceContext ctx) {
> System.out.println("Service cancelled");
> }
> @Override
> public void init(ServiceContext ctx) throws Exception {
> System.out.println("Service initialized");
> }
> @Override
> public void execute(ServiceContext ctx) throws Exception {
> System.out.println("Service running");
> }
> }
> {code}
> {code:title=MyCallerService.java|borderStyle=solid}
> package com.example.testing;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteException;
> import org.apache.ignite.Ignition;
> import org.apache.ignite.resources.IgniteInstanceResource;
> import org.apache.ignite.services.Service;
> import org.apache.ignite.services.ServiceContext;
> public class MyCallerService implements Service {
> @IgniteInstanceResource
> private Ignite ignite;
> private Boolean stopped;
> public void run() {
> stopped = false;
> MyCounterService service = 
> ignite.services().serviceProxy("MyCounterService", MyCounterService.class, 
> false);
> while (!stopped)
> {
> try {
> Thread.sleep(500);
> service.increment();
> } catch (MyUserException e) {
> System.out.println("Got exception");
> //e.printStackTrace();
> } catch (InterruptedException e) {
> //e.printStackTrace();
> }
> catch (IgniteException e) {
> System.out.println("Got critial exception");
> // would print the actual user exception
> //e.getCause().getCause().getCause().printStackTrace();
> break;
> }
> }
> }
> public static void main(String [] args) {
> Ignite ignite = Ignition.start();
> 
> ignite.services(ignite.cluster().forYoungest()).deployNodeSingleton("MyCallerService",
>  new MyCallerService());
> }
> @Override
> public void cancel(ServiceContext ctx) {
> stopped = true;
> }
> @Override
> public void init(ServiceContext ctx) throws Exception {
> }
> @Override
> public void execute(ServiceContext ctx) throws Exception {
> run();
> }
> }
> {code}
> {code:title=Output of MyCounterServiceImpl|borderStyle=solid}
> [18:23:23] Ignite node started OK (id=c82df19c)
> [18:23:23] Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, heap=3.5GB]
> Service initialized
> Service running
> [18:23:27] Topology snapshot [ver=2, 

[jira] [Resolved] (IGNITE-969) Failed to start node if 'textFields' in 'CacheTypeMetadata' contains non String value (Integer in my case)

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov resolved IGNITE-969.
-
Resolution: Won't Fix

{{CacheTypeMetadata}} deprecated and will be removed in Ignite 2.0.
Closing.

> Failed to start node if 'textFields' in 'CacheTypeMetadata' contains non 
> String value (Integer in my case)
> --
>
> Key: IGNITE-969
> URL: https://issues.apache.org/jira/browse/IGNITE-969
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, SQL
>Affects Versions: sprint-6
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Fix For: 2.0
>
>
> {code}
> 
> 
> 
>  value="org.gridgain.visor.tester.sql.AddressKey"/>
>  value="org.gridgain.visor.tester.sql.Address"/>
> 
> 
>  class="org.apache.ignite.cache.CacheTypeFieldMetadata">
> 
> 
>  static-field="java.sql.Types.INTEGER"/>
> 
> 
> 
> 
> 
> 
> 
> 
>  class="org.apache.ignite.cache.CacheTypeFieldMetadata">
> 
> 
>  static-field="java.sql.Types.INTEGER"/>
> 
> 
> 
> 
>  class="org.apache.ignite.cache.CacheTypeFieldMetadata">
> 
> 
>  static-field="java.sql.Types.VARCHAR"/>
> 
> 
>  value="java.lang.String"/>
> 
>  class="org.apache.ignite.cache.CacheTypeFieldMetadata">
> 
> 
>  static-field="java.sql.Types.INTEGER"/>
> 
> 
>  value="java.lang.Integer"/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> zip
> street
> 
> 
> 
> 
> 
> 
> 
>  class="org.apache.ignite.lang.IgniteBiTuple">
>  value="java.lang.String"/>
> 
> 
> 
> 
>  class="org.apache.ignite.lang.IgniteBiTuple">
>  value="java.lang.Integer"/>
> 
> 
> 
> 
> 
> 
> 
> 
>  class="org.apache.ignite.lang.IgniteBiTuple">
> 
> 
> 
> 
> 
>  class="org.apache.ignite.lang.IgniteBiTuple">
>  value="java.lang.String"/>
> 
>

[jira] [Updated] (IGNITE-969) Failed to start node if 'textFields' in 'CacheTypeMetadata' contains non String value (Integer in my case)

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-969:

Priority: Minor  (was: Critical)

> Failed to start node if 'textFields' in 'CacheTypeMetadata' contains non 
> String value (Integer in my case)
> --
>
> Key: IGNITE-969
> URL: https://issues.apache.org/jira/browse/IGNITE-969
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, SQL
>Affects Versions: sprint-6
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 2.0
>
>
> {code}
> 
> 
> 
>  value="org.gridgain.visor.tester.sql.AddressKey"/>
>  value="org.gridgain.visor.tester.sql.Address"/>
> 
> 
>  class="org.apache.ignite.cache.CacheTypeFieldMetadata">
> 
> 
>  static-field="java.sql.Types.INTEGER"/>
> 
> 
> 
> 
> 
> 
> 
> 
>  class="org.apache.ignite.cache.CacheTypeFieldMetadata">
> 
> 
>  static-field="java.sql.Types.INTEGER"/>
> 
> 
> 
> 
>  class="org.apache.ignite.cache.CacheTypeFieldMetadata">
> 
> 
>  static-field="java.sql.Types.VARCHAR"/>
> 
> 
>  value="java.lang.String"/>
> 
>  class="org.apache.ignite.cache.CacheTypeFieldMetadata">
> 
> 
>  static-field="java.sql.Types.INTEGER"/>
> 
> 
>  value="java.lang.Integer"/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> zip
> street
> 
> 
> 
> 
> 
> 
> 
>  class="org.apache.ignite.lang.IgniteBiTuple">
>  value="java.lang.String"/>
> 
> 
> 
> 
>  class="org.apache.ignite.lang.IgniteBiTuple">
>  value="java.lang.Integer"/>
> 
> 
> 
> 
> 
> 
> 
> 
>  class="org.apache.ignite.lang.IgniteBiTuple">
> 
> 
> 
> 
> 
>  class="org.apache.ignite.lang.IgniteBiTuple">
>  value="java.lang.String"/>
> 
> 
> 
>  

[jira] [Closed] (IGNITE-969) Failed to start node if 'textFields' in 'CacheTypeMetadata' contains non String value (Integer in my case)

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov closed IGNITE-969.
---

> Failed to start node if 'textFields' in 'CacheTypeMetadata' contains non 
> String value (Integer in my case)
> --
>
> Key: IGNITE-969
> URL: https://issues.apache.org/jira/browse/IGNITE-969
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, SQL
>Affects Versions: sprint-6
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Fix For: 2.0
>
>
> {code}
> 
> 
> 
>  value="org.gridgain.visor.tester.sql.AddressKey"/>
>  value="org.gridgain.visor.tester.sql.Address"/>
> 
> 
>  class="org.apache.ignite.cache.CacheTypeFieldMetadata">
> 
> 
>  static-field="java.sql.Types.INTEGER"/>
> 
> 
> 
> 
> 
> 
> 
> 
>  class="org.apache.ignite.cache.CacheTypeFieldMetadata">
> 
> 
>  static-field="java.sql.Types.INTEGER"/>
> 
> 
> 
> 
>  class="org.apache.ignite.cache.CacheTypeFieldMetadata">
> 
> 
>  static-field="java.sql.Types.VARCHAR"/>
> 
> 
>  value="java.lang.String"/>
> 
>  class="org.apache.ignite.cache.CacheTypeFieldMetadata">
> 
> 
>  static-field="java.sql.Types.INTEGER"/>
> 
> 
>  value="java.lang.Integer"/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> zip
> street
> 
> 
> 
> 
> 
> 
> 
>  class="org.apache.ignite.lang.IgniteBiTuple">
>  value="java.lang.String"/>
> 
> 
> 
> 
>  class="org.apache.ignite.lang.IgniteBiTuple">
>  value="java.lang.Integer"/>
> 
> 
> 
> 
> 
> 
> 
> 
>  class="org.apache.ignite.lang.IgniteBiTuple">
> 
> 
> 
> 
> 
>  class="org.apache.ignite.lang.IgniteBiTuple">
>  value="java.lang.String"/>
> 
> 
> 
> 
> 

[jira] [Assigned] (IGNITE-969) Failed to start node if 'textFields' in 'CacheTypeMetadata' contains non String value (Integer in my case)

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-969:
---

Assignee: Alexey Kuznetsov  (was: Sergi Vladykin)

> Failed to start node if 'textFields' in 'CacheTypeMetadata' contains non 
> String value (Integer in my case)
> --
>
> Key: IGNITE-969
> URL: https://issues.apache.org/jira/browse/IGNITE-969
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, SQL
>Affects Versions: sprint-6
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Fix For: 2.0
>
>
> {code}
> 
> 
> 
>  value="org.gridgain.visor.tester.sql.AddressKey"/>
>  value="org.gridgain.visor.tester.sql.Address"/>
> 
> 
>  class="org.apache.ignite.cache.CacheTypeFieldMetadata">
> 
> 
>  static-field="java.sql.Types.INTEGER"/>
> 
> 
> 
> 
> 
> 
> 
> 
>  class="org.apache.ignite.cache.CacheTypeFieldMetadata">
> 
> 
>  static-field="java.sql.Types.INTEGER"/>
> 
> 
> 
> 
>  class="org.apache.ignite.cache.CacheTypeFieldMetadata">
> 
> 
>  static-field="java.sql.Types.VARCHAR"/>
> 
> 
>  value="java.lang.String"/>
> 
>  class="org.apache.ignite.cache.CacheTypeFieldMetadata">
> 
> 
>  static-field="java.sql.Types.INTEGER"/>
> 
> 
>  value="java.lang.Integer"/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> zip
> street
> 
> 
> 
> 
> 
> 
> 
>  class="org.apache.ignite.lang.IgniteBiTuple">
>  value="java.lang.String"/>
> 
> 
> 
> 
>  class="org.apache.ignite.lang.IgniteBiTuple">
>  value="java.lang.Integer"/>
> 
> 
> 
> 
> 
> 
> 
> 
>  class="org.apache.ignite.lang.IgniteBiTuple">
> 
> 
> 
> 
> 
>  class="org.apache.ignite.lang.IgniteBiTuple">
>  value="java.lang.String"/>
> 
> 
> 
>   

[jira] [Assigned] (IGNITE-4290) SQL: Three-way join returns no results

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko reassigned IGNITE-4290:
---

Assignee: Alexander Paschenko

> SQL: Three-way join returns no results
> --
>
> Key: IGNITE-4290
> URL: https://issues.apache.org/jira/browse/IGNITE-4290
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>
> Join three tables (two from the same cache) - no results returned.
> {code}
>  select _T0._key, _T0._val, _T1._key, _T1._val, _T2._key, _T2._val from 
> "role_cache".Role as _T2 inner join "".Person as _T1 on (_T1._key = _T2._foo) 
> inner join "".Organization as _T0 on (_T0.Id = _T1.OrganizationId)
> {code}
> This is CacheLinqTest.TestMulticacheJoin in "Ignite Platform .NET" suite. 
> Works in master, does not work in ignite-1.8 after DML merge.
> Models:
> {code}
> CREATE MEMORY TABLE "".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ADDR_ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP,
> PERSON_ALIASTEST INT
> )
> CREATE MEMORY TABLE "role_cache".ROLE(
> _KEY OTHER NOT NULL,
> _VAL OTHER,
> _FOO INT,
> _BAR BIGINT,
> NAME VARCHAR,
> DATE TIMESTAMP
> )
> CREATE MEMORY TABLE "person_cache".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP
> )
> {code}



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

[jira] [Assigned] (IGNITE-4289) SQL: Intersect with subquery returns no results

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko reassigned IGNITE-4289:
---

Assignee: Alexander Paschenko

> SQL: Intersect with subquery returns no results
> ---
>
> Key: IGNITE-4289
> URL: https://issues.apache.org/jira/browse/IGNITE-4289
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>
> Whole entry intersect works:
> {code}
> select _T0._key, _T0._val from "".Person as _T0 intersect (select _T1._key, 
> _T1._val from "person_cache".Person as _T1)
> {code}
> but subquery intersect does not:
> {code}
> select _T0._key from "".Person as _T0 intersect (select _T1._foo from 
> "role_cache".Role as _T1)
> {code}
> This is CacheLinqTest.TestIntersect in "Ignite Platform .NET" suite. Works in 
> master, does not work in ignite-1.8 after DML merge.
> Models:
> {code}
> CREATE MEMORY TABLE "".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ADDR_ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP,
> PERSON_ALIASTEST INT
> )
> CREATE MEMORY TABLE "role_cache".ROLE(
> _KEY OTHER NOT NULL,
> _VAL OTHER,
> _FOO INT,
> _BAR BIGINT,
> NAME VARCHAR,
> DATE TIMESTAMP
> )
> CREATE MEMORY TABLE "person_cache".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP
> )
> {code}



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

[jira] [Updated] (IGNITE-4297) .NET: Upgrading NuGet to new version does not clean up jar files in bin folder

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-4297:
---
Description: 
Apache.Ignite.Core NuGet package updates post-build step with a script to copy 
jar files to the bin directory.

However, this script does not remove old versions of jar files. This causes a 
problem when upgrading to a new version of NuGet package: user gets an error 
like

{code}
Failed to initialize JVM. ---> Apache.Ignite.Core.Common.IgniteException: Java 
class method is not found (did you set IGNITE_HOME environment variable?): 
binaryProcessor ---> Apache.Ignite.Core.Common.JavaException: 
java.lang.NoSuchMethodError: binaryProcessor
{code}


  was:
Apache.Ignite.Core NuGet package updates post-build step with a script to copy 
jar files to the bin directory.

However, this script copies jar files only when the bin\libs folder does not 
exist. This causes a problem when upgrading to a new version of NuGet package: 
bin\libs does not get updated, and user gets an error like

{code}
Failed to initialize JVM. ---> Apache.Ignite.Core.Common.IgniteException: Java 
class method is not found (did you set IGNITE_HOME environment variable?): 
binaryProcessor ---> Apache.Ignite.Core.Common.JavaException: 
java.lang.NoSuchMethodError: binaryProcessor
{code}



> .NET: Upgrading NuGet to new version does not clean up jar files in bin folder
> --
>
> Key: IGNITE-4297
> URL: https://issues.apache.org/jira/browse/IGNITE-4297
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 1.8
>
>
> Apache.Ignite.Core NuGet package updates post-build step with a script to 
> copy jar files to the bin directory.
> However, this script does not remove old versions of jar files. This causes a 
> problem when upgrading to a new version of NuGet package: user gets an error 
> like
> {code}
> Failed to initialize JVM. ---> Apache.Ignite.Core.Common.IgniteException: 
> Java class method is not found (did you set IGNITE_HOME environment 
> variable?): binaryProcessor ---> Apache.Ignite.Core.Common.JavaException: 
> java.lang.NoSuchMethodError: binaryProcessor
> {code}



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

[jira] [Created] (IGNITE-4298) User exceptions cause IgniteException if Ignite services are deployed separately

[Ben (JIRA)]

Ben created IGNITE-4298:
---

 Summary: User exceptions cause IgniteException if Ignite services 
are deployed separately
 Key: IGNITE-4298
 URL: https://issues.apache.org/jira/browse/IGNITE-4298
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.7
Reporter: Ben


2 services, Service A and Service B, are deployed and restricted to individual 
nodes. If A calls a method of B thru the service proxy and a user exception is 
thrown inside that method, then an IgniteException is thrown due to an 
InvocationTargetException. See code below for a reproducable example.

{code:title=MyUserException.java|borderStyle=solid}
package com.example.testing;

public class MyUserException extends Throwable {}
{code}

{code:title=MyCounterService.java|borderStyle=solid}
package com.example.testing;

public interface MyCounterService {
int increment() throws MyUserException;
}
{code}

Note this error condition in the deployment of the two services: 
{{ignite.cluster().forYoungest()}}

{code:title=MyCounterServiceImpl.java|borderStyle=solid}
package com.example.testing;

import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteServices;
import org.apache.ignite.Ignition;
import org.apache.ignite.resources.IgniteInstanceResource;
import org.apache.ignite.services.Service;
import org.apache.ignite.services.ServiceContext;

public class MyCounterServiceImpl implements MyCounterService, Service {

@IgniteInstanceResource
private Ignite ignite;

private int value = 0;

public int increment() throws MyUserException {
if ((value % 2) == 0) {
throw new MyUserException();
} else {
value++;
}
return value;
}

public static void main(String [] args) {
Ignite ignite = Ignition.start();
IgniteServices svcs = ignite.services(ignite.cluster().forYoungest());
svcs.deployNodeSingleton("MyCounterService", new 
MyCounterServiceImpl());
}

@Override
public void cancel(ServiceContext ctx) {
System.out.println("Service cancelled");
}

@Override
public void init(ServiceContext ctx) throws Exception {
System.out.println("Service initialized");
}

@Override
public void execute(ServiceContext ctx) throws Exception {
System.out.println("Service running");
}
}
{code}

{code:title=MyCallerService.java|borderStyle=solid}
package com.example.testing;

import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteException;
import org.apache.ignite.Ignition;
import org.apache.ignite.resources.IgniteInstanceResource;
import org.apache.ignite.services.Service;
import org.apache.ignite.services.ServiceContext;

public class MyCallerService implements Service {

@IgniteInstanceResource
private Ignite ignite;

private Boolean stopped;

public void run() {
stopped = false;
MyCounterService service = 
ignite.services().serviceProxy("MyCounterService", MyCounterService.class, 
false);
while (!stopped)
{
try {
Thread.sleep(500);
service.increment();
} catch (MyUserException e) {
System.out.println("Got exception");
//e.printStackTrace();
} catch (InterruptedException e) {
//e.printStackTrace();
}
catch (IgniteException e) {
System.out.println("Got critial exception");
// would print the actual user exception
//e.getCause().getCause().getCause().printStackTrace();
break;
}
}
}

public static void main(String [] args) {
Ignite ignite = Ignition.start();

ignite.services(ignite.cluster().forYoungest()).deployNodeSingleton("MyCallerService",
 new MyCallerService());
}

@Override
public void cancel(ServiceContext ctx) {
stopped = true;
}

@Override
public void init(ServiceContext ctx) throws Exception {

}

@Override
public void execute(ServiceContext ctx) throws Exception {
run();
}
}
{code}

{code:title=Output of MyCounterServiceImpl|borderStyle=solid}
[18:23:23] Ignite node started OK (id=c82df19c)
[18:23:23] Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, heap=3.5GB]
Service initialized
Service running
[18:23:27] Topology snapshot [ver=2, servers=2, clients=0, CPUs=4, heap=7.0GB]
Nov 17, 2016 6:23:28 PM org.apache.ignite.logger.java.JavaLogger error
SCHWERWIEGEND: Failed to execute job 
[jobId=82580537851-3c0a354f-69b5-496c-af10-ee789a5387c3, ses=GridJobSessionImpl 
[ses=GridTaskSessionImpl 
[taskName=o.a.i.i.processors.service.GridServiceProxy$ServiceProxyCallable, 
dep=LocalDeployment [super=GridDeployment [ts=1479403401422, depMode=SHARED, 
clsLdr=sun.misc.Launcher$AppClassLoader@1d44bcfa, 

[jira] [Updated] (IGNITE-4297) .NET: Upgrading NuGet to new version does not clean up jar files in bin folder

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-4297:
---
Summary: .NET: Upgrading NuGet to new version does not clean up jar files 
in bin folder  (was: .NET: Upgrading NuGet to new version does not update jar 
files in bin folder)

> .NET: Upgrading NuGet to new version does not clean up jar files in bin folder
> --
>
> Key: IGNITE-4297
> URL: https://issues.apache.org/jira/browse/IGNITE-4297
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 1.8
>
>
> Apache.Ignite.Core NuGet package updates post-build step with a script to 
> copy jar files to the bin directory.
> However, this script copies jar files only when the bin\libs folder does not 
> exist. This causes a problem when upgrading to a new version of NuGet 
> package: bin\libs does not get updated, and user gets an error like
> {code}
> Failed to initialize JVM. ---> Apache.Ignite.Core.Common.IgniteException: 
> Java class method is not found (did you set IGNITE_HOME environment 
> variable?): binaryProcessor ---> Apache.Ignite.Core.Common.JavaException: 
> java.lang.NoSuchMethodError: binaryProcessor
> {code}



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

[jira] [Assigned] (IGNITE-4291) SQL: Multi-from join returns no results

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko reassigned IGNITE-4291:
---

Assignee: Alexander Paschenko

> SQL: Multi-from join returns no results
> ---
>
> Key: IGNITE-4291
> URL: https://issues.apache.org/jira/browse/IGNITE-4291
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>
> {code}
>  select _T0.Name, _T1.Name from "".Person as _T0 , "role_cache".Role as _T1 
> where (_T0._key < ?) and (_T0._key = _T1._foo)
> {code}
> This is CacheLinqTest.TestMultipleFrom in "Ignite Platform .NET" suite. Works 
> in master, does not work in ignite-1.8 after DML merge.
> Models:
> {code}
> CREATE MEMORY TABLE "".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ADDR_ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP,
> PERSON_ALIASTEST INT
> )
> CREATE MEMORY TABLE "role_cache".ROLE(
> _KEY OTHER NOT NULL,
> _VAL OTHER,
> _FOO INT,
> _BAR BIGINT,
> NAME VARCHAR,
> DATE TIMESTAMP
> )
> CREATE MEMORY TABLE "person_cache".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP
> )
> {code}



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

[jira] [Assigned] (IGNITE-4292) SQL: Except returns incorrect results

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko reassigned IGNITE-4292:
---

Assignee: Alexander Paschenko

> SQL: Except returns incorrect results
> -
>
> Key: IGNITE-4292
> URL: https://issues.apache.org/jira/browse/IGNITE-4292
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>
> {code}
> select _T0._key from "".Person as _T0 except (select _T1._foo from 
> "role_cache".Role as _T1)
> {code}
> Returns all keys even though some are present in both tables.
> This is CacheLinqTest.TestExcept in "Ignite Platform .NET" suite. Works in 
> master, does not work in ignite-1.8 after DML merge.
> Models:
> {code}
> CREATE MEMORY TABLE "".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ADDR_ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP,
> PERSON_ALIASTEST INT
> )
> CREATE MEMORY TABLE "role_cache".ROLE(
> _KEY OTHER NOT NULL,
> _VAL OTHER,
> _FOO INT,
> _BAR BIGINT,
> NAME VARCHAR,
> DATE TIMESTAMP
> )
> CREATE MEMORY TABLE "person_cache".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP
> )
> {code}



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

[jira] [Assigned] (IGNITE-4263) Hadoop: abstract out offheap/heap memory management.

[Taras Ledkov (JIRA)]

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

Taras Ledkov reassigned IGNITE-4263:


Assignee: Taras Ledkov  (was: Vladimir Ozerov)

> Hadoop: abstract out offheap/heap memory management.
> 
>
> Key: IGNITE-4263
> URL: https://issues.apache.org/jira/browse/IGNITE-4263
> Project: Ignite
>  Issue Type: Sub-task
>  Components: hadoop
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>




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

[jira] [Commented] (IGNITE-4288) ODBC: Fix ODBC and DML interoperability.

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-4288:
-

[~dmagda], no I don't.

I guess, we can open a new ticket if someone really needs such a feature, 
though I doubt anyone does.

> ODBC: Fix ODBC and DML interoperability.
> 
>
> Key: IGNITE-4288
> URL: https://issues.apache.org/jira/browse/IGNITE-4288
> Project: Ignite
>  Issue Type: Bug
>  Components: odbc
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Vladimir Ozerov
> Fix For: 1.8
>
>
> Need to fix ODBC-DML interoperability issues on ignite-1.8 branch.
> Failing tests list:
> * odbc-tests/QueriesTestSuite/TestInsertDeleteSelect  
> * odbc-tests/QueriesTestSuite/TestInsertMergeSelect   
> * odbc-tests/QueriesTestSuite/TestInsertSelect
> * odbc-tests/QueriesTestSuite/TestInsertUpdateSelect 



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

[jira] [Updated] (IGNITE-2845) Get operation might ignore entry update from EntryProcessor.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2845:

Priority: Major  (was: Critical)

> Get operation might ignore entry update from EntryProcessor.
> 
>
> Key: IGNITE-2845
> URL: https://issues.apache.org/jira/browse/IGNITE-2845
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
> Fix For: 2.0
>
>
> Originally issue was observed during work with IGFS. Steps to reproduce:
> 1) Start REPLICATE cache.
> 2) Start PESSIMISITC/REPEATABLE_READ transaction.
> 3) Invoke EntryProcessor on non-existent key and call 
> "MutableEntry.setValue()" inside it.
> 4) Call {{IgniteCache.get()}} on this value. It will return {{null}}, while 
> normally it should return value set inside EntryProcessor.



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

[jira] [Updated] (IGNITE-2671) Node cannot join topology when cache lock is held.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2671:

Priority: Major  (was: Critical)

> Node cannot join topology when cache lock is held.
> --
>
> Key: IGNITE-2671
> URL: https://issues.apache.org/jira/browse/IGNITE-2671
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>  Labels: community
> Fix For: 2.0
>
>
> The problem is originally reported by Mario: 
> http://apache-ignite-users.70518.x6.nabble.com/Semaphore-blocking-on-tryAcquire-while-holding-a-cache-lock-td3031.html
> *Description*
> When a lock is held on a cache key, another node cannot join topology. It 
> hangs somewhere on partition exchange future.
> *Steps to reproduce*
> Run the following code and observe that ">>> STARTED 2" is never printed 
> because we cannot leave Ignition.start() method.
> {code}
> public static void main(String[] args) {
> // Start the first node.
> Ignite ignite = Ignition.start(new 
> IgniteConfiguration().setGridName("1"));
> System.out.println(">>> STARTED 1");
> // Create cache and obtain a lock on it.
> CacheConfiguration ccfg =
> new CacheConfiguration String>().setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
> ignite.getOrCreateCache(ccfg).lock("key").lock();
> System.out.println(">>> LOCKED");
> Ignition.start(new IgniteConfiguration().setGridName("2"));
> System.out.println(">>> STARTED 2");
> }
> {code}



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

[jira] [Updated] (IGNITE-2216) Duplicate field names with aliases do not work in queries.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2216:

Priority: Major  (was: Critical)

> Duplicate field names with aliases do not work in queries.
> --
>
> Key: IGNITE-2216
> URL: https://issues.apache.org/jira/browse/IGNITE-2216
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
> Fix For: 2.0
>
>




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

[jira] [Updated] (IGNITE-744) removeAll() doesn't remove swapped entries for LOCAL cache.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-744:
---
Priority: Major  (was: Critical)

> removeAll() doesn't remove swapped entries for LOCAL cache.
> ---
>
> Key: IGNITE-744
> URL: https://issues.apache.org/jira/browse/IGNITE-744
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-1
>Reporter: Vladimir Ozerov
>
> For local cache we simply iterate over in-memory keyset. As a result, swapped 
> entries are not removed.



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

[jira] [Updated] (IGNITE-305) Inconsistent TTL update.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-305:
---
Priority: Minor  (was: Critical)

> Inconsistent TTL update.
> 
>
> Key: IGNITE-305
> URL: https://issues.apache.org/jira/browse/IGNITE-305
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-2
>Reporter: Vladimir Ozerov
>Priority: Minor
>
> TTL update messages must be sent in ordered mode and must contain expected 
> version. 
> If version do not match, ignore. If match - update TTL.



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

[jira] [Updated] (IGNITE-19) Race condition when offheaped value is being promoted to swap.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-19:
--
Priority: Major  (was: Critical)

> Race condition when offheaped value is being promoted to swap.
> --
>
> Key: IGNITE-19
> URL: https://issues.apache.org/jira/browse/IGNITE-19
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-1
>Reporter: Vladimir Ozerov
> Fix For: 2.0
>
>
> Eviction from offheap to swap is done using listener on GridUnsafeMap. 
> Notification of this listener happens when value is already deleted from 
> offheap and lock is released (GridUnsafeMap line 860). So "get" operation on 
> cache can miss the value while it is in between.
> Need to:
> 1) Review this code piece;
> 2) Create a test reproducing the issue;
> 3) Fix it.



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

[jira] [Updated] (IGNITE-835) IgniteCache.lock is broken for PARTITIONED cache without near cache.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-835:
---
Priority: Major  (was: Critical)

> IgniteCache.lock is broken for PARTITIONED cache without near cache.
> 
>
> Key: IGNITE-835
> URL: https://issues.apache.org/jira/browse/IGNITE-835
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-2
>Reporter: Vladimir Ozerov
>Assignee: Alexey Goncharuk
>  Labels: Muted_test
>
> Steps to reproduce:
> 1) Go to GridCacheLockAbstractTest
> 2) Add the test source below.
> 3) Make sure to disable near cache 
> (GridCacheLockAbstractTest.cacheConfiguration() -> 
> setNearConfiguration(null)).
> 4) Run GridCachePartitionedLockSelfTest.testLockReentrancy() and observe 
> assertion failure.
> 5) Enable near cache back and re-run the test. Observe that now it pass.
> {code}
> public void testLockReentrancy() throws Throwable {
> for (int i = 10; i < 100; i++) {
> System.out.println("Key: " + i);
> final int i0 = i;
> final Lock lock = cache1.lock(i);
> lock.lockInterruptibly();
> try {
> final AtomicReference err = new AtomicReference<>();
> Thread t =  new Thread(new Runnable() {
> @Override public void run() {
> try {
> assert !lock.tryLock();
> assert !lock.tryLock(100, TimeUnit.MILLISECONDS);
> assert !cache1.lock(i0).tryLock();
> assert !cache1.lock(i0).tryLock(100, 
> TimeUnit.MILLISECONDS);
> }
> catch (Throwable e) {
> err.set(e);
> }
> }
> });
> t.start();
> t.join();
> if (err.get() != null)
> throw err.get();
> lock.lock();
> lock.unlock();
> t =  new Thread(new Runnable() {
> @Override public void run() {
> try {
> assert !lock.tryLock();
> assert !lock.tryLock(100, TimeUnit.MILLISECONDS);
> assert !cache1.lock(i0).tryLock();
> assert !cache1.lock(i0).tryLock(100, 
> TimeUnit.MILLISECONDS);
> }
> catch (Throwable e) {
> err.set(e);
> }
> }
> });
> t.start();
> t.join();
> if (err.get() != null)
> throw err.get();
> }
> finally {
> lock.unlock();
> }
> }
> }
> {code}



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

[jira] [Updated] (IGNITE-1215) GridConnectionBytesVerifyFilter doesn't write magic header.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1215:

Priority: Minor  (was: Critical)

> GridConnectionBytesVerifyFilter doesn't write magic header.
> ---
>
> Key: IGNITE-1215
> URL: https://issues.apache.org/jira/browse/IGNITE-1215
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Priority: Minor
>
> GridConnectionBytesVerifyFilter performs magic header check on read, but do 
> not add magic header on write.
> Test:
> 1) Open GridNioSelfTest class.
> 2) Add filter {code}new GridConnectionBytesVerifyFilter(log){code} in the 
> serverBuilder() method.
> 3) Run testAsyncSendReceive() test and verify it fails.
> 4) Open GridConnectionBytesVerifyFilter class.
> 5) Add a field: 
> {code}
> private static final int MAGIC_WRITE_KEY  = 
> GridNioSessionMetaKey.nextUniqueKey();
> {code}
> 6) Change onSessionWriteMethod as follows:
> {code}
> /** {@inheritDoc} */
> @Override public GridNioFuture onSessionWrite(GridNioSession ses, 
> Object msg) throws IgniteCheckedException {
> if (!ses.accepted() && ses.meta(MAGIC_WRITE_KEY) == null) {
> proceedSessionWrite(ses, ByteBuffer.wrap(U.IGNITE_HEADER)).get();
> ses.addMeta(MAGIC_WRITE_KEY, true);
> }
> return proceedSessionWrite(ses, msg);
> }
> {code}
> 7) Re-run the test and verify that now it pass.
> Proposed implementation plan:
> 1) Apply the fix approximately as described above, but with magic header 
> being attached to the passed buffer (not being sent as a separate message).
> 2) Review all usages of GridConnectionBytesVerifyFilter and remove manual 
> magic header send there. As I see it is only used in TcpCommunicationSpi.



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