[jira] [Commented] (IGNITE-11008) JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH

[kcheng.mvp (Jira)]

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

kcheng.mvp commented on IGNITE-11008:
-

[~mmuzaf] Can you help to process the PR?

> JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH
> --
>
> Key: IGNITE-11008
> URL: https://issues.apache.org/jira/browse/IGNITE-11008
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: kcheng.mvp
>Priority: Minor
> Fix For: 2.8
>
>
> Found redundant spaces in 
> org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata#getColumns
> "IS_GENERATEDCOLUMN "
> "BUFFER_LENGTH "



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (IGNITE-12240) ReadOnlyCollectionView2X fails on iterator.next

[kcheng.mvp (Jira)]

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

kcheng.mvp reassigned IGNITE-12240:
---

Assignee: kcheng.mvp

> ReadOnlyCollectionView2X fails on iterator.next
> ---
>
> Key: IGNITE-12240
> URL: https://issues.apache.org/jira/browse/IGNITE-12240
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.7.6
>Reporter: Nikolay Izhikov
>Assignee: kcheng.mvp
>Priority: Major
>  Labels: newbie
>
> Simple reproducer below will throw {{NoSuchElementException}}.
> Iterator only works if one call {{hasNext}} before {{next}}.
> {code:java}
> /** */
> @Test
> public void testReadOnlyCollection() throws Exception {
> Collection c1 = Collections.emptyList();
> Collection c2 = Arrays.asList("1");
> ReadOnlyCollectionView2X view = new 
> ReadOnlyCollectionView2X<>(c1, c2);
> assertEquals("1", view.iterator().next());
> }
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Reopened] (IGNITE-11976) @SpringResource is silently ignored if no Spring context is provided

[kcheng.mvp (Jira)]

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

kcheng.mvp reopened IGNITE-11976:
-

> @SpringResource is silently ignored if no Spring context is provided
> 
>
> Key: IGNITE-11976
> URL: https://issues.apache.org/jira/browse/IGNITE-11976
> Project: Ignite
>  Issue Type: Improvement
>  Components: spring
>Affects Versions: 2.7
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Major
>  Labels: newbie
>
> @SpringResource annotation is silently ignored and the annotated field is 
> null if Spring context.
> For @SpringResource to work the node needs to be started with 
> IgniteSpring::start instead of Ignition::start, but the user may not know 
> that.
> Need to add a warning for this.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (IGNITE-11976) @SpringResource is silently ignored if no Spring context is provided

[kcheng.mvp (Jira)]

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

kcheng.mvp resolved IGNITE-11976.
-
Resolution: Resolved

> @SpringResource is silently ignored if no Spring context is provided
> 
>
> Key: IGNITE-11976
> URL: https://issues.apache.org/jira/browse/IGNITE-11976
> Project: Ignite
>  Issue Type: Improvement
>  Components: spring
>Affects Versions: 2.7
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Major
>  Labels: newbie
>
> @SpringResource annotation is silently ignored and the annotated field is 
> null if Spring context.
> For @SpringResource to work the node needs to be started with 
> IgniteSpring::start instead of Ignition::start, but the user may not know 
> that.
> Need to add a warning for this.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-11008) JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH

[kcheng.mvp (Jira)]

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

kcheng.mvp commented on IGNITE-11008:
-

[~mmuzaf] Can you help me to review the PR ?

> JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH
> --
>
> Key: IGNITE-11008
> URL: https://issues.apache.org/jira/browse/IGNITE-11008
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: kcheng.mvp
>Priority: Minor
> Fix For: 2.8
>
>
> Found redundant spaces in 
> org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata#getColumns
> "IS_GENERATEDCOLUMN "
> "BUFFER_LENGTH "



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-11868) GridClient#data() should be deprecated/removed.

[kcheng.mvp (Jira)]

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

kcheng.mvp commented on IGNITE-11868:
-

[~slava.koptilin] TeamCity is green 
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_BuildApacheIgnite_IgniteTests24Java8=pull%2F6868%2Fhead=buildTypeStatusDiv

Can you help do the further process.

Thanks

> GridClient#data() should be deprecated/removed.
> ---
>
> Key: IGNITE-11868
> URL: https://issues.apache.org/jira/browse/IGNITE-11868
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Vyacheslav Koptilin
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
> Fix For: 2.8
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> It seems that {{GridClient#data()}} does not make sense after IGNITE-3488 and 
> therefore it can be removed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-11008) JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH

[kcheng.mvp (Jira)]

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

kcheng.mvp commented on IGNITE-11008:
-

[~spilschikov] Seems that I dont have privilege to change *Status*

> JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH
> --
>
> Key: IGNITE-11008
> URL: https://issues.apache.org/jira/browse/IGNITE-11008
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: kcheng.mvp
>Priority: Minor
> Fix For: 2.8
>
>
> Found redundant spaces in 
> org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata#getColumns
> "IS_GENERATEDCOLUMN "
> "BUFFER_LENGTH "



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (IGNITE-11008) JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH

[kcheng.mvp (Jira)]

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

kcheng.mvp resolved IGNITE-11008.
-
Resolution: Fixed

> JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH
> --
>
> Key: IGNITE-11008
> URL: https://issues.apache.org/jira/browse/IGNITE-11008
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: kcheng.mvp
>Priority: Minor
> Fix For: 2.8
>
>
> Found redundant spaces in 
> org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata#getColumns
> "IS_GENERATEDCOLUMN "
> "BUFFER_LENGTH "



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Reopened] (IGNITE-11008) JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH

[kcheng.mvp (Jira)]

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

kcheng.mvp reopened IGNITE-11008:
-

> JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH
> --
>
> Key: IGNITE-11008
> URL: https://issues.apache.org/jira/browse/IGNITE-11008
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: kcheng.mvp
>Priority: Minor
> Fix For: 2.8
>
>
> Found redundant spaces in 
> org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata#getColumns
> "IS_GENERATEDCOLUMN "
> "BUFFER_LENGTH "



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-10515) In JDBC thick driver streaming mode, INSERTs ignored silently when trying to insert into wrong table

[kcheng.mvp (Jira)]

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

kcheng.mvp commented on IGNITE-10515:
-

I am trying to investigate this issue.

> In JDBC thick driver streaming mode, INSERTs ignored silently when trying to 
> insert into wrong table
> 
>
> Key: IGNITE-10515
> URL: https://issues.apache.org/jira/browse/IGNITE-10515
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc
>Reporter: Ilya Kasnacheev
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: usability
> Attachments: JdbcStreamingSelfTest.java
>
>
> It is not uncommon to do all your SQL from cache=default JDBC url and forget 
> about that.
> But, if you try to use streaming=true with that, your INSERTs will be ignored 
> when the destination cache is different.
> There should be some kind of error message if you try to stream to a 
> different cache than the one you are connected to.
> Please see reproducer in maillist or the attached test.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (IGNITE-10515) In JDBC thick driver streaming mode, INSERTs ignored silently when trying to insert into wrong table

[kcheng.mvp (Jira)]

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

kcheng.mvp reassigned IGNITE-10515:
---

Assignee: kcheng.mvp

> In JDBC thick driver streaming mode, INSERTs ignored silently when trying to 
> insert into wrong table
> 
>
> Key: IGNITE-10515
> URL: https://issues.apache.org/jira/browse/IGNITE-10515
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc
>Reporter: Ilya Kasnacheev
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: usability
> Attachments: JdbcStreamingSelfTest.java
>
>
> It is not uncommon to do all your SQL from cache=default JDBC url and forget 
> about that.
> But, if you try to use streaming=true with that, your INSERTs will be ignored 
> when the destination cache is different.
> There should be some kind of error message if you try to stream to a 
> different cache than the one you are connected to.
> Please see reproducer in maillist or the attached test.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-11868) GridClient#data() should be deprecated/removed.

[kcheng.mvp (Jira)]

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

kcheng.mvp commented on IGNITE-11868:
-

[~slava.koptilin] Can you help do the code review. 
PR is : https://github.com/apache/ignite/pull/6894
TeamCity is green : 
https://ci.ignite.apache.org/viewLog.html?buildId=4621223=IgniteTests24Java8_RunCache

> GridClient#data() should be deprecated/removed.
> ---
>
> Key: IGNITE-11868
> URL: https://issues.apache.org/jira/browse/IGNITE-11868
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Vyacheslav Koptilin
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> It seems that {{GridClient#data()}} does not make sense after IGNITE-3488 and 
> therefore it can be removed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-11868) GridClient#data() should be deprecated/removed.

[kcheng.mvp (Jira)]

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

kcheng.mvp commented on IGNITE-11868:
-

[~slava.koptilin] my fault, there are references from unit test. i will try to 
remove this method. 

> GridClient#data() should be deprecated/removed.
> ---
>
> Key: IGNITE-11868
> URL: https://issues.apache.org/jira/browse/IGNITE-11868
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Vyacheslav Koptilin
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
>
> It seems that {{GridClient#data()}} does not make sense after IGNITE-3488 and 
> therefore it can be removed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-11008) JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH

[kcheng.mvp (Jira)]

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

kcheng.mvp commented on IGNITE-11008:
-

[~spilschikov] Can you help do a code review? TeamCity is green 
https://ci.ignite.apache.org/viewLog.html?buildId=4618047=buildResultsDiv=IgniteTests24Java8_BuildApacheIgnite

> JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH
> --
>
> Key: IGNITE-11008
> URL: https://issues.apache.org/jira/browse/IGNITE-11008
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: kcheng.mvp
>Priority: Minor
> Fix For: 2.8
>
>
> Found redundant spaces in 
> org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata#getColumns
> "IS_GENERATEDCOLUMN "
> "BUFFER_LENGTH "



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-11817) org.apache.ignite.client.ClientCache#removeAll() and org.apache.ignite.client.ClientCache#clear missed Java Doc

[kcheng.mvp (Jira)]

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

kcheng.mvp commented on IGNITE-11817:
-

I have checked the code. somebody added the javadoc. so close it.

> org.apache.ignite.client.ClientCache#removeAll() and 
> org.apache.ignite.client.ClientCache#clear missed Java Doc
> ---
>
> Key: IGNITE-11817
> URL: https://issues.apache.org/jira/browse/IGNITE-11817
> Project: Ignite
>  Issue Type: Improvement
>  Components: documentation, thin client
>Affects Versions: 2.7
>Reporter: kcheng.mvp
>Assignee: kcheng.mvp
>Priority: Trivial
> Fix For: 2.8
>
>
> Use would be confused about the these api, need to address the difference in 
> the java doc.
> please see the mail list
> http://apache-ignite-users.70518.x6.nabble.com/What-s-the-difference-between-ClientCache-removeAll-and-ClientCache-clear-td28002.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (IGNITE-11817) org.apache.ignite.client.ClientCache#removeAll() and org.apache.ignite.client.ClientCache#clear missed Java Doc

[kcheng.mvp (Jira)]

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

kcheng.mvp resolved IGNITE-11817.
-
Resolution: Fixed

> org.apache.ignite.client.ClientCache#removeAll() and 
> org.apache.ignite.client.ClientCache#clear missed Java Doc
> ---
>
> Key: IGNITE-11817
> URL: https://issues.apache.org/jira/browse/IGNITE-11817
> Project: Ignite
>  Issue Type: Improvement
>  Components: documentation, thin client
>Affects Versions: 2.7
>Reporter: kcheng.mvp
>Assignee: kcheng.mvp
>Priority: Trivial
> Fix For: 2.8
>
>
> Use would be confused about the these api, need to address the difference in 
> the java doc.
> please see the mail list
> http://apache-ignite-users.70518.x6.nabble.com/What-s-the-difference-between-ClientCache-removeAll-and-ClientCache-clear-td28002.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-12088) Cache or template name should be validated before attempt to start

[kcheng.mvp (Jira)]

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

kcheng.mvp commented on IGNITE-12088:
-

TeamCity is green 
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_BuildApacheIgnite=buildTypeBranches

> Cache or template name should be validated before attempt to start
> --
>
> Key: IGNITE-12088
> URL: https://issues.apache.org/jira/browse/IGNITE-12088
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Pavel Kovalenko
>Assignee: kcheng.mvp
>Priority: Critical
>  Labels: usability
> Fix For: 2.8
>
>
> If set too long cache name it can be a cause of impossibility to create work 
> directory for that cache:
> {noformat}
> [2019-08-20 
> 19:35:42,139][ERROR][exchange-worker-#172%node1%][IgniteTestResources] 
> Critical system error detected. Will be handled accordingly to configured 
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler 
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, 
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext 
> [type=CRITICAL_ERROR, err=class o.a.i.IgniteCheckedException: Failed to 
> initialize cache working directory (failed to create, make sure the work 
> folder has correct permissions): 
> /home/gridgain/projects/incubator-ignite/work/db/node1/cache-CacheConfiguration
>  [name=ccfg3staticTemplate*, grpName=null, memPlcName=null, 
> storeConcurrentLoadAllThreshold=5, rebalancePoolSize=1, 
> rebalanceTimeout=1, evictPlc=null, evictPlcFactory=null, 
> onheapCache=false, sqlOnheapCache=false, sqlOnheapCacheMaxSize=0, 
> evictFilter=null, eagerTtl=true, dfltLockTimeout=0, nearCfg=null, 
> writeSync=null, storeFactory=null, storeKeepBinary=false, loadPrevVal=false, 
> aff=null, cacheMode=PARTITIONED, atomicityMode=null, backups=6, 
> invalidate=false, tmLookupClsName=null, rebalanceMode=ASYNC, 
> rebalanceOrder=0, rebalanceBatchSize=524288, rebalanceBatchesPrefetchCnt=2, 
> maxConcurrentAsyncOps=500, sqlIdxMaxInlineSize=-1, writeBehindEnabled=false, 
> writeBehindFlushSize=10240, writeBehindFlushFreq=5000, 
> writeBehindFlushThreadCnt=1, writeBehindBatchSize=512, 
> writeBehindCoalescing=true, maxQryIterCnt=1024, affMapper=null, 
> rebalanceDelay=0, rebalanceThrottle=0, interceptor=null, 
> longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true, 
> nodeFilter=null, sqlSchema=null, sqlEscapeAll=false, cpOnRead=true, 
> topValidator=null, partLossPlc=IGNORE, qryParallelism=1, evtsDisabled=false, 
> encryptionEnabled=false, diskPageCompression=null, 
> diskPageCompressionLevel=null]0]]
> class org.apache.ignite.IgniteCheckedException: Failed to initialize cache 
> working directory (failed to create, make sure the work folder has correct 
> permissions): 
> /home/gridgain/projects/incubator-ignite/work/db/node1/cache-CacheConfiguration
>  [name=ccfg3staticTemplate*, grpName=null, memPlcName=null, 
> storeConcurrentLoadAllThreshold=5, rebalancePoolSize=1, 
> rebalanceTimeout=1, evictPlc=null, evictPlcFactory=null, 
> onheapCache=false, sqlOnheapCache=false, sqlOnheapCacheMaxSize=0, 
> evictFilter=null, eagerTtl=true, dfltLockTimeout=0, nearCfg=null, 
> writeSync=null, storeFactory=null, storeKeepBinary=false, loadPrevVal=false, 
> aff=null, cacheMode=PARTITIONED, atomicityMode=null, backups=6, 
> invalidate=false, tmLookupClsName=null, rebalanceMode=ASYNC, 
> rebalanceOrder=0, rebalanceBatchSize=524288, rebalanceBatchesPrefetchCnt=2, 
> maxConcurrentAsyncOps=500, sqlIdxMaxInlineSize=-1, writeBehindEnabled=false, 
> writeBehindFlushSize=10240, writeBehindFlushFreq=5000, 
> writeBehindFlushThreadCnt=1, writeBehindBatchSize=512, 
> writeBehindCoalescing=true, maxQryIterCnt=1024, affMapper=null, 
> rebalanceDelay=0, rebalanceThrottle=0, interceptor=null, 
> longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true, 
> nodeFilter=null, sqlSchema=null, sqlEscapeAll=false, cpOnRead=true, 
> topValidator=null, partLossPlc=IGNORE, qryParallelism=1, evtsDisabled=false, 
> encryptionEnabled=false, diskPageCompression=null, 
> diskPageCompressionLevel=null]0
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.checkAndInitCacheWorkDir(FilePageStoreManager.java:769)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.checkAndInitCacheWorkDir(FilePageStoreManager.java:748)
>   at 
> org.apache.ignite.internal.processors.cache.CachesRegistry.persistCacheConfigurations(CachesRegistry.java:289)
>   at 
> org.apache.ignite.internal.processors.cache.CachesRegistry.registerAllCachesAndGroups(CachesRegistry.java:264)
>   at 
> 

[jira] [Commented] (IGNITE-11008) JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH

[kcheng.mvp (Jira)]

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

kcheng.mvp commented on IGNITE-11008:
-

[~spilschikov] Raised a PR https://github.com/apache/ignite/pull/6885. 

> JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH
> --
>
> Key: IGNITE-11008
> URL: https://issues.apache.org/jira/browse/IGNITE-11008
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: kcheng.mvp
>Priority: Minor
> Fix For: 2.8
>
>
> Found redundant spaces in 
> org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata#getColumns
> "IS_GENERATEDCOLUMN "
> "BUFFER_LENGTH "



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (IGNITE-11008) JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH

[kcheng.mvp (Jira)]

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

kcheng.mvp reassigned IGNITE-11008:
---

Assignee: kcheng.mvp

> JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH
> --
>
> Key: IGNITE-11008
> URL: https://issues.apache.org/jira/browse/IGNITE-11008
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: kcheng.mvp
>Priority: Minor
> Fix For: 2.8
>
>
> Found redundant spaces in 
> org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata#getColumns
> "IS_GENERATEDCOLUMN "
> "BUFFER_LENGTH "



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (IGNITE-11458) ClassCastException when reading objects in Collection and Map from ClientCache

[kcheng.mvp (Jira)]

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

kcheng.mvp reassigned IGNITE-11458:
---

Assignee: (was: kcheng.mvp)

> ClassCastException when reading objects in Collection and Map from ClientCache
> --
>
> Key: IGNITE-11458
> URL: https://issues.apache.org/jira/browse/IGNITE-11458
> Project: Ignite
>  Issue Type: Bug
>  Components: thin client
> Environment: ignite-core.2.8.0
>Reporter: Jinil Lee
>Priority: Major
>  Labels: newbie, patch, pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There is a ClassCastException when reading objects in Collection or Map 
> stored in ClientCache while using thin client.
> When deserializing a BinaryObject, I think that the Object in the Collection 
> is not being processed.
> I made a patch and I think it works well with the my patch,
>  so please let me know if this is not a problem or if you have any other 
> solutions.
> Below is the test code.
> {code:java}
> //Case 0. Object
> ClientCache cache1 = igniteClient.getOrCreateCache("Object");
> cache1.put("key", val);
> //OK!!!
> System.out.println(cache1.get("key").getStreet());
> //---
> //Case 1. Collection
> //---
> ClientCache> cache2 = 
> igniteClient.getOrCreateCache("Collection");
> List list = new ArrayList<>();
> list.add(val);
> cache2.put("key", list);
> //ClassCastException!!!
> System.out.println(cache2.get("key").get(0).getStreet()); 
> //---
> //Case 2. Map
> //---
> ClientCache> cache3 = 
> igniteClient.getOrCreateCache("Map");
> Map map = new HashMap<>();
> map.put("key", val);
> cache3.getAndPut("key", map);
> //ClassCastException!!!
> System.out.println(cache3.get("key").get("key").getStreet());
> //---
> //Case 3. Colection + Map
> //---
> ClientCache>> cache4 = 
> igniteClient.getOrCreateCache("Collection_Map");
> List> mapList = new ArrayList<>();
> mapList.add(map);
> cache4.put("key", mapList);
> //ClassCastException!!!
> System.out.println(cache4.get("key").get(0).get("key").getStreet());
> {code}
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (IGNITE-11458) ClassCastException when reading objects in Collection and Map from ClientCache

[kcheng.mvp (Jira)]

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

kcheng.mvp reassigned IGNITE-11458:
---

Assignee: kcheng.mvp

> ClassCastException when reading objects in Collection and Map from ClientCache
> --
>
> Key: IGNITE-11458
> URL: https://issues.apache.org/jira/browse/IGNITE-11458
> Project: Ignite
>  Issue Type: Bug
>  Components: thin client
> Environment: ignite-core.2.8.0
>Reporter: Jinil Lee
>Assignee: kcheng.mvp
>Priority: Major
>  Labels: newbie, patch, pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There is a ClassCastException when reading objects in Collection or Map 
> stored in ClientCache while using thin client.
> When deserializing a BinaryObject, I think that the Object in the Collection 
> is not being processed.
> I made a patch and I think it works well with the my patch,
>  so please let me know if this is not a problem or if you have any other 
> solutions.
> Below is the test code.
> {code:java}
> //Case 0. Object
> ClientCache cache1 = igniteClient.getOrCreateCache("Object");
> cache1.put("key", val);
> //OK!!!
> System.out.println(cache1.get("key").getStreet());
> //---
> //Case 1. Collection
> //---
> ClientCache> cache2 = 
> igniteClient.getOrCreateCache("Collection");
> List list = new ArrayList<>();
> list.add(val);
> cache2.put("key", list);
> //ClassCastException!!!
> System.out.println(cache2.get("key").get(0).getStreet()); 
> //---
> //Case 2. Map
> //---
> ClientCache> cache3 = 
> igniteClient.getOrCreateCache("Map");
> Map map = new HashMap<>();
> map.put("key", val);
> cache3.getAndPut("key", map);
> //ClassCastException!!!
> System.out.println(cache3.get("key").get("key").getStreet());
> //---
> //Case 3. Colection + Map
> //---
> ClientCache>> cache4 = 
> igniteClient.getOrCreateCache("Collection_Map");
> List> mapList = new ArrayList<>();
> mapList.add(map);
> cache4.put("key", mapList);
> //ClassCastException!!!
> System.out.println(cache4.get("key").get(0).get("key").getStreet());
> {code}
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-11721) IgniteJdbcDriver with streaming enabled doesn't use IgniteDataStreamer on executeBatch

[kcheng.mvp (Jira)]

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

kcheng.mvp commented on IGNITE-11721:
-

[~antkr] Can you supply a reproducer for this ticket? I would like to 
investigate this issue. thanks.

> IgniteJdbcDriver with streaming enabled doesn't use IgniteDataStreamer on 
> executeBatch
> --
>
> Key: IGNITE-11721
> URL: https://issues.apache.org/jira/browse/IGNITE-11721
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc, streaming
>Affects Versions: 2.7
>Reporter: Anton Kurbanov
>Priority: Minor
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-12088) Cache or template name should be validated before attempt to start

[kcheng.mvp (Jira)]

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

kcheng.mvp commented on IGNITE-12088:
-

[~Jokser] PR is read : https://github.com/apache/ignite/pull/6884. Can you help 
me do a code review?

> Cache or template name should be validated before attempt to start
> --
>
> Key: IGNITE-12088
> URL: https://issues.apache.org/jira/browse/IGNITE-12088
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Pavel Kovalenko
>Assignee: kcheng.mvp
>Priority: Critical
>  Labels: usability
> Fix For: 2.8
>
>
> If set too long cache name it can be a cause of impossibility to create work 
> directory for that cache:
> {noformat}
> [2019-08-20 
> 19:35:42,139][ERROR][exchange-worker-#172%node1%][IgniteTestResources] 
> Critical system error detected. Will be handled accordingly to configured 
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler 
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, 
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext 
> [type=CRITICAL_ERROR, err=class o.a.i.IgniteCheckedException: Failed to 
> initialize cache working directory (failed to create, make sure the work 
> folder has correct permissions): 
> /home/gridgain/projects/incubator-ignite/work/db/node1/cache-CacheConfiguration
>  [name=ccfg3staticTemplate*, grpName=null, memPlcName=null, 
> storeConcurrentLoadAllThreshold=5, rebalancePoolSize=1, 
> rebalanceTimeout=1, evictPlc=null, evictPlcFactory=null, 
> onheapCache=false, sqlOnheapCache=false, sqlOnheapCacheMaxSize=0, 
> evictFilter=null, eagerTtl=true, dfltLockTimeout=0, nearCfg=null, 
> writeSync=null, storeFactory=null, storeKeepBinary=false, loadPrevVal=false, 
> aff=null, cacheMode=PARTITIONED, atomicityMode=null, backups=6, 
> invalidate=false, tmLookupClsName=null, rebalanceMode=ASYNC, 
> rebalanceOrder=0, rebalanceBatchSize=524288, rebalanceBatchesPrefetchCnt=2, 
> maxConcurrentAsyncOps=500, sqlIdxMaxInlineSize=-1, writeBehindEnabled=false, 
> writeBehindFlushSize=10240, writeBehindFlushFreq=5000, 
> writeBehindFlushThreadCnt=1, writeBehindBatchSize=512, 
> writeBehindCoalescing=true, maxQryIterCnt=1024, affMapper=null, 
> rebalanceDelay=0, rebalanceThrottle=0, interceptor=null, 
> longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true, 
> nodeFilter=null, sqlSchema=null, sqlEscapeAll=false, cpOnRead=true, 
> topValidator=null, partLossPlc=IGNORE, qryParallelism=1, evtsDisabled=false, 
> encryptionEnabled=false, diskPageCompression=null, 
> diskPageCompressionLevel=null]0]]
> class org.apache.ignite.IgniteCheckedException: Failed to initialize cache 
> working directory (failed to create, make sure the work folder has correct 
> permissions): 
> /home/gridgain/projects/incubator-ignite/work/db/node1/cache-CacheConfiguration
>  [name=ccfg3staticTemplate*, grpName=null, memPlcName=null, 
> storeConcurrentLoadAllThreshold=5, rebalancePoolSize=1, 
> rebalanceTimeout=1, evictPlc=null, evictPlcFactory=null, 
> onheapCache=false, sqlOnheapCache=false, sqlOnheapCacheMaxSize=0, 
> evictFilter=null, eagerTtl=true, dfltLockTimeout=0, nearCfg=null, 
> writeSync=null, storeFactory=null, storeKeepBinary=false, loadPrevVal=false, 
> aff=null, cacheMode=PARTITIONED, atomicityMode=null, backups=6, 
> invalidate=false, tmLookupClsName=null, rebalanceMode=ASYNC, 
> rebalanceOrder=0, rebalanceBatchSize=524288, rebalanceBatchesPrefetchCnt=2, 
> maxConcurrentAsyncOps=500, sqlIdxMaxInlineSize=-1, writeBehindEnabled=false, 
> writeBehindFlushSize=10240, writeBehindFlushFreq=5000, 
> writeBehindFlushThreadCnt=1, writeBehindBatchSize=512, 
> writeBehindCoalescing=true, maxQryIterCnt=1024, affMapper=null, 
> rebalanceDelay=0, rebalanceThrottle=0, interceptor=null, 
> longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true, 
> nodeFilter=null, sqlSchema=null, sqlEscapeAll=false, cpOnRead=true, 
> topValidator=null, partLossPlc=IGNORE, qryParallelism=1, evtsDisabled=false, 
> encryptionEnabled=false, diskPageCompression=null, 
> diskPageCompressionLevel=null]0
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.checkAndInitCacheWorkDir(FilePageStoreManager.java:769)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.checkAndInitCacheWorkDir(FilePageStoreManager.java:748)
>   at 
> org.apache.ignite.internal.processors.cache.CachesRegistry.persistCacheConfigurations(CachesRegistry.java:289)
>   at 
> org.apache.ignite.internal.processors.cache.CachesRegistry.registerAllCachesAndGroups(CachesRegistry.java:264)
>   at 
> 

[jira] [Comment Edited] (IGNITE-12088) Cache or template name should be validated before attempt to start

[kcheng.mvp (Jira)]

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

kcheng.mvp edited comment on IGNITE-12088 at 9/18/19 5:25 PM:
--

[~Jokser] Right now I have reproduced this issue with a test, as the max file 
file length is OS specific. Can you advise an ideal max = cache name ?


was (Author: kcheng.mvp):
[~Jokser] Right now I have reproduce this issue with a test, as the max file 
file length is OS specific. Can you advise an ideal max = cache name ?

> Cache or template name should be validated before attempt to start
> --
>
> Key: IGNITE-12088
> URL: https://issues.apache.org/jira/browse/IGNITE-12088
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Pavel Kovalenko
>Assignee: kcheng.mvp
>Priority: Critical
>  Labels: usability
> Fix For: 2.8
>
>
> If set too long cache name it can be a cause of impossibility to create work 
> directory for that cache:
> {noformat}
> [2019-08-20 
> 19:35:42,139][ERROR][exchange-worker-#172%node1%][IgniteTestResources] 
> Critical system error detected. Will be handled accordingly to configured 
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler 
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, 
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext 
> [type=CRITICAL_ERROR, err=class o.a.i.IgniteCheckedException: Failed to 
> initialize cache working directory (failed to create, make sure the work 
> folder has correct permissions): 
> /home/gridgain/projects/incubator-ignite/work/db/node1/cache-CacheConfiguration
>  [name=ccfg3staticTemplate*, grpName=null, memPlcName=null, 
> storeConcurrentLoadAllThreshold=5, rebalancePoolSize=1, 
> rebalanceTimeout=1, evictPlc=null, evictPlcFactory=null, 
> onheapCache=false, sqlOnheapCache=false, sqlOnheapCacheMaxSize=0, 
> evictFilter=null, eagerTtl=true, dfltLockTimeout=0, nearCfg=null, 
> writeSync=null, storeFactory=null, storeKeepBinary=false, loadPrevVal=false, 
> aff=null, cacheMode=PARTITIONED, atomicityMode=null, backups=6, 
> invalidate=false, tmLookupClsName=null, rebalanceMode=ASYNC, 
> rebalanceOrder=0, rebalanceBatchSize=524288, rebalanceBatchesPrefetchCnt=2, 
> maxConcurrentAsyncOps=500, sqlIdxMaxInlineSize=-1, writeBehindEnabled=false, 
> writeBehindFlushSize=10240, writeBehindFlushFreq=5000, 
> writeBehindFlushThreadCnt=1, writeBehindBatchSize=512, 
> writeBehindCoalescing=true, maxQryIterCnt=1024, affMapper=null, 
> rebalanceDelay=0, rebalanceThrottle=0, interceptor=null, 
> longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true, 
> nodeFilter=null, sqlSchema=null, sqlEscapeAll=false, cpOnRead=true, 
> topValidator=null, partLossPlc=IGNORE, qryParallelism=1, evtsDisabled=false, 
> encryptionEnabled=false, diskPageCompression=null, 
> diskPageCompressionLevel=null]0]]
> class org.apache.ignite.IgniteCheckedException: Failed to initialize cache 
> working directory (failed to create, make sure the work folder has correct 
> permissions): 
> /home/gridgain/projects/incubator-ignite/work/db/node1/cache-CacheConfiguration
>  [name=ccfg3staticTemplate*, grpName=null, memPlcName=null, 
> storeConcurrentLoadAllThreshold=5, rebalancePoolSize=1, 
> rebalanceTimeout=1, evictPlc=null, evictPlcFactory=null, 
> onheapCache=false, sqlOnheapCache=false, sqlOnheapCacheMaxSize=0, 
> evictFilter=null, eagerTtl=true, dfltLockTimeout=0, nearCfg=null, 
> writeSync=null, storeFactory=null, storeKeepBinary=false, loadPrevVal=false, 
> aff=null, cacheMode=PARTITIONED, atomicityMode=null, backups=6, 
> invalidate=false, tmLookupClsName=null, rebalanceMode=ASYNC, 
> rebalanceOrder=0, rebalanceBatchSize=524288, rebalanceBatchesPrefetchCnt=2, 
> maxConcurrentAsyncOps=500, sqlIdxMaxInlineSize=-1, writeBehindEnabled=false, 
> writeBehindFlushSize=10240, writeBehindFlushFreq=5000, 
> writeBehindFlushThreadCnt=1, writeBehindBatchSize=512, 
> writeBehindCoalescing=true, maxQryIterCnt=1024, affMapper=null, 
> rebalanceDelay=0, rebalanceThrottle=0, interceptor=null, 
> longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true, 
> nodeFilter=null, sqlSchema=null, sqlEscapeAll=false, cpOnRead=true, 
> topValidator=null, partLossPlc=IGNORE, qryParallelism=1, evtsDisabled=false, 
> encryptionEnabled=false, diskPageCompression=null, 
> diskPageCompressionLevel=null]0
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.checkAndInitCacheWorkDir(FilePageStoreManager.java:769)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.checkAndInitCacheWorkDir(FilePageStoreManager.java:748)
>   at 
> 

[jira] [Comment Edited] (IGNITE-12088) Cache or template name should be validated before attempt to start

[kcheng.mvp (Jira)]

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

kcheng.mvp edited comment on IGNITE-12088 at 9/18/19 5:25 PM:
--

[~Jokser] Right now I have reproduced this issue with a test, as the max file 
file length is OS specific. Can you advise an ideal max length cache name ?


was (Author: kcheng.mvp):
[~Jokser] Right now I have reproduced this issue with a test, as the max file 
file length is OS specific. Can you advise an ideal max = cache name ?

> Cache or template name should be validated before attempt to start
> --
>
> Key: IGNITE-12088
> URL: https://issues.apache.org/jira/browse/IGNITE-12088
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Pavel Kovalenko
>Assignee: kcheng.mvp
>Priority: Critical
>  Labels: usability
> Fix For: 2.8
>
>
> If set too long cache name it can be a cause of impossibility to create work 
> directory for that cache:
> {noformat}
> [2019-08-20 
> 19:35:42,139][ERROR][exchange-worker-#172%node1%][IgniteTestResources] 
> Critical system error detected. Will be handled accordingly to configured 
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler 
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, 
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext 
> [type=CRITICAL_ERROR, err=class o.a.i.IgniteCheckedException: Failed to 
> initialize cache working directory (failed to create, make sure the work 
> folder has correct permissions): 
> /home/gridgain/projects/incubator-ignite/work/db/node1/cache-CacheConfiguration
>  [name=ccfg3staticTemplate*, grpName=null, memPlcName=null, 
> storeConcurrentLoadAllThreshold=5, rebalancePoolSize=1, 
> rebalanceTimeout=1, evictPlc=null, evictPlcFactory=null, 
> onheapCache=false, sqlOnheapCache=false, sqlOnheapCacheMaxSize=0, 
> evictFilter=null, eagerTtl=true, dfltLockTimeout=0, nearCfg=null, 
> writeSync=null, storeFactory=null, storeKeepBinary=false, loadPrevVal=false, 
> aff=null, cacheMode=PARTITIONED, atomicityMode=null, backups=6, 
> invalidate=false, tmLookupClsName=null, rebalanceMode=ASYNC, 
> rebalanceOrder=0, rebalanceBatchSize=524288, rebalanceBatchesPrefetchCnt=2, 
> maxConcurrentAsyncOps=500, sqlIdxMaxInlineSize=-1, writeBehindEnabled=false, 
> writeBehindFlushSize=10240, writeBehindFlushFreq=5000, 
> writeBehindFlushThreadCnt=1, writeBehindBatchSize=512, 
> writeBehindCoalescing=true, maxQryIterCnt=1024, affMapper=null, 
> rebalanceDelay=0, rebalanceThrottle=0, interceptor=null, 
> longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true, 
> nodeFilter=null, sqlSchema=null, sqlEscapeAll=false, cpOnRead=true, 
> topValidator=null, partLossPlc=IGNORE, qryParallelism=1, evtsDisabled=false, 
> encryptionEnabled=false, diskPageCompression=null, 
> diskPageCompressionLevel=null]0]]
> class org.apache.ignite.IgniteCheckedException: Failed to initialize cache 
> working directory (failed to create, make sure the work folder has correct 
> permissions): 
> /home/gridgain/projects/incubator-ignite/work/db/node1/cache-CacheConfiguration
>  [name=ccfg3staticTemplate*, grpName=null, memPlcName=null, 
> storeConcurrentLoadAllThreshold=5, rebalancePoolSize=1, 
> rebalanceTimeout=1, evictPlc=null, evictPlcFactory=null, 
> onheapCache=false, sqlOnheapCache=false, sqlOnheapCacheMaxSize=0, 
> evictFilter=null, eagerTtl=true, dfltLockTimeout=0, nearCfg=null, 
> writeSync=null, storeFactory=null, storeKeepBinary=false, loadPrevVal=false, 
> aff=null, cacheMode=PARTITIONED, atomicityMode=null, backups=6, 
> invalidate=false, tmLookupClsName=null, rebalanceMode=ASYNC, 
> rebalanceOrder=0, rebalanceBatchSize=524288, rebalanceBatchesPrefetchCnt=2, 
> maxConcurrentAsyncOps=500, sqlIdxMaxInlineSize=-1, writeBehindEnabled=false, 
> writeBehindFlushSize=10240, writeBehindFlushFreq=5000, 
> writeBehindFlushThreadCnt=1, writeBehindBatchSize=512, 
> writeBehindCoalescing=true, maxQryIterCnt=1024, affMapper=null, 
> rebalanceDelay=0, rebalanceThrottle=0, interceptor=null, 
> longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true, 
> nodeFilter=null, sqlSchema=null, sqlEscapeAll=false, cpOnRead=true, 
> topValidator=null, partLossPlc=IGNORE, qryParallelism=1, evtsDisabled=false, 
> encryptionEnabled=false, diskPageCompression=null, 
> diskPageCompressionLevel=null]0
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.checkAndInitCacheWorkDir(FilePageStoreManager.java:769)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.checkAndInitCacheWorkDir(FilePageStoreManager.java:748)
>   at 
> 

[jira] [Commented] (IGNITE-12088) Cache or template name should be validated before attempt to start

[kcheng.mvp (Jira)]

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

kcheng.mvp commented on IGNITE-12088:
-

[~Jokser] Right now I have reproduce this issue with a test, as the max file 
file length is OS specific. Can you advise an ideal max = cache name ?

> Cache or template name should be validated before attempt to start
> --
>
> Key: IGNITE-12088
> URL: https://issues.apache.org/jira/browse/IGNITE-12088
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Pavel Kovalenko
>Assignee: kcheng.mvp
>Priority: Critical
>  Labels: usability
> Fix For: 2.8
>
>
> If set too long cache name it can be a cause of impossibility to create work 
> directory for that cache:
> {noformat}
> [2019-08-20 
> 19:35:42,139][ERROR][exchange-worker-#172%node1%][IgniteTestResources] 
> Critical system error detected. Will be handled accordingly to configured 
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler 
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, 
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext 
> [type=CRITICAL_ERROR, err=class o.a.i.IgniteCheckedException: Failed to 
> initialize cache working directory (failed to create, make sure the work 
> folder has correct permissions): 
> /home/gridgain/projects/incubator-ignite/work/db/node1/cache-CacheConfiguration
>  [name=ccfg3staticTemplate*, grpName=null, memPlcName=null, 
> storeConcurrentLoadAllThreshold=5, rebalancePoolSize=1, 
> rebalanceTimeout=1, evictPlc=null, evictPlcFactory=null, 
> onheapCache=false, sqlOnheapCache=false, sqlOnheapCacheMaxSize=0, 
> evictFilter=null, eagerTtl=true, dfltLockTimeout=0, nearCfg=null, 
> writeSync=null, storeFactory=null, storeKeepBinary=false, loadPrevVal=false, 
> aff=null, cacheMode=PARTITIONED, atomicityMode=null, backups=6, 
> invalidate=false, tmLookupClsName=null, rebalanceMode=ASYNC, 
> rebalanceOrder=0, rebalanceBatchSize=524288, rebalanceBatchesPrefetchCnt=2, 
> maxConcurrentAsyncOps=500, sqlIdxMaxInlineSize=-1, writeBehindEnabled=false, 
> writeBehindFlushSize=10240, writeBehindFlushFreq=5000, 
> writeBehindFlushThreadCnt=1, writeBehindBatchSize=512, 
> writeBehindCoalescing=true, maxQryIterCnt=1024, affMapper=null, 
> rebalanceDelay=0, rebalanceThrottle=0, interceptor=null, 
> longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true, 
> nodeFilter=null, sqlSchema=null, sqlEscapeAll=false, cpOnRead=true, 
> topValidator=null, partLossPlc=IGNORE, qryParallelism=1, evtsDisabled=false, 
> encryptionEnabled=false, diskPageCompression=null, 
> diskPageCompressionLevel=null]0]]
> class org.apache.ignite.IgniteCheckedException: Failed to initialize cache 
> working directory (failed to create, make sure the work folder has correct 
> permissions): 
> /home/gridgain/projects/incubator-ignite/work/db/node1/cache-CacheConfiguration
>  [name=ccfg3staticTemplate*, grpName=null, memPlcName=null, 
> storeConcurrentLoadAllThreshold=5, rebalancePoolSize=1, 
> rebalanceTimeout=1, evictPlc=null, evictPlcFactory=null, 
> onheapCache=false, sqlOnheapCache=false, sqlOnheapCacheMaxSize=0, 
> evictFilter=null, eagerTtl=true, dfltLockTimeout=0, nearCfg=null, 
> writeSync=null, storeFactory=null, storeKeepBinary=false, loadPrevVal=false, 
> aff=null, cacheMode=PARTITIONED, atomicityMode=null, backups=6, 
> invalidate=false, tmLookupClsName=null, rebalanceMode=ASYNC, 
> rebalanceOrder=0, rebalanceBatchSize=524288, rebalanceBatchesPrefetchCnt=2, 
> maxConcurrentAsyncOps=500, sqlIdxMaxInlineSize=-1, writeBehindEnabled=false, 
> writeBehindFlushSize=10240, writeBehindFlushFreq=5000, 
> writeBehindFlushThreadCnt=1, writeBehindBatchSize=512, 
> writeBehindCoalescing=true, maxQryIterCnt=1024, affMapper=null, 
> rebalanceDelay=0, rebalanceThrottle=0, interceptor=null, 
> longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true, 
> nodeFilter=null, sqlSchema=null, sqlEscapeAll=false, cpOnRead=true, 
> topValidator=null, partLossPlc=IGNORE, qryParallelism=1, evtsDisabled=false, 
> encryptionEnabled=false, diskPageCompression=null, 
> diskPageCompressionLevel=null]0
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.checkAndInitCacheWorkDir(FilePageStoreManager.java:769)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.checkAndInitCacheWorkDir(FilePageStoreManager.java:748)
>   at 
> org.apache.ignite.internal.processors.cache.CachesRegistry.persistCacheConfigurations(CachesRegistry.java:289)
>   at 
> org.apache.ignite.internal.processors.cache.CachesRegistry.registerAllCachesAndGroups(CachesRegistry.java:264)
>   at 
> 

[jira] [Assigned] (IGNITE-12088) Cache or template name should be validated before attempt to start

[kcheng.mvp (Jira)]

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

kcheng.mvp reassigned IGNITE-12088:
---

Assignee: kcheng.mvp

> Cache or template name should be validated before attempt to start
> --
>
> Key: IGNITE-12088
> URL: https://issues.apache.org/jira/browse/IGNITE-12088
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Pavel Kovalenko
>Assignee: kcheng.mvp
>Priority: Critical
>  Labels: usability
> Fix For: 2.8
>
>
> If set too long cache name it can be a cause of impossibility to create work 
> directory for that cache:
> {noformat}
> [2019-08-20 
> 19:35:42,139][ERROR][exchange-worker-#172%node1%][IgniteTestResources] 
> Critical system error detected. Will be handled accordingly to configured 
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler 
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, 
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext 
> [type=CRITICAL_ERROR, err=class o.a.i.IgniteCheckedException: Failed to 
> initialize cache working directory (failed to create, make sure the work 
> folder has correct permissions): 
> /home/gridgain/projects/incubator-ignite/work/db/node1/cache-CacheConfiguration
>  [name=ccfg3staticTemplate*, grpName=null, memPlcName=null, 
> storeConcurrentLoadAllThreshold=5, rebalancePoolSize=1, 
> rebalanceTimeout=1, evictPlc=null, evictPlcFactory=null, 
> onheapCache=false, sqlOnheapCache=false, sqlOnheapCacheMaxSize=0, 
> evictFilter=null, eagerTtl=true, dfltLockTimeout=0, nearCfg=null, 
> writeSync=null, storeFactory=null, storeKeepBinary=false, loadPrevVal=false, 
> aff=null, cacheMode=PARTITIONED, atomicityMode=null, backups=6, 
> invalidate=false, tmLookupClsName=null, rebalanceMode=ASYNC, 
> rebalanceOrder=0, rebalanceBatchSize=524288, rebalanceBatchesPrefetchCnt=2, 
> maxConcurrentAsyncOps=500, sqlIdxMaxInlineSize=-1, writeBehindEnabled=false, 
> writeBehindFlushSize=10240, writeBehindFlushFreq=5000, 
> writeBehindFlushThreadCnt=1, writeBehindBatchSize=512, 
> writeBehindCoalescing=true, maxQryIterCnt=1024, affMapper=null, 
> rebalanceDelay=0, rebalanceThrottle=0, interceptor=null, 
> longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true, 
> nodeFilter=null, sqlSchema=null, sqlEscapeAll=false, cpOnRead=true, 
> topValidator=null, partLossPlc=IGNORE, qryParallelism=1, evtsDisabled=false, 
> encryptionEnabled=false, diskPageCompression=null, 
> diskPageCompressionLevel=null]0]]
> class org.apache.ignite.IgniteCheckedException: Failed to initialize cache 
> working directory (failed to create, make sure the work folder has correct 
> permissions): 
> /home/gridgain/projects/incubator-ignite/work/db/node1/cache-CacheConfiguration
>  [name=ccfg3staticTemplate*, grpName=null, memPlcName=null, 
> storeConcurrentLoadAllThreshold=5, rebalancePoolSize=1, 
> rebalanceTimeout=1, evictPlc=null, evictPlcFactory=null, 
> onheapCache=false, sqlOnheapCache=false, sqlOnheapCacheMaxSize=0, 
> evictFilter=null, eagerTtl=true, dfltLockTimeout=0, nearCfg=null, 
> writeSync=null, storeFactory=null, storeKeepBinary=false, loadPrevVal=false, 
> aff=null, cacheMode=PARTITIONED, atomicityMode=null, backups=6, 
> invalidate=false, tmLookupClsName=null, rebalanceMode=ASYNC, 
> rebalanceOrder=0, rebalanceBatchSize=524288, rebalanceBatchesPrefetchCnt=2, 
> maxConcurrentAsyncOps=500, sqlIdxMaxInlineSize=-1, writeBehindEnabled=false, 
> writeBehindFlushSize=10240, writeBehindFlushFreq=5000, 
> writeBehindFlushThreadCnt=1, writeBehindBatchSize=512, 
> writeBehindCoalescing=true, maxQryIterCnt=1024, affMapper=null, 
> rebalanceDelay=0, rebalanceThrottle=0, interceptor=null, 
> longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true, 
> nodeFilter=null, sqlSchema=null, sqlEscapeAll=false, cpOnRead=true, 
> topValidator=null, partLossPlc=IGNORE, qryParallelism=1, evtsDisabled=false, 
> encryptionEnabled=false, diskPageCompression=null, 
> diskPageCompressionLevel=null]0
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.checkAndInitCacheWorkDir(FilePageStoreManager.java:769)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.checkAndInitCacheWorkDir(FilePageStoreManager.java:748)
>   at 
> org.apache.ignite.internal.processors.cache.CachesRegistry.persistCacheConfigurations(CachesRegistry.java:289)
>   at 
> org.apache.ignite.internal.processors.cache.CachesRegistry.registerAllCachesAndGroups(CachesRegistry.java:264)
>   at 
> org.apache.ignite.internal.processors.cache.CachesRegistry.update(CachesRegistry.java:202)
>   at 
> 

[jira] [Commented] (IGNITE-9071) Failed to reinitialize local partitions on client node

[kcheng.mvp (Jira)]

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

kcheng.mvp commented on IGNITE-9071:


[~guseinov] I can not reproduce this issue on branch 2.6.0, 2.7.5 and 
2.8.0-SNAPSHOT.
here is the sample code. 
https://github.com/kcmvp/ignite-sandbox/tree/master/IGNITE-9071
seems that we can close this ticket.

> Failed to reinitialize local partitions on client node
> --
>
> Key: IGNITE-9071
> URL: https://issues.apache.org/jira/browse/IGNITE-9071
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.6
>Reporter: Roman Guseinov
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
> Attachments: Reproducer.java
>
>
> "Failed to reinitialize local partitions" message can confuse users when it 
> appears in the client node logs:
>  
> {code}
> [2018-07-25 
> 12:15:58,717][ERROR][exchange-worker-#80%client-node%][GridDhtPartitionsExchangeFuture]
>  Failed to reinitialize local partitions (rebalancing will be stopped): 
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=2, 
> minorTopVer=0], discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode 
> [id=aa407026-3050-4dac-899d-cec951b3c9e5, addrs=ArrayList [10.0.75.1, 
> 10.8.10.46, 127.0.0.1, 192.168.1.51, 192.168.192.1], sockAddrs=HashSet 
> [/10.0.75.1:0, /127.0.0.1:0, /192.168.192.1:0, /192.168.1.51:0, 
> /10.8.10.46:0], discPort=0, order=2, intOrder=0, 
> lastExchangeTime=1532492155372, loc=true, ver=2.7.0#19700101-sha1:, 
> isClient=true], topVer=2, nodeId8=aa407026, msg=null, type=NODE_JOINED, 
> tstamp=1532492158693], nodeId=aa407026, evt=NODE_JOINED]
> java.lang.OutOfMemoryError
>   at sun.misc.Unsafe.allocateMemory(Native Method)
>   at 
> org.apache.ignite.internal.util.GridUnsafe.allocateMemory(GridUnsafe.java:1090)
>   at 
> org.apache.ignite.internal.mem.unsafe.UnsafeMemoryProvider.nextRegion(UnsafeMemoryProvider.java:90)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager$2.nextRegion(IgniteCacheDatabaseSharedManager.java:1026)
>   at 
> org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.addSegment(PageMemoryNoStoreImpl.java:628)
> {code}
> Reproducer is attached.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (IGNITE-9071) Failed to reinitialize local partitions on client node

[kcheng.mvp (Jira)]

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

kcheng.mvp reassigned IGNITE-9071:
--

Assignee: kcheng.mvp

> Failed to reinitialize local partitions on client node
> --
>
> Key: IGNITE-9071
> URL: https://issues.apache.org/jira/browse/IGNITE-9071
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.6
>Reporter: Roman Guseinov
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
> Attachments: Reproducer.java
>
>
> "Failed to reinitialize local partitions" message can confuse users when it 
> appears in the client node logs:
>  
> {code}
> [2018-07-25 
> 12:15:58,717][ERROR][exchange-worker-#80%client-node%][GridDhtPartitionsExchangeFuture]
>  Failed to reinitialize local partitions (rebalancing will be stopped): 
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=2, 
> minorTopVer=0], discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode 
> [id=aa407026-3050-4dac-899d-cec951b3c9e5, addrs=ArrayList [10.0.75.1, 
> 10.8.10.46, 127.0.0.1, 192.168.1.51, 192.168.192.1], sockAddrs=HashSet 
> [/10.0.75.1:0, /127.0.0.1:0, /192.168.192.1:0, /192.168.1.51:0, 
> /10.8.10.46:0], discPort=0, order=2, intOrder=0, 
> lastExchangeTime=1532492155372, loc=true, ver=2.7.0#19700101-sha1:, 
> isClient=true], topVer=2, nodeId8=aa407026, msg=null, type=NODE_JOINED, 
> tstamp=1532492158693], nodeId=aa407026, evt=NODE_JOINED]
> java.lang.OutOfMemoryError
>   at sun.misc.Unsafe.allocateMemory(Native Method)
>   at 
> org.apache.ignite.internal.util.GridUnsafe.allocateMemory(GridUnsafe.java:1090)
>   at 
> org.apache.ignite.internal.mem.unsafe.UnsafeMemoryProvider.nextRegion(UnsafeMemoryProvider.java:90)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager$2.nextRegion(IgniteCacheDatabaseSharedManager.java:1026)
>   at 
> org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.addSegment(PageMemoryNoStoreImpl.java:628)
> {code}
> Reproducer is attached.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Commented] (IGNITE-11976) @SpringResource is silently ignored if no Spring context is provided

[kcheng.mvp (Jira)]

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

kcheng.mvp commented on IGNITE-11976:
-

TeamCity is green : 
https://ci.ignite.apache.org/viewLog.html?buildId=4599188=IgniteTests24Java8_BuildApacheIgnite=buildResultsDiv_IgniteTests24Java8=pull%2F6868%2Fhead

> @SpringResource is silently ignored if no Spring context is provided
> 
>
> Key: IGNITE-11976
> URL: https://issues.apache.org/jira/browse/IGNITE-11976
> Project: Ignite
>  Issue Type: Improvement
>  Components: spring
>Affects Versions: 2.7
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Major
>  Labels: newbie
>
> @SpringResource annotation is silently ignored and the annotated field is 
> null if Spring context.
> For @SpringResource to work the node needs to be started with 
> IgniteSpring::start instead of Ignition::start, but the user may not know 
> that.
> Need to add a warning for this.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Commented] (IGNITE-11423) Multiple configurations to SpringCacheManager

[kcheng.mvp (Jira)]

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

kcheng.mvp commented on IGNITE-11423:
-

[~usingsky] May I know what's the status of this jira? I noticed there is a PR 
but there is no Assignee

> Multiple configurations to SpringCacheManager
> -
>
> Key: IGNITE-11423
> URL: https://issues.apache.org/jira/browse/IGNITE-11423
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache, spring
>Reporter: Jinil Lee
>Priority: Minor
>  Labels: newbie, pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> I'm using SpringCacheManager for my project.
> I want to apply each cache-specific configuration (eg expiry policy),
> but only one configuration applies when I create the cachemanager.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Commented] (IGNITE-11868) GridClient#data() should be deprecated/removed.

[kcheng.mvp (Jira)]

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

kcheng.mvp commented on IGNITE-11868:
-

[~slava.koptilin] I noticed there are lots of tests use this method. Seems we 
can not simply remove this method, so can we just annotate it as deprecated?

> GridClient#data() should be deprecated/removed.
> ---
>
> Key: IGNITE-11868
> URL: https://issues.apache.org/jira/browse/IGNITE-11868
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Vyacheslav Koptilin
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
>
> It seems that {{GridClient#data()}} does not make sense after IGNITE-3488 and 
> therefore it can be removed.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Assigned] (IGNITE-11868) GridClient#data() should be deprecated/removed.

[kcheng.mvp (Jira)]

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

kcheng.mvp reassigned IGNITE-11868:
---

Assignee: kcheng.mvp

> GridClient#data() should be deprecated/removed.
> ---
>
> Key: IGNITE-11868
> URL: https://issues.apache.org/jira/browse/IGNITE-11868
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Vyacheslav Koptilin
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
>
> It seems that {{GridClient#data()}} does not make sense after IGNITE-3488 and 
> therefore it can be removed.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Assigned] (IGNITE-11976) @SpringResource is silently ignored if no Spring context is provided

[kcheng.mvp (Jira)]

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

kcheng.mvp reassigned IGNITE-11976:
---

Assignee: kcheng.mvp

> @SpringResource is silently ignored if no Spring context is provided
> 
>
> Key: IGNITE-11976
> URL: https://issues.apache.org/jira/browse/IGNITE-11976
> Project: Ignite
>  Issue Type: Improvement
>  Components: spring
>Affects Versions: 2.7
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Major
>  Labels: newbie
>
> @SpringResource annotation is silently ignored and the annotated field is 
> null if Spring context.
> For @SpringResource to work the node needs to be started with 
> IgniteSpring::start instead of Ignition::start, but the user may not know 
> that.
> Need to add a warning for this.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Commented] (IGNITE-5780) DDL: support custom schema creation

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-5780:


[~vozerov] I notice this issue closed. May I know this feature will be added to 
v2.8 or not? thank you very much!

> DDL: support custom schema creation
> ---
>
> Key: IGNITE-5780
> URL: https://issues.apache.org/jira/browse/IGNITE-5780
> Project: Ignite
>  Issue Type: New Feature
>  Components: sql
>Reporter: Denis Magda
>Priority: Major
>
> Presently if the one creates a SQL table using DDL "CREATE TABLE" command 
> then the table will be bound to the default "PUBLIC" schema. All the tables 
> created this way will fall under this rule.
> Ignite has to support the following:
> * custom schema creation with "CREATE SCHEMA" command.
> * provide an ability to assign any table created with "CREATE TABLE" name to 
> a custom schema.
> * schema and table configured this way has to survive restarts meaning that 
> Ignite Persistent Store has to preserve the configuration parameters.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-11685) Java thin client: Handle multiple async requests in parallel

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-11685:
-

[~alex_pl] If use async in the thin client. then how does the previous 
requester get the response/result? As the tcp socket is currently used by 
another thread.



> Java thin client: Handle multiple async requests in parallel
> 
>
> Key: IGNITE-11685
> URL: https://issues.apache.org/jira/browse/IGNITE-11685
> Project: Ignite
>  Issue Type: Improvement
>  Components: thin client
>Reporter: Aleksey Plekhanov
>Priority: Major
>  Labels: iep-34
>
> In the current implementation {{ReliableChannel}} uses an exclusive lock to 
> send a request and waits for response synchronously. In this implementation, 
> there are no benefits of using multiple threads. To improve throughput and 
> latency we can implement async request/response processing on the client 
> side, since the server side is already async.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-11817) org.apache.ignite.client.ClientCache#removeAll() and org.apache.ignite.client.ClientCache#clear missed Java Doc

[kcheng.mvp (JIRA)]

kcheng.mvp created IGNITE-11817:
---

 Summary: org.apache.ignite.client.ClientCache#removeAll() and 
org.apache.ignite.client.ClientCache#clear missed Java Doc
 Key: IGNITE-11817
 URL: https://issues.apache.org/jira/browse/IGNITE-11817
 Project: Ignite
  Issue Type: Improvement
  Components: thin client
Affects Versions: 2.7
Reporter: kcheng.mvp
Assignee: kcheng.mvp
 Fix For: 2.8


Use would be confused about the these api, need to address the difference in 
the java doc.
please see the mail list
http://apache-ignite-users.70518.x6.nabble.com/What-s-the-difference-between-ClientCache-removeAll-and-ClientCache-clear-td28002.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-5780) DDL: support custom schema creation

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-5780:


That's really what I want! Hope it will be released in 2.8. I have used v2.7 in 
production for small system. so far so good. I would like to use ignite in 
another system. The only thing makes me uncomfortable is that I count not keep 
the system module align with database schema. As with business goes on, it 
obviously  that there are some new tables added.
anyway it's very happy see there is a jira tack this.

> DDL: support custom schema creation
> ---
>
> Key: IGNITE-5780
> URL: https://issues.apache.org/jira/browse/IGNITE-5780
> Project: Ignite
>  Issue Type: New Feature
>  Components: sql
>Reporter: Denis Magda
>Priority: Major
>
> Presently if the one creates a SQL table using DDL "CREATE TABLE" command 
> then the table will be bound to the default "PUBLIC" schema. All the tables 
> created this way will fall under this rule.
> Ignite has to support the following:
> * custom schema creation with "CREATE SCHEMA" command.
> * provide an ability to assign any table created with "CREATE TABLE" name to 
> a custom schema.
> * schema and table configured this way has to survive restarts meaning that 
> Ignite Persistent Store has to preserve the configuration parameters.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-10612) java.lang.IllegalAccessError: tried to access field org.h2.util.LocalDateTimeUtils.LOCAL_DATE from class org.apache.ignite.internal.processors.query.h2.H2DatabaseType

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-10612:
-

Notice there is a change in 2.7 
https://issues.apache.org/jira/browse/IGNITE-9574

After change all java.util.Date to java.sql.Timestamp then everything goes well

> java.lang.IllegalAccessError: tried to access field 
> org.h2.util.LocalDateTimeUtils.LOCAL_DATE from class 
> org.apache.ignite.internal.processors.query.h2.H2DatabaseType
> --
>
> Key: IGNITE-10612
> URL: https://issues.apache.org/jira/browse/IGNITE-10612
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.7
>Reporter: kcheng.mvp
>Priority: Major
>
> below is my environment
> ignite 2.7
>  
> There are about 82 unit test for my system. it works fine in ignite 2.7
>  
> when I switch to 2.7 I got below error for my unit test.
>  
>  
>  
> java.lang.IllegalAccessError: tried to access field 
> org.h2.util.LocalDateTimeUtils.LOCAL_DATE from class 
> org.apache.ignite.internal.processors.query.h2.H2DatabaseType
>  at 
> org.apache.ignite.internal.processors.query.h2.H2DatabaseType.fromClass(H2DatabaseType.java:147)
>  at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.dbTypeFromClass(IgniteH2Indexing.java:2972)
>  at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createTable(IgniteH2Indexing.java:2869)
>  at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:2809)
>  at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.registerCache0(GridQueryProcessor.java:1633)
>  at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:805)
>  at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:866)
>  at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1330)
>  at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:2165)
>  at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processCacheStartRequests(CacheAffinitySharedManager.java:898)
>  at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:798)
>  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:1231)
>  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:738)
>  at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2667)
>  at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2539)
>  at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
>  at java.lang.Thread.run(Thread.java:748)
> 2018-12-10 11:47:21 INFO o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture - 
> Finish exchange future [startVer=AffinityTopologyVersion [topVer=1, 
> minorTopVer=2], resVer=null, err=java.lang.IllegalAccessError: tried to 
> access field org.h2.util.LocalDateTimeUtils.LOCAL_DATE from class 
> org.apache.ignite.internal.processors.query.h2.H2DatabaseType]
> 2018-12-10 11:47:21 ERROR - Critical system error detected. Will be handled 
> accordingly to configured handler [hnd=StopNodeOrHaltFailureHandler 
> [tryStop=false, timeout=0, super=AbstractFailureHandler 
> [ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext 
> [type=SYSTEM_WORKER_TERMINATION, err=java.lang.AssertionError: Missing user 
> future for cache: GIFT]]
> java.lang.AssertionError: Missing user future for cache: GIFT
>  at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.rebuildIndexesIfNeeded(GridCacheDatabaseSharedManager.java:1364)
>  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:2151)
>  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:138)
>  at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
>  at 
> 

[jira] [Created] (IGNITE-10612) java.lang.IllegalAccessError: tried to access field org.h2.util.LocalDateTimeUtils.LOCAL_DATE from class org.apache.ignite.internal.processors.query.h2.H2DatabaseType

[kcheng.mvp (JIRA)]

kcheng.mvp created IGNITE-10612:
---

 Summary: java.lang.IllegalAccessError: tried to access field 
org.h2.util.LocalDateTimeUtils.LOCAL_DATE from class 
org.apache.ignite.internal.processors.query.h2.H2DatabaseType
 Key: IGNITE-10612
 URL: https://issues.apache.org/jira/browse/IGNITE-10612
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.7
Reporter: kcheng.mvp


below is my environment

ignite 2.7

 

There are about 82 unit test for my system. it works fine in ignite 2.7

 

when I switch to 2.7 I got below error for my unit test.

 

 

 

java.lang.IllegalAccessError: tried to access field 
org.h2.util.LocalDateTimeUtils.LOCAL_DATE from class 
org.apache.ignite.internal.processors.query.h2.H2DatabaseType
 at 
org.apache.ignite.internal.processors.query.h2.H2DatabaseType.fromClass(H2DatabaseType.java:147)
 at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.dbTypeFromClass(IgniteH2Indexing.java:2972)
 at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createTable(IgniteH2Indexing.java:2869)
 at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:2809)
 at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.registerCache0(GridQueryProcessor.java:1633)
 at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:805)
 at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:866)
 at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1330)
 at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:2165)
 at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processCacheStartRequests(CacheAffinitySharedManager.java:898)
 at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:798)
 at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:1231)
 at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:738)
 at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2667)
 at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2539)
 at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
 at java.lang.Thread.run(Thread.java:748)
2018-12-10 11:47:21 INFO o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture - 
Finish exchange future [startVer=AffinityTopologyVersion [topVer=1, 
minorTopVer=2], resVer=null, err=java.lang.IllegalAccessError: tried to access 
field org.h2.util.LocalDateTimeUtils.LOCAL_DATE from class 
org.apache.ignite.internal.processors.query.h2.H2DatabaseType]
2018-12-10 11:47:21 ERROR - Critical system error detected. Will be handled 
accordingly to configured handler [hnd=StopNodeOrHaltFailureHandler 
[tryStop=false, timeout=0, super=AbstractFailureHandler 
[ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext 
[type=SYSTEM_WORKER_TERMINATION, err=java.lang.AssertionError: Missing user 
future for cache: GIFT]]
java.lang.AssertionError: Missing user future for cache: GIFT
 at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.rebuildIndexesIfNeeded(GridCacheDatabaseSharedManager.java:1364)
 at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:2151)
 at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:138)
 at 
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
 at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:860)
 at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2667)
 at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2539)
 at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
 at java.lang.Thread.run(Thread.java:748)

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-10501) javax.cache.CacheException: Failed to execute map query on the node: fddb7640-dc6b-467b-989f-7ea799710a52, class java.lang.ArrayIndexOutOfBoundsException:null

[kcheng.mvp (JIRA)]

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

kcheng.mvp updated IGNITE-10501:

Description: 
Runs into this error,  with below sql

 

 
{code:java}
select u._key, u.nickName, u.photoUrl from USER_BASIC.user u, table(uid bigint 
= ?) tuids where u._key = tuids.uid{code}
 

 
{code:java}
query = new SqlFieldsQuery(GET_USER_BASIC_INFO);
query.setArgs(createdByList.stream().toArray(Long[]::new));{code}
 

 

when *createdByList* is an empty list, then above sql will run into error.

 

here is the full stack

 
{code:java}
Caused by: javax.cache.CacheException: Failed to execute map query on the node: 
fddb7640-dc6b-467b-989f-7ea799710a52, class 
java.lang.ArrayIndexOutOfBoundsException:null
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:274)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:264)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:243)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$2.onMessage(GridReduceQueryExecutor.java:187)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:2333)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624){code}
 

 

 

 

  was:
Runs into this error,  with below sql

select u._key, u.nickName, u.photoUrl from USER_BASIC.user u, table(uid bigint 
= ?) tuids where u._key = tuids.uid

 

 

query = new SqlFieldsQuery(GET_USER_BASIC_INFO);
query.setArgs(createdByList.stream().toArray(Long[]::new));

 

when *createdByList* is an empty list, then above sql will run into error.

 

here is the full stack

 

 

Caused by: javax.cache.CacheException: Failed to execute map query on the node: 
fddb7640-dc6b-467b-989f-7ea799710a52, class 
java.lang.ArrayIndexOutOfBoundsException:null
 at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:274)
 at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:264)
 at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:243)
 at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$2.onMessage(GridReduceQueryExecutor.java:187)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:2333)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
 at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

 

 

 


> javax.cache.CacheException: Failed to execute map query on the node: 
> fddb7640-dc6b-467b-989f-7ea799710a52, class 
> java.lang.ArrayIndexOutOfBoundsException:null
> --
>
> Key: IGNITE-10501
> URL: https://issues.apache.org/jira/browse/IGNITE-10501
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.6
>Reporter: kcheng.mvp
>Priority: Major
>
> Runs into this error,  with below sql
>  
>  
> {code:java}
> select u._key, u.nickName, u.photoUrl from USER_BASIC.user u, table(uid 
> bigint = ?) tuids where u._key = tuids.uid{code}
>  
>  
> {code:java}
> query = new SqlFieldsQuery(GET_USER_BASIC_INFO);
> query.setArgs(createdByList.stream().toArray(Long[]::new));{code}
>  
>  
> when *createdByList* is an empty list, then above sql will run into error.
>  
> here is the full stack
>  
> {code:java}
> Caused by: javax.cache.CacheException: Failed to execute map query 

[jira] [Created] (IGNITE-10501) javax.cache.CacheException: Failed to execute map query on the node: fddb7640-dc6b-467b-989f-7ea799710a52, class java.lang.ArrayIndexOutOfBoundsException:null

[kcheng.mvp (JIRA)]

kcheng.mvp created IGNITE-10501:
---

 Summary: javax.cache.CacheException: Failed to execute map query 
on the node: fddb7640-dc6b-467b-989f-7ea799710a52, class 
java.lang.ArrayIndexOutOfBoundsException:null
 Key: IGNITE-10501
 URL: https://issues.apache.org/jira/browse/IGNITE-10501
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.6
Reporter: kcheng.mvp


Runs into this error,  with below sql

select u._key, u.nickName, u.photoUrl from USER_BASIC.user u, table(uid bigint 
= ?) tuids where u._key = tuids.uid

 

 

query = new SqlFieldsQuery(GET_USER_BASIC_INFO);
query.setArgs(createdByList.stream().toArray(Long[]::new));

 

when *createdByList* is an empty list, then above sql will run into error.

 

here is the full stack

 

 

Caused by: javax.cache.CacheException: Failed to execute map query on the node: 
fddb7640-dc6b-467b-989f-7ea799710a52, class 
java.lang.ArrayIndexOutOfBoundsException:null
 at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:274)
 at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:264)
 at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:243)
 at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$2.onMessage(GridReduceQueryExecutor.java:187)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:2333)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
 at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

 

 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6145) JDBC thin: support connection pooling

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-6145:


right now IGNITE-6140  not sure 2.7 support connection pool or not?

> JDBC thin: support connection pooling
> -
>
> Key: IGNITE-6145
> URL: https://issues.apache.org/jira/browse/IGNITE-6145
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc
>Affects Versions: 2.1
>Reporter: Taras Ledkov
>Priority: Major
>
> W have to support connection pool to JDBC compliance.
> At the very least we must test ourselves with well-known pooling providers 
> (DBCP, c3p0). 
> This is blocked by IGNITE-6140



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-6145) JDBC thin: support connection pooling

[kcheng.mvp (JIRA)]

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

kcheng.mvp edited comment on IGNITE-6145 at 11/8/18 12:03 PM:
--

right now IGNITE-6140  fix in  2.7, not sure the coming release support 
connection pool or not?


was (Author: kcheng.mvp):
right now IGNITE-6140  not sure 2.7 support connection pool or not?

> JDBC thin: support connection pooling
> -
>
> Key: IGNITE-6145
> URL: https://issues.apache.org/jira/browse/IGNITE-6145
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc
>Affects Versions: 2.1
>Reporter: Taras Ledkov
>Priority: Major
>
> W have to support connection pool to JDBC compliance.
> At the very least we must test ourselves with well-known pooling providers 
> (DBCP, c3p0). 
> This is blocked by IGNITE-6140



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-8952) Move CacheStore::loadCache to a separate interface

[kcheng.mvp (JIRA)]

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

kcheng.mvp reassigned IGNITE-8952:
--

Assignee: (was: kcheng.mvp)

> Move CacheStore::loadCache to a separate interface
> --
>
> Key: IGNITE-8952
> URL: https://issues.apache.org/jira/browse/IGNITE-8952
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Stanislav Lukyanov
>Priority: Major
>  Labels: newbie
>
> 3rd party persistence has three way of interacting with the backing storage:
> - JCache's CacheLoader methods for read-through
> - JCache's CacheWriter methods for write-through
> - Ignite's CacheStore::loadCache for bulk cache preloading
> Usually, one just uses a CacheStore implementation and provides a no-op 
> implementation for the methods that are not needed (e.g. no-op implementation 
> for write() if write-through isn't used). However, this adds certain 
> redundancy.
> In particular, if a user only wants cache preloading (loadCache()) but no 
> read-through or write-through, they will need to provide a bunch of these 
> no-op methods, which can seem messy.
> Instead, it would be nice to move loadCache() method to a separate interface, 
> say CachePreloader. This way we'll have 4 interfaces:
> - JCache's CacheLoader for read-through
> - JCache's CacheWriter for write-through
> - Ignite's CachePreloader for loadCache()
> - Ignite's CacheStore for all three together
> One can either choose any combination of loader, writer and preloader, OR set 
> the store.
> The task is to
> - extract CacheStore::loadCache into a new interface CachePreloader 
> - add CacheConfiguration::setCachePreloader
> - make sure that setCachePreloader works alone or in combination with loader 
> and writer, and doesn't work with store



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-9005) Eviction policy MBeans change failed LifecycleAwareTest on cache name injectoin

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-9005:


[~dpavlov],

I checked the source code and found that this issue may be caused by this line

org.apache.ignite.internal.processors.cache.GridCacheProcessor #1452

*CacheEvictionManager evictMgr = (nearEnabled || cfg.isOnheapCacheEnabled()) ? 
new GridCacheEvictionManager() : new CacheOffheapEvictionManager();*


as in this case a new *CacheOffheapEvictionManager()* will return, but this 
implementation does not do any eviction bean register/unregister, as there are 
no any policy.

are my findings wrong? 

> Eviction policy MBeans change failed LifecycleAwareTest on cache name 
> injectoin
> ---
>
> Key: IGNITE-9005
> URL: https://issues.apache.org/jira/browse/IGNITE-9005
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: kcheng.mvp
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> http://apache-ignite-developers.2346864.n4.nabble.com/MTCGA-new-failures-in-builds-1485687-needs-to-be-handled-td32531.html
> New test failure detected 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7246907407546697403=%3Cdefault%3E=testDetails
> after merging 
> IGNITE-8776 Eviction policy MBeans are never registered if 
> evictionPolicyFactory is used 
> Revert of commit makes test passing.
> Locally test also failed. Failed with message
> {noformat}
> Unexpected cache name for 
> org.apache.ignite.internal.processors.cache.GridCacheLifecycleAwareSelfTest$TestEvictionPolicy@322714f4
>  expected: but was:
> {noformat}
> Message of failure seems to be related to TestEvictionPolicy instance from 
> test class. 
> Seems that returing call to cctx.kernalContext (). resource (). 
> injectCacheName (rsrc, cfg.getName ()); should fix issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-9005) Eviction policy MBeans change failed LifecycleAwareTest on cache name injectoin

[kcheng.mvp (JIRA)]

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

kcheng.mvp reassigned IGNITE-9005:
--

Assignee: kcheng.mvp  (was: Stanislav Lukyanov)

> Eviction policy MBeans change failed LifecycleAwareTest on cache name 
> injectoin
> ---
>
> Key: IGNITE-9005
> URL: https://issues.apache.org/jira/browse/IGNITE-9005
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: kcheng.mvp
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> http://apache-ignite-developers.2346864.n4.nabble.com/MTCGA-new-failures-in-builds-1485687-needs-to-be-handled-td32531.html
> New test failure detected 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7246907407546697403=%3Cdefault%3E=testDetails
> after merging 
> IGNITE-8776 Eviction policy MBeans are never registered if 
> evictionPolicyFactory is used 
> Revert of commit makes test passing.
> Locally test also failed. Failed with message
> {noformat}
> Unexpected cache name for 
> org.apache.ignite.internal.processors.cache.GridCacheLifecycleAwareSelfTest$TestEvictionPolicy@322714f4
>  expected: but was:
> {noformat}
> Message of failure seems to be related to TestEvictionPolicy instance from 
> test class. 
> Seems that returing call to cctx.kernalContext (). resource (). 
> injectCacheName (rsrc, cfg.getName ()); should fix issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8776) Eviction policy MBeans are never registered if evictionPolicyFactory is used

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-8776:


[~dpavlov] Can you please take a look about this PR. it has been passed 
[~slukyanov] 's review.

> Eviction policy MBeans are never registered if evictionPolicyFactory is used
> 
>
> Key: IGNITE-8776
> URL: https://issues.apache.org/jira/browse/IGNITE-8776
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
> Fix For: 2.7
>
>
> Eviction policy MBeans, such as LruEvictionPolicyMBean, are never registered 
> if evictionPolicyFactory is set instead of evictionPolicy (the latter is 
> deprecated).
> This happens because GridCacheProcessor::registerMbean attempts to find 
> either an *MBean interface or IgniteMBeanAware interface on the passed 
> object. It works for LruEvictionPolicy but not for LruEvictionPolicyFactory 
> (which doesn't implement these interfaces).
> The code needs to be adjusted to handle factories correctly.
> New tests are needed to make sure that all standard beans are registered 
> (IgniteKernalMbeansTest does that for kernal mbeans - need the same for cache 
> beans).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-8952) Move CacheStore::loadCache to a separate interface

[kcheng.mvp (JIRA)]

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

kcheng.mvp reassigned IGNITE-8952:
--

Assignee: kcheng.mvp

> Move CacheStore::loadCache to a separate interface
> --
>
> Key: IGNITE-8952
> URL: https://issues.apache.org/jira/browse/IGNITE-8952
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Major
>  Labels: newbie
>
> 3rd party persistence has three way of interacting with the backing storage:
> - JCache's CacheLoader methods for read-through
> - JCache's CacheWriter methods for write-through
> - Ignite's CacheStore::loadCache for bulk cache preloading
> Usually, one just uses a CacheStore implementation and provides a no-op 
> implementation for the methods that are not needed (e.g. no-op implementation 
> for write() if write-through isn't used). However, this adds certain 
> redundancy.
> In particular, if a user only wants cache preloading (loadCache()) but no 
> read-through or write-through, they will need to provide a bunch of these 
> no-op methods, which can seem messy.
> Instead, it would be nice to move loadCache() method to a separate interface, 
> say CachePreloader. This way we'll have 4 interfaces:
> - JCache's CacheLoader for read-through
> - JCache's CacheWriter for write-through
> - Ignite's CachePreloader for loadCache()
> - Ignite's CacheStore for all three together
> One can either choose any combination of loader, writer and preloader, OR set 
> the store.
> The task is to
> - extract CacheStore::loadCache into a new interface CachePreloader 
> - add CacheConfiguration::setCachePreloader
> - make sure that setCachePreloader works alone or in combination with loader 
> and writer, and doesn't work with store



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-8376) Add cluster (de)activation events

[kcheng.mvp (JIRA)]

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

kcheng.mvp reassigned IGNITE-8376:
--

Assignee: (was: kcheng.mvp)

> Add cluster (de)activation events
> -
>
> Key: IGNITE-8376
> URL: https://issues.apache.org/jira/browse/IGNITE-8376
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Priority: Major
>  Labels: newbie
> Fix For: 2.7
>
>
> Currently, we do not have any way to detect that a cluster got activated, 
> which results in busy-loops polling {{cluster().active()}}.
> I suggest to add new events, {{EVT_CLUSTER_ACTIVATED}}, 
> {{EVT_CLUSTER_DEACTIVATED}}, {{EVT_CLUSTER_ACTIVATION_FAILED}} which will be 
> fired when corresponding steps are completed. The event should contain, if 
> possible, information about the activation source (public API or 
> auto-activation), topology version on which activation was performed. The 
> fail event should contain information about the cause of the failure. If 
> needed, a new class for this event should be introduced.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-8376) Add cluster (de)activation events

[kcheng.mvp (JIRA)]

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

kcheng.mvp edited comment on IGNITE-8376 at 7/9/18 10:22 AM:
-

[~DmitriyGovorukhin][~agoncharuk][~kuaw26]

Once thing need to clarify with you. from the source code. right now there are 
just two type of *internal* event as below

you means we make the mentioned events as *internal* as well?

1: *Cluster level* EVT_CLUSTER_ACTIVATED, EVT_CLUSTER_DEACTIVATED, 
EVT_CLUSTER_ACTIVATION_FAILED
2: *Node Level* EVT_NODE_ACTIVATE,EVT_NODE_DEACTIVATE,EVT_NODE_ACTIVATING, 
EVT_NODE_DEACTIVATING

is my understanding correct? 

{code:java}
   /**
 * Checks whether or not this event is an internal event.
 * 
 * Internal event types are always recordable for notification purposes
 * but may not be sent down to SPI level for storage and subsequent 
querying.
 *
 * @param type Event type.
 * @return {@code true} if this is an internal event.
 */
private boolean isInternalEvent(int type) {
return type == EVT_DISCOVERY_CUSTOM_EVT || 
F.contains(EVTS_DISCOVERY_ALL, type);
}
{code}



was (Author: kcheng.mvp):
[~DmitriyGovorukhin][~agoncharuk][~kuaw26]

Once thing need to clarify with you. from the source code. right now there are 
just two type of *internal* event as below

you means we make the mentioned events as *internal* as well?

1: "Cluster level* EVT_CLUSTER_ACTIVATED, EVT_CLUSTER_DEACTIVATED, 
EVT_CLUSTER_ACTIVATION_FAILED
2: "Node Level" EVT_NODE_ACTIVATE,EVT_NODE_DEACTIVATE,EVT_NODE_ACTIVATING, 
EVT_NODE_DEACTIVATING

is my understanding correct? 

{code:java}
   /**
 * Checks whether or not this event is an internal event.
 * 
 * Internal event types are always recordable for notification purposes
 * but may not be sent down to SPI level for storage and subsequent 
querying.
 *
 * @param type Event type.
 * @return {@code true} if this is an internal event.
 */
private boolean isInternalEvent(int type) {
return type == EVT_DISCOVERY_CUSTOM_EVT || 
F.contains(EVTS_DISCOVERY_ALL, type);
}
{code}


> Add cluster (de)activation events
> -
>
> Key: IGNITE-8376
> URL: https://issues.apache.org/jira/browse/IGNITE-8376
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: kcheng.mvp
>Priority: Major
>  Labels: newbie
> Fix For: 2.7
>
>
> Currently, we do not have any way to detect that a cluster got activated, 
> which results in busy-loops polling {{cluster().active()}}.
> I suggest to add new events, {{EVT_CLUSTER_ACTIVATED}}, 
> {{EVT_CLUSTER_DEACTIVATED}}, {{EVT_CLUSTER_ACTIVATION_FAILED}} which will be 
> fired when corresponding steps are completed. The event should contain, if 
> possible, information about the activation source (public API or 
> auto-activation), topology version on which activation was performed. The 
> fail event should contain information about the cause of the failure. If 
> needed, a new class for this event should be introduced.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8376) Add cluster (de)activation events

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-8376:


[~DmitriyGovorukhin][~agoncharuk][~kuaw26]

Once thing need to clarify with you. from the source code. right now there are 
just two type of *internal* event as below

you means we make the mentioned events as *internal* as well?

1: "Cluster level* EVT_CLUSTER_ACTIVATED, EVT_CLUSTER_DEACTIVATED, 
EVT_CLUSTER_ACTIVATION_FAILED
2: "Node Level" EVT_NODE_ACTIVATE,EVT_NODE_DEACTIVATE,EVT_NODE_ACTIVATING, 
EVT_NODE_DEACTIVATING

is my understanding correct? 

{code:java}
   /**
 * Checks whether or not this event is an internal event.
 * 
 * Internal event types are always recordable for notification purposes
 * but may not be sent down to SPI level for storage and subsequent 
querying.
 *
 * @param type Event type.
 * @return {@code true} if this is an internal event.
 */
private boolean isInternalEvent(int type) {
return type == EVT_DISCOVERY_CUSTOM_EVT || 
F.contains(EVTS_DISCOVERY_ALL, type);
}
{code}


> Add cluster (de)activation events
> -
>
> Key: IGNITE-8376
> URL: https://issues.apache.org/jira/browse/IGNITE-8376
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: kcheng.mvp
>Priority: Major
>  Labels: newbie
> Fix For: 2.7
>
>
> Currently, we do not have any way to detect that a cluster got activated, 
> which results in busy-loops polling {{cluster().active()}}.
> I suggest to add new events, {{EVT_CLUSTER_ACTIVATED}}, 
> {{EVT_CLUSTER_DEACTIVATED}}, {{EVT_CLUSTER_ACTIVATION_FAILED}} which will be 
> fired when corresponding steps are completed. The event should contain, if 
> possible, information about the activation source (public API or 
> auto-activation), topology version on which activation was performed. The 
> fail event should contain information about the cause of the failure. If 
> needed, a new class for this event should be introduced.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8827) Disable WAL during apply updates on recovery

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-8827:


[~DmitriyGovorukhin][~agura][~ilantukh]

Seems the checkin caused a Javadoc error. I have created a ticket 
https://issues.apache.org/jira/browse/IGNITE-8956 for this.

I raised a PR for the fix. please help me do a code review.

> Disable WAL during apply updates on recovery
> 
>
> Key: IGNITE-8827
> URL: https://issues.apache.org/jira/browse/IGNITE-8827
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.7
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8376) Add cluster (de)activation events

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-8376:


Thank you all very much for your comments. Right now I am working on it, once 
it's ready I will raise PR.

> Add cluster (de)activation events
> -
>
> Key: IGNITE-8376
> URL: https://issues.apache.org/jira/browse/IGNITE-8376
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: kcheng.mvp
>Priority: Major
>  Labels: newbie
> Fix For: 2.7
>
>
> Currently, we do not have any way to detect that a cluster got activated, 
> which results in busy-loops polling {{cluster().active()}}.
> I suggest to add new events, {{EVT_CLUSTER_ACTIVATED}}, 
> {{EVT_CLUSTER_DEACTIVATED}}, {{EVT_CLUSTER_ACTIVATION_FAILED}} which will be 
> fired when corresponding steps are completed. The event should contain, if 
> possible, information about the activation source (public API or 
> auto-activation), topology version on which activation was performed. The 
> fail event should contain information about the cause of the failure. If 
> needed, a new class for this event should be introduced.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8956) Javadoc build failure: Warnings:core/src/main/java/org/apache/ignite/internal/processors/cache/WalStateManager.java:1271: warning - @inheritDoc used but check() does n

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-8956:


[~ilantukh]

Please help do the code review, here is the PR

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

> Javadoc build failure: 
> Warnings:core/src/main/java/org/apache/ignite/internal/processors/cache/WalStateManager.java:1271:
>  warning - @inheritDoc used but check() does not override or implement any 
> method.
> ---
>
> Key: IGNITE-8956
> URL: https://issues.apache.org/jira/browse/IGNITE-8956
> Project: Ignite
>  Issue Type: Bug
>Reporter: kcheng.mvp
>Assignee: kcheng.mvp
>Priority: Minor
>
> Checked the history, seems it's caused by the checkin for 
> https://issues.apache.org/jira/browse/IGNITE-8827



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8776) Eviction policy MBeans are never registered if evictionPolicyFactory is used

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-8776:


[~slukyanov] I did the necessary changes, please view it again. Thanks.

> Eviction policy MBeans are never registered if evictionPolicyFactory is used
> 
>
> Key: IGNITE-8776
> URL: https://issues.apache.org/jira/browse/IGNITE-8776
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
> Fix For: 2.6
>
>
> Eviction policy MBeans, such as LruEvictionPolicyMBean, are never registered 
> if evictionPolicyFactory is set instead of evictionPolicy (the latter is 
> deprecated).
> This happens because GridCacheProcessor::registerMbean attempts to find 
> either an *MBean interface or IgniteMBeanAware interface on the passed 
> object. It works for LruEvictionPolicy but not for LruEvictionPolicyFactory 
> (which doesn't implement these interfaces).
> The code needs to be adjusted to handle factories correctly.
> New tests are needed to make sure that all standard beans are registered 
> (IgniteKernalMbeansTest does that for kernal mbeans - need the same for cache 
> beans).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8956) Javadoc build failure: Warnings:core/src/main/java/org/apache/ignite/internal/processors/cache/WalStateManager.java:1271: warning - @inheritDoc used but check() does n

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-8956:


The Javadoc error is fixed.

https://ci.ignite.apache.org/viewLog.html?buildId=1465101=IgniteTests24Java8_RunBasicTests=buildResultsDiv

Hi Dmitriy Govorukhin,
Can you have a review this PR https://github.com/apache/ignite/pull/4328?

> Javadoc build failure: 
> Warnings:core/src/main/java/org/apache/ignite/internal/processors/cache/WalStateManager.java:1271:
>  warning - @inheritDoc used but check() does not override or implement any 
> method.
> ---
>
> Key: IGNITE-8956
> URL: https://issues.apache.org/jira/browse/IGNITE-8956
> Project: Ignite
>  Issue Type: Bug
>Reporter: kcheng.mvp
>Assignee: kcheng.mvp
>Priority: Minor
>
> Checked the history, seems it's caused by the checkin for 
> https://issues.apache.org/jira/browse/IGNITE-8827



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8956) Javadoc build failure: Warnings:core/src/main/java/org/apache/ignite/internal/processors/cache/WalStateManager.java:1271: warning - @inheritDoc used but check() does not

[kcheng.mvp (JIRA)]

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

kcheng.mvp updated IGNITE-8956:
---
Summary: Javadoc build failure: 
Warnings:core/src/main/java/org/apache/ignite/internal/processors/cache/WalStateManager.java:1271:
 warning - @inheritDoc used but check() does not override or implement any 
method.  (was: Javadoc 
Warnings:core/src/main/java/org/apache/ignite/internal/processors/cache/WalStateManager.java:1271:
 warning - @inheritDoc used but check() does not override or implement any 
method.)

> Javadoc build failure: 
> Warnings:core/src/main/java/org/apache/ignite/internal/processors/cache/WalStateManager.java:1271:
>  warning - @inheritDoc used but check() does not override or implement any 
> method.
> ---
>
> Key: IGNITE-8956
> URL: https://issues.apache.org/jira/browse/IGNITE-8956
> Project: Ignite
>  Issue Type: Bug
>Reporter: kcheng.mvp
>Assignee: kcheng.mvp
>Priority: Minor
>
> Checked the history, seems it's caused by the checkin for 
> https://issues.apache.org/jira/browse/IGNITE-8827



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-8956) Javadoc Warnings:core/src/main/java/org/apache/ignite/internal/processors/cache/WalStateManager.java:1271: warning - @inheritDoc used but check() does not override or i

[kcheng.mvp (JIRA)]

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

kcheng.mvp reassigned IGNITE-8956:
--

Assignee: kcheng.mvp

> Javadoc 
> Warnings:core/src/main/java/org/apache/ignite/internal/processors/cache/WalStateManager.java:1271:
>  warning - @inheritDoc used but check() does not override or implement any 
> method.
> 
>
> Key: IGNITE-8956
> URL: https://issues.apache.org/jira/browse/IGNITE-8956
> Project: Ignite
>  Issue Type: Bug
>Reporter: kcheng.mvp
>Assignee: kcheng.mvp
>Priority: Minor
>
> Checked the history, seems it's caused by the checkin for 
> https://issues.apache.org/jira/browse/IGNITE-8827



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8956) Javadoc Warnings:core/src/main/java/org/apache/ignite/internal/processors/cache/WalStateManager.java:1271: warning - @inheritDoc used but check() does not override or im

[kcheng.mvp (JIRA)]

kcheng.mvp created IGNITE-8956:
--

 Summary: Javadoc 
Warnings:core/src/main/java/org/apache/ignite/internal/processors/cache/WalStateManager.java:1271:
 warning - @inheritDoc used but check() does not override or implement any 
method.
 Key: IGNITE-8956
 URL: https://issues.apache.org/jira/browse/IGNITE-8956
 Project: Ignite
  Issue Type: Bug
Reporter: kcheng.mvp


Checked the history, seems it's caused by the checkin for 
https://issues.apache.org/jira/browse/IGNITE-8827



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-8776) Eviction policy MBeans are never registered if evictionPolicyFactory is used

[kcheng.mvp (JIRA)]

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

kcheng.mvp edited comment on IGNITE-8776 at 7/6/18 4:00 PM:


[~slukyanov]

Everything is green 
https://ci.ignite.apache.org/viewLog.html?buildId=1462771=buildResultsDiv=IgniteTests24Java8_RunBasicTests

Can you help me do a code review?


was (Author: kcheng.mvp):
[~slukyanov]

Everything is greep 
https://ci.ignite.apache.org/viewLog.html?buildId=1462771=buildResultsDiv=IgniteTests24Java8_RunBasicTests

Can you help me do a code review?

> Eviction policy MBeans are never registered if evictionPolicyFactory is used
> 
>
> Key: IGNITE-8776
> URL: https://issues.apache.org/jira/browse/IGNITE-8776
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
>
> Eviction policy MBeans, such as LruEvictionPolicyMBean, are never registered 
> if evictionPolicyFactory is set instead of evictionPolicy (the latter is 
> deprecated).
> This happens because GridCacheProcessor::registerMbean attempts to find 
> either an *MBean interface or IgniteMBeanAware interface on the passed 
> object. It works for LruEvictionPolicy but not for LruEvictionPolicyFactory 
> (which doesn't implement these interfaces).
> The code needs to be adjusted to handle factories correctly.
> New tests are needed to make sure that all standard beans are registered 
> (IgniteKernalMbeansTest does that for kernal mbeans - need the same for cache 
> beans).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8776) Eviction policy MBeans are never registered if evictionPolicyFactory is used

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-8776:


[~slukyanov]

Everything is greep 
https://ci.ignite.apache.org/viewLog.html?buildId=1462771=buildResultsDiv=IgniteTests24Java8_RunBasicTests

Can you help me do a code review?

> Eviction policy MBeans are never registered if evictionPolicyFactory is used
> 
>
> Key: IGNITE-8776
> URL: https://issues.apache.org/jira/browse/IGNITE-8776
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
>
> Eviction policy MBeans, such as LruEvictionPolicyMBean, are never registered 
> if evictionPolicyFactory is set instead of evictionPolicy (the latter is 
> deprecated).
> This happens because GridCacheProcessor::registerMbean attempts to find 
> either an *MBean interface or IgniteMBeanAware interface on the passed 
> object. It works for LruEvictionPolicy but not for LruEvictionPolicyFactory 
> (which doesn't implement these interfaces).
> The code needs to be adjusted to handle factories correctly.
> New tests are needed to make sure that all standard beans are registered 
> (IgniteKernalMbeansTest does that for kernal mbeans - need the same for cache 
> beans).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-8776) Eviction policy MBeans are never registered if evictionPolicyFactory is used

[kcheng.mvp (JIRA)]

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

kcheng.mvp edited comment on IGNITE-8776 at 7/6/18 5:48 AM:


[~slukyanov]
I have triggered the tests many times on TeamCity. every time I get the same 
result.

Platform .NET (Core Linux)  pull/4300/head  #1109Exit code 1 (new) 

https://ci.ignite.apache.org/viewLog.html?buildId=1460429=buildResultsDiv=IgniteTests24Java8_RunBasicTests.

I checked the history of 'Platform .NET (Core Linux) ' and found there are many 
other build also runs into the same result.




was (Author: kcheng.mvp):
I have triggered the tests many times on TeamCity. every time I get the same 
result.

Platform .NET (Core Linux)  pull/4300/head  #1109Exit code 1 (new) 

https://ci.ignite.apache.org/viewLog.html?buildId=1460429=buildResultsDiv=IgniteTests24Java8_RunBasicTests.

I checked the history of 'Platform .NET (Core Linux) ' and found there are many 
other build also runs into the same result.



> Eviction policy MBeans are never registered if evictionPolicyFactory is used
> 
>
> Key: IGNITE-8776
> URL: https://issues.apache.org/jira/browse/IGNITE-8776
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
>
> Eviction policy MBeans, such as LruEvictionPolicyMBean, are never registered 
> if evictionPolicyFactory is set instead of evictionPolicy (the latter is 
> deprecated).
> This happens because GridCacheProcessor::registerMbean attempts to find 
> either an *MBean interface or IgniteMBeanAware interface on the passed 
> object. It works for LruEvictionPolicy but not for LruEvictionPolicyFactory 
> (which doesn't implement these interfaces).
> The code needs to be adjusted to handle factories correctly.
> New tests are needed to make sure that all standard beans are registered 
> (IgniteKernalMbeansTest does that for kernal mbeans - need the same for cache 
> beans).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8776) Eviction policy MBeans are never registered if evictionPolicyFactory is used

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-8776:


I have triggered the tests many times on TeamCity. every time I get the same 
result.

Platform .NET (Core Linux)  pull/4300/head  #1109Exit code 1 (new) 

https://ci.ignite.apache.org/viewLog.html?buildId=1460429=buildResultsDiv=IgniteTests24Java8_RunBasicTests.

I checked the history of 'Platform .NET (Core Linux) ' and found there are many 
other build also runs into the same result.



> Eviction policy MBeans are never registered if evictionPolicyFactory is used
> 
>
> Key: IGNITE-8776
> URL: https://issues.apache.org/jira/browse/IGNITE-8776
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
>
> Eviction policy MBeans, such as LruEvictionPolicyMBean, are never registered 
> if evictionPolicyFactory is set instead of evictionPolicy (the latter is 
> deprecated).
> This happens because GridCacheProcessor::registerMbean attempts to find 
> either an *MBean interface or IgniteMBeanAware interface on the passed 
> object. It works for LruEvictionPolicy but not for LruEvictionPolicyFactory 
> (which doesn't implement these interfaces).
> The code needs to be adjusted to handle factories correctly.
> New tests are needed to make sure that all standard beans are registered 
> (IgniteKernalMbeansTest does that for kernal mbeans - need the same for cache 
> beans).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (IGNITE-8776) Eviction policy MBeans are never registered if evictionPolicyFactory is used

[kcheng.mvp (JIRA)]

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

kcheng.mvp updated IGNITE-8776:
---
Comment: was deleted

(was: [~slukyanov]

Thank you very much!
The fix pretty much done, but I have an unclear and I posted in the forum. Can 
you have a check ?

http://apache-ignite-developers.2346864.n4.nabble.com/Why-GridCacheEvictionManager-always-use-cfg-getEvictionPolicy-cfg-getEvictionPolicyFactory-even-ther-td32230.html)

> Eviction policy MBeans are never registered if evictionPolicyFactory is used
> 
>
> Key: IGNITE-8776
> URL: https://issues.apache.org/jira/browse/IGNITE-8776
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
>
> Eviction policy MBeans, such as LruEvictionPolicyMBean, are never registered 
> if evictionPolicyFactory is set instead of evictionPolicy (the latter is 
> deprecated).
> This happens because GridCacheProcessor::registerMbean attempts to find 
> either an *MBean interface or IgniteMBeanAware interface on the passed 
> object. It works for LruEvictionPolicy but not for LruEvictionPolicyFactory 
> (which doesn't implement these interfaces).
> The code needs to be adjusted to handle factories correctly.
> New tests are needed to make sure that all standard beans are registered 
> (IgniteKernalMbeansTest does that for kernal mbeans - need the same for cache 
> beans).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8776) Eviction policy MBeans are never registered if evictionPolicyFactory is used

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-8776:


[~slukyanov]

I have raised PR, can you help me do the code review?
https://github.com/apache/ignite/pull/4300

Thanks,
kcmvp

> Eviction policy MBeans are never registered if evictionPolicyFactory is used
> 
>
> Key: IGNITE-8776
> URL: https://issues.apache.org/jira/browse/IGNITE-8776
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
>
> Eviction policy MBeans, such as LruEvictionPolicyMBean, are never registered 
> if evictionPolicyFactory is set instead of evictionPolicy (the latter is 
> deprecated).
> This happens because GridCacheProcessor::registerMbean attempts to find 
> either an *MBean interface or IgniteMBeanAware interface on the passed 
> object. It works for LruEvictionPolicy but not for LruEvictionPolicyFactory 
> (which doesn't implement these interfaces).
> The code needs to be adjusted to handle factories correctly.
> New tests are needed to make sure that all standard beans are registered 
> (IgniteKernalMbeansTest does that for kernal mbeans - need the same for cache 
> beans).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8776) Eviction policy MBeans are never registered if evictionPolicyFactory is used

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-8776:


[~slukyanov]

Thank you very much!
The fix pretty much done, but I have an unclear and I posted in the forum. Can 
you have a check ?

http://apache-ignite-developers.2346864.n4.nabble.com/Why-GridCacheEvictionManager-always-use-cfg-getEvictionPolicy-cfg-getEvictionPolicyFactory-even-ther-td32230.html

> Eviction policy MBeans are never registered if evictionPolicyFactory is used
> 
>
> Key: IGNITE-8776
> URL: https://issues.apache.org/jira/browse/IGNITE-8776
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
>
> Eviction policy MBeans, such as LruEvictionPolicyMBean, are never registered 
> if evictionPolicyFactory is set instead of evictionPolicy (the latter is 
> deprecated).
> This happens because GridCacheProcessor::registerMbean attempts to find 
> either an *MBean interface or IgniteMBeanAware interface on the passed 
> object. It works for LruEvictionPolicy but not for LruEvictionPolicyFactory 
> (which doesn't implement these interfaces).
> The code needs to be adjusted to handle factories correctly.
> New tests are needed to make sure that all standard beans are registered 
> (IgniteKernalMbeansTest does that for kernal mbeans - need the same for cache 
> beans).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8776) Eviction policy MBeans are never registered if evictionPolicyFactory is used

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-8776:


Hi [~slukyanov],Here is my investigation:

-- 
org.apache.ignite.internal.processors.cache.GridCacheProcessor#prepareCacheStart
- *call 
org.apache.ignite.internal.processors.cache.GridCacheProcessor#createCache* at 
line #1944
- *startCache(cache, desc.schema() != null ? desc.schema() : new 
QuerySchema());* at line #1963

For case using *FifoEvictionPolicyFactory* and *LruEvictionPolicyFactory* the 
backend eviction policy is generated by factory's *create()* method when 
starting a cache. That's to say even through the eviction factory full fill the 
*MBean interface or IgniteMBeanAware interface*, it can still not be registered 
at 
*org.apache.ignite.internal.processors.cache.GridCacheProcessor#registerMbean*, 
as the instances have not been generated.

so I think the best place to register the mbeans is in 
*org.apache.ignite.internal.processors.cache.GridCacheEvictionManager*.

please advise me if I am wrong.
[~slukyanov]

> Eviction policy MBeans are never registered if evictionPolicyFactory is used
> 
>
> Key: IGNITE-8776
> URL: https://issues.apache.org/jira/browse/IGNITE-8776
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
>
> Eviction policy MBeans, such as LruEvictionPolicyMBean, are never registered 
> if evictionPolicyFactory is set instead of evictionPolicy (the latter is 
> deprecated).
> This happens because GridCacheProcessor::registerMbean attempts to find 
> either an *MBean interface or IgniteMBeanAware interface on the passed 
> object. It works for LruEvictionPolicy but not for LruEvictionPolicyFactory 
> (which doesn't implement these interfaces).
> The code needs to be adjusted to handle factories correctly.
> New tests are needed to make sure that all standard beans are registered 
> (IgniteKernalMbeansTest does that for kernal mbeans - need the same for cache 
> beans).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-8776) Eviction policy MBeans are never registered if evictionPolicyFactory is used

[kcheng.mvp (JIRA)]

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

kcheng.mvp reassigned IGNITE-8776:
--

Assignee: kcheng.mvp

> Eviction policy MBeans are never registered if evictionPolicyFactory is used
> 
>
> Key: IGNITE-8776
> URL: https://issues.apache.org/jira/browse/IGNITE-8776
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
>
> Eviction policy MBeans, such as LruEvictionPolicyMBean, are never registered 
> if evictionPolicyFactory is set instead of evictionPolicy (the latter is 
> deprecated).
> This happens because GridCacheProcessor::registerMbean attempts to find 
> either an *MBean interface or IgniteMBeanAware interface on the passed 
> object. It works for LruEvictionPolicy but not for LruEvictionPolicyFactory 
> (which doesn't implement these interfaces).
> The code needs to be adjusted to handle factories correctly.
> New tests are needed to make sure that all standard beans are registered 
> (IgniteKernalMbeansTest does that for kernal mbeans - need the same for cache 
> beans).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-8776) Eviction policy MBeans are never registered if evictionPolicyFactory is used

[kcheng.mvp (JIRA)]

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

kcheng.mvp reassigned IGNITE-8776:
--

Assignee: (was: kcheng.mvp)

> Eviction policy MBeans are never registered if evictionPolicyFactory is used
> 
>
> Key: IGNITE-8776
> URL: https://issues.apache.org/jira/browse/IGNITE-8776
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Stanislav Lukyanov
>Priority: Minor
>  Labels: newbie
>
> Eviction policy MBeans, such as LruEvictionPolicyMBean, are never registered 
> if evictionPolicyFactory is set instead of evictionPolicy (the latter is 
> deprecated).
> This happens because GridCacheProcessor::registerMbean attempts to find 
> either an *MBean interface or IgniteMBeanAware interface on the passed 
> object. It works for LruEvictionPolicy but not for LruEvictionPolicyFactory 
> (which doesn't implement these interfaces).
> The code needs to be adjusted to handle factories correctly.
> New tests are needed to make sure that all standard beans are registered 
> (IgniteKernalMbeansTest does that for kernal mbeans - need the same for cache 
> beans).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-8776) Eviction policy MBeans are never registered if evictionPolicyFactory is used

[kcheng.mvp (JIRA)]

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

kcheng.mvp reassigned IGNITE-8776:
--

Assignee: kcheng.mvp

> Eviction policy MBeans are never registered if evictionPolicyFactory is used
> 
>
> Key: IGNITE-8776
> URL: https://issues.apache.org/jira/browse/IGNITE-8776
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Stanislav Lukyanov
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
>
> Eviction policy MBeans, such as LruEvictionPolicyMBean, are never registered 
> if evictionPolicyFactory is set instead of evictionPolicy (the latter is 
> deprecated).
> This happens because GridCacheProcessor::registerMbean attempts to find 
> either an *MBean interface or IgniteMBeanAware interface on the passed 
> object. It works for LruEvictionPolicy but not for LruEvictionPolicyFactory 
> (which doesn't implement these interfaces).
> The code needs to be adjusted to handle factories correctly.
> New tests are needed to make sure that all standard beans are registered 
> (IgniteKernalMbeansTest does that for kernal mbeans - need the same for cache 
> beans).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8376) Add cluster (de)activation events

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-8376:


[~agoncharuk]



After go through the code and found the active/deactive action will finally 
router to 

 
{code:java}
org.apache.ignite.internal.cluster.IgniteClusterImpl#active(boolean)

/** {@inheritDoc} */
@Override public void active(boolean active) {
guard();

try {
ctx.state().changeGlobalState(active, baselineNodes(), false).get();
}
catch (IgniteCheckedException e) {
throw U.convertException(e);
}
finally {
unguard();
}
}
{code}

ideally it's the best place to trigger the event, but if we trigger the event 
here, seems we can not get by which means this event is triggered(api, rest, 
mbean visitorcommand or auto).

is my understanding correct? Thank you very much!


> Add cluster (de)activation events
> -
>
> Key: IGNITE-8376
> URL: https://issues.apache.org/jira/browse/IGNITE-8376
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: kcheng.mvp
>Priority: Major
>  Labels: newbie
> Fix For: 2.7
>
>
> Currently, we do not have any way to detect that a cluster got activated, 
> which results in busy-loops polling {{cluster().active()}}.
> I suggest to add new events, {{EVT_CLUSTER_ACTIVATED}}, 
> {{EVT_CLUSTER_DEACTIVATED}}, {{EVT_CLUSTER_ACTIVATION_FAILED}} which will be 
> fired when corresponding steps are completed. The event should contain, if 
> possible, information about the activation source (public API or 
> auto-activation), topology version on which activation was performed. The 
> fail event should contain information about the cause of the failure. If 
> needed, a new class for this event should be introduced.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8376) Add cluster (de)activation events

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-8376:


I found below entries to  active/deactivate cluster. 

 

1: rest api  -> 
org.apache.ignite.internal.processors.rest.handlers.cluster.GridChangeStateCommandHandle

2: command visitor -> VisorTopologyCommand.scala

3: direct api call -> org.apache.ignite.Ignite

 

 

 

> Add cluster (de)activation events
> -
>
> Key: IGNITE-8376
> URL: https://issues.apache.org/jira/browse/IGNITE-8376
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: kcheng.mvp
>Priority: Major
>  Labels: newbie
> Fix For: 2.7
>
>
> Currently, we do not have any way to detect that a cluster got activated, 
> which results in busy-loops polling {{cluster().active()}}.
> I suggest to add new events, {{EVT_CLUSTER_ACTIVATED}}, 
> {{EVT_CLUSTER_DEACTIVATED}}, {{EVT_CLUSTER_ACTIVATION_FAILED}} which will be 
> fired when corresponding steps are completed. The event should contain, if 
> possible, information about the activation source (public API or 
> auto-activation), topology version on which activation was performed. The 
> fail event should contain information about the cause of the failure. If 
> needed, a new class for this event should be introduced.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8376) Add cluster (de)activation events

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-8376:


Hi [~agoncharuk],

I would like to take this ticket, would you please give me some 
hints/instructions?

 

Thanks,

Ken

> Add cluster (de)activation events
> -
>
> Key: IGNITE-8376
> URL: https://issues.apache.org/jira/browse/IGNITE-8376
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: kcheng.mvp
>Priority: Major
>  Labels: newbie
> Fix For: 2.7
>
>
> Currently, we do not have any way to detect that a cluster got activated, 
> which results in busy-loops polling {{cluster().active()}}.
> I suggest to add new events, {{EVT_CLUSTER_ACTIVATED}}, 
> {{EVT_CLUSTER_DEACTIVATED}}, {{EVT_CLUSTER_ACTIVATION_FAILED}} which will be 
> fired when corresponding steps are completed. The event should contain, if 
> possible, information about the activation source (public API or 
> auto-activation), topology version on which activation was performed. The 
> fail event should contain information about the cause of the failure. If 
> needed, a new class for this event should be introduced.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-8376) Add cluster (de)activation events

[kcheng.mvp (JIRA)]

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

kcheng.mvp reassigned IGNITE-8376:
--

Assignee: kcheng.mvp

> Add cluster (de)activation events
> -
>
> Key: IGNITE-8376
> URL: https://issues.apache.org/jira/browse/IGNITE-8376
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: kcheng.mvp
>Priority: Major
>  Labels: newbie
> Fix For: 2.7
>
>
> Currently, we do not have any way to detect that a cluster got activated, 
> which results in busy-loops polling {{cluster().active()}}.
> I suggest to add new events, {{EVT_CLUSTER_ACTIVATED}}, 
> {{EVT_CLUSTER_DEACTIVATED}}, {{EVT_CLUSTER_ACTIVATION_FAILED}} which will be 
> fired when corresponding steps are completed. The event should contain, if 
> possible, information about the activation source (public API or 
> auto-activation), topology version on which activation was performed. The 
> fail event should contain information about the cause of the failure. If 
> needed, a new class for this event should be introduced.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8197) ignite won't start with spring-boot 1.5.11 - h2 property NESTED_JOINS doesn't exist

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-8197:


As h2 is the core of ignite, so it should take every consideration into mind 
when do h2 upgrade.

for you case, you can simply to overwrite springboot's h2 version by add below 
to your pom

 


 1.4.195


 

> ignite won't start with spring-boot 1.5.11 - h2 property NESTED_JOINS doesn't 
> exist
> ---
>
> Key: IGNITE-8197
> URL: https://issues.apache.org/jira/browse/IGNITE-8197
> Project: Ignite
>  Issue Type: Bug
>Reporter: Scott Feldstein
>Priority: Major
> Attachments: spring-boot-ignite.zip
>
>
> I just upgraded to spring-boot 1.5.11 and am seeing the error below. I think 
> this is an issue with the version of h2 associated with spring boot 1.5.11. 
> In 1.5.10 the h2 version was 1.4.196 and with 1.5.11 it is 1.4.197. The 
> NESTED_JOINS property comes from 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing, i assume it 
> was deprecated but not sure. When I lock in my h2 version to 1.4.196 by 
> overriding the spring-dependencies parent everything works fine
> {code:java}
> Caused by: org.h2.jdbc.JdbcSQLException: Unsupported connection setting 
> "NESTED_JOINS" [90113-197]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:357) 
> ~[h2-1.4.197.jar:1.4.197]
> at org.h2.message.DbException.get(DbException.java:179) 
> ~[h2-1.4.197.jar:1.4.197]
> at org.h2.message.DbException.get(DbException.java:155) 
> ~[h2-1.4.197.jar:1.4.197]
> at org.h2.engine.ConnectionInfo.readSettingsFromURL(ConnectionInfo.java:268) 
> ~[h2-1.4.197.jar:1.4.197]
> at org.h2.engine.ConnectionInfo.(ConnectionInfo.java:76) 
> ~[h2-1.4.197.jar:1.4.197]
> at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:103) 
> ~[h2-1.4.197.jar:1.4.197]
> at org.h2.Driver.connect(Driver.java:69) ~[h2-1.4.197.jar:1.4.197]
> at java.sql.DriverManager.getConnection(DriverManager.java:664) ~[?:1.8.0_131]
> at java.sql.DriverManager.getConnection(DriverManager.java:270) ~[?:1.8.0_131]
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$1.initialValue(IgniteH2Indexing.java:317)
>  ~[ignite-indexing-2.4.0.jar:2.4.0]
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$1.initialValue(IgniteH2Indexing.java:288)
>  ~[ignite-indexing-2.4.0.jar:2.4.0]
> at java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:180) ~[?:1.8.0_131]
> at java.lang.ThreadLocal.get(ThreadLocal.java:170) ~[?:1.8.0_131]
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$1.get(IgniteH2Indexing.java:290)
>  ~[ignite-indexing-2.4.0.jar:2.4.0]
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$1.get(IgniteH2Indexing.java:288)
>  ~[ignite-indexing-2.4.0.jar:2.4.0]
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(IgniteH2Indexing.java:514)
>  ~[ignite-indexing-2.4.0.jar:2.4.0]
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeStatement(IgniteH2Indexing.java:582)
>  ~[ignite-indexing-2.4.0.jar:2.4.0]
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createSchema(IgniteH2Indexing.java:551)
>  ~[ignite-indexing-2.4.0.jar:2.4.0]
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerCache(IgniteH2Indexing.java:2667)
>  ~[ignite-indexing-2.4.0.jar:2.4.0]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.registerCache0(GridQueryProcessor.java:1594)
>  ~[ignite-core-2.4.0.jar:2.4.0]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:800)
>  ~[ignite-core-2.4.0.jar:2.4.0]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:861)
>  ~[ignite-core-2.4.0.jar:2.4.0]
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1158)
>  ~[ignite-core-2.4.0.jar:2.4.0]
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1900)
>  ~[ignite-core-2.4.0.jar:2.4.0]
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCachesOnLocalJoin(GridCacheProcessor.java:1764)
>  ~[ignite-core-2.4.0.jar:2.4.0]
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:744)
>  ~[ignite-core-2.4.0.jar:2.4.0]
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:626)
>  ~[ignite-core-2.4.0.jar:2.4.0]
> at 
> 

[jira] [Commented] (IGNITE-7093) Ignite compatibility test.jar does not builds

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-7093:


yeah, I run into this issue 
http://apache-ignite-developers.2346864.n4.nabble.com/Can-not-build-from-source-code-td24587.html#a24659

> Ignite compatibility test.jar does not builds
> -
>
> Key: IGNITE-7093
> URL: https://issues.apache.org/jira/browse/IGNITE-7093
> Project: Ignite
>  Issue Type: Bug
>Reporter: Oleg Ostanin
>Assignee: Oleg Ostanin
>
> Ignite compatibility test classes does not build into test.jar during package 
> phase. It may lead to a problem with test dependency.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-3204) java.lang.NoClassDefFoundError: org/h2/constant/SysProperties

[kcheng.mvp (JIRA)]

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

kcheng.mvp resolved IGNITE-3204.

Resolution: Invalid

> java.lang.NoClassDefFoundError: org/h2/constant/SysProperties
> -
>
> Key: IGNITE-3204
> URL: https://issues.apache.org/jira/browse/IGNITE-3204
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
>Reporter: kcheng.mvp
>
> Hi All,
> I ran into above issue. here is the error stack
> Caused by: java.lang.NoClassDefFoundError: org/h2/constant/SysProperties
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:1487)
>  ~[ignite-indexing-1.6.0.jar:1.6.0]
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:171)
>  ~[ignite-core-1.6.0.jar:1.6.0]
>   at 
> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1549)
>  ~[ignite-core-1.6.0.jar:1.6.0]
>   at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:869) 
> ~[ignite-core-1.6.0.jar:1.6.0]
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1736)
>  ~[ignite-core-1.6.0.jar:1.6.0]
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1589)
>  ~[ignite-core-1.6.0.jar:1.6.0]
>   at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1042) 
> ~[ignite-core-1.6.0.jar:1.6.0]
>   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:549) 
> ~[ignite-core-1.6.0.jar:1.6.0]
>   at org.apache.ignite.IgniteSpring.start(IgniteSpring.java:66) 
> ~[ignite-spring-1.6.0.jar:1.6.0]
>   at 
> org.apache.ignite.IgniteSpringBean.afterPropertiesSet(IgniteSpringBean.java:128)
>  ~[ignite-spring-1.6.0.jar:1.6.0]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1637)
>  ~[spring-beans-4.2.6.RELEASE.jar:4.2.6.RELEASE]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1574)
>  ~[spring-beans-4.2.6.RELEASE.jar:4.2.6.RELEASE]
>   ... 21 common frames omitted
> Caused by: java.lang.ClassNotFoundException: org.h2.constant.SysProperties
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381) 
> ~[na:1.8.0_77]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[na:1.8.0_77]
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) 
> ~[na:1.8.0_77]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[na:1.8.0_77]
> I am using v1.6.0
> 
> org.apache.ignite
> ignite-core
> ${ignite.version}
> 
> 
> org.apache.ignite
> ignite-spring
> ${ignite.version}
> 
> 
> org.apache.ignite
> ignite-indexing
> ${ignite.version}
> 
> below is the dependency tree
> [INFO] +- org.apache.ignite:ignite-core:jar:1.6.0:compile
> [INFO] |  +- javax.cache:cache-api:jar:1.0.0:compile
> [INFO] |  \- org.gridgain:ignite-shmem:jar:1.0.0:compile
> [INFO] +- org.apache.ignite:ignite-spring:jar:1.6.0:compile
> [INFO] |  +- org.springframework:spring-core:jar:4.2.6.RELEASE:compile
> [INFO] |  +- org.springframework:spring-aop:jar:4.2.6.RELEASE:compile
> [INFO] |  |  \- aopalliance:aopalliance:jar:1.0:compile
> [INFO] |  +- org.springframework:spring-beans:jar:4.2.6.RELEASE:compile
> [INFO] |  +- org.springframework:spring-context:jar:4.2.6.RELEASE:compile
> [INFO] |  +- org.springframework:spring-expression:jar:4.2.6.RELEASE:compile
> [INFO] |  +- org.springframework:spring-tx:jar:4.2.6.RELEASE:compile
> [INFO] |  +- org.springframework:spring-jdbc:jar:4.2.6.RELEASE:compile
> [INFO] |  \- commons-logging:commons-logging:jar:1.1.1:compile
> [INFO] \- org.apache.ignite:ignite-indexing:jar:1.6.0:compile
> [INFO]+- commons-codec:commons-codec:jar:1.6:compile
> [INFO]+- org.apache.lucene:lucene-core:jar:3.5.0:compile
> [INFO]\- com.h2database:h2:jar:1.4.191:compile
> I check there is no org/h2/constant/SysProperties, on the contrary 
> there is org.h2.engine.SysProperties



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

[jira] [Commented] (IGNITE-3204) java.lang.NoClassDefFoundError: org/h2/constant/SysProperties

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-3204:


oh, found the cause.

I am using spring-boot, and h2 1.4.191 inherit from it. I will close it.


org.springframework.boot
spring-boot-starter-parent
1.3.5.RELEASE




Thanks,
kcheng

On Thu, May 26, 2016 at 6:29 PM, Valentin Kulichenko (JIRA)  java.lang.NoClassDefFoundError: org/h2/constant/SysProperties
> -
>
> Key: IGNITE-3204
> URL: https://issues.apache.org/jira/browse/IGNITE-3204
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
>Reporter: kcheng.mvp
>
> Hi All,
> I ran into above issue. here is the error stack
> Caused by: java.lang.NoClassDefFoundError: org/h2/constant/SysProperties
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:1487)
>  ~[ignite-indexing-1.6.0.jar:1.6.0]
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:171)
>  ~[ignite-core-1.6.0.jar:1.6.0]
>   at 
> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1549)
>  ~[ignite-core-1.6.0.jar:1.6.0]
>   at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:869) 
> ~[ignite-core-1.6.0.jar:1.6.0]
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1736)
>  ~[ignite-core-1.6.0.jar:1.6.0]
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1589)
>  ~[ignite-core-1.6.0.jar:1.6.0]
>   at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1042) 
> ~[ignite-core-1.6.0.jar:1.6.0]
>   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:549) 
> ~[ignite-core-1.6.0.jar:1.6.0]
>   at org.apache.ignite.IgniteSpring.start(IgniteSpring.java:66) 
> ~[ignite-spring-1.6.0.jar:1.6.0]
>   at 
> org.apache.ignite.IgniteSpringBean.afterPropertiesSet(IgniteSpringBean.java:128)
>  ~[ignite-spring-1.6.0.jar:1.6.0]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1637)
>  ~[spring-beans-4.2.6.RELEASE.jar:4.2.6.RELEASE]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1574)
>  ~[spring-beans-4.2.6.RELEASE.jar:4.2.6.RELEASE]
>   ... 21 common frames omitted
> Caused by: java.lang.ClassNotFoundException: org.h2.constant.SysProperties
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381) 
> ~[na:1.8.0_77]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[na:1.8.0_77]
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) 
> ~[na:1.8.0_77]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[na:1.8.0_77]
> I am using v1.6.0
> 
> org.apache.ignite
> ignite-core
> ${ignite.version}
> 
> 
> org.apache.ignite
> ignite-spring
> ${ignite.version}
> 
> 
> org.apache.ignite
> ignite-indexing
> ${ignite.version}
> 
> below is the dependency tree
> [INFO] +- org.apache.ignite:ignite-core:jar:1.6.0:compile
> [INFO] |  +- javax.cache:cache-api:jar:1.0.0:compile
> [INFO] |  \- org.gridgain:ignite-shmem:jar:1.0.0:compile
> [INFO] +- org.apache.ignite:ignite-spring:jar:1.6.0:compile
> [INFO] |  +- org.springframework:spring-core:jar:4.2.6.RELEASE:compile
> [INFO] |  +- org.springframework:spring-aop:jar:4.2.6.RELEASE:compile
> [INFO] |  |  \- aopalliance:aopalliance:jar:1.0:compile
> [INFO] |  +- org.springframework:spring-beans:jar:4.2.6.RELEASE:compile
> [INFO] |  +- org.springframework:spring-context:jar:4.2.6.RELEASE:compile
> [INFO] |  +- org.springframework:spring-expression:jar:4.2.6.RELEASE:compile
> [INFO] |  +- org.springframework:spring-tx:jar:4.2.6.RELEASE:compile
> [INFO] |  +- org.springframework:spring-jdbc:jar:4.2.6.RELEASE:compile
> [INFO] |  \- commons-logging:commons-logging:jar:1.1.1:compile
> [INFO] \- org.apache.ignite:ignite-indexing:jar:1.6.0:compile
> [INFO]+- commons-codec:commons-codec:jar:1.6:compile
> [INFO]+- org.apache.lucene:lucene-core:jar:3.5.0:compile
> [INFO]\- com.h2database:h2:jar:1.4.191:compile
> I check there is no org/h2/constant/SysProperties, on the contrary 
> there is org.h2.engine.SysProperties



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

[jira] [Commented] (IGNITE-3204) java.lang.NoClassDefFoundError: org/h2/constant/SysProperties

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-3204:


oh, found the cause.

I am using spring-boot, and h2 1.4.191 inherit from it. I will close it.

org.springframework.boot
spring-boot-starter-parent
1.3.5.RELEASE




> java.lang.NoClassDefFoundError: org/h2/constant/SysProperties
> -
>
> Key: IGNITE-3204
> URL: https://issues.apache.org/jira/browse/IGNITE-3204
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
>Reporter: kcheng.mvp
>
> Hi All,
> I ran into above issue. here is the error stack
> Caused by: java.lang.NoClassDefFoundError: org/h2/constant/SysProperties
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:1487)
>  ~[ignite-indexing-1.6.0.jar:1.6.0]
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:171)
>  ~[ignite-core-1.6.0.jar:1.6.0]
>   at 
> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1549)
>  ~[ignite-core-1.6.0.jar:1.6.0]
>   at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:869) 
> ~[ignite-core-1.6.0.jar:1.6.0]
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1736)
>  ~[ignite-core-1.6.0.jar:1.6.0]
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1589)
>  ~[ignite-core-1.6.0.jar:1.6.0]
>   at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1042) 
> ~[ignite-core-1.6.0.jar:1.6.0]
>   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:549) 
> ~[ignite-core-1.6.0.jar:1.6.0]
>   at org.apache.ignite.IgniteSpring.start(IgniteSpring.java:66) 
> ~[ignite-spring-1.6.0.jar:1.6.0]
>   at 
> org.apache.ignite.IgniteSpringBean.afterPropertiesSet(IgniteSpringBean.java:128)
>  ~[ignite-spring-1.6.0.jar:1.6.0]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1637)
>  ~[spring-beans-4.2.6.RELEASE.jar:4.2.6.RELEASE]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1574)
>  ~[spring-beans-4.2.6.RELEASE.jar:4.2.6.RELEASE]
>   ... 21 common frames omitted
> Caused by: java.lang.ClassNotFoundException: org.h2.constant.SysProperties
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381) 
> ~[na:1.8.0_77]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[na:1.8.0_77]
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) 
> ~[na:1.8.0_77]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[na:1.8.0_77]
> I am using v1.6.0
> 
> org.apache.ignite
> ignite-core
> ${ignite.version}
> 
> 
> org.apache.ignite
> ignite-spring
> ${ignite.version}
> 
> 
> org.apache.ignite
> ignite-indexing
> ${ignite.version}
> 
> below is the dependency tree
> [INFO] +- org.apache.ignite:ignite-core:jar:1.6.0:compile
> [INFO] |  +- javax.cache:cache-api:jar:1.0.0:compile
> [INFO] |  \- org.gridgain:ignite-shmem:jar:1.0.0:compile
> [INFO] +- org.apache.ignite:ignite-spring:jar:1.6.0:compile
> [INFO] |  +- org.springframework:spring-core:jar:4.2.6.RELEASE:compile
> [INFO] |  +- org.springframework:spring-aop:jar:4.2.6.RELEASE:compile
> [INFO] |  |  \- aopalliance:aopalliance:jar:1.0:compile
> [INFO] |  +- org.springframework:spring-beans:jar:4.2.6.RELEASE:compile
> [INFO] |  +- org.springframework:spring-context:jar:4.2.6.RELEASE:compile
> [INFO] |  +- org.springframework:spring-expression:jar:4.2.6.RELEASE:compile
> [INFO] |  +- org.springframework:spring-tx:jar:4.2.6.RELEASE:compile
> [INFO] |  +- org.springframework:spring-jdbc:jar:4.2.6.RELEASE:compile
> [INFO] |  \- commons-logging:commons-logging:jar:1.1.1:compile
> [INFO] \- org.apache.ignite:ignite-indexing:jar:1.6.0:compile
> [INFO]+- commons-codec:commons-codec:jar:1.6:compile
> [INFO]+- org.apache.lucene:lucene-core:jar:3.5.0:compile
> [INFO]\- com.h2database:h2:jar:1.4.191:compile
> I check there is no org/h2/constant/SysProperties, on the contrary 
> there is org.h2.engine.SysProperties



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

[jira] [Updated] (IGNITE-3204) java.lang.NoClassDefFoundError: org/h2/constant/SysProperties

[kcheng.mvp (JIRA)]

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

kcheng.mvp updated IGNITE-3204:
---
Assignee: (was: kcheng.mvp)

> java.lang.NoClassDefFoundError: org/h2/constant/SysProperties
> -
>
> Key: IGNITE-3204
> URL: https://issues.apache.org/jira/browse/IGNITE-3204
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
>Reporter: kcheng.mvp
>
> Hi All,
> I ran into above issue. here is the error stack
> Caused by: java.lang.NoClassDefFoundError: org/h2/constant/SysProperties
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:1487)
>  ~[ignite-indexing-1.6.0.jar:1.6.0]
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:171)
>  ~[ignite-core-1.6.0.jar:1.6.0]
>   at 
> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1549)
>  ~[ignite-core-1.6.0.jar:1.6.0]
>   at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:869) 
> ~[ignite-core-1.6.0.jar:1.6.0]
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1736)
>  ~[ignite-core-1.6.0.jar:1.6.0]
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1589)
>  ~[ignite-core-1.6.0.jar:1.6.0]
>   at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1042) 
> ~[ignite-core-1.6.0.jar:1.6.0]
>   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:549) 
> ~[ignite-core-1.6.0.jar:1.6.0]
>   at org.apache.ignite.IgniteSpring.start(IgniteSpring.java:66) 
> ~[ignite-spring-1.6.0.jar:1.6.0]
>   at 
> org.apache.ignite.IgniteSpringBean.afterPropertiesSet(IgniteSpringBean.java:128)
>  ~[ignite-spring-1.6.0.jar:1.6.0]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1637)
>  ~[spring-beans-4.2.6.RELEASE.jar:4.2.6.RELEASE]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1574)
>  ~[spring-beans-4.2.6.RELEASE.jar:4.2.6.RELEASE]
>   ... 21 common frames omitted
> Caused by: java.lang.ClassNotFoundException: org.h2.constant.SysProperties
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381) 
> ~[na:1.8.0_77]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[na:1.8.0_77]
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) 
> ~[na:1.8.0_77]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[na:1.8.0_77]
> I am using v1.6.0
> 
> org.apache.ignite
> ignite-core
> ${ignite.version}
> 
> 
> org.apache.ignite
> ignite-spring
> ${ignite.version}
> 
> 
> org.apache.ignite
> ignite-indexing
> ${ignite.version}
> 
> below is the dependency tree
> [INFO] +- org.apache.ignite:ignite-core:jar:1.6.0:compile
> [INFO] |  +- javax.cache:cache-api:jar:1.0.0:compile
> [INFO] |  \- org.gridgain:ignite-shmem:jar:1.0.0:compile
> [INFO] +- org.apache.ignite:ignite-spring:jar:1.6.0:compile
> [INFO] |  +- org.springframework:spring-core:jar:4.2.6.RELEASE:compile
> [INFO] |  +- org.springframework:spring-aop:jar:4.2.6.RELEASE:compile
> [INFO] |  |  \- aopalliance:aopalliance:jar:1.0:compile
> [INFO] |  +- org.springframework:spring-beans:jar:4.2.6.RELEASE:compile
> [INFO] |  +- org.springframework:spring-context:jar:4.2.6.RELEASE:compile
> [INFO] |  +- org.springframework:spring-expression:jar:4.2.6.RELEASE:compile
> [INFO] |  +- org.springframework:spring-tx:jar:4.2.6.RELEASE:compile
> [INFO] |  +- org.springframework:spring-jdbc:jar:4.2.6.RELEASE:compile
> [INFO] |  \- commons-logging:commons-logging:jar:1.1.1:compile
> [INFO] \- org.apache.ignite:ignite-indexing:jar:1.6.0:compile
> [INFO]+- commons-codec:commons-codec:jar:1.6:compile
> [INFO]+- org.apache.lucene:lucene-core:jar:3.5.0:compile
> [INFO]\- com.h2database:h2:jar:1.4.191:compile
> I check there is no org/h2/constant/SysProperties, on the contrary 
> there is org.h2.engine.SysProperties



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

[jira] [Created] (IGNITE-3204) java.lang.NoClassDefFoundError: org/h2/constant/SysProperties

[kcheng.mvp (JIRA)]

kcheng.mvp created IGNITE-3204:
--

 Summary: java.lang.NoClassDefFoundError: 
org/h2/constant/SysProperties
 Key: IGNITE-3204
 URL: https://issues.apache.org/jira/browse/IGNITE-3204
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.6
Reporter: kcheng.mvp
Assignee: kcheng.mvp


Hi All,

I ran into above issue. here is the error stack


Caused by: java.lang.NoClassDefFoundError: org/h2/constant/SysProperties
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:1487)
 ~[ignite-indexing-1.6.0.jar:1.6.0]
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:171)
 ~[ignite-core-1.6.0.jar:1.6.0]
at 
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1549) 
~[ignite-core-1.6.0.jar:1.6.0]
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:869) 
~[ignite-core-1.6.0.jar:1.6.0]
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1736)
 ~[ignite-core-1.6.0.jar:1.6.0]
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1589)
 ~[ignite-core-1.6.0.jar:1.6.0]
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1042) 
~[ignite-core-1.6.0.jar:1.6.0]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:549) 
~[ignite-core-1.6.0.jar:1.6.0]
at org.apache.ignite.IgniteSpring.start(IgniteSpring.java:66) 
~[ignite-spring-1.6.0.jar:1.6.0]
at 
org.apache.ignite.IgniteSpringBean.afterPropertiesSet(IgniteSpringBean.java:128)
 ~[ignite-spring-1.6.0.jar:1.6.0]
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1637)
 ~[spring-beans-4.2.6.RELEASE.jar:4.2.6.RELEASE]
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1574)
 ~[spring-beans-4.2.6.RELEASE.jar:4.2.6.RELEASE]
... 21 common frames omitted
Caused by: java.lang.ClassNotFoundException: org.h2.constant.SysProperties
at java.net.URLClassLoader.findClass(URLClassLoader.java:381) 
~[na:1.8.0_77]
at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[na:1.8.0_77]
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) 
~[na:1.8.0_77]
at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[na:1.8.0_77]


I am using v1.6.0


org.apache.ignite
ignite-core
${ignite.version}


org.apache.ignite
ignite-spring
${ignite.version}


org.apache.ignite
ignite-indexing
${ignite.version}


below is the dependency tree
[INFO] +- org.apache.ignite:ignite-core:jar:1.6.0:compile
[INFO] |  +- javax.cache:cache-api:jar:1.0.0:compile
[INFO] |  \- org.gridgain:ignite-shmem:jar:1.0.0:compile
[INFO] +- org.apache.ignite:ignite-spring:jar:1.6.0:compile
[INFO] |  +- org.springframework:spring-core:jar:4.2.6.RELEASE:compile
[INFO] |  +- org.springframework:spring-aop:jar:4.2.6.RELEASE:compile
[INFO] |  |  \- aopalliance:aopalliance:jar:1.0:compile
[INFO] |  +- org.springframework:spring-beans:jar:4.2.6.RELEASE:compile
[INFO] |  +- org.springframework:spring-context:jar:4.2.6.RELEASE:compile
[INFO] |  +- org.springframework:spring-expression:jar:4.2.6.RELEASE:compile
[INFO] |  +- org.springframework:spring-tx:jar:4.2.6.RELEASE:compile
[INFO] |  +- org.springframework:spring-jdbc:jar:4.2.6.RELEASE:compile
[INFO] |  \- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] \- org.apache.ignite:ignite-indexing:jar:1.6.0:compile
[INFO]+- commons-codec:commons-codec:jar:1.6:compile
[INFO]+- org.apache.lucene:lucene-core:jar:3.5.0:compile
[INFO]\- com.h2database:h2:jar:1.4.191:compile




I check there is no org/h2/constant/SysProperties, on the contrary 
there is org.h2.engine.SysProperties





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

[jira] [Assigned] (IGNITE-2997) Failed to get field because type ID of passed object differs from type ID this BinaryField

[kcheng.mvp (JIRA)]

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

kcheng.mvp reassigned IGNITE-2997:
--

Assignee: (was: kcheng.mvp)

> Failed to get field because type ID of passed object differs from type ID 
> this BinaryField
> --
>
> Key: IGNITE-2997
> URL: https://issues.apache.org/jira/browse/IGNITE-2997
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Vladislav Pyatkov
> Attachments: Main2.java
>
>
> I have got this exception when had been developing cache load benchmark.
> This exception reproduced in configuration of cache:
> {code}
> 
>
>
>
>
>
>
>   
>  java.lang.Integer
>  org.apache.ignite.yardstick.cache.model.Organization
>  java.lang.Integer
>  org.apache.ignite.yardstick.cache.model.Person
>   
>
> 
> {code}
> {noformat}
> [18:00:39,708][ERROR][benchmark-worker-43][GridDhtAtomicCache] 
>  Unexpected exception during cache update
> class org.apache.ignite.binary.BinaryObjectException: Failed to get field 
> because type ID of passed object differs from type ID this BinaryField 
> belongs to [expected=-865473396, actual=1199651114]
>   at 
> org.apache.ignite.internal.binary.BinaryFieldImpl.fieldOrder(BinaryFieldImpl.java:92)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldImpl.value(BinaryFieldImpl.java:79)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$BinaryProperty.fieldValue(GridQueryProcessor.java:2051)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$BinaryProperty.value(GridQueryProcessor.java:2011)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$RowDescriptor.columnValue(IgniteH2Indexing.java:2498)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:289)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2IndexBase.compareRows(GridH2IndexBase.java:116)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:248)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:49)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1350)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1346)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2102)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> 

[jira] [Assigned] (IGNITE-2997) Failed to get field because type ID of passed object differs from type ID this BinaryField

[kcheng.mvp (JIRA)]

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

kcheng.mvp reassigned IGNITE-2997:
--

Assignee: kcheng.mvp

> Failed to get field because type ID of passed object differs from type ID 
> this BinaryField
> --
>
> Key: IGNITE-2997
> URL: https://issues.apache.org/jira/browse/IGNITE-2997
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Vladislav Pyatkov
>Assignee: kcheng.mvp
> Attachments: Main2.java
>
>
> I have got this exception when had been developing cache load benchmark.
> This exception reproduced in configuration of cache:
> {code}
> 
>
>
>
>
>
>
>   
>  java.lang.Integer
>  org.apache.ignite.yardstick.cache.model.Organization
>  java.lang.Integer
>  org.apache.ignite.yardstick.cache.model.Person
>   
>
> 
> {code}
> {noformat}
> [18:00:39,708][ERROR][benchmark-worker-43][GridDhtAtomicCache] 
>  Unexpected exception during cache update
> class org.apache.ignite.binary.BinaryObjectException: Failed to get field 
> because type ID of passed object differs from type ID this BinaryField 
> belongs to [expected=-865473396, actual=1199651114]
>   at 
> org.apache.ignite.internal.binary.BinaryFieldImpl.fieldOrder(BinaryFieldImpl.java:92)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldImpl.value(BinaryFieldImpl.java:79)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$BinaryProperty.fieldValue(GridQueryProcessor.java:2051)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$BinaryProperty.value(GridQueryProcessor.java:2011)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$RowDescriptor.columnValue(IgniteH2Indexing.java:2498)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:289)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2IndexBase.compareRows(GridH2IndexBase.java:116)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:248)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:49)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1350)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1346)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2102)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2217)
>   at 
> 

[jira] [Assigned] (IGNITE-1248) Add a method to retrieve Spring application context

[kcheng.mvp (JIRA)]

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

kcheng.mvp reassigned IGNITE-1248:
--

Assignee: (was: kcheng.mvp)

> Add a method to retrieve Spring application context
> ---
>
> Key: IGNITE-1248
> URL: https://issues.apache.org/jira/browse/IGNITE-1248
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>
> Currently there is a way to inject application context instance into task, 
> closure, cache store using {{@SpringApplicationContextResource}} annotation. 
> But there is no way to get context associated with an {{Ignite}} instance 
> from user code.



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

[jira] [Assigned] (IGNITE-1069) Need to add information about node's type:server or client (visorcmd)

[kcheng.mvp (JIRA)]

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

kcheng.mvp reassigned IGNITE-1069:
--

Assignee: kcheng.mvp

> Need to add information about node's type:server or client (visorcmd)
> -
>
> Key: IGNITE-1069
> URL: https://issues.apache.org/jira/browse/IGNITE-1069
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Affects Versions: sprint-7
> Environment: OS X 10.10.3
> jdk1.7.0_79
>Reporter: Ilya Suntsov
>Assignee: kcheng.mvp
> Fix For: 1.6
>
>
> Steps for reproduction:
> 1. Start one server node and two clients
> 1. Start ignitevisorcmd.sh 
> 2. Connect to grid (open)
> 3. Print topology (top)
> Results:
> {noformat}
> top
> Hosts: 1
> ++
> |  Int./Ext. IPs  |   Node ID8(@)|   OS   
>  | CPUs |   MACs| CPU Load |
> ++
> | 2001:db8:85a3:0:0:8a2e:370:7334 | 1: 9D4F0AC0(@n0) | Mac OS X x86_64 
> 10.10.3 | 8| 10:40:F3:A7:6A:B6 | 0.16 %   |
> | 192.168.3.7 | 2: 6D746DAC(@n1) |
>  |  |   |  |
> | 0:0:0:0:0:0:0:1 | 3: A496C669(@n2) |
>  |  |   |  |
> | 127.0.0.1   |  |
>  |  |   |  |
> ++
> Summary:
> +-+
> | Total hosts| 1  |
> | Total nodes| 3  |
> | Total CPUs | 8  |
> | Avg. CPU load  | 0.16 % |
> | Avg. free heap | 80.00 %|
> | Avg. Up time   | 00:02:44   |
> | Snapshot time  | 07/01/15, 17:59:14 |
> +-+
> {noformat}
> I think here we should print node's types in order to know how many in a 
> topology of servers and how many clients



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

[jira] [Assigned] (IGNITE-1505) Error on stopping cache in visorcmd

[kcheng.mvp (JIRA)]

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

kcheng.mvp reassigned IGNITE-1505:
--

Assignee: kcheng.mvp

> Error on stopping cache in visorcmd
> ---
>
> Key: IGNITE-1505
> URL: https://issues.apache.org/jira/browse/IGNITE-1505
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: kcheng.mvp
>Priority: Minor
> Attachments: screenshot-1.png
>
>
> I'm start my tester and trying to stop cache created only on one node and got
> {code}
> visor> cache -stop
> Time of the snapshot: 09/18/15, 13:31:40
> +===+
> | # |   Name(@)   |Mode | Size  |
> +===+
> | 0 | c_partitioned3(@c4) | PARTITIONED | min: 0|
> |   | | | avg: 1.50 |
> |   | | | max: 3|
> +---+-+-+---+
> | 1 | c_replicated(@c5)   | REPLICATED  | min: 0|
> |   | | | avg: 8121.00  |
> |   | | | max: 10828|
> +---+-+-+---+
> | 2 | dcp_1(@c6)  | PARTITIONED | min: 0|
> |   | | | avg: 2700.00  |
> |   | | | max: 3773 |
> +---+-+-+---+
> | 3 | dcp_2(@c7)  | PARTITIONED | min: 2496 |
> |   | | | avg: 2672.00  |
> |   | | | max: 2809 |
> +---+-+-+---+
> | 4 | dcr_1(@c8)  | REPLICATED  | min: 0|
> |   | | | avg: 8075.50  |
> |   | | | max: 10768|
> +---+-+-+---+
> | 5 | dcr_2(@c9)  | REPLICATED  | min: 0|
> |   | | | avg: 8039.75  |
> |   | | | max: 10720|
> +---+-+-+---+
> | 6 | local-nid(@c10) | LOCAL   | min: 10792|
> |   | | | avg: 10792.00 |
> |   | | | max: 10792|
> +---+
> Choose cache number ('c' to cancel) [c]: 6
> java.lang.IllegalArgumentException: Ouch! Argument is invalid: ids must not 
> be empty.
> at 
> org.apache.ignite.internal.util.GridArgumentCheck.notEmpty(GridArgumentCheck.java:122)
> at 
> org.apache.ignite.internal.cluster.ClusterGroupAdapter.forNodeIds(ClusterGroupAdapter.java:481)
> at org.apache.ignite.visor.visor$.groupForDataNode(visor.scala:272)
> at 
> org.apache.ignite.visor.commands.cache.VisorCacheStopCommand.scan(VisorCacheStopCommand.scala:96)
> at 
> org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$cache$1.apply(VisorCacheCommand.scala:284)
> at 
> org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$cache$1.apply(VisorCacheCommand.scala:274)
> at scala.Option.foreach(Option.scala:245)
> at 
> org.apache.ignite.visor.commands.cache.VisorCacheCommand.cache(VisorCacheCommand.scala:274)
> at 
> org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$20.apply(VisorCacheCommand.scala:783)
> at 
> org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$20.apply(VisorCacheCommand.scala:783)
> at 
> org.apache.ignite.visor.commands.VisorConsole.mainLoop(VisorConsole.scala:214)
> at 
> org.apache.ignite.visor.commands.VisorConsole$.delayedEndpoint$org$apache$ignite$visor$commands$VisorConsole$1(VisorConsole.scala:326)
> at 
> org.apache.ignite.visor.commands.VisorConsole$delayedInit$body.apply(VisorConsole.scala:315)
> at scala.Function0$class.apply$mcV$sp(Function0.scala:40)
> at 
> scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12)
> at scala.App$$anonfun$main$1.apply(App.scala:76)
> at scala.App$$anonfun$main$1.apply(App.scala:76)
> at scala.collection.immutable.List.foreach(List.scala:381)
> at 
> scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:35)
> at scala.App$class.main(App.scala:76)
> at 
> org.apache.ignite.visor.commands.VisorConsole$.main(VisorConsole.scala:315)
> at 
> org.apache.ignite.visor.commands.VisorConsole.main(VisorConsole.scala)
> {code}



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

[jira] [Commented] (IGNITE-1505) Error on stopping cache in visorcmd

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-1505:


[~pkonstantinov]


Please see the attachment, test with the latest source code, can not reproduce 
it.

> Error on stopping cache in visorcmd
> ---
>
> Key: IGNITE-1505
> URL: https://issues.apache.org/jira/browse/IGNITE-1505
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Priority: Minor
> Attachments: screenshot-1.png
>
>
> I'm start my tester and trying to stop cache created only on one node and got
> {code}
> visor> cache -stop
> Time of the snapshot: 09/18/15, 13:31:40
> +===+
> | # |   Name(@)   |Mode | Size  |
> +===+
> | 0 | c_partitioned3(@c4) | PARTITIONED | min: 0|
> |   | | | avg: 1.50 |
> |   | | | max: 3|
> +---+-+-+---+
> | 1 | c_replicated(@c5)   | REPLICATED  | min: 0|
> |   | | | avg: 8121.00  |
> |   | | | max: 10828|
> +---+-+-+---+
> | 2 | dcp_1(@c6)  | PARTITIONED | min: 0|
> |   | | | avg: 2700.00  |
> |   | | | max: 3773 |
> +---+-+-+---+
> | 3 | dcp_2(@c7)  | PARTITIONED | min: 2496 |
> |   | | | avg: 2672.00  |
> |   | | | max: 2809 |
> +---+-+-+---+
> | 4 | dcr_1(@c8)  | REPLICATED  | min: 0|
> |   | | | avg: 8075.50  |
> |   | | | max: 10768|
> +---+-+-+---+
> | 5 | dcr_2(@c9)  | REPLICATED  | min: 0|
> |   | | | avg: 8039.75  |
> |   | | | max: 10720|
> +---+-+-+---+
> | 6 | local-nid(@c10) | LOCAL   | min: 10792|
> |   | | | avg: 10792.00 |
> |   | | | max: 10792|
> +---+
> Choose cache number ('c' to cancel) [c]: 6
> java.lang.IllegalArgumentException: Ouch! Argument is invalid: ids must not 
> be empty.
> at 
> org.apache.ignite.internal.util.GridArgumentCheck.notEmpty(GridArgumentCheck.java:122)
> at 
> org.apache.ignite.internal.cluster.ClusterGroupAdapter.forNodeIds(ClusterGroupAdapter.java:481)
> at org.apache.ignite.visor.visor$.groupForDataNode(visor.scala:272)
> at 
> org.apache.ignite.visor.commands.cache.VisorCacheStopCommand.scan(VisorCacheStopCommand.scala:96)
> at 
> org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$cache$1.apply(VisorCacheCommand.scala:284)
> at 
> org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$cache$1.apply(VisorCacheCommand.scala:274)
> at scala.Option.foreach(Option.scala:245)
> at 
> org.apache.ignite.visor.commands.cache.VisorCacheCommand.cache(VisorCacheCommand.scala:274)
> at 
> org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$20.apply(VisorCacheCommand.scala:783)
> at 
> org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$20.apply(VisorCacheCommand.scala:783)
> at 
> org.apache.ignite.visor.commands.VisorConsole.mainLoop(VisorConsole.scala:214)
> at 
> org.apache.ignite.visor.commands.VisorConsole$.delayedEndpoint$org$apache$ignite$visor$commands$VisorConsole$1(VisorConsole.scala:326)
> at 
> org.apache.ignite.visor.commands.VisorConsole$delayedInit$body.apply(VisorConsole.scala:315)
> at scala.Function0$class.apply$mcV$sp(Function0.scala:40)
> at 
> scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12)
> at scala.App$$anonfun$main$1.apply(App.scala:76)
> at scala.App$$anonfun$main$1.apply(App.scala:76)
> at scala.collection.immutable.List.foreach(List.scala:381)
> at 
> scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:35)
> at scala.App$class.main(App.scala:76)
> at 
> org.apache.ignite.visor.commands.VisorConsole$.main(VisorConsole.scala:315)
> at 
> org.apache.ignite.visor.commands.VisorConsole.main(VisorConsole.scala)
> {code}



--
This message 

[jira] [Updated] (IGNITE-1505) Error on stopping cache in visorcmd

[kcheng.mvp (JIRA)]

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

kcheng.mvp updated IGNITE-1505:
---
Attachment: screenshot-1.png

> Error on stopping cache in visorcmd
> ---
>
> Key: IGNITE-1505
> URL: https://issues.apache.org/jira/browse/IGNITE-1505
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Priority: Minor
> Attachments: screenshot-1.png
>
>
> I'm start my tester and trying to stop cache created only on one node and got
> {code}
> visor> cache -stop
> Time of the snapshot: 09/18/15, 13:31:40
> +===+
> | # |   Name(@)   |Mode | Size  |
> +===+
> | 0 | c_partitioned3(@c4) | PARTITIONED | min: 0|
> |   | | | avg: 1.50 |
> |   | | | max: 3|
> +---+-+-+---+
> | 1 | c_replicated(@c5)   | REPLICATED  | min: 0|
> |   | | | avg: 8121.00  |
> |   | | | max: 10828|
> +---+-+-+---+
> | 2 | dcp_1(@c6)  | PARTITIONED | min: 0|
> |   | | | avg: 2700.00  |
> |   | | | max: 3773 |
> +---+-+-+---+
> | 3 | dcp_2(@c7)  | PARTITIONED | min: 2496 |
> |   | | | avg: 2672.00  |
> |   | | | max: 2809 |
> +---+-+-+---+
> | 4 | dcr_1(@c8)  | REPLICATED  | min: 0|
> |   | | | avg: 8075.50  |
> |   | | | max: 10768|
> +---+-+-+---+
> | 5 | dcr_2(@c9)  | REPLICATED  | min: 0|
> |   | | | avg: 8039.75  |
> |   | | | max: 10720|
> +---+-+-+---+
> | 6 | local-nid(@c10) | LOCAL   | min: 10792|
> |   | | | avg: 10792.00 |
> |   | | | max: 10792|
> +---+
> Choose cache number ('c' to cancel) [c]: 6
> java.lang.IllegalArgumentException: Ouch! Argument is invalid: ids must not 
> be empty.
> at 
> org.apache.ignite.internal.util.GridArgumentCheck.notEmpty(GridArgumentCheck.java:122)
> at 
> org.apache.ignite.internal.cluster.ClusterGroupAdapter.forNodeIds(ClusterGroupAdapter.java:481)
> at org.apache.ignite.visor.visor$.groupForDataNode(visor.scala:272)
> at 
> org.apache.ignite.visor.commands.cache.VisorCacheStopCommand.scan(VisorCacheStopCommand.scala:96)
> at 
> org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$cache$1.apply(VisorCacheCommand.scala:284)
> at 
> org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$cache$1.apply(VisorCacheCommand.scala:274)
> at scala.Option.foreach(Option.scala:245)
> at 
> org.apache.ignite.visor.commands.cache.VisorCacheCommand.cache(VisorCacheCommand.scala:274)
> at 
> org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$20.apply(VisorCacheCommand.scala:783)
> at 
> org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$20.apply(VisorCacheCommand.scala:783)
> at 
> org.apache.ignite.visor.commands.VisorConsole.mainLoop(VisorConsole.scala:214)
> at 
> org.apache.ignite.visor.commands.VisorConsole$.delayedEndpoint$org$apache$ignite$visor$commands$VisorConsole$1(VisorConsole.scala:326)
> at 
> org.apache.ignite.visor.commands.VisorConsole$delayedInit$body.apply(VisorConsole.scala:315)
> at scala.Function0$class.apply$mcV$sp(Function0.scala:40)
> at 
> scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12)
> at scala.App$$anonfun$main$1.apply(App.scala:76)
> at scala.App$$anonfun$main$1.apply(App.scala:76)
> at scala.collection.immutable.List.foreach(List.scala:381)
> at 
> scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:35)
> at scala.App$class.main(App.scala:76)
> at 
> org.apache.ignite.visor.commands.VisorConsole$.main(VisorConsole.scala:315)
> at 
> org.apache.ignite.visor.commands.VisorConsole.main(VisorConsole.scala)
> {code}



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

[jira] [Commented] (IGNITE-1243) HTTP REST: top command returns wrong result

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-1243:


[~skozlov]
I have tested with the latest source code can not reproduce this issue. 
Thanks

> HTTP REST: top command returns wrong result 
> 
>
> Key: IGNITE-1243
> URL: https://issues.apache.org/jira/browse/IGNITE-1243
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
>
> HTTP REST: top command returns wrong result via a client node if all server 
> nodes left from topology: last server node is still in response.
> Steps to repeat
> 1. Create client node config: copy examples/config/example-ignite.xml to 
> examples/config/example-ignite-client.xml and set client mode:
> {code:title=examples/config/example-ignite-client.xml|borderStyle=solid}
> ...
>  class="org.apache.ignite.configuration.IgniteConfiguration">
> 
> 
> 
> ...
> {code}
> 2. Copy libs/optional/ignite-rest-http directory into libs
> 3. Start two server nodes with example-ignite.xml: 
> bin/ignite.sh examples/config/example-ignite.xml
> 4. Start client node with example-ignite-client.xml: 
> bin/ignite.sh examples/config/example-ignite.xml
> 5. Now all nodes should print out following topology:
> {noformat}
> Topology snapshot [ver=3, servers=2, clients=1, CPUs=8, heap=3.0GB]
> {noformat}
> 5. Open url http://127.0.0.1:8082/ignite?cmd=top in your browser
> The response should be following
> {noformat}
> {"error":"","response":[{"attributes":null,"caches":null,"consistentId":"0:0:0:0:0:0:0:1,10.0.0.9,127.0.0.1,192.168.222.100,2001:0:9d38:6ab8:188c:2ebf:a1b7:c399:47500","defaultCacheMode":"","metrics":null,"nodeId":"4e5b8efb-eab9-4d24-9a3b-52e88c3220ae","tcpAddresses":["127.0.0.1","2001:0:9d38:6ab8:188c:2ebf:a1b7:c399","192.168.222.100","0:0:0:0:0:0:0:1","10.0.0.9"],"tcpHostNames":["rr","rr","rr"],"tcpPort":11211},{"attributes":null,"caches":null,"consistentId":"0:0:0:0:0:0:0:1,10.0.0.9,127.0.0.1,192.168.222.100,2001:0:9d38:6ab8:188c:2ebf:a1b7:c399:47501","defaultCacheMode":"","metrics":null,"nodeId":"c5fd0979-4f28-4e26-a3f9-37a3af78005b","tcpAddresses":["0:0:0:0:0:0:0:1","2001:0:9d38:6ab8:188c:2ebf:a1b7:c399","192.168.222.100","10.0.0.9","127.0.0.1"],"tcpHostNames":["rr","rr","rr"],"tcpPort":11212},{"attributes":null,"caches":null,"consistentId":"0:0:0:0:0:0:0:1,10.0.0.9,127.0.0.1,192.168.222.100,2001:0:9d38:6ab8:188c:2ebf:a1b7:c399:0","defaultCacheMode":"","metrics":null,"nodeId":"07bbe0ae-b0fc-4536-b5d0-64bb748e38a2","tcpAddresses":["10.0.0.9","0:0:0:0:0:0:0:1","2001:0:9d38:6ab8:188c:2ebf:a1b7:c399","192.168.222.100","127.0.0.1"],"tcpHostNames":["rr","rr","rr"],"tcpPort":11213}],"sessionToken":"","successStatus":0}
> {noformat}
> Take a look on NodeID. There're same strings as node ids printed out in node 
> log (or on node console if node started with option -v):
> {noformat}
> {"error":"","response":[
> ..."nodeId":"4e5b8efb-eab9-4d24-9a3b-52e88c3220ae", 
> ..."nodeId":"c5fd0979-4f28-4e26-a3f9-37a3af78005b", 
> ..."nodeId":"07bbe0ae-b0fc-4536-b5d0-64bb748e38a2",
> ..."sessionToken":"","successStatus":0}
> {noformat}
> 6. Stop both server nodes and open the url 
> http://127.0.0.1:8082/ignite?cmd=top again:
> {noformat}
> {"error":"","response":[
> ..."nodeId":"c5fd0979-4f28-4e26-a3f9-37a3af78005b",
> ..."nodeId":"8d4c80da-3e64-43ff-aff0-112e45afa73f",],
> ..."sessionToken":"","successStatus":0}
> {noformat}
> First nodeid points out on disconnected server node, second one is 
> non-existing id and there's no client node id.



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

[jira] [Assigned] (IGNITE-1243) HTTP REST: top command returns wrong result

[kcheng.mvp (JIRA)]

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

kcheng.mvp reassigned IGNITE-1243:
--

Assignee: kcheng.mvp

> HTTP REST: top command returns wrong result 
> 
>
> Key: IGNITE-1243
> URL: https://issues.apache.org/jira/browse/IGNITE-1243
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: kcheng.mvp
>Priority: Minor
>  Labels: newbie
>
> HTTP REST: top command returns wrong result via a client node if all server 
> nodes left from topology: last server node is still in response.
> Steps to repeat
> 1. Create client node config: copy examples/config/example-ignite.xml to 
> examples/config/example-ignite-client.xml and set client mode:
> {code:title=examples/config/example-ignite-client.xml|borderStyle=solid}
> ...
>  class="org.apache.ignite.configuration.IgniteConfiguration">
> 
> 
> 
> ...
> {code}
> 2. Copy libs/optional/ignite-rest-http directory into libs
> 3. Start two server nodes with example-ignite.xml: 
> bin/ignite.sh examples/config/example-ignite.xml
> 4. Start client node with example-ignite-client.xml: 
> bin/ignite.sh examples/config/example-ignite.xml
> 5. Now all nodes should print out following topology:
> {noformat}
> Topology snapshot [ver=3, servers=2, clients=1, CPUs=8, heap=3.0GB]
> {noformat}
> 5. Open url http://127.0.0.1:8082/ignite?cmd=top in your browser
> The response should be following
> {noformat}
> {"error":"","response":[{"attributes":null,"caches":null,"consistentId":"0:0:0:0:0:0:0:1,10.0.0.9,127.0.0.1,192.168.222.100,2001:0:9d38:6ab8:188c:2ebf:a1b7:c399:47500","defaultCacheMode":"","metrics":null,"nodeId":"4e5b8efb-eab9-4d24-9a3b-52e88c3220ae","tcpAddresses":["127.0.0.1","2001:0:9d38:6ab8:188c:2ebf:a1b7:c399","192.168.222.100","0:0:0:0:0:0:0:1","10.0.0.9"],"tcpHostNames":["rr","rr","rr"],"tcpPort":11211},{"attributes":null,"caches":null,"consistentId":"0:0:0:0:0:0:0:1,10.0.0.9,127.0.0.1,192.168.222.100,2001:0:9d38:6ab8:188c:2ebf:a1b7:c399:47501","defaultCacheMode":"","metrics":null,"nodeId":"c5fd0979-4f28-4e26-a3f9-37a3af78005b","tcpAddresses":["0:0:0:0:0:0:0:1","2001:0:9d38:6ab8:188c:2ebf:a1b7:c399","192.168.222.100","10.0.0.9","127.0.0.1"],"tcpHostNames":["rr","rr","rr"],"tcpPort":11212},{"attributes":null,"caches":null,"consistentId":"0:0:0:0:0:0:0:1,10.0.0.9,127.0.0.1,192.168.222.100,2001:0:9d38:6ab8:188c:2ebf:a1b7:c399:0","defaultCacheMode":"","metrics":null,"nodeId":"07bbe0ae-b0fc-4536-b5d0-64bb748e38a2","tcpAddresses":["10.0.0.9","0:0:0:0:0:0:0:1","2001:0:9d38:6ab8:188c:2ebf:a1b7:c399","192.168.222.100","127.0.0.1"],"tcpHostNames":["rr","rr","rr"],"tcpPort":11213}],"sessionToken":"","successStatus":0}
> {noformat}
> Take a look on NodeID. There're same strings as node ids printed out in node 
> log (or on node console if node started with option -v):
> {noformat}
> {"error":"","response":[
> ..."nodeId":"4e5b8efb-eab9-4d24-9a3b-52e88c3220ae", 
> ..."nodeId":"c5fd0979-4f28-4e26-a3f9-37a3af78005b", 
> ..."nodeId":"07bbe0ae-b0fc-4536-b5d0-64bb748e38a2",
> ..."sessionToken":"","successStatus":0}
> {noformat}
> 6. Stop both server nodes and open the url 
> http://127.0.0.1:8082/ignite?cmd=top again:
> {noformat}
> {"error":"","response":[
> ..."nodeId":"c5fd0979-4f28-4e26-a3f9-37a3af78005b",
> ..."nodeId":"8d4c80da-3e64-43ff-aff0-112e45afa73f",],
> ..."sessionToken":"","successStatus":0}
> {noformat}
> First nodeid points out on disconnected server node, second one is 
> non-existing id and there's no client node id.



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

[jira] [Assigned] (IGNITE-472) Do not show system caches in visor console by default

[kcheng.mvp (JIRA)]

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

kcheng.mvp reassigned IGNITE-472:
-

Assignee: kcheng.mvp

> Do not show system caches in visor console by default
> -
>
> Key: IGNITE-472
> URL: https://issues.apache.org/jira/browse/IGNITE-472
> Project: Ignite
>  Issue Type: Task
>  Components: UI
>Affects Versions: sprint-2
>Reporter: Pavel Konstantinov
>Assignee: kcheng.mvp
>Priority: Minor
> Attachments: screenshot.png
>
>
> I think we need to add a special option like '-sys' to show system caches



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

[jira] [Commented] (IGNITE-1481) It is possible to configure local cache with affinity function

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-1481:


PR : https://github.com/apache/ignite/pull/617

> It is possible to configure local cache with affinity function
> --
>
> Key: IGNITE-1481
> URL: https://issues.apache.org/jira/browse/IGNITE-1481
> Project: Ignite
>  Issue Type: Bug
>  Components: newbie
>Reporter: Andrey Gura
>Assignee: kcheng.mvp
>  Labels: newbie
>
> {{LOCAL}} cache always uses {{GridCacheProcessor.LocalAffinityFunction}}.
> Durign configuration of local cache it is possible to pass other affinity 
> function to cache configuration. All cache operations will work correctly, 
> but user can obtain affinity manager that internally uses incorrect affinity 
> function ({{GridCacheContext.cctx.affinity().aff.aff}}).
> Expected behaviour: {{GridCacheContext.cctx.affinity().aff.aff}} always 
> refers to {{GridCacheProcessor.LocalAffinityFunction}} for {{LOCAL}} caches.



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

[jira] [Updated] (IGNITE-472) Do not show system caches in visor console by default

[kcheng.mvp (JIRA)]

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

kcheng.mvp updated IGNITE-472:
--
Attachment: screenshot.png

Describe how to turn on/off show/hide system cache.

> Do not show system caches in visor console by default
> -
>
> Key: IGNITE-472
> URL: https://issues.apache.org/jira/browse/IGNITE-472
> Project: Ignite
>  Issue Type: Task
>  Components: UI
>Affects Versions: sprint-2
>Reporter: Pavel Konstantinov
>Assignee: kcheng.mvp
>Priority: Minor
> Attachments: screenshot.png
>
>
> I think we need to add a special option like '-sys' to show system caches



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

[jira] [Commented] (IGNITE-472) Do not show system caches in visor console by default

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-472:
---

In fact there is a such option called "-system" to turn on/off show system 
cache, but the "help cache" command does not address this. 
Right now the  "cache" command would not show system cache by default. 

 

> Do not show system caches in visor console by default
> -
>
> Key: IGNITE-472
> URL: https://issues.apache.org/jira/browse/IGNITE-472
> Project: Ignite
>  Issue Type: Task
>  Components: UI
>Affects Versions: sprint-2
>Reporter: Pavel Konstantinov
>Assignee: kcheng.mvp
>Priority: Minor
>
> I think we need to add a special option like '-sys' to show system caches



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

[jira] [Assigned] (IGNITE-472) Do not show system caches in visor console by default

[kcheng.mvp (JIRA)]

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

kcheng.mvp reassigned IGNITE-472:
-

Assignee: kcheng.mvp

> Do not show system caches in visor console by default
> -
>
> Key: IGNITE-472
> URL: https://issues.apache.org/jira/browse/IGNITE-472
> Project: Ignite
>  Issue Type: Task
>  Components: UI
>Affects Versions: sprint-2
>Reporter: Pavel Konstantinov
>Assignee: kcheng.mvp
>Priority: Minor
>
> I think we need to add a special option like '-sys' to show system caches



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

[jira] [Commented] (IGNITE-1481) It is possible to configure local cache with affinity function

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-1481:


All the cases has passed in the teamcity
http://204.14.53.153/viewLog.html?buildId=223902=buildResultsDiv=IgniteTests_IgniteDataGrid

Please help to review, thanks

> It is possible to configure local cache with affinity function
> --
>
> Key: IGNITE-1481
> URL: https://issues.apache.org/jira/browse/IGNITE-1481
> Project: Ignite
>  Issue Type: Bug
>  Components: newbie
>Reporter: Andrey Gura
>Assignee: kcheng.mvp
>  Labels: newbie
>
> {{LOCAL}} cache always uses {{GridCacheProcessor.LocalAffinityFunction}}.
> Durign configuration of local cache it is possible to pass other affinity 
> function to cache configuration. All cache operations will work correctly, 
> but user can obtain affinity manager that internally uses incorrect affinity 
> function ({{GridCacheContext.cctx.affinity().aff.aff}}).
> Expected behaviour: {{GridCacheContext.cctx.affinity().aff.aff}} always 
> refers to {{GridCacheProcessor.LocalAffinityFunction}} for {{LOCAL}} caches.



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

[jira] [Assigned] (IGNITE-1069) Need to add information about node's type:server or client (visorcmd)

[kcheng.mvp (JIRA)]

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

kcheng.mvp reassigned IGNITE-1069:
--

Assignee: kcheng.mvp

> Need to add information about node's type:server or client (visorcmd)
> -
>
> Key: IGNITE-1069
> URL: https://issues.apache.org/jira/browse/IGNITE-1069
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Affects Versions: sprint-7
> Environment: OS X 10.10.3
> jdk1.7.0_79
>Reporter: Ilya Suntsov
>Assignee: kcheng.mvp
> Fix For: 1.6
>
>
> Steps for reproduction:
> 1. Start one server node and two clients
> 1. Start ignitevisorcmd.sh 
> 2. Connect to grid (open)
> 3. Print topology (top)
> Results:
> {noformat}
> top
> Hosts: 1
> ++
> |  Int./Ext. IPs  |   Node ID8(@)|   OS   
>  | CPUs |   MACs| CPU Load |
> ++
> | 2001:db8:85a3:0:0:8a2e:370:7334 | 1: 9D4F0AC0(@n0) | Mac OS X x86_64 
> 10.10.3 | 8| 10:40:F3:A7:6A:B6 | 0.16 %   |
> | 192.168.3.7 | 2: 6D746DAC(@n1) |
>  |  |   |  |
> | 0:0:0:0:0:0:0:1 | 3: A496C669(@n2) |
>  |  |   |  |
> | 127.0.0.1   |  |
>  |  |   |  |
> ++
> Summary:
> +-+
> | Total hosts| 1  |
> | Total nodes| 3  |
> | Total CPUs | 8  |
> | Avg. CPU load  | 0.16 % |
> | Avg. free heap | 80.00 %|
> | Avg. Up time   | 00:02:44   |
> | Snapshot time  | 07/01/15, 17:59:14 |
> +-+
> {noformat}
> I think here we should print node's types in order to know how many in a 
> topology of servers and how many clients



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

[jira] [Issue Comment Deleted] (IGNITE-1481) It is possible to configure local cache with affinity function

[kcheng.mvp (JIRA)]

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

kcheng.mvp updated IGNITE-1481:
---
Comment: was deleted

(was: I checked the latest code, seems some did the fix. if so can we close 
this jira?)

> It is possible to configure local cache with affinity function
> --
>
> Key: IGNITE-1481
> URL: https://issues.apache.org/jira/browse/IGNITE-1481
> Project: Ignite
>  Issue Type: Bug
>  Components: newbie
>Reporter: Andrey Gura
>Assignee: kcheng.mvp
>  Labels: newbie
>
> {{LOCAL}} cache always uses {{GridCacheProcessor.LocalAffinityFunction}}.
> Durign configuration of local cache it is possible to pass other affinity 
> function to cache configuration. All cache operations will work correctly, 
> but user can obtain affinity manager that internally uses incorrect affinity 
> function ({{GridCacheContext.cctx.affinity().aff.aff}}).
> Expected behaviour: {{GridCacheContext.cctx.affinity().aff.aff}} always 
> refers to {{GridCacheProcessor.LocalAffinityFunction}} for {{LOCAL}} caches.



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

[jira] [Commented] (IGNITE-1481) It is possible to configure local cache with affinity function

[kcheng.mvp (JIRA)]

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

kcheng.mvp commented on IGNITE-1481:


I checked the latest code, seems some did the fix. if so can we close this jira?

> It is possible to configure local cache with affinity function
> --
>
> Key: IGNITE-1481
> URL: https://issues.apache.org/jira/browse/IGNITE-1481
> Project: Ignite
>  Issue Type: Bug
>  Components: newbie
>Reporter: Andrey Gura
>Assignee: kcheng.mvp
>  Labels: newbie
>
> {{LOCAL}} cache always uses {{GridCacheProcessor.LocalAffinityFunction}}.
> Durign configuration of local cache it is possible to pass other affinity 
> function to cache configuration. All cache operations will work correctly, 
> but user can obtain affinity manager that internally uses incorrect affinity 
> function ({{GridCacheContext.cctx.affinity().aff.aff}}).
> Expected behaviour: {{GridCacheContext.cctx.affinity().aff.aff}} always 
> refers to {{GridCacheProcessor.LocalAffinityFunction}} for {{LOCAL}} caches.



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