[jira] [Updated] (IGNITE-802) [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue
[ https://issues.apache.org/jira/browse/IGNITE-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-802: --- Attachment: ignite-802.patch > [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue > --- > > Key: IGNITE-802 > URL: https://issues.apache.org/jira/browse/IGNITE-802 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Denis Magda > Labels: failedtest > Fix For: ignite-1.4 > > Attachments: ignite-802.patch > > > The test had been already fixed (see GG-5620), but it was not uncommented > after. Now it fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-613) [Test] IgniteCacheReplicatedQuerySelfTest # testNodeLeft fails
[ https://issues.apache.org/jira/browse/IGNITE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-613: -- Assignee: Denis Magda > [Test] IgniteCacheReplicatedQuerySelfTest # testNodeLeft fails > -- > > Key: IGNITE-613 > URL: https://issues.apache.org/jira/browse/IGNITE-613 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Denis Magda > 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] [Created] (IGNITE-1396) Remove platforms from public API for ignite-1.4.
Vladimir Ozerov created IGNITE-1396: --- Summary: Remove platforms from public API for ignite-1.4. Key: IGNITE-1396 URL: https://issues.apache.org/jira/browse/IGNITE-1396 Project: Ignite Issue Type: Task Components: interop Affects Versions: 1.1.4 Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Priority: Critical Fix For: ignite-1.4 It appears that adding platforms in the current release will shift release date without real necessity. Lets hide platforms API from release for now and re-add it in 1.5. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14738427#comment-14738427 ] Pavel Konstantinov edited comment on IGNITE-1177 at 9/10/15 9:02 AM: - 1)'Group indexes' has broken UI and has no code completion (ctrl+space) 2)Need to sort database types drop down list alphabetically was (Author: pkonstantinov): 1)'Group indexes' has broken UI 2)Need to sort database types drop down list alphabetically > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-802) [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue
[ https://issues.apache.org/jira/browse/IGNITE-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-802. -- > [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue > --- > > Key: IGNITE-802 > URL: https://issues.apache.org/jira/browse/IGNITE-802 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Denis Magda > Labels: failedtest > Fix For: ignite-1.4 > > Attachments: ignite-802.patch > > > The test had been already fixed (see GG-5620), but it was not uncommented > after. Now it fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1397) Load/consistency test framework
[ https://issues.apache.org/jira/browse/IGNITE-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Shutak updated IGNITE-1397: - Priority: Critical (was: Major) > Load/consistency test framework > --- > > Key: IGNITE-1397 > URL: https://issues.apache.org/jira/browse/IGNITE-1397 > Project: Ignite > Issue Type: Task >Reporter: Artem Shutak >Assignee: Artem Shutak >Priority: Critical > > Need to create "Load/consistency test framework". See: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61316109. > As POC it should be implemented test cases described on the wiki. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-802) [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue
[ https://issues.apache.org/jira/browse/IGNITE-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14738451#comment-14738451 ] tc_commenter commented on IGNITE-802: - There was triggered next test builds for last attached patch-file: 01. http://204.14.53.152/viewQueued.html?itemId=105412 - Ignite AOP 02. http://204.14.53.152/viewQueued.html?itemId=105413 - Ignite Basic 03. http://204.14.53.152/viewQueued.html?itemId=105414 - Ignite Cache 04. http://204.14.53.152/viewQueued.html?itemId=105415 - Ignite Cache 2 05. http://204.14.53.152/viewQueued.html?itemId=105416 - Ignite Cache 3 06. http://204.14.53.152/viewQueued.html?itemId=105417 - Ignite Cache 4 07. http://204.14.53.152/viewQueued.html?itemId=105418 - Ignite Cache Expiry Policy 08. http://204.14.53.152/viewQueued.html?itemId=105419 - Ignite Cache Failover 09. http://204.14.53.152/viewQueued.html?itemId=105420 - Ignite Cache Failover Multi JVM 10. http://204.14.53.152/viewQueued.html?itemId=105421 - Ignite Cache Failover2 11. http://204.14.53.152/viewQueued.html?itemId=105422 - Ignite Cache Full API 12. http://204.14.53.152/viewQueued.html?itemId=105423 - Ignite Cache Full API Multi JVM 13. http://204.14.53.152/viewQueued.html?itemId=105424 - Ignite Cache Full API Portable 14. http://204.14.53.152/viewQueued.html?itemId=105425 - Ignite Cache Portable 15. http://204.14.53.152/viewQueued.html?itemId=105426 - Ignite Cache Query Portable 16. http://204.14.53.152/viewQueued.html?itemId=105427 - Ignite Cache Restarts 17. http://204.14.53.152/viewQueued.html?itemId=105428 - Ignite Cache Tx Recovery 18. http://204.14.53.152/viewQueued.html?itemId=105429 - Ignite Cloud 19. http://204.14.53.152/viewQueued.html?itemId=105430 - Ignite Compute Grid 20. http://204.14.53.152/viewQueued.html?itemId=105431 - Ignite Data Strucutures 21. http://204.14.53.152/viewQueued.html?itemId=105432 - Ignite Examples 22. http://204.14.53.152/viewQueued.html?itemId=105433 - Ignite GCE 23. http://204.14.53.152/viewQueued.html?itemId=105434 - Ignite Geospacial Indexing 24. http://204.14.53.152/viewQueued.html?itemId=105435 - Ignite H2 Indexing 25. http://204.14.53.152/viewQueued.html?itemId=105436 - Ignite Hadoop 26. http://204.14.53.152/viewQueued.html?itemId=105437 - Ignite Hibernate 27. http://204.14.53.152/viewQueued.html?itemId=105438 - Ignite IGFS 28. http://204.14.53.152/viewQueued.html?itemId=105439 - Ignite IGFS Examples 29. http://204.14.53.152/viewQueued.html?itemId=105440 - Ignite IGFS Linux and MacOS 30. http://204.14.53.152/viewQueued.html?itemId=105441 - Ignite Java Client 31. http://204.14.53.152/viewQueued.html?itemId=105442 - Ignite JDBC Driver 32. http://204.14.53.152/viewQueued.html?itemId=105443 - Ignite JTA 33. http://204.14.53.152/viewQueued.html?itemId=105444 - Ignite Logging 34. http://204.14.53.152/viewQueued.html?itemId=105445 - Ignite Portables Basic 35. http://204.14.53.152/viewQueued.html?itemId=105446 - Ignite Queries 36. http://204.14.53.152/viewQueued.html?itemId=105447 - Ignite Scalar Examples 37. http://204.14.53.152/viewQueued.html?itemId=105448 - Ignite SPI 38. http://204.14.53.152/viewQueued.html?itemId=105449 - Ignite Spring 39. http://204.14.53.152/viewQueued.html?itemId=105450 - Ignite Start Nodes 40. http://204.14.53.152/viewQueued.html?itemId=105451 - Ignite URI Deploy SPI 41. http://204.14.53.152/viewQueued.html?itemId=105452 - Ignite Visor Console 42. http://204.14.53.152/viewQueued.html?itemId=105453 - Ignite WebSessions 43. http://204.14.53.152/viewQueued.html?itemId=105454 - JCache TCK > [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue > --- > > Key: IGNITE-802 > URL: https://issues.apache.org/jira/browse/IGNITE-802 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Denis Magda > Labels: failedtest > Fix For: ignite-1.4 > > Attachments: ignite-802.patch > > > The test had been already fixed (see GG-5620), but it was not uncommented > after. Now it fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-842) Do full run of Ignite tests under open JDK.
[ https://issues.apache.org/jira/browse/IGNITE-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Shutak updated IGNITE-842: Fix Version/s: (was: ignite-1.4) ignite-1.5 > Do full run of Ignite tests under open JDK. > --- > > Key: IGNITE-842 > URL: https://issues.apache.org/jira/browse/IGNITE-842 > Project: Ignite > Issue Type: Task >Reporter: Artem Shutak >Assignee: Artem Shutak > Fix For: ignite-1.5 > > > Do full run of Ignite tests under open JDK. Configure TC for it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-870) Need to add more information on Ignite Contribute page
[ https://issues.apache.org/jira/browse/IGNITE-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Shutak updated IGNITE-870: Fix Version/s: (was: ignite-1.4) ignite-1.5 > Need to add more information on Ignite Contribute page > --- > > Key: IGNITE-870 > URL: https://issues.apache.org/jira/browse/IGNITE-870 > Project: Ignite > Issue Type: Task >Reporter: Artem Shutak >Assignee: Artem Shutak > Fix For: ignite-1.5 > > > Add information about: > - AL2 header > - it'd be nice to have an explanation how one can contribute to > the website, documentation, etc. After all, the project doesn't consist of > code only. In fact, user facing part of it isn't the code at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1126) Make sure REST is covered with tests
[ https://issues.apache.org/jira/browse/IGNITE-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Shutak updated IGNITE-1126: - Fix Version/s: (was: ignite-1.4) ignite-1.5 > Make sure REST is covered with tests > > > Key: IGNITE-1126 > URL: https://issues.apache.org/jira/browse/IGNITE-1126 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Alexey Goncharuk >Assignee: Artem Shutak > Fix For: ignite-1.5 > > > Need to make sure all REST commands are covered with tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1397) Load/consistency test framework
Artem Shutak created IGNITE-1397: Summary: Load/consistency test framework Key: IGNITE-1397 URL: https://issues.apache.org/jira/browse/IGNITE-1397 Project: Ignite Issue Type: Task Reporter: Artem Shutak Assignee: Artem Shutak Need to create "Load/consistency test framework". See: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61316109. As POC it should be implemented test cases described on the wiki. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1374) Error org.apache.ignite.IgniteCheckedException: Failed to send response to node. Unsupported direct type during a cache iteration
[
https://issues.apache.org/jira/browse/IGNITE-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov resolved IGNITE-1374.
--
Resolution: Cannot Reproduce
> 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: 1374.patch, 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] [Comment Edited] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14738427#comment-14738427 ] Pavel Konstantinov edited comment on IGNITE-1177 at 9/10/15 10:59 AM: -- 1)'Group indexes' has broken UI and has no code completion (ctrl+space) 2)Need to sort database types drop down list alphabetically 3)I've loaded metadata from DB - single table, this metadata became the active (current) in the list, I'm did not link any caches with this metadata yet, but drop down list shows as marked caches I selected for prev metadata. was (Author: pkonstantinov): 1)'Group indexes' has broken UI and has no code completion (ctrl+space) 2)Need to sort database types drop down list alphabetically > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1372) Move C++ example to Ignite.
[ https://issues.apache.org/jira/browse/IGNITE-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-1372. - Resolution: Fixed > Move C++ example to Ignite. > --- > > Key: IGNITE-1372 > URL: https://issues.apache.org/jira/browse/IGNITE-1372 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Fix For: ignite-1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1322) Platofrms: Abstract-out interaction with portables in "PlatformTarget" classes.
[ https://issues.apache.org/jira/browse/IGNITE-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-1322. - Resolution: Won't Fix No longer relevant. > Platofrms: Abstract-out interaction with portables in "PlatformTarget" > classes. > --- > > Key: IGNITE-1322 > URL: https://issues.apache.org/jira/browse/IGNITE-1322 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: ignite-1.5 > > > As portables is implementation-dependent and may or moay not present > depending on marshaller configuration, we need to abstract out all work with > them somehow (e.g. during Java task execution initiated by native platform). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-613) [Test] IgniteCacheReplicatedQuerySelfTest # testNodeLeft fails
[
https://issues.apache.org/jira/browse/IGNITE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14738662#comment-14738662
]
Denis Magda commented on IGNITE-613:
Altered the test. The patch is attached.
However the test fails because seems that {{pageSize}} is ignored by SQL engine.
Test does the following.
At the beginning it starts 3 server nodes and 1 client node. Fills a replicated
cache with 1000 entries.
Right after that the following query is executed from the client node
{noformat}
QueryCursor> q =
cache.query(new SqlQuery(Integer.class, "_key
>= 0 order by _key").setPageSize(10));
{noformat}
Then the test gets the first key
{noformat}
q.iterator().next().getKey()
{noformat}
However, the iterator loads all 1000 entries ignoring the page size that is
equal to 10.
{GridMapQueryExecutor.qryRess}} map on servers side is empty meaning that the
whole data was transferred to the client.
Start discussion regarding the issue on the dev list.
> [Test] IgniteCacheReplicatedQuerySelfTest # testNodeLeft fails
> --
>
> Key: IGNITE-613
> URL: https://issues.apache.org/jira/browse/IGNITE-613
> Project: Ignite
> Issue Type: Bug
>Reporter: Artem Shutak
>Assignee: Denis Magda
> 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] [Closed] (IGNITE-1398) Platform .Net configuration should not be marshalled as portable type.
[ https://issues.apache.org/jira/browse/IGNITE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-1398. --- > Platform .Net configuration should not be marshalled as portable type. > --- > > Key: IGNITE-1398 > URL: https://issues.apache.org/jira/browse/IGNITE-1398 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Fix For: ignite-1.5 > > > We need to pass .Net configuration between Java and .Net platforms. However, > this only needed for inter-process interaction. This object is never passed > over a wire. > We should remove its registration from portable marshaller and pass it by > hand instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1398) Platform .Net configuration should not be marshalled as portable type.
[ https://issues.apache.org/jira/browse/IGNITE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-1398. - Resolution: Fixed > Platform .Net configuration should not be marshalled as portable type. > --- > > Key: IGNITE-1398 > URL: https://issues.apache.org/jira/browse/IGNITE-1398 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Fix For: ignite-1.5 > > > We need to pass .Net configuration between Java and .Net platforms. However, > this only needed for inter-process interaction. This object is never passed > over a wire. > We should remove its registration from portable marshaller and pass it by > hand instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-971) IgniteCacheQueryOffheapEvictsMultiThreadedSelfTest fails on TC
[
https://issues.apache.org/jira/browse/IGNITE-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14738816#comment-14738816
]
Semen Boikov commented on IGNITE-971:
-
Except issues in cache there was race in GridH2AbstractKeyValueRow.getValue: it
was possible to read from swap wrong value (fixed by Sergey Vladykin).
Attached patch with all fixes.
> IgniteCacheQueryOffheapEvictsMultiThreadedSelfTest fails on TC
> --
>
> Key: IGNITE-971
> URL: https://issues.apache.org/jira/browse/IGNITE-971
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Reporter: Semen Boikov
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: ignite-1.4
>
> Attachments: 971.patch
>
>
> IgniteCacheQueryOffheapEvictsMultiThreadedSelfTest fails on TC. Do not forget
> to uncomment test in the suite when fixed. Example of error:
> {noformat}
> [10:35:18] : [org.apache.ignite:ignite-indexing]
> [11:35:18,301][INFO ][main][root] >>> Starting test:
> testMultiThreadedSwapUnswapLongString <<<
> [10:35:24]W: [org.apache.ignite:ignite-indexing]
> [11:35:24,832][ERROR][ignite-#49878%sys-cache.IgniteCacheQueryOffheapEvictsMultiThreadedSelfTest1%][GridNearTxLocal]
> Heuristic transaction failure.
> [10:35:24]W: [org.apache.ignite:ignite-indexing] class
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
> Failed to locally write to cache (all transaction entries will be
> invalidated, however there was a window when entries for this transaction
> were visible to others): GridDhtTxLocal
> [nearNodeId=0095b759-3aa4-48bf-be10-f09ce7bfd000,
> nearFutId=0b1f33fbd41-7219c9fa-e9a6-4381-845f-2aafcc0b59bd,
> nearMiniId=3b1f33fbd41-7219c9fa-e9a6-4381-845f-2aafcc0b59bd,
> nearFinFutId=null, nearFinMiniId=null, nearXidVer=GridCacheVersion
> [topVer=44710331, nodeOrderDrId=1, globalTime=1433230524823,
> order=1433248068995], super=GridDhtTxLocalAdapter [dhtThreadId=67019,
> needsCompletedVers=true, nearNodes=[],
> dhtNodes=[20de3568-1dc7-49e0-9435-247bd63e7002], explicitLock=false,
> super=IgniteTxLocalAdapter [txMap={IgniteTxKey [key=KeyCacheObjectImpl
> [val=971, hasValBytes=true], cacheId=1]=IgniteTxEntry [key=KeyCacheObjectImpl
> [val=971, hasValBytes=true], cacheId=1, txKey=IgniteTxKey
> [key=KeyCacheObjectImpl [val=971, hasValBytes=true], cacheId=1],
> val=[op=UPDATE, val=CacheObjectImpl [val=8985, hasValBytes=true]],
> prevVal=[op=NOOP, val=null], entryProcessorsCol=null, ttl=-1,
> conflictExpireTime=-1, conflictVer=null, explicitVer=null, dhtVer=null,
> filters=[], filtersPassed=false, filtersSet=false, entry=GridDhtCacheEntry
> [rdrs=[ReaderId [nodeId=0095b759-3aa4-48bf-be10-f09ce7bfd000, msgId=10088345,
> txFut=null]], locPart=GridDhtLocalPartition [id=971, mapPubSize=1,
> rmvQueue=GridCircularBuffer [sizeMask=31, idxGen=0], state=OWNING,
> reservations=0, empty=false, createTime=06/02/2015 11:32:10, mapPubSize=1],
> super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [val=971, hasValBytes=true], val=CacheObjectImpl
> [val=6057, hasValBytes=true], startVer=1433230330069, ver=GridCacheVersion
> [topVer=44710331, nodeOrderDrId=3, globalTime=1433230524572,
> order=1433247981564], hash=1002565290,
> extras=GridCacheAttributesMvccEntryExtras [mvcc=GridCacheMvcc
> [locs=[GridCacheMvccCandidate [nodeId=1060cec4-68bb-4cd8-9cf4-400803a23001,
> ver=GridCacheVersion [topVer=44710331, nodeOrderDrId=3,
> globalTime=1433230524826, order=1433248070220], timeout=0, ts=1433230524820,
> threadId=67439, id=7990216, topVer=AffinityTopologyVersion [topVer=3,
> minorTopVer=0], reentry=null,
> otherNodeId=0095b759-3aa4-48bf-be10-f09ce7bfd000, otherVer=GridCacheVersion
> [topVer=44710331, nodeOrderDrId=1, globalTime=1433230524823,
> order=1433248068995], mappedDhtNodes=null, mappedNearNodes=null,
> ownerVer=null, key=KeyCacheObjectImpl [val=971, hasValBytes=true],
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=1|dht_local=1|near_local=0|removed=0,
> prevVer=null, nextVer=null]], rmts=null]], flags=2]]], prepared=true,
> locked=false, nodeId=null, locMapped=false, expiryPlc=null,
> transferExpiryPlc=false, flags=0, xidVer=null]}, completedBase=null,
> sndTransformedVals=false, super=IgniteTxAdapter [xidVer=GridCacheVersion
> [topVer=44710331, nodeOrderDrId=3, globalTime=1433230524826,
> order=1433248070220], writeVer=GridCacheVersion [topVer=44710331,
> nodeOrderDrId=3, globalTime=1433230524826, order=1433248070222],
> implicit=true, implicitSingle=true, loc=true, threadId=67439,
> startTime=1433230524820, nodeId=1060cec4-68bb-4cd8-9cf4-400803a23001,
> startVer=GridCacheVersion [topVer=44710331, nodeOrderDrId=3,
> globalTime=1433230524826, order=1433248070220],
[jira] [Commented] (IGNITE-1374) Error org.apache.ignite.IgniteCheckedException: Failed to send response to node. Unsupported direct type during a cache iteration
[
https://issues.apache.org/jira/browse/IGNITE-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14738835#comment-14738835
]
Enrico Olivelli commented on IGNITE-1374:
-
I'm sorry, I cannot reproduce the problem. Next week I will try to revert my
code to the original (buggy) version and deploy to the DEV environment, which
is made of many clients and 2 servers
> 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: 1374.patch, 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] [Updated] (IGNITE-1127) Query with result size more then one page doesn't increase Query executions count metric
[ https://issues.apache.org/jira/browse/IGNITE-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergi Vladykin updated IGNITE-1127: --- Fix Version/s: (was: ignite-1.4) ignite-1.5 > Query with result size more then one page doesn't increase Query executions > count metric > - > > Key: IGNITE-1127 > URL: https://issues.apache.org/jira/browse/IGNITE-1127 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: sprint-7 >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov > Fix For: ignite-1.5 > > Attachments: master_d9acbd1_ignite-1127.patch > > > Queries for partitioned caches and limited page size doesn't increase > executions count metric in case if not all records was actually fetched by > client code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1404) Any distributed cache operation should throw CacheServerNotFoundException if there are no server nodes
Valentin Kulichenko created IGNITE-1404:
---
Summary: Any distributed cache operation should throw
CacheServerNotFoundException if there are no server nodes
Key: IGNITE-1404
URL: https://issues.apache.org/jira/browse/IGNITE-1404
Project: Ignite
Issue Type: Improvement
Components: cache
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
Priority: Blocker
Fix For: ignite-1.4
Currently the behavior is inconsistent. E.g., {{remove()}} method throws an
exception, but {{clear()}} does not. Need to check all distributed operations
and make them throw the exception when appropriate.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1250) Migrate JDBC driver from Java client to Ignite node in client mode
[ https://issues.apache.org/jira/browse/IGNITE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-1250: Priority: Blocker (was: Major) > Migrate JDBC driver from Java client to Ignite node in client mode > -- > > Key: IGNITE-1250 > URL: https://issues.apache.org/jira/browse/IGNITE-1250 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Gura >Assignee: Valentin Kulichenko >Priority: Blocker > Fix For: ignite-1.4 > > > JDBC driver is still based on legacy Java client which is deprecated, not > supported and much slower than native query API. > Needs to replace thin client with an embedded client node. > See also: > http://apache-ignite-developers.2346864.n4.nabble.com/JDBC-driver-td2177.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1400) Race during concurrent node stop and cache creation
[
https://issues.apache.org/jira/browse/IGNITE-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14739990#comment-14739990
]
Alexey Goncharuk commented on IGNITE-1400:
--
Semyon, please review my changes (branch ignite-1400). I changed
{{CacheProcessor}} to call {{onKernalStop}} on exchange manager before stopping
caches so that no caches are added after we iterate over the started caches.
> Race during concurrent node stop and cache creation
> ---
>
> Key: IGNITE-1400
> URL: https://issues.apache.org/jira/browse/IGNITE-1400
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
> Fix For: ignite-1.4
>
>
> When node attempts to create a cache and is being stopped, both processes
> hang. The hang happens because gateway is blocked and cache create future is
> not cancelled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1402) Logging uses root logger in some cases
Valentin Kulichenko created IGNITE-1402:
---
Summary: Logging uses root logger in some cases
Key: IGNITE-1402
URL: https://issues.apache.org/jira/browse/IGNITE-1402
Project: Ignite
Issue Type: Bug
Components: general
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
Priority: Blocker
Fix For: ignite-1.4
{{GridKernalContext.log()}} method returns root logger which should not be used
by any of Ignite classes. This can cause the following scenario:
# User configures logger with DEBUG level as default and INFO level for
{{org.apache.ignite}} package.
# Ignite class takes logger using {{GridKernalContext.log()}} and checks if
debug is enabled. It will get true regardless of the settings for Ignite
package.
There are places in code that uses {{GridKernalContext.log()}} method
incorrectly, so it should be removed. We should always use
{{GridKernalContext.log(Class cls)}} properly specifying the category.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-970) Restore IPC shared memory TCP communication SPI
[ https://issues.apache.org/jira/browse/IGNITE-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk resolved IGNITE-970. - Resolution: Fixed > Restore IPC shared memory TCP communication SPI > --- > > Key: IGNITE-970 > URL: https://issues.apache.org/jira/browse/IGNITE-970 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk > Fix For: ignite-1.4 > > > TCP communication SPI should check for our IPC library to be available and if > available, try IPC communication for local nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-970) Restore IPC shared memory TCP communication SPI
[ https://issues.apache.org/jira/browse/IGNITE-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk closed IGNITE-970. --- > Restore IPC shared memory TCP communication SPI > --- > > Key: IGNITE-970 > URL: https://issues.apache.org/jira/browse/IGNITE-970 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk > Fix For: ignite-1.4 > > > TCP communication SPI should check for our IPC library to be available and if > available, try IPC communication for local nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-970) Restore IPC shared memory TCP communication SPI
[ https://issues.apache.org/jira/browse/IGNITE-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14739403#comment-14739403 ] Alexey Goncharuk commented on IGNITE-970: - Closing this ticket as shmem is a part of release. > Restore IPC shared memory TCP communication SPI > --- > > Key: IGNITE-970 > URL: https://issues.apache.org/jira/browse/IGNITE-970 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk > Fix For: ignite-1.4 > > > TCP communication SPI should check for our IPC library to be available and if > available, try IPC communication for local nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1112) Atomic cache #get method returns old value if near cache enabled after second putAll.
[
https://issues.apache.org/jira/browse/IGNITE-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14739434#comment-14739434
]
Andrey Gura commented on IGNITE-1112:
-
The issue is reproduced when near cache enabled and cache store with write
through configured. The first part of the problem is related with
{{TestCacheStore}} implementation that uses static {{ConcurrentMap}}. But
{{load}} method never invokes during {{testPutAllPutAll}} test execution. It is
very strange. But there is one more weird issue. Test executes successfully if
just create one more cache.
> Atomic cache #get method returns old value if near cache enabled after second
> putAll.
> -
>
> Key: IGNITE-1112
> URL: https://issues.apache.org/jira/browse/IGNITE-1112
> Project: Ignite
> Issue Type: Bug
>Reporter: Artem Shutak
>Assignee: Andrey Gura
>
> These tests failed:
> GridCacheAtomicNearEnabledMultiJvmFullApiSelfTest.testPutAllPutAll
> GridCacheAtomicNearEnabledFairAffinityMultiJvmFullApiSelfTest.testPutAllPutAll
>
> These tests work fine in one jvm, but fails in multi-JVM case.
> Looks like, second putAll does not update data at near cache and get method
> returns old value. But iteration from cache return actual data.
> See ignite-648-putAll branch with more debug information.
> Original log for
> GridCacheAtomicNearEnabledMultiJvmFullApiSelfTest.testPutAllPutAll.
> {noformat}
> junit.framework.AssertionFailedError: expected:<64> but was:<8>
> 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.distributed.near.GridCachePartitionedMultiNodeFullApiSelfTest.testPutAllPutAll(GridCachePartitionedMultiNodeFullApiSelfTest.java:126)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1618)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:70)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1561)
> --- Stdout: ---
> [17:59:33,524][INFO ][main][root] >>> Starting test: testPutAllPutAll <<<
> [17:59:33,527][INFO ][test-runner][root] > Grid0:
> 00ac324c-cfd0-4433-b00b-1048858b6000
> [17:59:33,528][INFO ][test-runner][root] > Grid1:
> 0a0c6919-127f-4d44-988d-8a236d033379
> [17:59:33,530][INFO ][test-runner][root] > Grid2:
> 17e5a787-5b00-4c68-88ea-cf0e393fefd1
> [17:59:33,531][INFO ][test-runner][root] > Grid3:
> d63de793-e754-4849-826e-2f43669385ba
> [17:59:33,544][INFO ][Thread-110][jvm-0a0c6919]
> [17:59:33,544][INFO][ignite-#12%pub-multijvm.GridCacheAtomicNearEnabledMultiJvmFullApiSelfTest1%][GridDeploymentLocalStore]
> Class locally deployed: class
> org.apache.ignite.testframework.junits.multijvm.IgniteCacheProcessProxy$10
> [17:59:33,736][INFO ][test-runner][root] >>> Before second put.
> [17:59:33,736][INFO ][test-runner][GridDeploymentLocalStore] Class locally
> deployed: class
> org.apache.ignite.testframework.junits.multijvm.IgniteCacheProcessProxy$17
> [17:59:33,741][INFO ][Thread-110][jvm-0a0c6919]
> [17:59:33,741][INFO][ignite-#16%pub-multijvm.GridCacheAtomicNearEnabledMultiJvmFullApiSelfTest1%][GridDeploymentLocalStore]
> Class locally deployed: class
> org.apache.ignite.testframework.junits.multijvm.IgniteCacheProcessProxy$17
> [17:59:33,757][INFO ][test-runner][root] >>> After second put.
> [17:59:33,766][INFO ][main][root] >>> Stopping test: testPutAllPutAll in 240
> ms <<<
> [17:59:33,766][INFO ][main][root] Checking grid: 0
> [17:59:33,787][INFO ][main][root] Size after [idx=0, size=0, keySize=0,
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries
> []]
> [17:59:33,787][INFO ][main][root] Checking grid: 1
> [17:59:33,812][INFO ][main][root] Size after [idx=1, size=0, keySize=0,
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=[]]
> [17:59:33,815][INFO ][main][root] Checking grid: 2
> [17:59:33,839][INFO ][main][root] Size after [idx=2, size=0, keySize=0,
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=[]]
> [17:59:33,842][INFO ][main][root] Checking grid: 3
>
[jira] [Commented] (IGNITE-1016) Add excludeNeighbors and backupFilter to FairAffinityFunction
[
https://issues.apache.org/jira/browse/IGNITE-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14739466#comment-14739466
]
Andrey Gura commented on IGNITE-1016:
-
# Checking of affinity function type and {{excludeNeighbors}} flag is removed.
{{FairAffinityFunction}} was modified in order to correctly work with
{{REPLICATED}} cache. Full API tests added. Waiting for TC. But already there
is failed tests in
{{CacheReplicatedRendezvousAffinityExcludeNeighborsMultiNodeFullApiSelfTest}}
class: {{testSize}}, {{testIgniteCacheIterator}}, {{testWithSkipStore}} and
{{testIterator}}.
# Warning printed only once now.
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] [Commented] (IGNITE-1016) Add excludeNeighbors and backupFilter to FairAffinityFunction
[
https://issues.apache.org/jira/browse/IGNITE-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14739385#comment-14739385
]
Alexey Goncharuk commented on IGNITE-1016:
--
- I think we should remove the check forbidding usage of FairAffinityFunction
and RendezvousAffinityFunction with excludeNeighbors=true for REPLICATED cache.
I do not see any reason why it cannot be used with REPLICATED cache given that
affinity function works properly.
- The warning about the flag being ignored should be printed only once when
such a situation is detected.
> 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: Alexey Goncharuk
> 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] [Updated] (IGNITE-1016) Add excludeNeighbors and backupFilter to FairAffinityFunction
[
https://issues.apache.org/jira/browse/IGNITE-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-1016:
-
Assignee: Andrey Gura (was: Alexey Goncharuk)
> 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-1381) Incorrect marshalling and/or unmarshalling of unregistered types
[
https://issues.apache.org/jira/browse/IGNITE-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14738229#comment-14738229
]
Denis Magda commented on IGNITE-1381:
-
TC looks good. Please review.
> 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
>
> Attachments: patch.diff
>
>
> 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)
