[jira] [Assigned] (IGNITE-829) [Test] BaseH2CompareQueryTest # testCrossCache was disabled.

[Semen Boikov (JIRA)]

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

Semen Boikov reassigned IGNITE-829:
---

Assignee: Artem Shutak

Artem,

BaseH2CompareQueryTest.testCrossCache does not fail for me, please take a look. 
If it does not fail anymore please remove TODO from it, enable and unmute on TC.

Thanks


> [Test] BaseH2CompareQueryTest # testCrossCache was disabled.
> 
>
> Key: IGNITE-829
> URL: https://issues.apache.org/jira/browse/IGNITE-829
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>Assignee: Artem Shutak
>  Labels: failedtest
>
> BaseH2CompareQueryTest # testCrossCache was disabled. It has to be fixed or 
> removed.



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

[jira] [Closed] (IGNITE-580) [Test] Grid cannot stop with ongoing cache operations

[Semen Boikov (JIRA)]

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

Semen Boikov closed IGNITE-580.
---

> [Test] Grid cannot stop with ongoing cache operations
> -
>
> Key: IGNITE-580
> URL: https://issues.apache.org/jira/browse/IGNITE-580
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>  Labels: failedtest
>
> org.gridgain.grid.kernal.GridStartStopSelfTest#testStopWhileInUse
> see GG-7704



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

[jira] [Resolved] (IGNITE-580) [Test] Grid cannot stop with ongoing cache operations

[Semen Boikov (JIRA)]

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

Semen Boikov resolved IGNITE-580.
-
Resolution: Fixed

Enabled test, this functionality should work now.

> [Test] Grid cannot stop with ongoing cache operations
> -
>
> Key: IGNITE-580
> URL: https://issues.apache.org/jira/browse/IGNITE-580
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>  Labels: failedtest
>
> org.gridgain.grid.kernal.GridStartStopSelfTest#testStopWhileInUse
> see GG-7704



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

[jira] [Assigned] (IGNITE-1369) CacheClientPortableQueryExample need to update javadoc

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-1369:
---

Assignee: Denis Magda  (was: Vasilisa  Sidorova)

> CacheClientPortableQueryExample need to update javadoc
> --
>
> Key: IGNITE-1369
> URL: https://issues.apache.org/jira/browse/IGNITE-1369
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: ignite-1.4
>Reporter: Vasilisa  Sidorova
>Assignee: Denis Magda
>Priority: Minor
> Fix For: ignite-1.4
>
>
> CacheClientPortableQueryExample fails with exception:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Failed to run map 
> query remotely.
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:575)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:864)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:898)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:73)
>   at 
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.sqlQuery(CacheClientPortableQueryExample.java:196)
>   at 
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.main(CacheClientPortableQueryExample.java:107)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: javax.cache.CacheException: Failed to execute map query on the 
> node: da4ddf09-acdd-4b4b-a945-64c1a60fd8b1, class 
> org.apache.ignite.IgniteCheckedException:Failed to parse SQL query: SELECT
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._KEY __C0,
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._VAL __C1
> FROM "CacheClientPortableQueryExampleEmployees".EMPLOYEE
> WHERE ZIP = ?1
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:255)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:245)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:226)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:174)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1887)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
>   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}
> if it's running with node from command line. And 
> CacheClientPortableQueryExample is running OK with GridExampleNodeStartup. 
> So, it's need to delete text:
> {noformat}
> * Alternatively you can run {@link ExamplePortableNodeStartup} in another JVM 
> which will
>  * start node with {@code 
> examples/config/portable/example-ignite-portable.xml} configuration.
> {noformat}
> from example description



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

[jira] [Updated] (IGNITE-1374) Error org.apache.ignite.IgniteCheckedException: Failed to send response to node. Unsupported direct type during a cache iteration

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-1374:
-
Attachment: QueryResponseTest.java

> Error org.apache.ignite.IgniteCheckedException: Failed to send response to 
> node. Unsupported direct type during a cache iteration
> -
>
> Key: IGNITE-1374
> URL: https://issues.apache.org/jira/browse/IGNITE-1374
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Enrico Olivelli
>Assignee: Anton Vinogradov
>Priority: Blocker
>  Labels: user-request
> Attachments: QueryResponseTest.java
>
>
> Using ignite 1.3.0-incubating I get this error while issuing an iteration on 
> a cache
> {code}
>  Set keys = new HashSet<>();
> for (Iterator> it = cache.iterator(); 
> it.hasNext();) {
> String key = it.next().getKey();
> if (key.startsWith(prefix)) {
> keys.add(remaining);
> }
> }
> {code}
> This is the error
> {code}
> GRAVE: Failed to process message 
> [senderId=a9548f63-2ac4-4600-a593-dfcdca71aa38, messageType=class 
> o.a.i.i.processors.cache.query.GridCacheQueryResponse]
> class org.apache.ignite.IgniteCheckedException: Failed to send response to 
> node. Unsupported direct type [message=GridCacheQueryResponse 
> [finished=false, reqId=934, err=null, fields=false, metadata=null]]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:507)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:232)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:48)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1018)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2086)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:942)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:59)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:911)
>   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)
> {code}



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

[jira] [Commented] (IGNITE-1374) Error org.apache.ignite.IgniteCheckedException: Failed to send response to node. Unsupported direct type during a cache iteration

[Enrico Olivelli (JIRA)]

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

Enrico Olivelli commented on IGNITE-1374:
-

I will try to reproduce, maybe I did an error doing copy

Working code (with PeerClassLoadingEnabled=false, and the KeyPrefixPredicate 
class deployed on all the nodes):

{code}
ScanQuery scan = new ScanQuery<>(new 
KeyPrefixPredicate(prefix));
Set keys = new HashSet<>();
try (QueryCursor> cursor = 
getCache().query(scan)) {
for (Cache.Entry entry : cursor) {
String key = entry.getKey();
if (key.startsWith(prefix)) { // inutile
String remaining = key.substring(prefixlenght);
keys.add(remaining);
}
}
return keys;
}

public class KeyPrefixPredicate implements IgniteBiPredicate, 
Serializable {

private static final long serialVersionUID = 1;
private final String prefix;

public KeyPrefixPredicate(String prefix) {
this.prefix = prefix;
}

@Override
public boolean apply(String e1, Object e2) {
return e1 != null && e1.startsWith(prefix);
}

}
{code}

Code with the error (PeerClassLoadingEnabled=true, using lambda expression):
{code}


  String prefix = "myprefix...";
ScanQuery scan = new ScanQuery<>((key, value) -> {
return key.startsWith(prefix);
});
Set keys = new HashSet<>();
try (QueryCursor> cursor = 
getCache().query(scan)) {
for (Cache.Entry entry : cursor) {
String key = entry.getKey();
if (key.startsWith(prefix)) { // redundant
String remaining = key.substring(prefixlenght);
keys.add(remaining);
}
}
return keys;
}
{code}

The error is not throw on the thead which execute the example but is printed on 
on system log (maybe System.err or System.out, not in a "logger"), maybe it 
could be a system wiade UncatchedExceptionHandler

> Error org.apache.ignite.IgniteCheckedException: Failed to send response to 
> node. Unsupported direct type during a cache iteration
> -
>
> Key: IGNITE-1374
> URL: https://issues.apache.org/jira/browse/IGNITE-1374
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Enrico Olivelli
>Assignee: Anton Vinogradov
>Priority: Blocker
>  Labels: user-request
>
> Using ignite 1.3.0-incubating I get this error while issuing an iteration on 
> a cache
> {code}
>  Set keys = new HashSet<>();
> for (Iterator> it = cache.iterator(); 
> it.hasNext();) {
> String key = it.next().getKey();
> if (key.startsWith(prefix)) {
> keys.add(remaining);
> }
> }
> {code}
> This is the error
> {code}
> GRAVE: Failed to process message 
> [senderId=a9548f63-2ac4-4600-a593-dfcdca71aa38, messageType=class 
> o.a.i.i.processors.cache.query.GridCacheQueryResponse]
> class org.apache.ignite.IgniteCheckedException: Failed to send response to 
> node. Unsupported direct type [message=GridCacheQueryResponse 
> [finished=false, reqId=934, err=null, fields=false, metadata=null]]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:507)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:232)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:48)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1018)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2086)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:942)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:59)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:911)
>   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)
> {code}



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

[jira] [Updated] (IGNITE-1381) Incorrect marshalling and/or unmarshalling of unregistered types

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-1381:

Affects Version/s: (was: 1.1.4)
   ignite-1.4

> Incorrect marshalling and/or unmarshalling of unregistered types
> 
>
> Key: IGNITE-1381
> URL: https://issues.apache.org/jira/browse/IGNITE-1381
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Denis Magda
>Priority: Critical
> Fix For: ignite-1.5
>
>
> Unmarshalling logic does not correspond to marshalling in case of 
> unregistered types:
> * Write: PortableClassDescriptor.writeHeader. Header length includes the 
> length of class name string.
> * Read: PortableReaderExImpl:2161 ("rawOff += clsNameLen") implies that 
> clsNameLen is not included in header length.



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

[jira] [Updated] (IGNITE-1369) CacheClientPortableQueryExample need to update javadoc

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-1369:

Fix Version/s: ignite-1.4

> CacheClientPortableQueryExample need to update javadoc
> --
>
> Key: IGNITE-1369
> URL: https://issues.apache.org/jira/browse/IGNITE-1369
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: ignite-1.4
>Reporter: Vasilisa  Sidorova
>Assignee: Denis Magda
>Priority: Minor
> Fix For: ignite-1.4
>
>
> CacheClientPortableQueryExample fails with exception:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Failed to run map 
> query remotely.
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:575)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:864)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:898)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:73)
>   at 
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.sqlQuery(CacheClientPortableQueryExample.java:196)
>   at 
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.main(CacheClientPortableQueryExample.java:107)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: javax.cache.CacheException: Failed to execute map query on the 
> node: da4ddf09-acdd-4b4b-a945-64c1a60fd8b1, class 
> org.apache.ignite.IgniteCheckedException:Failed to parse SQL query: SELECT
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._KEY __C0,
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._VAL __C1
> FROM "CacheClientPortableQueryExampleEmployees".EMPLOYEE
> WHERE ZIP = ?1
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:255)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:245)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:226)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:174)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1887)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
>   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}
> if it's running with node from command line. And 
> CacheClientPortableQueryExample is running OK with GridExampleNodeStartup. 
> So, it's need to delete text:
> {noformat}
> * Alternatively you can run {@link ExamplePortableNodeStartup} in another JVM 
> which will
>  * start node with {@code 
> examples/config/portable/example-ignite-portable.xml} configuration.
> {noformat}
> from example description



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

[jira] [Updated] (IGNITE-1123) Instability and broken topology when multiple server and client nodes are restarted

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-1123:
-
Issue Type: Sub-task  (was: Bug)
Parent: IGNITE-1345

> Instability and broken topology when multiple server and client nodes are 
> restarted
> ---
>
> Key: IGNITE-1123
> URL: https://issues.apache.org/jira/browse/IGNITE-1123
> Project: Ignite
>  Issue Type: Sub-task
>  Components: clients, general
>Affects Versions: sprint-7
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Critical
> Fix For: ignite-1.5
>
>
> The bug is always reproduced with 
> TcpDiscoveryMultiThreadedTest.testMultiThreadedClientsServersRestart.
> The test starts multiple servers and clients and then restarts them from 
> multiple thread. At some point it will lead to one or all of the following:
> 1) Broken topology on a client side:
> {noformat}
> java.lang.AssertionError: TcpDiscoveryNodeAddFinishedMessage 
> [nodeId=70576075-b528-43f4-b490-33d079dc7007, 
> super=TcpDiscoveryAbstractMessage [sndNodeId=null, 
> id=8f7e19c8e41-10b88275-1868-4faf-9ae0-d61d627b1001, 
> verifierNodeId=10b88275-1868-4faf-9ae0-d61d627b1001, topVer=89, pendingIdx=0, 
> isClient=false]]
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl.updateTopologyHistory(ClientImpl.java:589)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl.access$2500(ClientImpl.java:48)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddFinishedMessage(ClientImpl.java:1370)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1227)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processClientReconnectMessage(ClientImpl.java:1552)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1235)
>   at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1197)
>   at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {noformat} 
> 2) Clients segmentation that is not properly processed by 
> GridCachePartionExchangeManager and that leads to the test hang:
> {noformat}
> Still waiting for initial partition map exchange 
> [fut=GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false, 
> reassign=false, discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode 
> [id=60b736c0-a2ad-4465-a3c1-7656e1fa9006, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:0], discPort=0, order=255, intOrder=0, loc=true, 
> ver=1.4.1#19700101-sha1:, isClient=true], topVer=255, 
> nodeId8=60b736c0, msg=null, type=NODE_JOINED, tstamp=1436877471568], 
> rcvdIds=GridConcurrentHashSet 
> [elements=[7098ffd9-f81b-40bf-9b9e-b0935d394007, 
> 30b30924-a9e7-45fb-9aeb-361bbb482003, 00d7e953-ce8b-45e0-a1f3-be7a6dea1000, 
> 301559de-a129-4b85-852f-f8325649f003, 7078cd7a-e6b9-4bed-b829-a2e792a0c007, 
> 20de002e-7e98-4e55-b25f-d873e25db002, 00c444ad-b221-4695-9a6d-5ea529779000, 
> 40dc3691-7b20-41d7-a436-65ad27f74004, 308f0e4a-507a-4da6-b086-bdecc08e1003, 
> 20b1d488-7aa1-41d7-ac0b-e8730002, 00da0ab2-9441-4cc2-b787-c34dcf6a2000, 
> 4096e7dd-e3fe-4704-9d11-3b267430e004, 1059ba84-4ca7-4d8f-9563-b90334d48001]], 
> rmtIds=[30b30924-a9e7-45fb-9aeb-361bbb482003, 
> 20de002e-7e98-4e55-b25f-d873e25db002, 4096e7dd-e3fe-4704-9d11-3b267430e004, 
> 00c444ad-b221-4695-9a6d-5ea529779000], exchId=GridDhtPartitionExchangeId 
> [topVer=AffinityTopologyVersion [topVer=255, minorTopVer=0], nodeId=60b736c0, 
> evt=NODE_JOINED], init=true, ready=false, replied=false, added=true, 
> initFut=GridFutureAdapter [resFlag=2, res=true, startTime=1436877471578, 
> endTime=1436877471578, ignoreInterrupts=false, lsnr=null, state=DONE], 
> topSnapshot=null, lastVer=null, partReleaseFut=null, skipPreload=true, 
> clientOnlyExchange=true, oldest=20de002e-7e98-4e55-b25f-d873e25db002, 
> oldestOrder=254, evtLatch=0, remaining=[], super=GridFutureAdapter 
> [resFlag=0, res=null, startTime=1436877471578, endTime=0, 
> ignoreInterrupts=false, lsnr=null, state=INIT]]]
> {noformat}



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

[jira] [Updated] (IGNITE-1386) IPC semaphores are not released on server endpoint abrupt stop

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-1386:

Affects Version/s: ignite-1.4

> IPC semaphores are not released on server endpoint abrupt stop
> --
>
> Key: IGNITE-1386
> URL: https://issues.apache.org/jira/browse/IGNITE-1386
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Priority: Critical
> Fix For: ignite-1.5
>
>
> {{IpcSharedMemoryCrashDetectionSelfTest.testIgfsClientServerInteractionsUponServerKilling}}
>  stops a server endpoint abruptly with 'kill' command and right after that 
> start a new endpoint. 
> The test expects that such a flow will release all previously allocated 
> memory segments and semaphores. 
> In fact, only memory segments are released while semaphores stay in the 
> system. However, the test successfully ends.
> Steps to reproduce:
> - check existing semaphores with {{ipcs -s}};
> - start the test on Linux or Mac OS;
> - call {{ipcs -s}} and you will see that semaphores hasn't been released.
> In addition, TeamCity agents fail a test suite because of this reason from 
> time to time
> {noformat}
> [16:14:03][Step 7/7] Failing build because of remaining IPC resources.
> [16:14:03][Step 7/7] Process exited with code 1
> [16:14:03][Step 7/7] Step Check IPC / Clean up (Command Line) failed
> {noformat}



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

[jira] [Commented] (IGNITE-613) [Test] IgniteCacheReplicatedQuerySelfTest # testNodeLeft fails

[Semen Boikov (JIRA)]

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

Semen Boikov commented on IGNITE-613:
-

Test was created to check that internal resources are properly cleaned in case 
of node initiated query failed. It should be rewritten since qeries 
implementation was completely changed. 

Test scenario:
- start new client node
- client node executes query which consists of several pages but gets only 
first page
- stop client node
- all resources related to client query should be cleared on server node


> [Test] IgniteCacheReplicatedQuerySelfTest # testNodeLeft fails
> --
>
> Key: IGNITE-613
> URL: https://issues.apache.org/jira/browse/IGNITE-613
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>  Labels: failedtest
>
> IgniteCacheReplicatedQuerySelfTest #testNodeLeft  test fails by unknown 
> reason (should be unmuted on TC after fix). 
> Test works long and fails after. Should be enabled after fix.



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

[jira] [Commented] (IGNITE-1387) Platform .Net: cache.Invoke does not work with portable objects without Java counterpart

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-1387:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-1387 Platform .Net: cache.Invoke does not work with portable objects 
without Java counterpart



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

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

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

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


commit 2326bb53fd62104b8816fe6da6f388963dc268cd
Author: ptupitsyn 
Date:   2015-09-08T09:29:34Z

IGNITE-1387 Platform .Net: cache.Invoke does not work with portable objects 
without Java counterpart




> Platform .Net: cache.Invoke does not work with portable objects without Java 
> counterpart
> 
>
> Key: IGNITE-1387
> URL: https://issues.apache.org/jira/browse/IGNITE-1387
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Pavel  Tupitsyn
> Fix For: ignite-1.4
>
>
> PlatformCacheEntryProcessorImpl.readResultAndUpdateEntry uses readObject 
> instead of readObjectDetached, so it tries to deserialize portable objects 
> from other platforms,



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

[jira] [Updated] (IGNITE-1272) PortableMarshaller: issues when different class loaders are used

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-1272:

Fix Version/s: ignite-1.5

> PortableMarshaller: issues when different class loaders are used
> 
>
> Key: IGNITE-1272
> URL: https://issues.apache.org/jira/browse/IGNITE-1272
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: ignite-1.5
>
>
> The reason is that a loader is not passed to required places when needed.
> Reproduced with the following tests:
> - {{IgniteCacheAbstractExecutionContextTest.testUserClassLoader()}} fails 
> with PortableMarshaller enabled.
> - {{GridDeploymentMessageCountSelfTest.testCacheValueDeploymentOnPut()}}
> Another issue is when {{PortableContext}} returns {{PortableClassDescriptor}} 
> by type id. Returned descriptor has a constructor which already has been 
> loaded with another class loader. Fix is not trivial and issue is reproduced 
> with {{GridP2PRemoteClassLoadersSelfTest}}
> Look for corresponding TODOs in the code.
> Unmute tests when fixed



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

[jira] [Updated] (IGNITE-1294) Assertion in TCP communication SPI: client already created

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-1294:

Fix Version/s: ignite-1.5

> Assertion in TCP communication SPI: client already created
> --
>
> Key: IGNITE-1294
> URL: https://issues.apache.org/jira/browse/IGNITE-1294
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Alexey Goncharuk
>Assignee: Denis Magda
> Fix For: ignite-1.5
>
> Attachments: ignite-1294.patch
>
>
> Observed this failure on TC in master branch:
> {code}
> [19:39:53]W:   [org.apache.ignite:ignite-core] 
> java.lang.AssertionError: Client already created [
>   node=TcpDiscoveryNode [id=00db22a2-37de-4d41-9a81-1b3ccb7a3000, 
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, 
> intOrder=1, lastExchangeTime=1440434393018, loc=false, 
> ver=1.4.1#19700101-sha1:, isClient=false],
>   client=GridShmemCommunicationClient 
> [shmem=IpcSharedMemoryClientEndpoint [inSpace=IpcSharedMemorySpace 
> [opSize=262144, shmemPtr=139828001624128, shmemId=815824901, semId=696811527, 
> closed=false, isReader=true, writerPid=23710, readerPid=23710, 
> tokFileName=/opt/TeamcityAgent/temp/buildTmp/ignite/work/ipc/shmem/00db22a2-37de-4d41-9a81-1b3ccb7a3000-23710/gg-shmem-space-1087-23710-262144,
>  closed=false], outSpace=IpcSharedMemorySpace [opSize=262144, 
> shmemPtr=139828001357888, shmemId=815792132, semId=696778758, closed=false, 
> isReader=false, writerPid=23710, readerPid=23710, 
> tokFileName=/opt/TeamcityAgent/temp/buildTmp/ignite/work/ipc/shmem/00db22a2-37de-4d41-9a81-1b3ccb7a3000-23710/gg-shmem-space-1086-23710-262144,
>  closed=false], checkIn=true, checkOut=true], 
> writeBuf=java.nio.HeapByteBuffer[pos=0 lim=8192 cap=8192], 
> formatter=org.apache.ignite.internal.managers.communication.GridIoManager$2@489a1849,
>  super=GridAbstractCommunicationClient [lastUsed=1440434393133, reserves=0]], 
>   oldClient=GridTcpNioCommunicationClient [ses=GridSelectorNioSessionImpl 
> [selectorIdx=0, queueSize=0, writeBuf=java.nio.DirectByteBuffer[pos=0 
> lim=32768 cap=32768], readBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 
> cap=32768], recovery=GridNioRecoveryDescriptor [acked=0, resendCnt=0, 
> rcvCnt=2, reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode 
> [id=00db22a2-37de-4d41-9a81-1b3ccb7a3000, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
> lastExchangeTime=1440434393018, loc=false, ver=1.4.1#19700101-sha1:, 
> isClient=false], connected=true, connectCnt=0, queueLimit=5120], 
> super=GridNioSessionImpl [locAddr=/127.0.0.1:45254, rmtAddr=/127.0.0.1:53055, 
> createTime=1440434393174, closeTime=0, bytesSent=26, bytesRcvd=345, 
> sndSchedTime=1440434393174, lastSndTime=1440434393174, 
> lastRcvTime=1440434393184, readsPaused=false, 
> filterChain=FilterChain[filters=[GridNioCodecFilter 
> [parser=org.apache.ignite.internal.util.nio.GridDirectParser@1cc9616c, 
> directMode=true], GridConnectionBytesVerifyFilter], accepted=true]], 
> super=GridAbstractCommunicationClient [lastUsed=1440434393174, reserves=0]]]
> [19:39:53]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:1909)
> [19:39:53]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:1840)
> [19:39:53]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:1806)
> [19:39:53]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1020)
> [19:39:53]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1168)
> [19:39:53]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:598)
> [19:39:53]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendLocalPartitions(GridDhtPartitionsExchangeFuture.java:932)
> [19:39:53]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendPartitions(GridDhtPartitionsExchangeFuture.java:973)
> [19:39:53]W:   [org.apache.ignite:ignite-core]at 
> 

[jira] [Updated] (IGNITE-1358) PortableMarshaller: 'userType' flag is not written for objects of some types

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-1358:

Affects Version/s: ignite-1.4

> PortableMarshaller: 'userType' flag is not written for objects of some types
> 
>
> Key: IGNITE-1358
> URL: https://issues.apache.org/jira/browse/IGNITE-1358
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Critical
> Fix For: ignite-1.5
>
>
> The 'userType' flag is not written when the following classes are serialized:
> - enums;
> - object and enum arrays;
> - classes.
> This leads to the situation that the predefined types map is ignored during 
> deserialization and the type is always considered as user's.
> To support this feature requires changes in the portable protocol.
> For now there is a workaround in the code. 
> Ideally, the protocol must be changes and the workaround must be removed.
>  



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

[jira] [Updated] (IGNITE-1294) Assertion in TCP communication SPI: client already created

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-1294:

Affects Version/s: (was: 1.1.4)
   ignite-1.4

> Assertion in TCP communication SPI: client already created
> --
>
> Key: IGNITE-1294
> URL: https://issues.apache.org/jira/browse/IGNITE-1294
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Alexey Goncharuk
>Assignee: Denis Magda
> Fix For: ignite-1.5
>
> Attachments: ignite-1294.patch
>
>
> Observed this failure on TC in master branch:
> {code}
> [19:39:53]W:   [org.apache.ignite:ignite-core] 
> java.lang.AssertionError: Client already created [
>   node=TcpDiscoveryNode [id=00db22a2-37de-4d41-9a81-1b3ccb7a3000, 
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, 
> intOrder=1, lastExchangeTime=1440434393018, loc=false, 
> ver=1.4.1#19700101-sha1:, isClient=false],
>   client=GridShmemCommunicationClient 
> [shmem=IpcSharedMemoryClientEndpoint [inSpace=IpcSharedMemorySpace 
> [opSize=262144, shmemPtr=139828001624128, shmemId=815824901, semId=696811527, 
> closed=false, isReader=true, writerPid=23710, readerPid=23710, 
> tokFileName=/opt/TeamcityAgent/temp/buildTmp/ignite/work/ipc/shmem/00db22a2-37de-4d41-9a81-1b3ccb7a3000-23710/gg-shmem-space-1087-23710-262144,
>  closed=false], outSpace=IpcSharedMemorySpace [opSize=262144, 
> shmemPtr=139828001357888, shmemId=815792132, semId=696778758, closed=false, 
> isReader=false, writerPid=23710, readerPid=23710, 
> tokFileName=/opt/TeamcityAgent/temp/buildTmp/ignite/work/ipc/shmem/00db22a2-37de-4d41-9a81-1b3ccb7a3000-23710/gg-shmem-space-1086-23710-262144,
>  closed=false], checkIn=true, checkOut=true], 
> writeBuf=java.nio.HeapByteBuffer[pos=0 lim=8192 cap=8192], 
> formatter=org.apache.ignite.internal.managers.communication.GridIoManager$2@489a1849,
>  super=GridAbstractCommunicationClient [lastUsed=1440434393133, reserves=0]], 
>   oldClient=GridTcpNioCommunicationClient [ses=GridSelectorNioSessionImpl 
> [selectorIdx=0, queueSize=0, writeBuf=java.nio.DirectByteBuffer[pos=0 
> lim=32768 cap=32768], readBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 
> cap=32768], recovery=GridNioRecoveryDescriptor [acked=0, resendCnt=0, 
> rcvCnt=2, reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode 
> [id=00db22a2-37de-4d41-9a81-1b3ccb7a3000, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
> lastExchangeTime=1440434393018, loc=false, ver=1.4.1#19700101-sha1:, 
> isClient=false], connected=true, connectCnt=0, queueLimit=5120], 
> super=GridNioSessionImpl [locAddr=/127.0.0.1:45254, rmtAddr=/127.0.0.1:53055, 
> createTime=1440434393174, closeTime=0, bytesSent=26, bytesRcvd=345, 
> sndSchedTime=1440434393174, lastSndTime=1440434393174, 
> lastRcvTime=1440434393184, readsPaused=false, 
> filterChain=FilterChain[filters=[GridNioCodecFilter 
> [parser=org.apache.ignite.internal.util.nio.GridDirectParser@1cc9616c, 
> directMode=true], GridConnectionBytesVerifyFilter], accepted=true]], 
> super=GridAbstractCommunicationClient [lastUsed=1440434393174, reserves=0]]]
> [19:39:53]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:1909)
> [19:39:53]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:1840)
> [19:39:53]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:1806)
> [19:39:53]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1020)
> [19:39:53]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1168)
> [19:39:53]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:598)
> [19:39:53]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendLocalPartitions(GridDhtPartitionsExchangeFuture.java:932)
> [19:39:53]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendPartitions(GridDhtPartitionsExchangeFuture.java:973)
> [19:39:53]W:   [org.apache.ignite:ignite-core]at 
> 

[jira] [Updated] (IGNITE-1369) CacheClientPortableQueryExample need to update javadoc

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-1369:

Assignee: Vasilisa  Sidorova  (was: Denis Magda)

> CacheClientPortableQueryExample need to update javadoc
> --
>
> Key: IGNITE-1369
> URL: https://issues.apache.org/jira/browse/IGNITE-1369
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: ignite-1.4
>Reporter: Vasilisa  Sidorova
>Assignee: Vasilisa  Sidorova
>Priority: Minor
> Fix For: ignite-1.4
>
>
> CacheClientPortableQueryExample fails with exception:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Failed to run map 
> query remotely.
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:575)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:864)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:898)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:73)
>   at 
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.sqlQuery(CacheClientPortableQueryExample.java:196)
>   at 
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.main(CacheClientPortableQueryExample.java:107)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: javax.cache.CacheException: Failed to execute map query on the 
> node: da4ddf09-acdd-4b4b-a945-64c1a60fd8b1, class 
> org.apache.ignite.IgniteCheckedException:Failed to parse SQL query: SELECT
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._KEY __C0,
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._VAL __C1
> FROM "CacheClientPortableQueryExampleEmployees".EMPLOYEE
> WHERE ZIP = ?1
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:255)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:245)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:226)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:174)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1887)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
>   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}
> if it's running with node from command line. And 
> CacheClientPortableQueryExample is running OK with GridExampleNodeStartup. 
> So, it's need to delete text:
> {noformat}
> * Alternatively you can run {@link ExamplePortableNodeStartup} in another JVM 
> which will
>  * start node with {@code 
> examples/config/portable/example-ignite-portable.xml} configuration.
> {noformat}
> from example description



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

[jira] [Updated] (IGNITE-1128) A single node without any load produces 200MB of garbage

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-1128:

Affects Version/s: (was: sprint-7)
   ignite-1.4

> A single node without any load produces 200MB of garbage 
> -
>
> Key: IGNITE-1128
> URL: https://issues.apache.org/jira/browse/IGNITE-1128
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Denis Magda
> Fix For: ignite-1.6
>
> Attachments: heap_profiling_one_node.png, ig-1128.png
>
>
> Just start one node with default-config.xml
> See attached screenshot from VisualVm.
> If I try to take heap dump from VisualVm it first do GC and heap dump is not 
> useful than.
> But in VisualVm memory profiler I see that some arrays of Objects constantly 
> generated.



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

[jira] [Updated] (IGNITE-1128) A single node without any load produces 200MB of garbage

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-1128:

Fix Version/s: (was: ignite-1.4)
   ignite-1.6

> A single node without any load produces 200MB of garbage 
> -
>
> Key: IGNITE-1128
> URL: https://issues.apache.org/jira/browse/IGNITE-1128
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Denis Magda
> Fix For: ignite-1.6
>
> Attachments: heap_profiling_one_node.png, ig-1128.png
>
>
> Just start one node with default-config.xml
> See attached screenshot from VisualVm.
> If I try to take heap dump from VisualVm it first do GC and heap dump is not 
> useful than.
> But in VisualVm memory profiler I see that some arrays of Objects constantly 
> generated.



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

[jira] [Resolved] (IGNITE-1275) 'Get' from marshaller cache hangs on topology change

[Semen Boikov (JIRA)]

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

Semen Boikov resolved IGNITE-1275.
--

Fixed issue with topology wait in case of response with invalidPartitions.

> 'Get' from marshaller cache hangs on topology change
> 
>
> Key: IGNITE-1275
> URL: https://issues.apache.org/jira/browse/IGNITE-1275
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: ignite-1.4
>
>
> Observed this hang on TC in test 
> IgniteCachePutRetryTransactionalSelfTest.testExplicitTransactionRetries:
> {noformat}
> [11:27:17] :   [org.apache.ignite:ignite-core] Thread 
> [name="ignite-#91721%sys-dht.IgniteCachePutRetryTransactionalSelfTest2%", 
> id=115833, state=WAITING, blockCnt=0, waitCnt=3]
> [11:27:17] :   [org.apache.ignite:ignite-core] Lock 
> [object=o.a.i.i.processors.cache.distributed.dht.GridPartitionedGetFuture@4a555b67,
>  ownerName=null, ownerId=-1]
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> sun.misc.Unsafe.park(Native Method)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4404)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1448)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> o.a.i.i.MarshallerContextImpl.className(MarshallerContextImpl.java:139)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> o.a.i.i.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:166)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> o.a.i.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(OptimizedMarshallerUtils.java:252)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> o.a.i.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:246)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> java.io.ObjectInputStream.readObject(ObjectInputStream.java:364)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> o.a.i.lang.IgniteBiTuple.readExternal(IgniteBiTuple.java:268)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> o.a.i.marshaller.optimized.OptimizedObjectInputStream.readExternalizable(OptimizedObjectInputStream.java:451)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> o.a.i.marshaller.optimized.OptimizedClassDescriptor.read(OptimizedClassDescriptor.java:746)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> o.a.i.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:252)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> java.io.ObjectInputStream.readObject(ObjectInputStream.java:364)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> o.a.i.marshaller.optimized.OptimizedObjectInputStream.readLinkedList(OptimizedObjectInputStream.java:610)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> o.a.i.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:227)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> java.io.ObjectInputStream.readObject(ObjectInputStream.java:364)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> o.a.i.marshaller.optimized.OptimizedMarshaller.unmarshal(OptimizedMarshaller.java:236)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> o.a.i.i.processors.cache.transactions.IgniteTxEntry.unmarshal(IgniteTxEntry.java:749)
> [11:27:17] :   [org.apache.ignite:ignite-core] at 
> 

[jira] [Updated] (IGNITE-1377) Portable metadata update on changing topology causes hangs in tests

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-1377:
-
Issue Type: Sub-task  (was: Bug)
Parent: IGNITE-1345

> Portable metadata update on changing topology causes hangs in tests
> ---
>
> Key: IGNITE-1377
> URL: https://issues.apache.org/jira/browse/IGNITE-1377
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Alexey Goncharuk
>
> I removed metadata update on for objects not defined in configuration (this 
> is not an introduced bug, it existed before) because it causes portable 
> failover suite to hang.
> Need to investigate further the cause of the hang and unmute 
> {{testNoConfiguration}}.



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

[jira] [Created] (IGNITE-1387) Platform .Net: cache.Invoke does not work with portable objects without Java counterpart

[Pavel Tupitsyn (JIRA)]

Pavel  Tupitsyn created IGNITE-1387:
---

 Summary: Platform .Net: cache.Invoke does not work with portable 
objects without Java counterpart
 Key: IGNITE-1387
 URL: https://issues.apache.org/jira/browse/IGNITE-1387
 Project: Ignite
  Issue Type: Bug
  Components: interop
Affects Versions: 1.1.4
Reporter: Pavel  Tupitsyn
Assignee: Pavel  Tupitsyn
 Fix For: ignite-1.4


PlatformCacheEntryProcessorImpl.readResultAndUpdateEntry uses readObject 
instead of readObjectDetached, so it tries to deserialize portable objects from 
other platforms,



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

[jira] [Commented] (IGNITE-806) [Test] GridCachePartitionedTxMultiThreadedSelfTest hangs

[Semen Boikov (JIRA)]

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

Semen Boikov commented on IGNITE-806:
-

Now only 
GridCachePartitionedTxMultiThreadedSelfTest.testOptimisticSerializableCommitMultithreaded
 fails for me, enabled others testcases.

> [Test] GridCachePartitionedTxMultiThreadedSelfTest hangs
> 
>
> Key: IGNITE-806
> URL: https://issues.apache.org/jira/browse/IGNITE-806
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>  Labels: failedtest
>
> See gg-4066.



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

[jira] [Updated] (IGNITE-584) Need to make sure that scan query returns consistent results on topology changes

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-584:

Description: 

Next test(s) should be unmuted on TC: GridCacheSetAbstractSelfTest 
testNodeJoinsAndLeaves and testNodeJoinsAndLeavesCollocated; 
Also see todos here GridCacheSetFailoverAbstractSelfTest

  was:
First, create query failover test then let's see the results.

see GG-7952

Next test(s) should be unmuted on TC: GridCacheSetAbstractSelfTest 
testNodeJoinsAndLeaves and testNodeJoinsAndLeavesCollocated; 
Also see todos here GridCacheSetFailoverAbstractSelfTest


> Need to make sure that scan query returns consistent results on topology 
> changes
> 
>
> Key: IGNITE-584
> URL: https://issues.apache.org/jira/browse/IGNITE-584
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>  Labels: failedtest
>
> Next test(s) should be unmuted on TC: GridCacheSetAbstractSelfTest 
> testNodeJoinsAndLeaves and testNodeJoinsAndLeavesCollocated; 
> Also see todos here GridCacheSetFailoverAbstractSelfTest



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

[jira] [Closed] (IGNITE-1387) Platform .Net: cache.Invoke does not work with portable objects without Java counterpart

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-1387.
---

> Platform .Net: cache.Invoke does not work with portable objects without Java 
> counterpart
> 
>
> Key: IGNITE-1387
> URL: https://issues.apache.org/jira/browse/IGNITE-1387
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel  Tupitsyn
>Assignee: Vladimir Ozerov
> Fix For: ignite-1.4
>
>
> PlatformCacheEntryProcessorImpl.readResultAndUpdateEntry uses readObject 
> instead of readObjectDetached, so it tries to deserialize portable objects 
> from other platforms,



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

[jira] [Updated] (IGNITE-618) binary release should be buildable without git, but revision should stay

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-618:

Fix Version/s: (was: ignite-1.4)
   ignite-1.5

> binary release should be buildable without git, but revision should stay
> 
>
> Key: IGNITE-618
> URL: https://issues.apache.org/jira/browse/IGNITE-618
> Project: Ignite
>  Issue Type: Task
>Reporter: Yakov Zhdanov
>Assignee: Anton Vinogradov
> Fix For: ignite-1.5
>
>
> Probably, this may help - 
> http://git-scm.com/book/it/v2/Customizing-Git-Git-Attributes#Keyword-Expansion



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

[jira] [Commented] (IGNITE-170) GridCachePartitionedAtomicSetFailoverSelfTest

[Semen Boikov (JIRA)]

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

Semen Boikov commented on IGNITE-170:
-

Test does not fail for me, unmuted it, will monitor TC.

> GridCachePartitionedAtomicSetFailoverSelfTest
> -
>
> Key: IGNITE-170
> URL: https://issues.apache.org/jira/browse/IGNITE-170
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Irina Vasilinets
>Assignee: Semen Boikov
>
> GridCachePartitionedAtomicSetFailoverSelfTest.testNodeRestart fails sometimes.



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

[jira] [Created] (IGNITE-1390) Use custom classes in failover tests instead of strings/primitives

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-1390:


 Summary: Use custom classes in failover tests instead of 
strings/primitives
 Key: IGNITE-1390
 URL: https://issues.apache.org/jira/browse/IGNITE-1390
 Project: Ignite
  Issue Type: Sub-task
  Components: cache
Reporter: Semen Boikov
 Fix For: ignite-1.5


Now most of failover tests use cache with JDK types (string, primitives), need 
to change tests to use some custom classes instead. This will help to find 
issues with marshaller cache.



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

[jira] [Updated] (IGNITE-1369) CacheClientPortableQueryExample fails when remote node is started without test objects in classpath

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-1369:

Priority: Critical  (was: Minor)

> CacheClientPortableQueryExample fails when remote node is started without 
> test objects in classpath
> ---
>
> Key: IGNITE-1369
> URL: https://issues.apache.org/jira/browse/IGNITE-1369
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: ignite-1.4
>Reporter: Vasilisa  Sidorova
>Assignee: Denis Magda
>Priority: Critical
> Fix For: ignite-1.4
>
>
> CacheClientPortableQueryExample fails with exception:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Failed to run map 
> query remotely.
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:575)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:864)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:898)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:73)
>   at 
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.sqlQuery(CacheClientPortableQueryExample.java:196)
>   at 
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.main(CacheClientPortableQueryExample.java:107)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: javax.cache.CacheException: Failed to execute map query on the 
> node: da4ddf09-acdd-4b4b-a945-64c1a60fd8b1, class 
> org.apache.ignite.IgniteCheckedException:Failed to parse SQL query: SELECT
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._KEY __C0,
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._VAL __C1
> FROM "CacheClientPortableQueryExampleEmployees".EMPLOYEE
> WHERE ZIP = ?1
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:255)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:245)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:226)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:174)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1887)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
>   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}
> if it's running with node from command line. And 
> CacheClientPortableQueryExample is running OK with GridExampleNodeStartup. 
> So, it's need to delete text:
> {noformat}
> * Alternatively you can run {@link ExamplePortableNodeStartup} in another JVM 
> which will
>  * start node with {@code 
> examples/config/portable/example-ignite-portable.xml} configuration.
> {noformat}
> from example description



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

[jira] [Updated] (IGNITE-1369) CacheClientPortableQueryExample fails when remote node is started without test objects in classpath

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-1369:

Summary: CacheClientPortableQueryExample fails when remote node is started 
without test objects in classpath  (was: CacheClientPortableQueryExample need 
to update javadoc)

> CacheClientPortableQueryExample fails when remote node is started without 
> test objects in classpath
> ---
>
> Key: IGNITE-1369
> URL: https://issues.apache.org/jira/browse/IGNITE-1369
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: ignite-1.4
>Reporter: Vasilisa  Sidorova
>Assignee: Denis Magda
>Priority: Minor
> Fix For: ignite-1.4
>
>
> CacheClientPortableQueryExample fails with exception:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Failed to run map 
> query remotely.
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:575)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:864)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:898)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:73)
>   at 
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.sqlQuery(CacheClientPortableQueryExample.java:196)
>   at 
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.main(CacheClientPortableQueryExample.java:107)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: javax.cache.CacheException: Failed to execute map query on the 
> node: da4ddf09-acdd-4b4b-a945-64c1a60fd8b1, class 
> org.apache.ignite.IgniteCheckedException:Failed to parse SQL query: SELECT
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._KEY __C0,
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._VAL __C1
> FROM "CacheClientPortableQueryExampleEmployees".EMPLOYEE
> WHERE ZIP = ?1
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:255)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:245)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:226)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:174)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1887)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
>   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}
> if it's running with node from command line. And 
> CacheClientPortableQueryExample is running OK with GridExampleNodeStartup. 
> So, it's need to delete text:
> {noformat}
> * Alternatively you can run {@link ExamplePortableNodeStartup} in another JVM 
> which will
>  * start node with {@code 
> examples/config/portable/example-ignite-portable.xml} configuration.
> {noformat}
> from example description



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

[jira] [Reopened] (IGNITE-1369) CacheClientPortableQueryExample fails when remote node is started without test objects in classpath

[Denis Magda (JIRA)]

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

Denis Magda reopened IGNITE-1369:
-

> CacheClientPortableQueryExample fails when remote node is started without 
> test objects in classpath
> ---
>
> Key: IGNITE-1369
> URL: https://issues.apache.org/jira/browse/IGNITE-1369
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: ignite-1.4
>Reporter: Vasilisa  Sidorova
>Assignee: Denis Magda
>Priority: Critical
> Fix For: ignite-1.4
>
>
> CacheClientPortableQueryExample fails with exception:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Failed to run map 
> query remotely.
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:575)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:864)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:898)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
>   at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:73)
>   at 
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.sqlQuery(CacheClientPortableQueryExample.java:196)
>   at 
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.main(CacheClientPortableQueryExample.java:107)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: javax.cache.CacheException: Failed to execute map query on the 
> node: da4ddf09-acdd-4b4b-a945-64c1a60fd8b1, class 
> org.apache.ignite.IgniteCheckedException:Failed to parse SQL query: SELECT
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._KEY __C0,
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._VAL __C1
> FROM "CacheClientPortableQueryExampleEmployees".EMPLOYEE
> WHERE ZIP = ?1
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:255)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:245)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:226)
>   at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:174)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1887)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
>   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}
> if it's running with node from command line. And 
> CacheClientPortableQueryExample is running OK with GridExampleNodeStartup. 
> So, it's need to delete text:
> {noformat}
> * Alternatively you can run {@link ExamplePortableNodeStartup} in another JVM 
> which will
>  * start node with {@code 
> examples/config/portable/example-ignite-portable.xml} configuration.
> {noformat}
> from example description



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

[jira] [Closed] (IGNITE-583) [Test] Need to create test that checks cache queue contents for consistency.

[Semen Boikov (JIRA)]

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

Semen Boikov closed IGNITE-583.
---

> [Test] Need to create test that checks cache queue contents for consistency.
> 
>
> Key: IGNITE-583
> URL: https://issues.apache.org/jira/browse/IGNITE-583
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>  Labels: failedtest
>
> See SPT-2 support ticket, we need to add test for customer scenario to make 
> sure queue contents obtained by different methods are consistent across 
> nodes. 
> Ask Alexey Zlobin for details.
> see GG-4807
> Next test(s) should be unmuted on TC: GridCacheQueueMultiNodeAbstractSelfTest 
> # testIterator



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

[jira] [Resolved] (IGNITE-583) [Test] Need to create test that checks cache queue contents for consistency.

[Semen Boikov (JIRA)]

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

Semen Boikov resolved IGNITE-583.
-
Resolution: Fixed

Fixed muted tests. Also there are already tests for queue consistency, so close 
this issue.

> [Test] Need to create test that checks cache queue contents for consistency.
> 
>
> Key: IGNITE-583
> URL: https://issues.apache.org/jira/browse/IGNITE-583
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>  Labels: failedtest
>
> See SPT-2 support ticket, we need to add test for customer scenario to make 
> sure queue contents obtained by different methods are consistent across 
> nodes. 
> Ask Alexey Zlobin for details.
> see GG-4807
> Next test(s) should be unmuted on TC: GridCacheQueueMultiNodeAbstractSelfTest 
> # testIterator



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

[jira] [Updated] (IGNITE-584) Need to make sure that scan query returns consistent results on topology changes

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-584:

Description: 
Consistent results on topology changes was implemented for sql queries, but 
looks like it still does not work for scan queries.

This affects 'cache set' tests since set uses scan query for set iteration (to 
be unmuted on TC): 
GridCacheSetAbstractSelfTest testNodeJoinsAndLeaves and 
testNodeJoinsAndLeavesCollocated; 
Also see todos here GridCacheSetFailoverAbstractSelfTest

  was:

Next test(s) should be unmuted on TC: GridCacheSetAbstractSelfTest 
testNodeJoinsAndLeaves and testNodeJoinsAndLeavesCollocated; 
Also see todos here GridCacheSetFailoverAbstractSelfTest


> Need to make sure that scan query returns consistent results on topology 
> changes
> 
>
> Key: IGNITE-584
> URL: https://issues.apache.org/jira/browse/IGNITE-584
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>  Labels: failedtest
>
> Consistent results on topology changes was implemented for sql queries, but 
> looks like it still does not work for scan queries.
> This affects 'cache set' tests since set uses scan query for set iteration 
> (to be unmuted on TC): 
> GridCacheSetAbstractSelfTest testNodeJoinsAndLeaves and 
> testNodeJoinsAndLeavesCollocated; 
> Also see todos here GridCacheSetFailoverAbstractSelfTest



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

[jira] [Updated] (IGNITE-808) [Test] GridReplicatedTxPreloadTest fails

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-808:

Fix Version/s: ignite-1.5

> [Test] GridReplicatedTxPreloadTest fails
> 
>
> Key: IGNITE-808
> URL: https://issues.apache.org/jira/browse/IGNITE-808
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>Assignee: Semen Boikov
>  Labels: failedtest
> Fix For: ignite-1.5
>
>
> GridReplicatedTxPreloadTest fails. 
> See gg-7434 already fixed, but tests fail.



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

[jira] [Assigned] (IGNITE-808) [Test] GridReplicatedTxPreloadTest fails

[Semen Boikov (JIRA)]

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

Semen Boikov reassigned IGNITE-808:
---

Assignee: Semen Boikov

> [Test] GridReplicatedTxPreloadTest fails
> 
>
> Key: IGNITE-808
> URL: https://issues.apache.org/jira/browse/IGNITE-808
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>Assignee: Semen Boikov
>  Labels: failedtest
> Fix For: ignite-1.5
>
>
> GridReplicatedTxPreloadTest fails. 
> See gg-7434 already fixed, but tests fail.



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

[jira] [Updated] (IGNITE-1230) Add a boolean flag that will indicate that rebalance in progress or not

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-1230:
-
Fix Version/s: (was: ignite-1.4)
   ignite-1.5

> Add a boolean flag that will indicate that rebalance in progress or not
> ---
>
> Key: IGNITE-1230
> URL: https://issues.apache.org/jira/browse/IGNITE-1230
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Alexey Kuznetsov
>Assignee: Anton Vinogradov
> Fix For: ignite-1.5
>
>
> It will be useful in some cases to check single boolean flag instead of 
> looping over partitions.



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

[jira] [Updated] (IGNITE-1231) Show more details in node log when rebalancing started / finished.

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-1231:
-
Fix Version/s: (was: ignite-1.4)
   ignite-1.5

> Show more details in node log when rebalancing started / finished.
> --
>
> Key: IGNITE-1231
> URL: https://issues.apache.org/jira/browse/IGNITE-1231
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Alexey Kuznetsov
>Assignee: Anton Vinogradov
> Fix For: ignite-1.5
>
>
> Current implementation just show cache name and elapsed time, but it will be 
> useful if we will print such info as:
>  how many partitions will be moved and on what node.
> You can add more info if there is something to add.



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

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

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-614:

Fix Version/s: (was: ignite-1.4)
   ignite-1.5

> 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
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: ignite-1.5
>
>
> 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] [Resolved] (IGNITE-828) [Test] GridIndexingSpiAbstractSelfTest # testResultReuse was disabled.

[Semen Boikov (JIRA)]

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

Semen Boikov resolved IGNITE-828.
-
Resolution: Won't Fix

Removed test, it is not valid anymore.

> [Test] GridIndexingSpiAbstractSelfTest # testResultReuse was disabled.
> --
>
> Key: IGNITE-828
> URL: https://issues.apache.org/jira/browse/IGNITE-828
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>  Labels: failedtest
>
> GridIndexingSpiAbstractSelfTest # testResultReuse was disabled. It has to be 
> fixed or removed.



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

[jira] [Commented] (IGNITE-264) Queue failover tests fail in transactional cache

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-264:
-

Thanks for the review, Semyon! I addressed the ticket and will re-run the TC 
and merge the ticket if all is ok:

 * Removed embedded futures for both cases.
 * Removed the method. I planned to use it in the beginning, but later I added 
a flag to the tx instance, which should be a smaller overhead.
 * This is done intentionally, in favor to fix 
https://issues.apache.org/jira/browse/IGNITE-1377 later.

> Queue failover tests fail in transactional cache
> 
>
> Key: IGNITE-264
> URL: https://issues.apache.org/jira/browse/IGNITE-264
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-1
>Reporter: Valentin Kulichenko
>Assignee: Alexey Goncharuk
> Fix For: ignite-1.4
>
>
> See {{GridCachePartitionedQueueFailoverDataConsistencySelfTest}}.



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

[jira] [Assigned] (IGNITE-1016) Add excludeNeighbors and backupFilter to FairAffinityFunction

[Andrey Gura (JIRA)]

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

Andrey Gura reassigned IGNITE-1016:
---

Assignee: Valentin Kulichenko  (was: Andrey Gura)

> Add excludeNeighbors and backupFilter to FairAffinityFunction
> -
>
> Key: IGNITE-1016
> URL: https://issues.apache.org/jira/browse/IGNITE-1016
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>  Labels: Usability
> Fix For: ignite-1.4
>
> Attachments: ignite-1016.patch, ignite-1016.patch
>
>
> These properties are currently available only for 
> {{RendezvousAffinityFunction}}.



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

[jira] [Resolved] (IGNITE-818) [Test] GridSuppressedExceptionSelfTest # testStackTrace was disabled

[Semen Boikov (JIRA)]

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

Semen Boikov resolved IGNITE-818.
-
Resolution: Fixed

Removed test (it was not a real test, just some demonstration).

> [Test] GridSuppressedExceptionSelfTest # testStackTrace was disabled
> 
>
> Key: IGNITE-818
> URL: https://issues.apache.org/jira/browse/IGNITE-818
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>  Labels: failedtest
>
> GridSuppressedExceptionSelfTest # testStackTrace was disabled. It has to be 
> fixed or deleted.



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

[jira] [Commented] (IGNITE-1389) GridCacheAbstractFullApiSelfTest.testWithSkipStore fails periodically on different configuration

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-1389:
-

The issue is really hard to reproduce locally.
There should be a race condition that causes the bug because 'skipStore' flag 
seems to be passed properly to all the places participating in requests.

However, figured out that when a cache projection with skipStore enabled 
returns a wrong value it doesn't retrieve it from a storage. Looks like a near 
cache or something else is not cleaned for such projections.

> GridCacheAbstractFullApiSelfTest.testWithSkipStore fails periodically on 
> different configuration
> 
>
> Key: IGNITE-1389
> URL: https://issues.apache.org/jira/browse/IGNITE-1389
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Denis Magda
>
> The test fails on different configurations in different places.
> As an example, this is a stack trace for 
> {{GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore}}
>  configuration
> {noformat}
> junit.framework.AssertionFailedError: expected:<-1> but was:<21>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4534)
> at sun.reflect.GeneratedMethodAccessor108.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> {noformat}



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

[jira] [Closed] (IGNITE-823) [Test] GridUnsafeMemorySelfTest # testGuardedOpsPerformance was disabled.

[Semen Boikov (JIRA)]

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

Semen Boikov closed IGNITE-823.
---

> [Test] GridUnsafeMemorySelfTest # testGuardedOpsPerformance was disabled.
> -
>
> Key: IGNITE-823
> URL: https://issues.apache.org/jira/browse/IGNITE-823
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>  Labels: failedtest
>
> GridUnsafeMemorySelfTest # testGuardedOpsPerformance was disabled. It has to 
> be fixed or removed.



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

[jira] [Resolved] (IGNITE-823) [Test] GridUnsafeMemorySelfTest # testGuardedOpsPerformance was disabled.

[Semen Boikov (JIRA)]

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

Semen Boikov resolved IGNITE-823.
-
Resolution: Fixed

This is performance test which is supposed to be run manually, moved it to 
separate class (GridUnsafeMemoryPerformanceTest).

> [Test] GridUnsafeMemorySelfTest # testGuardedOpsPerformance was disabled.
> -
>
> Key: IGNITE-823
> URL: https://issues.apache.org/jira/browse/IGNITE-823
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>  Labels: failedtest
>
> GridUnsafeMemorySelfTest # testGuardedOpsPerformance was disabled. It has to 
> be fixed or removed.



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

[jira] [Created] (IGNITE-1391) Platform .Net: Messaging.RemoteListen causes deadlock when remote node interop is initializing

[Pavel Tupitsyn (JIRA)]

Pavel  Tupitsyn created IGNITE-1391:
---

 Summary: Platform .Net: Messaging.RemoteListen causes deadlock 
when remote node interop is initializing
 Key: IGNITE-1391
 URL: https://issues.apache.org/jira/browse/IGNITE-1391
 Project: Ignite
  Issue Type: Bug
  Components: interop
Affects Versions: 1.1.4
Reporter: Pavel  Tupitsyn
Assignee: Pavel  Tupitsyn
Priority: Critical
 Fix For: ignite-1.4


* when node joins the topology, interop processor is not yet ready (Ignite 
instance is not created in .Net)
* When that node receives a remote message listener, 
UnmanagedCallbacks.MessagingFilterCreate gets called, and it blocks on 
"_initEvent.Wait()"
* This blocks whole messaging mechanism, so interop processor initialization 
can't be completed

We need to:
* Override onKernalStart in PlatformProcessorImpl and call platform.onStart 
from there
* In .Net, release _initEvent from that callback



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

[jira] [Closed] (IGNITE-805) [Test] Need to create multi-threaded tests for full API on GridCache

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov closed IGNITE-805.
---

> [Test] Need to create multi-threaded tests for full API on GridCache
> 
>
> Key: IGNITE-805
> URL: https://issues.apache.org/jira/browse/IGNITE-805
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>Assignee: Anton Vinogradov
>  Labels: failedtest
>
> See GG-708
> We have multi-node tesgts, but are there multi-threaded tests? Multi-threaded 
> tests should be for both, one node and multiple nodes.



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

[jira] [Updated] (IGNITE-1016) Add excludeNeighbors and backupFilter to FairAffinityFunction

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-1016:

Assignee: Andrey Gura  (was: Valentin Kulichenko)

> Add excludeNeighbors and backupFilter to FairAffinityFunction
> -
>
> Key: IGNITE-1016
> URL: https://issues.apache.org/jira/browse/IGNITE-1016
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: Andrey Gura
>  Labels: Usability
> Fix For: ignite-1.4
>
> Attachments: ignite-1016.patch, ignite-1016.patch
>
>
> These properties are currently available only for 
> {{RendezvousAffinityFunction}}.



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

[jira] [Commented] (IGNITE-1383) Need to have ability to use apply-pull-request.sh script for non-master branches

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-1383:


Github user asfgit closed the pull request at:

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


> Need to have ability to use apply-pull-request.sh script for non-master 
> branches
> 
>
> Key: IGNITE-1383
> URL: https://issues.apache.org/jira/browse/IGNITE-1383
> Project: Ignite
>  Issue Type: Task
>Reporter: Artem Shutak
>Assignee: Artem Shutak
>
> Sometimes it's need to apply patch to non-master branch. So, it need to have 
> ability to use apply-pull-request.sh script for non-master branches.



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

[jira] [Commented] (IGNITE-1383) Need to have ability to use apply-pull-request.sh script for non-master branches

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov commented on IGNITE-1383:
--

Reviewed. Merged.
Thank you for your contribution!

> Need to have ability to use apply-pull-request.sh script for non-master 
> branches
> 
>
> Key: IGNITE-1383
> URL: https://issues.apache.org/jira/browse/IGNITE-1383
> Project: Ignite
>  Issue Type: Task
>Reporter: Artem Shutak
>Assignee: Nikolay Tikhonov
>
> Sometimes it's need to apply patch to non-master branch. So, it need to have 
> ability to use apply-pull-request.sh script for non-master branches.



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

[jira] [Closed] (IGNITE-1383) Need to have ability to use apply-pull-request.sh script for non-master branches

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov closed IGNITE-1383.


> Need to have ability to use apply-pull-request.sh script for non-master 
> branches
> 
>
> Key: IGNITE-1383
> URL: https://issues.apache.org/jira/browse/IGNITE-1383
> Project: Ignite
>  Issue Type: Task
>Reporter: Artem Shutak
>Assignee: Nikolay Tikhonov
>
> Sometimes it's need to apply patch to non-master branch. So, it need to have 
> ability to use apply-pull-request.sh script for non-master branches.



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

[jira] [Commented] (IGNITE-1383) Need to have ability to use apply-pull-request.sh script for non-master branches

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-1383:


GitHub user ashutakGG opened a pull request:

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

IGNITE-1383 Ability to use apply-pull-request.sh script for non-master 
branches

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

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

$ git pull https://github.com/ashutakGG/incubator-ignite ignite-1383-script

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

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


commit 108dd8f9721b80a5355bd0b472037276ad7d4c5f
Author: ashutak 
Date:   2015-09-08T14:30:15Z

ignite-1383: Fixed.




> Need to have ability to use apply-pull-request.sh script for non-master 
> branches
> 
>
> Key: IGNITE-1383
> URL: https://issues.apache.org/jira/browse/IGNITE-1383
> Project: Ignite
>  Issue Type: Task
>Reporter: Artem Shutak
>Assignee: Artem Shutak
>
> Sometimes it's need to apply patch to non-master branch. So, it need to have 
> ability to use apply-pull-request.sh script for non-master branches.



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

[jira] [Commented] (IGNITE-1016) Add excludeNeighbors and backupFilter to FairAffinityFunction

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-1016:
-

Force update is needed only if {{excludeNeighbors == false}}. Otherwise we risk 
to assign partition to neighbor node during force update.

Code from {{AffinityUtils}} are moved to {{GridCacheUtils}}. PR updated.

> Add excludeNeighbors and backupFilter to FairAffinityFunction
> -
>
> Key: IGNITE-1016
> URL: https://issues.apache.org/jira/browse/IGNITE-1016
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: Andrey Gura
>  Labels: Usability
> Fix For: ignite-1.4
>
> Attachments: ignite-1016.patch, ignite-1016.patch
>
>
> These properties are currently available only for 
> {{RendezvousAffinityFunction}}.



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

[jira] [Created] (IGNITE-1392) IGFS example configuration must have IPC endpoint enabled by default.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-1392:
---

 Summary: IGFS example configuration must have IPC endpoint enabled 
by default.
 Key: IGNITE-1392
 URL: https://issues.apache.org/jira/browse/IGNITE-1392
 Project: Ignite
  Issue Type: Bug
  Components: hadoop
Affects Versions: 1.1.4
Reporter: Vladimir Ozerov
 Fix For: ignite-1.4


example-igfs.xml has IPC endpoint disabled. I do not understand why it is so. 
As a result if user is trying to use this config with Hadoop, he receives 
"Failed to communicate with IGFS." error.

It looks like we have to:
1) Enable IPC endpoint.
2) Improve error message with suggestions to the user (e.g. "did you enable IPC 
endpoint?").



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