[jira] [Created] (IGNITE-2134) .Net: Query configuration via attributes

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-2134:
--

 Summary: .Net: Query configuration via attributes
 Key: IGNITE-2134
 URL: https://issues.apache.org/jira/browse/IGNITE-2134
 Project: Ignite
  Issue Type: Sub-task
  Components: interop
Affects Versions: 1.1.4
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.6


See QuerySqlField and related annotations in Java.
Need a similar mechanism in .NET



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

[jira] [Closed] (IGNITE-773) [Backport] thread pool management - allow to configure system utility cache size

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-773.


> [Backport] thread pool management - allow to configure system utility cache 
> size
> 
>
> Key: IGNITE-773
> URL: https://issues.apache.org/jira/browse/IGNITE-773
> Project: Ignite
>  Issue Type: Task
>Affects Versions: sprint-4
>Reporter: Artem Shutak
>Assignee: Dmitriy Setrakyan
> Fix For: 1.5
>
> Attachments: ignite-sprint-4_ignite-773.patch, 
> ignite-sprint-4_ignite-773.patch
>
>




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

[jira] [Created] (IGNITE-2136) Issue with tx entry lock assignment when near cache is used

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-2136:


 Summary: Issue with tx entry lock assignment when near cache is 
used
 Key: IGNITE-2136
 URL: https://issues.apache.org/jira/browse/IGNITE-2136
 Project: Ignite
  Issue Type: Sub-task
  Components: cache
Reporter: Semen Boikov
Assignee: Semen Boikov
Priority: Critical
 Fix For: 1.6


Adde test reproducing hang on tx putAll when near cache is used: 
NearCachePutAllMultinodeTest.

Root cause for this issue is that remote mvcc candidates are marked as owners 
during tx finish step. To fix it we can try to move logic from 'tx.doneRemote' 
to prepare step.



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

[jira] [Commented] (IGNITE-2131) NPE in GridJobProcessor (non-reproducible, sibling bytes are null)

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov commented on IGNITE-2131:
---

This cannot be reproduced. Most probably, sibling byte in request were null and 
disabled assertions provoked NPE.

> NPE in GridJobProcessor (non-reproducible, sibling bytes are null)
> --
>
> Key: IGNITE-2131
> URL: https://issues.apache.org/jira/browse/IGNITE-2131
> Project: Ignite
>  Issue Type: Bug
>  Components: compute
>Affects Versions: 1.5
>Reporter: Alexey Kuznetsov
> Fix For: 1.5
>
>
> I got this NPE.
> Looking into GridJobProcessor.java:1024 code, I see that NPE could happen if 
> marshaler return null.
> Maybe we could throw exception with appropriate message?
> {code}
> Exception in thread "pub-#7%null%" Exception in thread "pub-#8%null%" 
> java.lang.NullPointerException
>  at java.util.ArrayList.(ArrayList.java:164)
>  at 
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1024)
>  at 
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1770)
>  at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
> {code}



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

[jira] [Assigned] (IGNITE-2082) Documentationd for C++/.Net missed in fabric binary package

[Igor Sapego (JIRA)]

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

Igor Sapego reassigned IGNITE-2082:
---

Assignee: Igor Sapego  (was: Sergey Kozlov)

> Documentationd for C++/.Net missed in fabric binary package
> ---
>
> Key: IGNITE-2082
> URL: https://issues.apache.org/jira/browse/IGNITE-2082
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Reporter: Sergey Kozlov
>Assignee: Igor Sapego
>Priority: Critical
> Fix For: 1.5
>
>
> There's no documentation generated by Doxygen for /platforms/cpp and 
> platforms/dotnet in Apache Ignite fabric binary package



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

[jira] [Updated] (IGNITE-2131) NPE in GridJobProcessor (non-reproducible, sibling bytes are null)

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-2131:
--
Fix Version/s: (was: 1.5)

> NPE in GridJobProcessor (non-reproducible, sibling bytes are null)
> --
>
> Key: IGNITE-2131
> URL: https://issues.apache.org/jira/browse/IGNITE-2131
> Project: Ignite
>  Issue Type: Bug
>  Components: compute
>Affects Versions: 1.5
>Reporter: Alexey Kuznetsov
>
> I got this NPE.
> Looking into GridJobProcessor.java:1024 code, I see that NPE could happen if 
> marshaler return null.
> Maybe we could throw exception with appropriate message?
> {code}
> Exception in thread "pub-#7%null%" Exception in thread "pub-#8%null%" 
> java.lang.NullPointerException
>  at java.util.ArrayList.(ArrayList.java:164)
>  at 
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1024)
>  at 
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1770)
>  at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
> {code}



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

[jira] [Resolved] (IGNITE-1932) Wrong value of BusyTimePercentage metric after ignite.cluster().resetMetrics()

[Alexey Kuznetsov (JIRA)]

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

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

Fixed in ignite-1.5. Please test.

> Wrong value of BusyTimePercentage metric after ignite.cluster().resetMetrics()
> --
>
> Key: IGNITE-1932
> URL: https://issues.apache.org/jira/browse/IGNITE-1932
> Project: Ignite
>  Issue Type: Bug
>  Components: compute
>Affects Versions: ignite-1.4
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 1.5
>
>
> I found that after call of
>   ignite.cluster().resetMetrics()
> BusyTimePercentage became 100% 
> After some debug I found that BusyTimePercentage - calculated as:
> 1 - IdleTimePercentage 
> and IdleTimePercentage  calculated as  IdleTime / UpTime
> and on reset we set IdleTime to 0.
> So the possible fix is to preserve IdleTime on reset.



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

[jira] [Closed] (IGNITE-393) We need to add benchmarks pages to Ignite web site

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-393.


> We need to add benchmarks pages to Ignite web site
> --
>
> Key: IGNITE-393
> URL: https://issues.apache.org/jira/browse/IGNITE-393
> Project: Ignite
>  Issue Type: Task
>Affects Versions: sprint-2
>Reporter: Alexey Kuznetsov
>Assignee: Dmitriy Setrakyan
> Fix For: 1.5
>
> Attachments: ignite benchmarks.zip
>
>
> Create pages for Ignite web site: 
> http://ignite.incubator.apache.org/index.html
> # yardstick
> # ignite vs hz
> # ignite vs. infinispan
> HTML code could be taken from 
> http://www.gridgain.com/developer-central/benchmarks/



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

[jira] [Closed] (IGNITE-1554) igniterouter scripts are not working

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-1554.
-
Assignee: Sergey Kozlov  (was: Raúl Kripalani)

> igniterouter scripts are not working
> 
>
> Key: IGNITE-1554
> URL: https://issues.apache.org/jira/browse/IGNITE-1554
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Raúl Kripalani
>Assignee: Sergey Kozlov
> Fix For: 1.5
>
>
> Executing the {{igniterouter}} script fails with:
> {code}
> Error: Could not find or load main class 
> org.apache.ignite.client.router.impl.GridRouterCommandLineStartup
> {code}
> Since a refactoring in commit b88a1012e9031b760193179463ce852032c2e334.



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

[jira] [Closed] (IGNITE-2128) Incorrect output in CacheClientBinaryQueryExample

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov closed IGNITE-2128.


Fix confirmed

> Incorrect output in CacheClientBinaryQueryExample
> -
>
> Key: IGNITE-2128
> URL: https://issues.apache.org/jira/browse/IGNITE-2128
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5
> Environment: OS X 10.10.2
> jdk 1.7
>Reporter: Ilya Suntsov
>Assignee: Ilya Suntsov
>Priority: Critical
> Fix For: 1.5
>
>
> Steps to reproduce:
> 1. Start 1 node in IDEA
> 2. Start 
> org/apache/ignite/examples/binary/datagrid/CacheClientBinaryQueryExample.java
> Result:
> {noformat}
> [17:41:30]__   
> [17:41:30]   /  _/ ___/ |/ /  _/_  __/ __/ 
> [17:41:30]  _/ // (7 7// /  / / / _/   
> [17:41:30] /___/\___/_/|_/___/ /_/ /___/  
> [17:41:30] 
> [17:41:30] ver. 1.5.0-b2#20151210-sha1:d2008c53
> [17:41:30] 2015 Copyright(C) Apache Software Foundation
> [17:41:30] 
> [17:41:30] Ignite documentation: http://ignite.apache.org
> [17:41:30] 
> [17:41:30] Quiet mode.
> [17:41:30]   ^-- Logging to file 
> '/Users/gridgain/Downloads/apache-ignite-fabric-1.5-2.0-b2-bin/work/log/ignite-c96bd940.log'
> [17:41:30]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
> "-v" to ignite.{sh|bat}
> [17:41:30] 
> [17:41:30] OS: Mac OS X 10.10.3 x86_64
> [17:41:30] VM information: Java(TM) SE Runtime Environment 1.7.0_79-b15 
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 24.79-b02
> [17:41:30] Initial heap size is 192MB (should be no less than 512MB, use 
> -Xms512m -Xmx512m).
> [17:41:30] Configured plugins:
> [17:41:30]   ^-- None
> [17:41:30] 
> [17:41:30] Security status [authentication=off, tls/ssl=off]
> [17:41:32] Attempting to start more nodes than physical RAM available on 
> current host (this can cause significant slowdown)
> [17:41:33] Performance suggestions for grid  (fix if possible)
> [17:41:33] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [17:41:33]   ^-- Disable peer class loading (set 'peerClassLoadingEnabled' to 
> false)
> [17:41:33]   ^-- Disable grid events (remove 'includeEventTypes' from 
> configuration)
> [17:41:33] 
> [17:41:33] To start Console Management & Monitoring run 
> ignitevisorcmd.{sh|bat}
> [17:41:33] 
> [17:41:33] Ignite node started OK (id=c96bd940)
> [17:41:33] Topology snapshot [ver=7, servers=5, clients=0, CPUs=8, 
> heap=13.0GB]
> >>> Binary objects cache query example started.
> >>> Employees with zip 94109:
> >>> Employees working for GridGain:
> >>> Employee [idHash=1570448684, hash=1704762760, 
> >>> departments=BinaryObject [idHash=1957010358, hash=-1143237694, 
> >>> typeId=179563853], addr=Address [idHash=613549454, hash=220889046, 
> >>> street=1096 Eddy Street, San Francisco, CA, zip=94109], name=James 
> >>> Wilson, salary=12500]
> >>> Employee [idHash=1856684131, hash=1443330375, 
> >>> departments=BinaryObject [idHash=205315160, hash=1785031702, 
> >>> typeId=179563853], addr=Address [idHash=1873157038, hash=78336113, 
> >>> street=184 Fidler Drive, San Antonio, TX, zip=78130], name=Daniel Adams, 
> >>> salary=11000]
> >>> Employee [idHash=40072646, hash=1100837732, departments=BinaryObject 
> >>> [idHash=1338579811, hash=290257426, typeId=179563853], addr=Address 
> >>> [idHash=472197505, hash=1208142819, street=667 Jerry Dove Drive, 
> >>> Florence, SC, zip=29501], name=Cristian Moss, salary=12500]
> >>> Employee names and their salaries:
> >>> [Name=James Wilson, salary=12500]
> >>> [Name=Daniel Adams, salary=11000]
> >>> [Name=Cristian Moss, salary=12500]
> >>> [Name=Allison Mathis, salary=25300]
> >>> [Name=Breana Robbin, salary=6500]
> >>> [Name=Philip Horsley, salary=19800]
> >>> [Name=Brian Peters, salary=10600]
> >>> Employees living in Texas:
> {noformat}
> as you can see in output no employees with zip code "94109" and no employees 
> from Texas but in code were created 2 employees with zip  "94109":
> {noformat}
>  employeeCache.put(new EmployeeKey(1, 1), new Employee(
> "James Wilson",
> 12500,
> new Address("1096 Eddy Street, San Francisco, CA", 94109),
> Arrays.asList("Human Resources", "Customer Service")
> ));
> employeeCache.put(new EmployeeKey(4, 2), new Employee(
> "Allison Mathis",
> 25300,
> new Address("2702 Freedom Lane, San Francisco, CA", 94109),
> Arrays.asList("Development")
> ));
> {noformat}
>  and two employees from TX:
> {noformat}
>  employeeCache.put(new EmployeeKey(2, 1), new Employee(
> "Daniel Adams",
> 11000,
> new Address("184 Fidler Drive, San Antonio, TX", 78130),
> 

[jira] [Closed] (IGNITE-808) invokeAll fails with ClassCastException on unstable topology

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-808.


> invokeAll fails with ClassCastException on unstable topology
> 
>
> Key: IGNITE-808
> URL: https://issues.apache.org/jira/browse/IGNITE-808
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Artem Shutak
>Assignee: Semen Boikov
>  Labels: Muted_test
> Fix For: 1.5
>
>
> GridReplicatedTxPreloadTest fails. 
> See gg-7434 already fixed, but tests fail.



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

[jira] [Closed] (IGNITE-636) Artifact deployment needs to fixed

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-636.


> Artifact deployment needs to fixed
> --
>
> Key: IGNITE-636
> URL: https://issues.apache.org/jira/browse/IGNITE-636
> Project: Ignite
>  Issue Type: Bug
> Environment: Apache CI
>Reporter: Konstantin Boudnik
>Assignee: Konstantin Boudnik
> Fix For: 1.5
>
>
> The maven build has a number of warnings that need to be fixed.
> Also, something weird seems to be happening around the versions of the 
> artifacts as it expects to resolve version 1.0 that yet to be released.
>   https://builds.apache.org/view/All/job/Ignite-artifacts/409/console



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

[jira] [Closed] (IGNITE-431) Need to document CacheJdbcPojoStore

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-431.


> Need to document CacheJdbcPojoStore
> ---
>
> Key: IGNITE-431
> URL: https://issues.apache.org/jira/browse/IGNITE-431
> Project: Ignite
>  Issue Type: Improvement
>  Components: documentation
>Reporter: Dmitriy Setrakyan
>Assignee: Dmitriy Setrakyan
> Fix For: 1.5
>
>
> http://apacheignite.readme.io/v1.0/docs/automatic-persistence



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

[jira] [Created] (IGNITE-2135) ClassNotFoundException for CacheContinuousQueryExample

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-2135:
-

 Summary: ClassNotFoundException for CacheContinuousQueryExample
 Key: IGNITE-2135
 URL: https://issues.apache.org/jira/browse/IGNITE-2135
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.5
Reporter: Sergey Kozlov
Priority: Critical
 Fix For: 1.5


1. Start 3 nodes with examples/config/example-ignite.xml
2. Run CacheContinuousQueryExample in IDEA
3. The example fails:
{noformat}
>>> Cache continuous query example started.
[14:15:07] Ignite node stopped OK [uptime=00:00:00:898]
Exception in thread "main" javax.cache.CacheException: class 
org.apache.ignite.IgniteCheckedException: Query execution failed: 
GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN, clsName=null, 
clause=null, 
filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
 part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
prj=null, keepPortable=false, subjId=2908e088-371e-4528-9141-52efb5ef42d6, 
taskHash=0], rdc=null, trans=null]
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1634)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:181)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy$5.onHasNext(IgniteCacheProxy.java:528)
at 
org.apache.ignite.internal.util.GridCloseableIteratorAdapter.hasNextX(GridCloseableIteratorAdapter.java:53)
at 
org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
at 
org.apache.ignite.examples.datagrid.CacheContinuousQueryExample.main(CacheContinuousQueryExample.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
Caused by: class org.apache.ignite.IgniteCheckedException: Query execution 
failed: GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN, clsName=null, 
clause=null, 
filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
 part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
prj=null, keepPortable=false, subjId=2908e088-371e-4528-9141-52efb5ef42d6, 
taskHash=0], rdc=null, trans=null]
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.checkError(GridCacheQueryFutureAdapter.java:267)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.internalIterator(GridCacheQueryFutureAdapter.java:325)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:171)
... 9 more
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute 
query on node [query=GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN, 
clsName=null, clause=null, 
filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
 part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
prj=null, keepPortable=false, subjId=2908e088-371e-4528-9141-52efb5ef42d6, 
taskHash=0], rdc=null, trans=null], nodeId=a17e9748-7771-441c-a594-122c598b7b8e]
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.onPage(GridCacheQueryFutureAdapter.java:390)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.processQueryResponse(GridCacheDistributedQueryManager.java:395)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.access$000(GridCacheDistributedQueryManager.java:60)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$1.apply(GridCacheDistributedQueryManager.java:90)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$1.apply(GridCacheDistributedQueryManager.java:88)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:582)
at 

[jira] [Commented] (IGNITE-1993) JDBC discovery uses non-standard SQL when creating table (not compatible with Oracle)

[Nigel Westbury (JIRA)]

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

Nigel Westbury commented on IGNITE-1993:


Hi Nikolav,

Thanks for testing it.  I was wondering if you were testing with the attached 
patch or were testing the code in the pull 
request.  Unfortunately the patch did create an error introduced when i did 
some last minute code clean-up while 
submitting the patch.  Sorry about that.  That patch was superceded by the 
pull-request as Denis said not to submit as 
a patch.  Table names passed to the metadata tables request in upper case.  
Using lower case does not work with 
Oracle even if the table was created with lower case characters.

If you are testing the pull-request then I am surprised as it works with Oracle 
here.

I don't think Ignite should allow user configuration of SQL unless really 
necessary.  In any case the query of the 
metadata is not done using SQL, it is JDBC API, so allowing user configurable 
SQL would not help here.  Though I 
have not tested with various different databases, in my experience the JDBC 
metadata API is consistently implemented 
by the various drivers I have used from time to time.


> JDBC discovery uses non-standard SQL when creating table (not compatible with 
> Oracle)
> -
>
> Key: IGNITE-1993
> URL: https://issues.apache.org/jira/browse/IGNITE-1993
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: ignite-1.4
> Environment: Oracle database
>Reporter: Nigel Westbury
>  Labels: easyfix, patch
> Fix For: 1.4
>
> Attachments: IGNITE1993.patch
>
>
> The SQL used by TcpDiscoveryJdbcIpFinder to create the table (defined by 
> CREATE_ADDRS_TABLE_QRY) uses 'if not exists' clause.  However this clause is 
> not supported by Oracle and causes SQLSyntaxErrorException: "ORA-00922: 
> missing or invalid option" to be thrown.  This prevents JDBC discovery from 
> being used with an Oracle database.



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

[jira] [Commented] (IGNITE-2082) Documentationd for C++/.Net missed in fabric binary package

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov commented on IGNITE-2082:
---

There's still no cpp doc

> Documentationd for C++/.Net missed in fabric binary package
> ---
>
> Key: IGNITE-2082
> URL: https://issues.apache.org/jira/browse/IGNITE-2082
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Critical
> Fix For: 1.5
>
>
> There's no documentation generated by Doxygen for /platforms/cpp and 
> platforms/dotnet in Apache Ignite fabric binary package



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

[jira] [Updated] (IGNITE-2131) NPE in GridJobProcessor (non-reproducible, sibling bytes are null)

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-2131:
--
Summary: NPE in GridJobProcessor (non-reproducible, sibling bytes are null) 
 (was: NPE in GridJobProcessor)

> NPE in GridJobProcessor (non-reproducible, sibling bytes are null)
> --
>
> Key: IGNITE-2131
> URL: https://issues.apache.org/jira/browse/IGNITE-2131
> Project: Ignite
>  Issue Type: Bug
>  Components: compute
>Affects Versions: 1.5
>Reporter: Alexey Kuznetsov
> Fix For: 1.5
>
>
> I got this NPE.
> Looking into GridJobProcessor.java:1024 code, I see that NPE could happen if 
> marshaler return null.
> Maybe we could throw exception with appropriate message?
> {code}
> Exception in thread "pub-#7%null%" Exception in thread "pub-#8%null%" 
> java.lang.NullPointerException
>  at java.util.ArrayList.(ArrayList.java:164)
>  at 
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1024)
>  at 
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1770)
>  at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
> {code}



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

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

[Artem Shutak (JIRA)]

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

Artem Shutak commented on IGNITE-2065:
--

"portable" packages renamed to "binary".

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



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

[jira] [Closed] (IGNITE-2035) Misprint in javadoc

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov closed IGNITE-2035.


Fix confirmed

> Misprint in javadoc
> ---
>
> Key: IGNITE-2035
> URL: https://issues.apache.org/jira/browse/IGNITE-2035
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Affects Versions: 1.5
> Environment: OS X 10.10.2
> jdk 1.8.45
>Reporter: Ilya Suntsov
>Assignee: Ilya Suntsov
>Priority: Minor
> Fix For: 1.5
>
>
> ComputeClientBinaryTaskExecutionExample:
> {noformat}
> * 
>  * Remote nodes should always be started with special configuration file which
>  * enables the binary marshaller: {@code 'ignite.{sh|bat} 
> examples/config/binary/example-ignite-binary.xml'}.
>  * 
> {noformat}
> There isn't examples/config/binary/example-ignite-binary.xml in build



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

[jira] [Closed] (IGNITE-1885) Ignite ZooKeeper: Upgrade Curator to 2.9.1

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-1885.
-
Assignee: Sergey Kozlov  (was: Raúl Kripalani)

> Ignite ZooKeeper: Upgrade Curator to 2.9.1
> --
>
> Key: IGNITE-1885
> URL: https://issues.apache.org/jira/browse/IGNITE-1885
> Project: Ignite
>  Issue Type: Improvement
>  Components: ignite-zookeeper
>Affects Versions: ignite-1.4
>Reporter: Raúl Kripalani
>Assignee: Sergey Kozlov
> Fix For: 1.5
>
>
> Upgrade the Apache Curator dependencies to 2.9.1.



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

[jira] [Closed] (IGNITE-2028) Missing package descriptors

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-2028.
-

> Missing package descriptors
> ---
>
> Key: IGNITE-2028
> URL: https://issues.apache.org/jira/browse/IGNITE-2028
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Dmitriy Setrakyan
>Assignee: Sergey Kozlov
>Priority: Blocker
> Fix For: 1.5
>
>
> {code}
> org.apache.ignite.stream.camel
> org.apache.ignite.stream.flume
> org.apache.ignite.stream.jms11
> org.apache.ignite.stream.kafka
> org.apache.ignite.stream.mqtt
> org.apache.ignite.stream.twitter
> …
> org.apache.ignite.yarn.utils
> {code}



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

[jira] [Resolved] (IGNITE-2028) Missing package descriptors

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov resolved IGNITE-2028.
---
Resolution: Fixed

> Missing package descriptors
> ---
>
> Key: IGNITE-2028
> URL: https://issues.apache.org/jira/browse/IGNITE-2028
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Dmitriy Setrakyan
>Assignee: Sergey Kozlov
>Priority: Blocker
> Fix For: 1.5
>
>
> {code}
> org.apache.ignite.stream.camel
> org.apache.ignite.stream.flume
> org.apache.ignite.stream.jms11
> org.apache.ignite.stream.kafka
> org.apache.ignite.stream.mqtt
> org.apache.ignite.stream.twitter
> …
> org.apache.ignite.yarn.utils
> {code}



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

[jira] [Created] (IGNITE-2133) Schema Import Utility should print warning about wrong IGNITE_HOME

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-2133:


 Summary: Schema Import Utility should print warning about wrong 
IGNITE_HOME
 Key: IGNITE-2133
 URL: https://issues.apache.org/jira/browse/IGNITE-2133
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: ignite-1.4
Reporter: Alexey Kuznetsov
 Fix For: 1.5






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

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

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-2074.
-

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



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

[jira] [Closed] (IGNITE-620) Add CI tooling code for patch validation

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-620.

Assignee: Sergey Kozlov  (was: Konstantin Boudnik)

> Add CI tooling code for patch validation
> 
>
> Key: IGNITE-620
> URL: https://issues.apache.org/jira/browse/IGNITE-620
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Affects Versions: sprint-1
>Reporter: Konstantin Boudnik
>Assignee: Sergey Kozlov
> Fix For: 1.5
>
>
> The code for automatic patch validation in public TC is pretty much ready. It 
> needs to be added to the Ignite source code repo to facilitate the completion 
> of the project.
> Without adding the code in we'll have to resort to manage a separate repo for 
> projects like that and deal with multiple repo builds, which might be messy 
> at times.



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

[jira] [Closed] (IGNITE-2030) ignite.bat file does not work when JAVA_HOME contains parethensis

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-2030.
-
Assignee: Sergey Kozlov  (was: Vladimir Ershov)

> ignite.bat file does not work when JAVA_HOME contains parethensis
> -
>
> Key: IGNITE-2030
> URL: https://issues.apache.org/jira/browse/IGNITE-2030
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Sergey Kozlov
> Fix For: 1.5
>
> Attachments: IGNITE-2030_fix_error_on_startup_.patch, bad_start.txt, 
> good_start.txt
>
>
> When starting ignite.bat with a folder which contains parenthesis, the 
> launcher will fail:
> For example, JAVA_HOME=C:\Program Files (x86)\jdk1.7.0_76\
> Program Files (x86)
> Error (happens @ parseargs.bat script): 
> \Java\jre1.8.0_25\bin\java.exe" -cp 
> C:\ignite\gridgain-enterprise-fabric-7.5.0\g
> ridgain-enterprise-fabric-7.5.0\libs\*;C:\ignite\gridgain-enterprise-fabric-7.5.
> 0\gridgain-enterprise-fabric-7.5.0\libs\ignite-indexing\*;C:\ignite\gridgain-ent
> erprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\ignite-spring\*;C:\ig
> nite\gridgain-enterprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\lice
> nses\* org.apache.ignite.startup.cmdline.CommandLineTransformer "`) was 
> unexpect
> ed at this time.



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

[jira] [Closed] (IGNITE-535) Implement IgniteMqttStreamer to stream data from MQTT

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-535.

Assignee: Sergey Kozlov  (was: Raúl Kripalani)

> Implement IgniteMqttStreamer to stream data from MQTT
> -
>
> Key: IGNITE-535
> URL: https://issues.apache.org/jira/browse/IGNITE-535
> Project: Ignite
>  Issue Type: Sub-task
>  Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Sergey Kozlov
> Fix For: 1.5
>
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under 
> high load. It was previously named {{IgniteDataLoader}}, see ticket 
> IGNITE-394.
> See [MQTT|http://mqtt.org/] site for more info.
> We should create {{IgniteMqttStreamer}} which will consume messages from 
> Twitter and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert MQTT messages to Ignite data using an optional pluggable converter. 
> If not provided, we should have some default mechanism.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.



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

[jira] [Commented] (IGNITE-2125) Refactoring popup more-info on configuration pages

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2125:


GitHub user Dmitriyff opened a pull request:

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

IGNITE-2125 added common directive to show dialog message, apllied on pages



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

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

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

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


commit 50225fe77ca199c9030274a1736b2068226ada40
Author: Dmitriyff 
Date:   2015-12-10T09:17:53Z

IGNITE-2125 develop common directive to show dialog with info

commit b0fbb55992bcfbb90fbb6ac8ddf207749e84bb6d
Author: Dmitriyff 
Date:   2015-12-11T10:28:26Z

IGNITE-2125 added common dialog to show message, applied on pages

commit 3bf8cafa5a8e802ee19716a4d8188e77d599
Author: Dmitriyff 
Date:   2015-12-11T10:44:05Z

Merge branch 'ignite-843-rc2' of https://github.com/apache/ignite into 
ignite-2125




> Refactoring popup more-info on configuration pages
> --
>
> Key: IGNITE-2125
> URL: https://issues.apache.org/jira/browse/IGNITE-2125
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Dmitriyff
>Assignee: Dmitriyff
> Fix For: 1.6
>
>




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

[jira] [Updated] (IGNITE-2124) Deserialization of a BinaryObject key on a remote node

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk updated IGNITE-2124:
-
Assignee: Denis Magda  (was: Alexey Goncharuk)

> Deserialization of a BinaryObject key on a remote node
> --
>
> Key: IGNITE-2124
> URL: https://issues.apache.org/jira/browse/IGNITE-2124
> Project: Ignite
>  Issue Type: Bug
>  Components: general, interop
>Affects Versions: 1.5
> Environment: Windows 7
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Blocker
> Fix For: 1.5
>
>
> BinaryObject key gets deserialized on a remote node. In my understanding this 
> mustn't happen when {{BinaryMarshaller}} is enabled.
> Steps to reproduce:
> - start a remote node using ignite.bat/sh;
> - launch {{CacheClientBinaryQueryExample}};
> The example will fail with the following stack trace:
> {noformat}
> Exception in thread "main" 
> org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys 
> (retry update if possible).: [EmployeeKey [id=4, organizationId=2]]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1620)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1078)
>   at 
> org.apache.ignite.examples.binary.datagrid.CacheClientBinaryQueryExample.populateCache(CacheClientBinaryQueryExample.java:301)
>   at 
> org.apache.ignite.examples.binary.datagrid.CacheClientBinaryQueryExample.main(CacheClientBinaryQueryExample.java:98)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: class 
> org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
>  Failed to update keys (retry update if possible).: [EmployeeKey [id=4, 
> organizationId=2]]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.addFailedKeys(GridNearAtomicUpdateFuture.java:1189)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.onResult(GridNearAtomicUpdateFuture.java:658)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.onResult(GridNearAtomicUpdateFuture.java:352)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateResponse(GridDhtAtomicCache.java:2617)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$700(GridDhtAtomicCache.java:127)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:262)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:260)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:579)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:277)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:201)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:80)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:163)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
>   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)
>   Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to 
> update keys on primary node.
>   at 
> 

[jira] [Resolved] (IGNITE-2124) Deserialization of a BinaryObject key on a remote node

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk resolved IGNITE-2124.
--
Resolution: Fixed

> Deserialization of a BinaryObject key on a remote node
> --
>
> Key: IGNITE-2124
> URL: https://issues.apache.org/jira/browse/IGNITE-2124
> Project: Ignite
>  Issue Type: Bug
>  Components: general, interop
>Affects Versions: 1.5
> Environment: Windows 7
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 1.5
>
>
> BinaryObject key gets deserialized on a remote node. In my understanding this 
> mustn't happen when {{BinaryMarshaller}} is enabled.
> Steps to reproduce:
> - start a remote node using ignite.bat/sh;
> - launch {{CacheClientBinaryQueryExample}};
> The example will fail with the following stack trace:
> {noformat}
> Exception in thread "main" 
> org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys 
> (retry update if possible).: [EmployeeKey [id=4, organizationId=2]]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1620)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1078)
>   at 
> org.apache.ignite.examples.binary.datagrid.CacheClientBinaryQueryExample.populateCache(CacheClientBinaryQueryExample.java:301)
>   at 
> org.apache.ignite.examples.binary.datagrid.CacheClientBinaryQueryExample.main(CacheClientBinaryQueryExample.java:98)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: class 
> org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
>  Failed to update keys (retry update if possible).: [EmployeeKey [id=4, 
> organizationId=2]]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.addFailedKeys(GridNearAtomicUpdateFuture.java:1189)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.onResult(GridNearAtomicUpdateFuture.java:658)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.onResult(GridNearAtomicUpdateFuture.java:352)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateResponse(GridDhtAtomicCache.java:2617)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$700(GridDhtAtomicCache.java:127)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:262)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:260)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:579)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:277)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:201)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:80)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:163)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
>   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)
>   Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to 
> update keys on primary node.
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKeys(GridNearAtomicUpdateResponse.java:368)
>

[jira] [Updated] (IGNITE-751) Implement MBean for H2 indexing

[Vladimir Ershov (JIRA)]

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

Vladimir Ershov updated IGNITE-751:
---
Description: 
See TODO @ 
org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java:1171
Andsome other TODO in IgniteH2Indexing

  was:See TODO @ 
org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java:1171


> Implement MBean for H2 indexing
> ---
>
> Key: IGNITE-751
> URL: https://issues.apache.org/jira/browse/IGNITE-751
> Project: Ignite
>  Issue Type: Task
>  Components: SQL
>Reporter: Yakov Zhdanov
>Assignee: Anton Vinogradov
> Fix For: sprint-5
>
>
> See TODO @ 
> org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java:1171
> Andsome other TODO in IgniteH2Indexing



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

[jira] [Commented] (IGNITE-1993) JDBC discovery uses non-standard SQL when creating table (not compatible with Oracle)

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov commented on IGNITE-1993:
--

I've tested your pull request on Oracle 12C. When table exists in database your 
changes are working well, but if table doesn't exist then 
TcpDiscoveryJdbcIpFinder tries to execute query ("create table if not 
exists...") and fails with the same error (SQLSyntaxErrorException: "ORA-00922: 
missing or invalid option"). Did you test this scenario? You can change jdbc 
driver for TcpDiscoveryJdbcIpFinderSelfTest and check the ip finder with Oracle.

I think that checking the metadata it's good idea, but it will not work without 
changes init query (CREATE_ADDRS_TABLE_QRY). I propose to implement both of 
these ideas.

Thoughts?

> JDBC discovery uses non-standard SQL when creating table (not compatible with 
> Oracle)
> -
>
> Key: IGNITE-1993
> URL: https://issues.apache.org/jira/browse/IGNITE-1993
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: ignite-1.4
> Environment: Oracle database
>Reporter: Nigel Westbury
>  Labels: easyfix, patch
> Fix For: 1.4
>
> Attachments: IGNITE1993.patch
>
>
> The SQL used by TcpDiscoveryJdbcIpFinder to create the table (defined by 
> CREATE_ADDRS_TABLE_QRY) uses 'if not exists' clause.  However this clause is 
> not supported by Oracle and causes SQLSyntaxErrorException: "ORA-00922: 
> missing or invalid option" to be thrown.  This prevents JDBC discovery from 
> being used with an Oracle database.



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

[jira] [Commented] (IGNITE-2124) Deserialization of a BinaryObject key on a remote node

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-2124:
--

Denis,

I have fixed this in ignite-1.5, can you confirm the fix works?

> Deserialization of a BinaryObject key on a remote node
> --
>
> Key: IGNITE-2124
> URL: https://issues.apache.org/jira/browse/IGNITE-2124
> Project: Ignite
>  Issue Type: Bug
>  Components: general, interop
>Affects Versions: 1.5
> Environment: Windows 7
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 1.5
>
>
> BinaryObject key gets deserialized on a remote node. In my understanding this 
> mustn't happen when {{BinaryMarshaller}} is enabled.
> Steps to reproduce:
> - start a remote node using ignite.bat/sh;
> - launch {{CacheClientBinaryQueryExample}};
> The example will fail with the following stack trace:
> {noformat}
> Exception in thread "main" 
> org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys 
> (retry update if possible).: [EmployeeKey [id=4, organizationId=2]]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1620)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1078)
>   at 
> org.apache.ignite.examples.binary.datagrid.CacheClientBinaryQueryExample.populateCache(CacheClientBinaryQueryExample.java:301)
>   at 
> org.apache.ignite.examples.binary.datagrid.CacheClientBinaryQueryExample.main(CacheClientBinaryQueryExample.java:98)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: class 
> org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
>  Failed to update keys (retry update if possible).: [EmployeeKey [id=4, 
> organizationId=2]]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.addFailedKeys(GridNearAtomicUpdateFuture.java:1189)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.onResult(GridNearAtomicUpdateFuture.java:658)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.onResult(GridNearAtomicUpdateFuture.java:352)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateResponse(GridDhtAtomicCache.java:2617)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$700(GridDhtAtomicCache.java:127)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:262)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:260)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:579)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:277)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:201)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:80)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:163)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
>   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)
>   Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to 
> update keys on primary node.
>   at 
> 

[jira] [Updated] (IGNITE-2139) Expose indexing metrics using MBean

[Vladimir Ershov (JIRA)]

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

Vladimir Ershov updated IGNITE-2139:

Description: See TODO @ 
org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java

> Expose indexing metrics using MBean
> ---
>
> Key: IGNITE-2139
> URL: https://issues.apache.org/jira/browse/IGNITE-2139
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Vladimir Ershov
>Assignee: Vladimir Ershov
>
> See TODO @ 
> org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java



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

[jira] [Created] (IGNITE-2139) Expose indexing metrics using MBean

[Vladimir Ershov (JIRA)]

Vladimir Ershov created IGNITE-2139:
---

 Summary: Expose indexing metrics using MBean
 Key: IGNITE-2139
 URL: https://issues.apache.org/jira/browse/IGNITE-2139
 Project: Ignite
  Issue Type: Task
  Components: cache
Reporter: Vladimir Ershov
Assignee: Vladimir Ershov






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

[jira] [Updated] (IGNITE-996) IgniteMessagingWithClientTest hangs on TC

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh updated IGNITE-996:

Attachment: ignite-996_thread_dump.log

I managed to reproduce this problem only once after 500+ attempts, so the 
probability is <1%. Attached log with thread dump.

> IgniteMessagingWithClientTest hangs on TC
> -
>
> Key: IGNITE-996
> URL: https://issues.apache.org/jira/browse/IGNITE-996
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Semen Boikov
>Assignee: Ilya Lantukh
>  Labels: Muted_test
> Attachments: ignite-996_thread_dump.log
>
>
> Test IgniteMessagingWithClientTest sometimes hangs on TC.



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

[jira] [Assigned] (IGNITE-2138) Add toBuilder() method on BinaryObject interface

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk reassigned IGNITE-2138:


Assignee: Alexey Goncharuk

> Add toBuilder() method on BinaryObject interface
> 
>
> Key: IGNITE-2138
> URL: https://issues.apache.org/jira/browse/IGNITE-2138
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 1.5
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
> Fix For: 1.5
>
>
> Creating this ticket as per this devlist thread:
> http://apache-ignite-developers.2346864.n4.nabble.com/BinaryObjectBuilder-in-EntryProcessor-td5743.html



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

[jira] [Created] (IGNITE-2137) CacheAutoStoreExample fails with ClassNotFoundException

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-2137:
-

 Summary: CacheAutoStoreExample fails with ClassNotFoundException
 Key: IGNITE-2137
 URL: https://issues.apache.org/jira/browse/IGNITE-2137
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.5
Reporter: Sergey Kozlov
 Fix For: 1.5


1. Start DbH2ServerStartup in Idea
2. Start 1 node by bin/ignite.sh  examples/config/example-ignite.xml
3. Start CacheAutoStoreExample.
4. Examples hangs up and node got following exception:
{noformat}
[16:30:51,501][SEVERE][tcp-disco-msg-worker-#2%null%][TcpDiscoverySpi] Failed 
to unmarshal discovery custom message.
class org.apache.ignite.IgniteCheckedException: Failed to find class with given 
class loader for unmarshalling (make sur
e same versions of all classes are available on all nodes or enable 
peer-class-loading): sun.misc.Launcher$AppClassLoade
r@1a752144
at 
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:108)
at 
org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMarshaller.java:78)
at 
org.apache.ignite.spi.discovery.tcp.messages.TcpDiscoveryCustomEventMessage.message(TcpDiscoveryCustomEventMe
ssage.java:78)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.notifyDiscoveryListener(ServerImpl.java:4731
)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processCustomMessage(ServerImpl.java:4592)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2276)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5784)
at 
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2161)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
Caused by: java.lang.ClassNotFoundException: 
org.apache.ignite.examples.datagrid.store.auto.CacheAutoStoreExample$CacheJ
dbcPojoStoreExampleFactory
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:278)
at 
org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
at 
org.apache.ignite.marshaller.jdk.JdkMarshallerObjectInputStream.resolveClass(JdkMarshallerObjectInputStream.j
ava:54)
at 
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1612)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517)
at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
at 
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1990)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1915)
at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1798)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
at 
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1990)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1915)
at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1798)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at java.util.ArrayList.readObject(ArrayList.java:771)
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 
java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1017)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1893)
at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1798)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
at 
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1990)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1915)
at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1798)
at 

[jira] [Updated] (IGNITE-900) GridContinuousProcessor: routine with autoUnsubscribe=false does not register on new nodes

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-900:
-
 Assignee: Semen Boikov  (was: Sergey Evdokimov)
Fix Version/s: (was: 1.5)
   1.6

> GridContinuousProcessor: routine with autoUnsubscribe=false does not register 
> on new nodes
> --
>
> Key: IGNITE-900
> URL: https://issues.apache.org/jira/browse/IGNITE-900
> Project: Ignite
>  Issue Type: Bug
>Reporter: Sergey Evdokimov
>Assignee: Semen Boikov
>Priority: Minor
> Fix For: 1.6
>
>
> Consider the case:
> 1.) Node A created a routine with autoUnsubscribe=false
> 2.) Node A leave the topology
> 3.) Node B join to topology
> Expected: node B has registered routine although node A left.
> Actual: node B has no routine



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

[jira] [Resolved] (IGNITE-1991) CacheClientBinaryPutGetExample fails with remote node, started from command line

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk resolved IGNITE-1991.
--
Resolution: Fixed

This should be fixed in ignite-1.5 now (as a part of IGNITE-2124)

> CacheClientBinaryPutGetExample fails with remote node, started from command 
> line
> 
>
> Key: IGNITE-1991
> URL: https://issues.apache.org/jira/browse/IGNITE-1991
> Project: Ignite
>  Issue Type: Bug
>  Components: general, interop
>Affects Versions: 1.5
> Environment: Win7/Ubuntu14.04, Apache Ignite 1.5.0 build #82
>Reporter: Vasilisa  Sidorova
> Fix For: 1.5
>
>
> -
> DESCRIPTION
> -
> CacheClientBinaryPutGetExample is good running with ExampleBinaryNodeStartup 
> started from IDE but fails if remote node is started from command line
> -
> STEPS FOR REPRODUCE
> -
> # Build example project in IDE (Idea)
> # Run remote node from IGNITE_HOME by the command
> {noformat}
> ./bin/ignite.sh ./examples/config/binary/example-ignite-binary.xml
> {noformat}
> # Run CacheClientBinaryPutGetExample
> -
> ACTUAL RESULT
> -
> Examples fails with exception:
> {noformat}
> Exception in thread "main" 
> org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys 
> (retry update if possible).: [1]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1620)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1758)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1032)
>   at 
> org.apache.ignite.examples.binary.datagrid.CacheClientBinaryPutGetExample.putGet(CacheClientBinaryPutGetExample.java:110)
>   at 
> org.apache.ignite.examples.binary.datagrid.CacheClientBinaryPutGetExample.main(CacheClientBinaryPutGetExample.java:82)
>   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: class 
> org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
>  Failed to update keys (retry update if possible).: [1]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.addFailedKeys(GridNearAtomicUpdateFuture.java:1188)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.onResult(GridNearAtomicUpdateFuture.java:657)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.onResult(GridNearAtomicUpdateFuture.java:351)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateResponse(GridDhtAtomicCache.java:2587)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$700(GridDhtAtomicCache.java:127)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:263)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:261)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:576)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:275)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:199)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:78)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:161)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:823)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:105)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:786)
>   at 
> 

[jira] [Updated] (IGNITE-1098) IgniteCache.invoke() throws synchronous exception in async mode.

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-1098:
--
 Assignee: Semen Boikov  (was: Sergey Evdokimov)
Fix Version/s: (was: 1.5)
   1.6

> IgniteCache.invoke() throws synchronous exception in async mode.
> 
>
> Key: IGNITE-1098
> URL: https://issues.apache.org/jira/browse/IGNITE-1098
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: 1.6
>
>
> Steps to reproduce:
> 1) Open class GridCacheAbstractFullApiSelfTest.
> 2) Add the following field:
> {code}
> public static final CacheEntryProcessor 
> ERR_PROCESSOR =
> new CacheEntryProcessor() {
> @Override public String process(MutableEntry e, 
> Object... args) {
> throw new RuntimeException("Failed!");
> }
> };
> {code}
> 3) Add the following test:
> {code}
> public void testTransformException() throws Exception {
> IgniteCache cache = jcache().withAsync();
> cache.invoke("key2", ERR_PROCESSOR);
> }
> {code}
> 4) Run this test from GridCacheAtomicMultiNodeFullApiSelfTest - it finishes 
> normally.
> 5) Run the same test from GridCacheAtomicFullApiSelfTest - it fails with 
> exception as if it was a synchronous call.



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

[jira] [Assigned] (IGNITE-1991) CacheClientBinaryPutGetExample fails with remote node, started from command line

[Vasilisa Sidorova (JIRA)]

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

Vasilisa  Sidorova reassigned IGNITE-1991:
--

Assignee: Vasilisa  Sidorova

> CacheClientBinaryPutGetExample fails with remote node, started from command 
> line
> 
>
> Key: IGNITE-1991
> URL: https://issues.apache.org/jira/browse/IGNITE-1991
> Project: Ignite
>  Issue Type: Bug
>  Components: general, interop
>Affects Versions: 1.5
> Environment: Win7/Ubuntu14.04, Apache Ignite 1.5.0 build #82
>Reporter: Vasilisa  Sidorova
>Assignee: Vasilisa  Sidorova
> Fix For: 1.5
>
>
> -
> DESCRIPTION
> -
> CacheClientBinaryPutGetExample is good running with ExampleBinaryNodeStartup 
> started from IDE but fails if remote node is started from command line
> -
> STEPS FOR REPRODUCE
> -
> # Build example project in IDE (Idea)
> # Run remote node from IGNITE_HOME by the command
> {noformat}
> ./bin/ignite.sh ./examples/config/binary/example-ignite-binary.xml
> {noformat}
> # Run CacheClientBinaryPutGetExample
> -
> ACTUAL RESULT
> -
> Examples fails with exception:
> {noformat}
> Exception in thread "main" 
> org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys 
> (retry update if possible).: [1]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1620)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1758)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1032)
>   at 
> org.apache.ignite.examples.binary.datagrid.CacheClientBinaryPutGetExample.putGet(CacheClientBinaryPutGetExample.java:110)
>   at 
> org.apache.ignite.examples.binary.datagrid.CacheClientBinaryPutGetExample.main(CacheClientBinaryPutGetExample.java:82)
>   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: class 
> org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
>  Failed to update keys (retry update if possible).: [1]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.addFailedKeys(GridNearAtomicUpdateFuture.java:1188)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.onResult(GridNearAtomicUpdateFuture.java:657)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.onResult(GridNearAtomicUpdateFuture.java:351)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateResponse(GridDhtAtomicCache.java:2587)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$700(GridDhtAtomicCache.java:127)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:263)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:261)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:576)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:275)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:199)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:78)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:161)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:823)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:105)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:786)
>   at 
> 

[jira] [Updated] (IGNITE-751) Implement MBean for H2 indexing

[Vladimir Ershov (JIRA)]

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

Vladimir Ershov updated IGNITE-751:
---
Description: 
See TODO @ 
org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java:1171
And some other TODO in IgniteH2Indexing

  was:
See TODO @ 
org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java:1171
Andsome other TODO in IgniteH2Indexing


> Implement MBean for H2 indexing
> ---
>
> Key: IGNITE-751
> URL: https://issues.apache.org/jira/browse/IGNITE-751
> Project: Ignite
>  Issue Type: Task
>  Components: SQL
>Reporter: Yakov Zhdanov
>Assignee: Anton Vinogradov
> Fix For: sprint-5
>
>
> See TODO @ 
> org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java:1171
> And some other TODO in IgniteH2Indexing



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

[jira] [Created] (IGNITE-2138) Add toBuilder() method on BinaryObject interface

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-2138:


 Summary: Add toBuilder() method on BinaryObject interface
 Key: IGNITE-2138
 URL: https://issues.apache.org/jira/browse/IGNITE-2138
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 1.5
Reporter: Alexey Goncharuk
 Fix For: 1.5


Creating this ticket as per this devlist thread:
http://apache-ignite-developers.2346864.n4.nabble.com/BinaryObjectBuilder-in-EntryProcessor-td5743.html



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

[jira] [Assigned] (IGNITE-1905) High contention for CacheLockImpl causes AssertionErrors

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov reassigned IGNITE-1905:
-

Assignee: Semen Boikov

Sam, can you please take a look or move it to 1.6

> High contention for CacheLockImpl causes AssertionErrors
> 
>
> Key: IGNITE-1905
> URL: https://issues.apache.org/jira/browse/IGNITE-1905
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
> Environment: Windows 7
>Reporter: Denis Magda
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: 1.5
>
> Attachments: ClientTest.java, ServerTest.java
>
>
> When multiple threads, running on the same client node, compete for 
> CacheLockImpl this leads to AssertionErrors.
> Pseudo-code snippet, that is called from multiple threads and causes the 
> assertions, looks like this:
> {noformat}
> boolean locked = lock.tryLock(100, TimeUnit.MILLISECONDS);
> if (locked)
> lock.unlock();
> {noformat}
> Initially the issue was detected on ignite-1.4.
> In server's node logs the following assertion appears
> {noformat}
> java.lang.AssertionError
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.addOwned(GridDhtLockFuture.java:958)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.map(GridDhtLockFuture.java:918)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.onOwnerChanged(GridDhtLockFuture.java:663)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$2.onOwnerChanged(GridCacheMvccManager.java:155)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedCacheEntry.checkOwnerChanged(GridDistributedCacheEntry.java:810)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedCacheEntry.readyLock(GridDistributedCacheEntry.java:516)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.readyLocks(GridDhtLockFuture.java:576)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.map(GridDhtLockFuture.java:764)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.lockAllAsync(GridDhtTransactionalCacheAdapter.java:973)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processNearLockRequest(GridDhtTransactionalCacheAdapter.java:557)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$000(GridDhtTransactionalCacheAdapter.java:88)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$2.apply(GridDhtTransactionalCacheAdapter.java:132)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$2.apply(GridDhtTransactionalCacheAdapter.java:130)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:580)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:280)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:198)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:77)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:160)
>   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}
>   
> In addition from time to time a client node also outputs a different kind of 
> assertion:
> {noformat}
> Exception in thread "ignite-#4%sys-null%" java.lang.AssertionError
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheExplicitLockSpan.markOwned(GridCacheExplicitLockSpan.java:196)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager.markExplicitOwner(GridCacheMvccManager.java:862)
>   at 
> 

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

[Artem Shutak (JIRA)]

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

Artem Shutak commented on IGNITE-2065:
--

Renamed Portable classes to Binary. Updated TC accordingly.

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



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

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

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-614:
-
Fix Version/s: (was: 1.5)
   1.6

> 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
>  Labels: Muted_test
> Fix For: 1.6
>
>
> 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] [Updated] (IGNITE-1040) NPE if indexing fails with exception

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-1040:
--
Fix Version/s: (was: 1.5)
   1.6

> NPE if indexing fails with exception
> 
>
> Key: IGNITE-1040
> URL: https://issues.apache.org/jira/browse/IGNITE-1040
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.6
>
>
> If cache start process fails with exception during indexing, it doesn't 
> actually stop and fails with NPE because some other components were not 
> started.
> {code}
> Jun 19, 2015 11:44:26 AM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Failed to reinitialize local partitions (preloading will be stopped): 
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=1, 
> minorTopVer=1], nodeId=8aec2f87, evt=DISCOVERY_CUSTOM_EVT]
> class org.apache.ignite.IgniteCheckedException: Property with name 'id' 
> already exists.
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$TypeDescriptor.addProperty(GridQueryProcessor.java:1736)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.processAnnotationsInClass(GridQueryProcessor.java:978)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.processAnnotation(GridQueryProcessor.java:1017)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.processAnnotationsInClass(GridQueryProcessor.java:976)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.processKeyAndValueClasses(GridQueryProcessor.java:210)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:163)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:242)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:867)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1450)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCachesStart(GridCacheProcessor.java:1372)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.startCaches(GridDhtPartitionsExchangeFuture.java:735)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:458)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:997)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
>   at java.lang.Thread.run(Thread.java:744)
> Jun 19, 2015 11:44:26 AM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Runtime error caught during grid runnable execution: GridWorker 
> [name=partition-exchanger, gridName=null, finished=false, isCancelled=false, 
> hashCode=1158985979, interrupted=false, runner=exchange-worker-#49%null%]
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onExchangeDone(GridCacheProcessor.java:1519)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:851)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:52)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:313)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:632)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:997)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
>   at java.lang.Thread.run(Thread.java:744)
> {code}



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

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-618:
-
Fix Version/s: (was: 1.5)
   1.6

> 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: 1.6
>
>
> 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] [Updated] (IGNITE-324) Partition exchange: node should be assigned as primary only after preloading is finished

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-324:
-
Fix Version/s: (was: 1.5)
   1.6

> Partition exchange: node should be assigned as primary only after preloading 
> is finished
> 
>
> Key: IGNITE-324
> URL: https://issues.apache.org/jira/browse/IGNITE-324
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Affects Versions: sprint-2
>Reporter: Alexey Goncharuk
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.6
>
>
> After node joins topology, affinity assignment should not be changed 
> immediately. New node is assigned as a backup node even for those partitions 
> that are supposed to be primary. Node becomes primary only when all 
> partitions are loaded.



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

[jira] [Updated] (IGNITE-1021) There isn't $IGNITE_HOME/docs/javadoc/resources directory

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-1021:
--
Fix Version/s: (was: 1.5)
   1.6

> There isn't  $IGNITE_HOME/docs/javadoc/resources directory
> --
>
> Key: IGNITE-1021
> URL: https://issues.apache.org/jira/browse/IGNITE-1021
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Affects Versions: sprint-6
> Environment: jdk1.7.0_71
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Anton Vinogradov
>Priority: Minor
> Fix For: 1.6
>
> Attachments: LinkCheckerResults.html
>
>
> Steps for reproduce:
> 1. Build ignite from sources: 
> {noformat} mvn clean package -DskipTests -Prelease,lgpl -Dscala-2.10
> {noformat}
> 2. Check links in 
> {noformat}$IGNITE_HOME/docs/javadoc{noformat}
>  (result file in attachment). 
> LinkChecker doesn't find
>  {noformat}$IGNITE_HOME/docs/javadoc/resources directory{noformat}



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

[jira] [Updated] (IGNITE-424) Update success flag is not checked in atomic cache

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-424:
-
Fix Version/s: (was: 1.5)
   1.6

> Update success flag is not checked in atomic cache
> --
>
> Key: IGNITE-424
> URL: https://issues.apache.org/jira/browse/IGNITE-424
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-2
>Reporter: Valentin Kulichenko
>Assignee: Anton Vinogradov
> Fix For: 1.6
>
>
> It looks suspicious {{GridDhtAtomicCache.updatePartialBatch}} calls 
> interceptor even if update was not successful.
> This code needs to be reviewed, tested and fixed appropriately if needed.



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

[jira] [Updated] (IGNITE-2003) Some optional modules don't have Apache licenses file and README.txt

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-2003:
--
Assignee: Vasilisa  Sidorova  (was: Anton Vinogradov)

> Some optional modules don't have Apache licenses file and README.txt
> 
>
> Key: IGNITE-2003
> URL: https://issues.apache.org/jira/browse/IGNITE-2003
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
> Environment: Apache Ignite 1.5.0 build #84
>Reporter: Vasilisa  Sidorova
>Assignee: Vasilisa  Sidorova
>Priority: Critical
> Fix For: 1.5
>
>
> README.txt is absent for:
> ignite-jms11
> ignite-kafka
> ignite-mqtt
> ignite-zookeeper
> apache-2.0.txt is absent for:
> ignite-jms11
> ignite-mqtt
> ignite-zookeeper
> Please, add it



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

[jira] [Comment Edited] (IGNITE-996) IgniteMessagingWithClientTest hangs on TC

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh edited comment on IGNITE-996 at 12/11/15 3:32 PM:
---

I managed to reproduce this problem only once after 500+ attempts and only in 
local environment, so the probability is <1%. Attached log with thread dump.


was (Author: ilantukh):
I managed to reproduce this problem only once after 500+ attempts, so the 
probability is <1%. Attached log with thread dump.

> IgniteMessagingWithClientTest hangs on TC
> -
>
> Key: IGNITE-996
> URL: https://issues.apache.org/jira/browse/IGNITE-996
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Semen Boikov
>Assignee: Ilya Lantukh
>  Labels: Muted_test
> Attachments: ignite-996_thread_dump.log
>
>
> Test IgniteMessagingWithClientTest sometimes hangs on TC.



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

[jira] [Assigned] (IGNITE-2003) Some optional modules don't have Apache licenses file and README.txt

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov reassigned IGNITE-2003:


Assignee: Anton Vinogradov

> Some optional modules don't have Apache licenses file and README.txt
> 
>
> Key: IGNITE-2003
> URL: https://issues.apache.org/jira/browse/IGNITE-2003
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
> Environment: Apache Ignite 1.5.0 build #84
>Reporter: Vasilisa  Sidorova
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.5
>
>
> README.txt is absent for:
> ignite-jms11
> ignite-kafka
> ignite-mqtt
> ignite-zookeeper
> apache-2.0.txt is absent for:
> ignite-jms11
> ignite-mqtt
> ignite-zookeeper
> Please, add it



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

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

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov closed IGNITE-2064.


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



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

[jira] [Resolved] (IGNITE-2137) CacheAutoStoreExample fails with ClassNotFoundException

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov resolved IGNITE-2137.
--
Resolution: Not A Problem

In this case store should be in node class path.
This exception is expected.

> CacheAutoStoreExample fails with ClassNotFoundException
> ---
>
> Key: IGNITE-2137
> URL: https://issues.apache.org/jira/browse/IGNITE-2137
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
> Fix For: 1.5
>
>
> 1. Start DbH2ServerStartup in Idea
> 2. Start 1 node by bin/ignite.sh  examples/config/example-ignite.xml
> 3. Start CacheAutoStoreExample.
> 4. Examples hangs up and node got following exception:
> {noformat}
> [16:30:51,501][SEVERE][tcp-disco-msg-worker-#2%null%][TcpDiscoverySpi] Failed 
> to unmarshal discovery custom message.
> class org.apache.ignite.IgniteCheckedException: Failed to find class with 
> given class loader for unmarshalling (make sur
> e same versions of all classes are available on all nodes or enable 
> peer-class-loading): sun.misc.Launcher$AppClassLoade
> r@1a752144
> at 
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:108)
> at 
> org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMarshaller.java:78)
> at 
> org.apache.ignite.spi.discovery.tcp.messages.TcpDiscoveryCustomEventMessage.message(TcpDiscoveryCustomEventMe
> ssage.java:78)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.notifyDiscoveryListener(ServerImpl.java:4731
> )
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processCustomMessage(ServerImpl.java:4592)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2276)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5784)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2161)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.ignite.examples.datagrid.store.auto.CacheAutoStoreExample$CacheJ
> dbcPojoStoreExampleFactory
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:278)
> at 
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
> at 
> org.apache.ignite.marshaller.jdk.JdkMarshallerObjectInputStream.resolveClass(JdkMarshallerObjectInputStream.j
> ava:54)
> at 
> java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1612)
> at 
> java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517)
> at 
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
> at 
> java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1990)
> at 
> java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1915)
> at 
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1798)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
> at 
> java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1990)
> at 
> java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1915)
> at 
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1798)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
> at java.util.ArrayList.readObject(ArrayList.java:771)
> 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 
> java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1017)
> at 
> java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1893)
>

[jira] [Resolved] (IGNITE-2003) Some optional modules don't have Apache licenses file and README.txt

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov resolved IGNITE-2003.
--
Resolution: Fixed

> Some optional modules don't have Apache licenses file and README.txt
> 
>
> Key: IGNITE-2003
> URL: https://issues.apache.org/jira/browse/IGNITE-2003
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
> Environment: Apache Ignite 1.5.0 build #84
>Reporter: Vasilisa  Sidorova
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.5
>
>
> README.txt is absent for:
> ignite-jms11
> ignite-kafka
> ignite-mqtt
> ignite-zookeeper
> apache-2.0.txt is absent for:
> ignite-jms11
> ignite-mqtt
> ignite-zookeeper
> Please, add it



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

[jira] [Resolved] (IGNITE-2106) BinaryMarshaller: near cache mustn't keep a copy on put() operation

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov resolved IGNITE-2106.
--
Resolution: Fixed

Problem was with incorrect near entry invalidation when node becomes backup for 
this entry.
Fixed. New test added.


> BinaryMarshaller: near cache mustn't keep a copy on put() operation
> ---
>
> Key: IGNITE-2106
> URL: https://issues.apache.org/jira/browse/IGNITE-2106
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Blocker
>
> Binary marshaller is an opensouced Gridgain Prortable marshaller,
> So bug http://atlassian.gridgain.com/jira/browse/GG-10791 moved to Ignite 
> jira.
> There are several deployment related tests that fail when PortableMarshaller 
> is used.
> GridPortableCacheDeploymentSelftTest.testDeployment3()/testDeployemnt4();
> GridPortableCacheDeploymentOffHeapSelfTest.testDeployment3()/testDeployemnt4();
> The reason of the failure is that a near cache stores a copy of a cache entry 
> when the cache.put() is being executed. No cache.get() was explicitly called 
> during the test.



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

[jira] [Closed] (IGNITE-2106) BinaryMarshaller: near cache mustn't keep a copy on put() operation

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov closed IGNITE-2106.


> BinaryMarshaller: near cache mustn't keep a copy on put() operation
> ---
>
> Key: IGNITE-2106
> URL: https://issues.apache.org/jira/browse/IGNITE-2106
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Blocker
>
> Binary marshaller is an opensouced Gridgain Prortable marshaller,
> So bug http://atlassian.gridgain.com/jira/browse/GG-10791 moved to Ignite 
> jira.
> There are several deployment related tests that fail when PortableMarshaller 
> is used.
> GridPortableCacheDeploymentSelftTest.testDeployment3()/testDeployemnt4();
> GridPortableCacheDeploymentOffHeapSelfTest.testDeployment3()/testDeployemnt4();
> The reason of the failure is that a near cache stores a copy of a cache entry 
> when the cache.put() is being executed. No cache.get() was explicitly called 
> during the test.



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

[jira] [Closed] (IGNITE-2137) CacheAutoStoreExample fails with ClassNotFoundException

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov closed IGNITE-2137.


> CacheAutoStoreExample fails with ClassNotFoundException
> ---
>
> Key: IGNITE-2137
> URL: https://issues.apache.org/jira/browse/IGNITE-2137
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
> Fix For: 1.5
>
>
> 1. Start DbH2ServerStartup in Idea
> 2. Start 1 node by bin/ignite.sh  examples/config/example-ignite.xml
> 3. Start CacheAutoStoreExample.
> 4. Examples hangs up and node got following exception:
> {noformat}
> [16:30:51,501][SEVERE][tcp-disco-msg-worker-#2%null%][TcpDiscoverySpi] Failed 
> to unmarshal discovery custom message.
> class org.apache.ignite.IgniteCheckedException: Failed to find class with 
> given class loader for unmarshalling (make sur
> e same versions of all classes are available on all nodes or enable 
> peer-class-loading): sun.misc.Launcher$AppClassLoade
> r@1a752144
> at 
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:108)
> at 
> org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMarshaller.java:78)
> at 
> org.apache.ignite.spi.discovery.tcp.messages.TcpDiscoveryCustomEventMessage.message(TcpDiscoveryCustomEventMe
> ssage.java:78)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.notifyDiscoveryListener(ServerImpl.java:4731
> )
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processCustomMessage(ServerImpl.java:4592)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2276)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5784)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2161)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.ignite.examples.datagrid.store.auto.CacheAutoStoreExample$CacheJ
> dbcPojoStoreExampleFactory
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:278)
> at 
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
> at 
> org.apache.ignite.marshaller.jdk.JdkMarshallerObjectInputStream.resolveClass(JdkMarshallerObjectInputStream.j
> ava:54)
> at 
> java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1612)
> at 
> java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517)
> at 
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
> at 
> java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1990)
> at 
> java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1915)
> at 
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1798)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
> at 
> java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1990)
> at 
> java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1915)
> at 
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1798)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
> at java.util.ArrayList.readObject(ArrayList.java:771)
> 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 
> java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1017)
> at 
> java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1893)
> at 
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1798)
> at 

[jira] [Resolved] (IGNITE-2105) DirectMessageWriter cannot write nested collections.

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko resolved IGNITE-2105.
-
Resolution: Fixed

Merged into ignite-1.5

> DirectMessageWriter cannot write nested collections.
> 
>
> Key: IGNITE-2105
> URL: https://issues.apache.org/jira/browse/IGNITE-2105
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Fix For: 1.5
>
>
> Steps to reproduce:
> 1) Run GridMessageCollectionTest in ignite-1.5 branch
> 2) Observe class-cast exception.
> The problem is caused by DirectByteBufferStreamImplV2 which is re-used across 
> all nested objects. 
> This class is stateful. When nested collection is written, instead of writing 
> collection element it writes element of another collection which is upper in 
> call stack.
> Looks pretty critical for me.



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

[jira] [Resolved] (IGNITE-2095) SpringCacheManager doesn't support withKeepBinary() flag

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko resolved IGNITE-2095.
-
Resolution: Won't Fix

Adding this to Spring Caching doesn't make much sense, because switching 
{{withKeepBinary}} flag on will force user to work with Ignite's 
{{BinaryObject}}, which eliminates advantages of cache abstraction. In this 
case it's easier to fully switch to Ignite API.

> SpringCacheManager doesn't support withKeepBinary() flag
> 
>
> Key: IGNITE-2095
> URL: https://issues.apache.org/jira/browse/IGNITE-2095
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.5
>
>
> Currently {{SpringCacheManager}} doesn't allow to switch to 
> {{withKeepBinary()}} cache.
> SO thread: 
> http://stackoverflow.com/questions/34049172/ignite-and-spring-with-multiple-class-loaders/



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

[jira] [Updated] (IGNITE-2096) AtomicConfiguration and CollectionConfiguration should be properly checked for consistency

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-2096:

Fix Version/s: (was: 1.5)
   1.6

> AtomicConfiguration and CollectionConfiguration should be properly checked 
> for consistency
> --
>
> Key: IGNITE-2096
> URL: https://issues.apache.org/jira/browse/IGNITE-2096
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
> Fix For: 1.6
>
>
> Currently {{AtomicConfiguration}} and {{CollectionConfiguration}} are mapped 
> to system caches configuration and consistency is checked like for any other 
> cache. This leads to unintuitive errors.



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

[jira] [Commented] (IGNITE-2105) DirectMessageWriter cannot write nested collections.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2105:


Github user vkulichenko closed the pull request at:

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


> DirectMessageWriter cannot write nested collections.
> 
>
> Key: IGNITE-2105
> URL: https://issues.apache.org/jira/browse/IGNITE-2105
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Fix For: 1.5
>
>
> Steps to reproduce:
> 1) Run GridMessageCollectionTest in ignite-1.5 branch
> 2) Observe class-cast exception.
> The problem is caused by DirectByteBufferStreamImplV2 which is re-used across 
> all nested objects. 
> This class is stateful. When nested collection is written, instead of writing 
> collection element it writes element of another collection which is upper in 
> call stack.
> Looks pretty critical for me.



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

[jira] [Closed] (IGNITE-2105) DirectMessageWriter cannot write nested collections.

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko closed IGNITE-2105.
---

> DirectMessageWriter cannot write nested collections.
> 
>
> Key: IGNITE-2105
> URL: https://issues.apache.org/jira/browse/IGNITE-2105
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Fix For: 1.5
>
>
> Steps to reproduce:
> 1) Run GridMessageCollectionTest in ignite-1.5 branch
> 2) Observe class-cast exception.
> The problem is caused by DirectByteBufferStreamImplV2 which is re-used across 
> all nested objects. 
> This class is stateful. When nested collection is written, instead of writing 
> collection element it writes element of another collection which is upper in 
> call stack.
> Looks pretty critical for me.



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

[jira] [Closed] (IGNITE-2095) SpringCacheManager doesn't support withKeepBinary() flag

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko closed IGNITE-2095.
---

> SpringCacheManager doesn't support withKeepBinary() flag
> 
>
> Key: IGNITE-2095
> URL: https://issues.apache.org/jira/browse/IGNITE-2095
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.5
>
>
> Currently {{SpringCacheManager}} doesn't allow to switch to 
> {{withKeepBinary()}} cache.
> SO thread: 
> http://stackoverflow.com/questions/34049172/ignite-and-spring-with-multiple-class-loaders/



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

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

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov resolved IGNITE-2064.
--
Resolution: Fixed

Fixed all stable failing tests at 1.5.

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



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

[jira] [Commented] (IGNITE-2082) Documentationd for C++/.Net missed in fabric binary package

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-2082:
-

Sergey, fixed.

> Documentationd for C++/.Net missed in fabric binary package
> ---
>
> Key: IGNITE-2082
> URL: https://issues.apache.org/jira/browse/IGNITE-2082
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Reporter: Sergey Kozlov
>Assignee: Igor Sapego
>Priority: Critical
> Fix For: 1.5
>
>
> There's no documentation generated by Doxygen for /platforms/cpp and 
> platforms/dotnet in Apache Ignite fabric binary package



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

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

[Artem Shutak (JIRA)]

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

Artem Shutak commented on IGNITE-2065:
--

Tried to merge with the latest ignite-1.5. Got lots conflicts and have no 
assurance that my changes and changes at 1.5 are compatible. WIll rework it and 
implement the ticket by parts. First 2 steps: packages and class names. All 
other staff can be fixed in one commit after.

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



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

[jira] [Commented] (IGNITE-1906) .Net: Ignite configuration without Spring

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-1906:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-1906 .Net: Ignite configuration without Spring



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

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

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

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


commit 39a8bc65a3d8f20145153c614ca4e9746ce331d6
Author: Pavel Tupitsyn 
Date:   2015-11-16T13:40:03Z

IGNITE-1907 .Net: Cache configuration

commit c73d82dfe0e47d16fbfbb0a270d822bd9c8246db
Author: Pavel Tupitsyn 
Date:   2015-11-16T13:47:22Z

IGNITE-1907 .Net: Cache configuration

commit 5e94417d8946d1b92541e83869f14cb8fdc38da9
Author: Pavel Tupitsyn 
Date:   2015-11-16T13:54:51Z

wip

commit 5fce7a1247c4bc34789b8733b921ecfcb4cbdf64
Author: Pavel Tupitsyn 
Date:   2015-11-16T14:17:43Z

wip

commit a4e9c1da1c50dc1081dc97b3aa8eafdecf52fec2
Author: Pavel Tupitsyn 
Date:   2015-11-16T15:23:00Z

wip

commit ad0ff6eb90246c71bd7e7687f3855820e2a9621d
Author: Pavel Tupitsyn 
Date:   2015-11-16T15:29:28Z

wip

commit 1ceca1200fbb98b96c10c173c24d30d80712b94b
Author: Pavel Tupitsyn 
Date:   2015-11-16T15:35:59Z

unit test skeleton

commit 11ed6a55c9d6f1d6a6a77b9f9ecbece135402796
Author: Pavel Tupitsyn 
Date:   2015-11-16T15:41:51Z

wip GetConfiguration

commit 033c5e35d2304976cddd428ccf92e76e2eb039c1
Author: Pavel Tupitsyn 
Date:   2015-11-16T15:50:34Z

wip

commit 45938e6ff0cf0a51726bf82886f53d3f20bc8a9b
Author: Pavel Tupitsyn 
Date:   2015-11-16T15:52:02Z

wip test

commit 8bbb57919397f36697ea6d885418d0de92c02b02
Author: Pavel Tupitsyn 
Date:   2015-11-16T16:36:10Z

wip

commit 3fc284307f15e63c8d12e6a1a13c61f2a3b01ebc
Author: Pavel Tupitsyn 
Date:   2015-11-16T16:49:02Z

wip CacheConfiguration

commit 8a702577910b6d263c99b39c0bccbdd34a09aaf1
Author: Pavel Tupitsyn 
Date:   2015-11-17T07:08:52Z

wip

commit 3bde86ddc3f81b767c8718673b6f8e0c7a89ddcb
Author: Pavel Tupitsyn 
Date:   2015-11-17T07:12:38Z

wip

commit 3960e0aee4c36b6f47181bf79fbd7eb962ae7344
Author: Pavel Tupitsyn 
Date:   2015-11-17T07:16:50Z

wip enums

commit c80dfc80379c3c2640ec2dcf36494112d4bdcd94
Author: Pavel Tupitsyn 
Date:   2015-11-17T07:20:08Z

wip enums

commit 17fb91293a5569f4d0bc924008f7fabbfff2eb73
Author: Pavel Tupitsyn 
Date:   2015-11-17T07:28:34Z

wip enums

commit b74e4c705843d3e9822fcbf2415ae0666b9a8ec5
Author: Pavel Tupitsyn 
Date:   2015-11-17T07:32:58Z

enums done

commit 58f0611a519fd2c82d0af8329145089726deea51
Author: Pavel Tupitsyn 
Date:   2015-11-17T07:59:41Z

wip default values

commit 6d4c3deb39d18ad5a01a74da37acc464fb2889fc
Author: Pavel Tupitsyn 
Date:   2015-11-17T08:09:56Z

Default values done

commit c23078a52683d998e2f5265fa511600418de8dfa
Author: Pavel Tupitsyn 
Date:   2015-11-17T08:13:37Z

cleanup wip

commit 27f12b17c6e00eb1125b1b7ce0fb2025e096b337
Author: Pavel Tupitsyn 
Date:   2015-11-17T08:22:29Z

wip docs

commit 88f52a6ff309f03934bdb4f5da558d9eb8155965
Author: Pavel Tupitsyn 
Date:   2015-11-17T08:32:20Z

Docs done

commit e8ad49508b93ce50dde1f4bfcfe1c19890588c82
Author: Pavel Tupitsyn 
Date:   2015-11-17T08:38:22Z

Timespans instead of milliseconds

commit b2a2382c2fed12ca0ee3e456d4b8f46a4766963c
Author: Pavel Tupitsyn 
Date:   2015-11-17T08:45:19Z

Read from stream

commit 6fbe92cf73a13b856d89dce44bd5bbb5d7283f67
Author: Pavel Tupitsyn 
Date:   2015-11-17T08:51:46Z

write to stream

commit 929477791e9acac41e3ac3d040d082ea8c1f88a9
Author: Pavel Tupitsyn 
Date:   2015-11-17T08:55:32Z

wip

commit e8fbf65080d06726681e753a1b7a446dcd861295
Author: Pavel Tupitsyn 
Date:   2015-11-17T09:02:39Z

wip

commit c89d43c0cd9e50f22ad69f4eb17c9e069f39bb92
Author: Pavel Tupitsyn 
Date:   2015-11-17T09:14:35Z

wip tests

commit 

[jira] [Resolved] (IGNITE-2030) ignite.bat file does not work when JAVA_HOME contains parethensis

[Vladimir Ershov (JIRA)]

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

Vladimir Ershov resolved IGNITE-2030.
-
Resolution: Fixed

> ignite.bat file does not work when JAVA_HOME contains parethensis
> -
>
> Key: IGNITE-2030
> URL: https://issues.apache.org/jira/browse/IGNITE-2030
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Vladimir Ershov
> Fix For: 1.5
>
> Attachments: IGNITE-2030_fix_error_on_startup_.patch, bad_start.txt, 
> good_start.txt
>
>
> When starting ignite.bat with a folder which contains parenthesis, the 
> launcher will fail:
> For example, JAVA_HOME=C:\Program Files (x86)\jdk1.7.0_76\
> Program Files (x86)
> Error (happens @ parseargs.bat script): 
> \Java\jre1.8.0_25\bin\java.exe" -cp 
> C:\ignite\gridgain-enterprise-fabric-7.5.0\g
> ridgain-enterprise-fabric-7.5.0\libs\*;C:\ignite\gridgain-enterprise-fabric-7.5.
> 0\gridgain-enterprise-fabric-7.5.0\libs\ignite-indexing\*;C:\ignite\gridgain-ent
> erprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\ignite-spring\*;C:\ig
> nite\gridgain-enterprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\lice
> nses\* org.apache.ignite.startup.cmdline.CommandLineTransformer "`) was 
> unexpect
> ed at this time.



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

[jira] [Created] (IGNITE-2131) NPE in GridJobProcessor

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-2131:


 Summary: NPE in GridJobProcessor
 Key: IGNITE-2131
 URL: https://issues.apache.org/jira/browse/IGNITE-2131
 Project: Ignite
  Issue Type: Bug
  Components: compute
Affects Versions: 1.5
Reporter: Alexey Kuznetsov
 Fix For: 1.5


I got this NPE.

Looking into GridJobProcessor.java:1024 code, I see that NPE could happen if 
marshaler return null.

Maybe we could throw exception with appropriate message?

{code}
Exception in thread "pub-#7%null%" Exception in thread "pub-#8%null%" 
java.lang.NullPointerException
 at java.util.ArrayList.(ArrayList.java:164)
 at 
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1024)
 at 
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1770)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
{code}



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

[jira] [Closed] (IGNITE-959) Indexing: avoid sending key-value class definitions to servers when starting a cache

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk closed IGNITE-959.
---

> Indexing: avoid sending key-value class definitions to servers when starting 
> a cache
> 
>
> Key: IGNITE-959
> URL: https://issues.apache.org/jira/browse/IGNITE-959
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
> Fix For: 1.5
>
>
> Currently when indexed types are set to cache configuration, we send them to 
> server nodes. It defeats the purpose of optimized marshaller improvements.
> Instead, we should analyze class annotations on clients, convert them to 
> metadata and use this metadata on servers.



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

[jira] [Resolved] (IGNITE-959) Indexing: avoid sending key-value class definitions to servers when starting a cache

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk resolved IGNITE-959.
-
Resolution: Fixed

Merged to ignite-1.5

> Indexing: avoid sending key-value class definitions to servers when starting 
> a cache
> 
>
> Key: IGNITE-959
> URL: https://issues.apache.org/jira/browse/IGNITE-959
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
> Fix For: 1.5
>
>
> Currently when indexed types are set to cache configuration, we send them to 
> server nodes. It defeats the purpose of optimized marshaller improvements.
> Instead, we should analyze class annotations on clients, convert them to 
> metadata and use this metadata on servers.



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

[jira] [Created] (IGNITE-2142) CPP: Move ODBC MSVS projects to separate solution.

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-2142:
---

 Summary: CPP: Move ODBC MSVS projects to separate solution.
 Key: IGNITE-2142
 URL: https://issues.apache.org/jira/browse/IGNITE-2142
 Project: Ignite
  Issue Type: Sub-task
  Components: odbc
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 1.6


Currently ODBC project are included in general CPP solution. Move them to 
separate solution for the ODBC.



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

[jira] [Created] (IGNITE-2141) Cleanup ODBC configuration.

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-2141:
---

 Summary: Cleanup ODBC configuration.
 Key: IGNITE-2141
 URL: https://issues.apache.org/jira/browse/IGNITE-2141
 Project: Ignite
  Issue Type: Sub-task
  Components: odbc
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 1.6


Currently {{OdbcConfiguration}} contatins a lot of dead code. It should be 
removed.

Also, currenty {{OdbcConfiguration#isEnabled}} used to determine if ODBC is 
enabled which seems unnecessary - just check for presence of the 
{{OdbcConfiguration}} itself to find out whether ODBC is enabled.



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

[jira] [Created] (IGNITE-2132) Start test-drive on agent from web

[Andrey Novikov (JIRA)]

Andrey Novikov created IGNITE-2132:
--

 Summary: Start test-drive on agent from web
 Key: IGNITE-2132
 URL: https://issues.apache.org/jira/browse/IGNITE-2132
 Project: Ignite
  Issue Type: Sub-task
Reporter: Andrey Novikov
Assignee: Andrey Novikov


* Test-drive for metadata
* Test-drive for sql



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

[jira] [Commented] (IGNITE-1906) .Net: Ignite configuration without Spring

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-1906:


Github user ptupitsyn closed the pull request at:

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


> .Net: Ignite configuration without Spring
> -
>
> Key: IGNITE-1906
> URL: https://issues.apache.org/jira/browse/IGNITE-1906
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 1.6
>
>
> * Spring is alien for .NET developers
> * In-code configuration is often preferrable



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

[jira] [Closed] (IGNITE-2127) Javadoc still points on OptmizedMarshaller as default one

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-2127.
-

> Javadoc still points on OptmizedMarshaller as default one
> -
>
> Key: IGNITE-2127
> URL: https://issues.apache.org/jira/browse/IGNITE-2127
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
> Fix For: 1.5
>
>
> docs/javadoc/overview-summary.html:
> Marshallers 
> ...
> {{org.apache.ignite.marshaller.optimized}} Contains default Optimized 
> marshaller.



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

[jira] [Closed] (IGNITE-2117) Javadoc: osgi packages have no description

[Sergey Kozlov (JIRA)]

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

Sergey Kozlov closed IGNITE-2117.
-

> Javadoc: osgi packages have no description
> --
>
> Key: IGNITE-2117
> URL: https://issues.apache.org/jira/browse/IGNITE-2117
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Ilya Suntsov
> Fix For: 1.5
>
>
> Take a look on summary-overview.hml. following packages have no description:
> org.apache.ignite.osgi 
> org.apache.ignite.osgi.classloaders



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