[jira] [Commented] (IGNITE-2450) Proxy classes are not serialized properly using OptimizedMarshaller and BinaryMarshaller
[
https://issues.apache.org/jira/browse/IGNITE-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15166750#comment-15166750
]
Valentin Kulichenko commented on IGNITE-2450:
-
Calling {{toBinary()}} for Proxy ends up in exception:
{noformat}
Exception in thread "main" class
org.apache.ignite.binary.BinaryObjectException: Invalid flag value: 35
at
org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:1765)
at
org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:1597)
at
org.apache.ignite.internal.binary.BinaryUtils.unmarshal(BinaryUtils.java:1588)
at
org.apache.ignite.internal.binary.GridBinaryMarshaller.unmarshal(GridBinaryMarshaller.java:254)
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.marshalToBinary(CacheObjectBinaryProcessorImpl.java:519)
at
org.apache.ignite.internal.processors.cache.binary.IgniteBinaryImpl.toBinary(IgniteBinaryImpl.java:67)
{noformat}
> Proxy classes are not serialized properly using OptimizedMarshaller and
> BinaryMarshaller
>
>
> Key: IGNITE-2450
> URL: https://issues.apache.org/jira/browse/IGNITE-2450
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: ignite-1.4, 1.5.0.final
> Environment: Ubuntu 12.04 64 bit
> java version "1.8.0_60"
> Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
> Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
> Ignite 1.4.0
>Reporter: Avihai Berkovitz
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: community, important
> Fix For: 1.6
>
> Attachments: master_500bd3a_ignite-2450.patch
>
>
> I tried to deploy several services using Java's Proxy class, to dynamically
> define the needed interfaces. When using a single process (even with several
> nodes running in the same JVM) everything worked. But when working with a
> large cluster of several machines I got the following error:
> {noformat}
> Error when executing service: ServicePluginsDeployer
> org.apache.ignite.IgniteException: Failed to unmarshall object.
> at
> org.apache.ignite.internal.processors.cache.CacheObjectImpl.value(CacheObjectImpl.java:84)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:280)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:145)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:132)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry$LazyValueEntry.getValue(GridCacheMapEntry.java:4339)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.service.GridServiceProcessor$TopologyListener$1.run0(GridServiceProcessor.java:1214)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.service.GridServiceProcessor$BusyRunnable.run(GridServiceProcessor.java:1399)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [na:1.8.0_60]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [na:1.8.0_60]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [na:1.8.0_60]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [na:1.8.0_60]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to find class
> with given class loader for unmarshalling (make sure same version of all
> classes are available on all nodes or enable peer-class-loading): null
> at
> org.apache.ignite.marshaller.optimized.OptimizedMarshaller.unmarshal(OptimizedMarshaller.java:254)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cacheobject.IgniteCacheObjectProcessorImpl.unmarshal(IgniteCacheObjectProcessorImpl.java:110)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.unmarshal(CacheObjectBinaryProcessorImpl.java:700)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cache.CacheObjectImpl.value(CacheObjectImpl.java:76)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
>
[jira] [Updated] (IGNITE-2455) SQL query fails if there are caches that were never used on this client
[
https://issues.apache.org/jira/browse/IGNITE-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2455:
Priority: Blocker (was: Critical)
> SQL query fails if there are caches that were never used on this client
> ---
>
> Key: IGNITE-2455
> URL: https://issues.apache.org/jira/browse/IGNITE-2455
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Sergi Vladykin
>Priority: Blocker
> Labels: important
> Fix For: 1.6
>
> Attachments: QueryTest.java
>
>
> Test attached.
> If SQL query contains caches that were never acquired on the current client,
> it fails with the following exception:
> {noformat}
> org.h2.jdbc.JdbcSQLException: Schema "cache2" not found;
> {noformat}
> We should automatically detect the list of required caches and create them
> before executing the query.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2722) Inconsistent "keepBinary" flag propagation for EVT_CACHE_REBALANCE_OBJECT_LOADED event.
[
https://issues.apache.org/jira/browse/IGNITE-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167799#comment-15167799
]
Valentin Kulichenko commented on IGNITE-2722:
-
We also should properly document this behavior and outline all the events that
always work with binary objects regardless of {{keepBinary}} flag.
> Inconsistent "keepBinary" flag propagation for
> EVT_CACHE_REBALANCE_OBJECT_LOADED event.
> ---
>
> Key: IGNITE-2722
> URL: https://issues.apache.org/jira/browse/IGNITE-2722
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: 1.6
>
>
> I searched through usages of EVT_CACHE_REBALANCE_OBJECT_LOADED event and
> noticed that we pass different value of "keepBinary" flag in different
> situations:
> 1) {{GridDhtLockFuture.MiniFuture.onResult}} - false
> 2) {{GridDhtTxPrepareFuture.MiniFuture.onResult}} - false
> 2) {{GridDhtForceKeysFuture.MiniFuture.onResult}} - false
> 4) {{GridDhtPartitionDemander.preloadEntry}} - true
> Looks like with this approach user is not able to use corresponding event
> listener normally because he will receive both serialized and de-serialized
> objects.
> As I understand, we must always pass {{true}} here because we do not know
> whether node has corresponding classes or not.
> Other rebalance events must be reviewed as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2726) Visor shows zero size for OFFHEAP_TIERED cache
Valentin Kulichenko created IGNITE-2726:
---
Summary: Visor shows zero size for OFFHEAP_TIERED cache
Key: IGNITE-2726
URL: https://issues.apache.org/jira/browse/IGNITE-2726
Project: Ignite
Issue Type: Bug
Components: visor
Reporter: Valentin Kulichenko
Priority: Critical
Fix For: 1.6
To reproduce:
1. Change cache memory mode in {{CachePutGetExample}} to {{OFFHEAP_TIERED}}.
2. Run the example.
3. Connect with Visor and run {{cache -a}} command. See result below - number
of entries is zero. With {{ONHEAP_TIERED}} is shows the correct cache size.
{noformat}
visor> cache -a
Time of the snapshot: 02/25/16, 13:10:44
+==+
| Name(@) |Mode | Nodes | Entries |Hits|
Misses | Reads| Writes |
+==+
| CachePutGetExample(@c0) | PARTITIONED | 1 | min: 0| min: 40| min:
0| min: 40| min: 40|
| | | | avg: 0.00 | avg: 40.00 | avg:
0.00 | avg: 40.00 | avg: 40.00 |
| | | | max: 0| max: 40| max:
0| max: 40| max: 40|
+--+
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2466) OutOfMemory when ONHEAP_TIERED mode is used
[ https://issues.apache.org/jira/browse/IGNITE-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167978#comment-15167978 ] Valentin Kulichenko commented on IGNITE-2466: - The attached test still fails with OOME. > OutOfMemory when ONHEAP_TIERED mode is used > --- > > Key: IGNITE-2466 > URL: https://issues.apache.org/jira/browse/IGNITE-2466 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.5.0.final >Reporter: Denis Magda >Assignee: Nikolay Tikhonov > Fix For: 1.6 > > Attachments: MemTest.java, example-ignite.xml > > > To reproduce, run two server nodes with 2g of heap each and then MemTest. > Servers will fail with OOME. If backups are disabled or there is only one > server node, it works. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-2450) Proxy classes are not serialized properly using OptimizedMarshaller and BinaryMarshaller
[
https://issues.apache.org/jira/browse/IGNITE-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko resolved IGNITE-2450.
-
Resolution: Fixed
Fixed in master.
> Proxy classes are not serialized properly using OptimizedMarshaller and
> BinaryMarshaller
>
>
> Key: IGNITE-2450
> URL: https://issues.apache.org/jira/browse/IGNITE-2450
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: ignite-1.4, 1.5.0.final
> Environment: Ubuntu 12.04 64 bit
> java version "1.8.0_60"
> Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
> Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
> Ignite 1.4.0
>Reporter: Avihai Berkovitz
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: community, important
> Fix For: 1.6
>
> Attachments: master_500bd3a_ignite-2450.patch
>
>
> I tried to deploy several services using Java's Proxy class, to dynamically
> define the needed interfaces. When using a single process (even with several
> nodes running in the same JVM) everything worked. But when working with a
> large cluster of several machines I got the following error:
> {noformat}
> Error when executing service: ServicePluginsDeployer
> org.apache.ignite.IgniteException: Failed to unmarshall object.
> at
> org.apache.ignite.internal.processors.cache.CacheObjectImpl.value(CacheObjectImpl.java:84)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:280)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:145)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:132)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry$LazyValueEntry.getValue(GridCacheMapEntry.java:4339)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.service.GridServiceProcessor$TopologyListener$1.run0(GridServiceProcessor.java:1214)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.service.GridServiceProcessor$BusyRunnable.run(GridServiceProcessor.java:1399)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [na:1.8.0_60]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [na:1.8.0_60]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [na:1.8.0_60]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [na:1.8.0_60]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to find class
> with given class loader for unmarshalling (make sure same version of all
> classes are available on all nodes or enable peer-class-loading): null
> at
> org.apache.ignite.marshaller.optimized.OptimizedMarshaller.unmarshal(OptimizedMarshaller.java:254)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cacheobject.IgniteCacheObjectProcessorImpl.unmarshal(IgniteCacheObjectProcessorImpl.java:110)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.unmarshal(CacheObjectBinaryProcessorImpl.java:700)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cache.CacheObjectImpl.value(CacheObjectImpl.java:76)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> ... 11 common frames omitted
> Caused by: java.lang.ClassNotFoundException: com.sun.proxy.$Proxy55
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> ~[na:1.8.0_60]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> ~[na:1.8.0_60]
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> ~[na:1.8.0_60]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ~[na:1.8.0_60]
> at java.lang.Class.forName0(Native Method) ~[na:1.8.0_60]
> at java.lang.Class.forName(Class.java:348) ~[na:1.8.0_60]
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.MarshallerContextAdapter.get
[jira] [Closed] (IGNITE-2450) Proxy classes are not serialized properly using OptimizedMarshaller and BinaryMarshaller
[
https://issues.apache.org/jira/browse/IGNITE-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko closed IGNITE-2450.
---
> Proxy classes are not serialized properly using OptimizedMarshaller and
> BinaryMarshaller
>
>
> Key: IGNITE-2450
> URL: https://issues.apache.org/jira/browse/IGNITE-2450
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: ignite-1.4, 1.5.0.final
> Environment: Ubuntu 12.04 64 bit
> java version "1.8.0_60"
> Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
> Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
> Ignite 1.4.0
>Reporter: Avihai Berkovitz
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: community, important
> Fix For: 1.6
>
> Attachments: master_500bd3a_ignite-2450.patch
>
>
> I tried to deploy several services using Java's Proxy class, to dynamically
> define the needed interfaces. When using a single process (even with several
> nodes running in the same JVM) everything worked. But when working with a
> large cluster of several machines I got the following error:
> {noformat}
> Error when executing service: ServicePluginsDeployer
> org.apache.ignite.IgniteException: Failed to unmarshall object.
> at
> org.apache.ignite.internal.processors.cache.CacheObjectImpl.value(CacheObjectImpl.java:84)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:280)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:145)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:132)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry$LazyValueEntry.getValue(GridCacheMapEntry.java:4339)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.service.GridServiceProcessor$TopologyListener$1.run0(GridServiceProcessor.java:1214)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.service.GridServiceProcessor$BusyRunnable.run(GridServiceProcessor.java:1399)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [na:1.8.0_60]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [na:1.8.0_60]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [na:1.8.0_60]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [na:1.8.0_60]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to find class
> with given class loader for unmarshalling (make sure same version of all
> classes are available on all nodes or enable peer-class-loading): null
> at
> org.apache.ignite.marshaller.optimized.OptimizedMarshaller.unmarshal(OptimizedMarshaller.java:254)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cacheobject.IgniteCacheObjectProcessorImpl.unmarshal(IgniteCacheObjectProcessorImpl.java:110)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.unmarshal(CacheObjectBinaryProcessorImpl.java:700)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.processors.cache.CacheObjectImpl.value(CacheObjectImpl.java:76)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> ... 11 common frames omitted
> Caused by: java.lang.ClassNotFoundException: com.sun.proxy.$Proxy55
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> ~[na:1.8.0_60]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> ~[na:1.8.0_60]
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> ~[na:1.8.0_60]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ~[na:1.8.0_60]
> at java.lang.Class.forName0(Native Method) ~[na:1.8.0_60]
> at java.lang.Class.forName(Class.java:348) ~[na:1.8.0_60]
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
> ~[ignite-core-1.5.0.final.jar:1.5.0.final]
> at
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
>
[jira] [Created] (IGNITE-2728) User
Valentin Kulichenko created IGNITE-2728: --- Summary: User Key: IGNITE-2728 URL: https://issues.apache.org/jira/browse/IGNITE-2728 Project: Ignite Issue Type: Bug Reporter: Valentin Kulichenko -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2727) User
Valentin Kulichenko created IGNITE-2727: --- Summary: User Key: IGNITE-2727 URL: https://issues.apache.org/jira/browse/IGNITE-2727 Project: Ignite Issue Type: Bug Reporter: Valentin Kulichenko -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-2727) User
[ https://issues.apache.org/jira/browse/IGNITE-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-2727. --- > User > > > Key: IGNITE-2727 > URL: https://issues.apache.org/jira/browse/IGNITE-2727 > Project: Ignite > Issue Type: Bug >Reporter: Valentin Kulichenko > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2728) User's closures are wrapped into Externalizable classes
[ https://issues.apache.org/jira/browse/IGNITE-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2728: Summary: User's closures are wrapped into Externalizable classes (was: User) > User's closures are wrapped into Externalizable classes > --- > > Key: IGNITE-2728 > URL: https://issues.apache.org/jira/browse/IGNITE-2728 > Project: Ignite > Issue Type: Bug > Components: compute >Reporter: Valentin Kulichenko > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-2727) User
[ https://issues.apache.org/jira/browse/IGNITE-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-2727. - Resolution: Invalid Ticket created by mistake. > User > > > Key: IGNITE-2727 > URL: https://issues.apache.org/jira/browse/IGNITE-2727 > Project: Ignite > Issue Type: Bug >Reporter: Valentin Kulichenko > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2728) User's closures are wrapped into Externalizable classes
[ https://issues.apache.org/jira/browse/IGNITE-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2728: Component/s: compute > User's closures are wrapped into Externalizable classes > --- > > Key: IGNITE-2728 > URL: https://issues.apache.org/jira/browse/IGNITE-2728 > Project: Ignite > Issue Type: Bug > Components: compute >Reporter: Valentin Kulichenko > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2728) User's closures are wrapped into Externalizable classes
[ https://issues.apache.org/jira/browse/IGNITE-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2728: Fix Version/s: 1.6 > User's closures are wrapped into Externalizable classes > --- > > Key: IGNITE-2728 > URL: https://issues.apache.org/jira/browse/IGNITE-2728 > Project: Ignite > Issue Type: Bug > Components: compute >Reporter: Valentin Kulichenko >Priority: Blocker > Labels: community, customer, important > Fix For: 1.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2728) User's closures are wrapped into Externalizable classes
[ https://issues.apache.org/jira/browse/IGNITE-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2728: Flags: Important > User's closures are wrapped into Externalizable classes > --- > > Key: IGNITE-2728 > URL: https://issues.apache.org/jira/browse/IGNITE-2728 > Project: Ignite > Issue Type: Bug > Components: compute >Reporter: Valentin Kulichenko >Priority: Blocker > Labels: community, customer, important > Fix For: 1.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2728) User's closures are wrapped into Externalizable classes
[ https://issues.apache.org/jira/browse/IGNITE-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2728: Priority: Blocker (was: Critical) > User's closures are wrapped into Externalizable classes > --- > > Key: IGNITE-2728 > URL: https://issues.apache.org/jira/browse/IGNITE-2728 > Project: Ignite > Issue Type: Bug > Components: compute >Reporter: Valentin Kulichenko >Priority: Blocker > Labels: community, customer, important > Fix For: 1.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2728) User's closures are wrapped into Externalizable classes
[ https://issues.apache.org/jira/browse/IGNITE-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2728: Labels: community customer important (was: ) > User's closures are wrapped into Externalizable classes > --- > > Key: IGNITE-2728 > URL: https://issues.apache.org/jira/browse/IGNITE-2728 > Project: Ignite > Issue Type: Bug > Components: compute >Reporter: Valentin Kulichenko > Labels: community, customer, important > Fix For: 1.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2728) User's closures are wrapped into Externalizable classes
[ https://issues.apache.org/jira/browse/IGNITE-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2728: Priority: Critical (was: Major) > User's closures are wrapped into Externalizable classes > --- > > Key: IGNITE-2728 > URL: https://issues.apache.org/jira/browse/IGNITE-2728 > Project: Ignite > Issue Type: Bug > Components: compute >Reporter: Valentin Kulichenko >Priority: Critical > Labels: community, customer, important > Fix For: 1.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2728) User's closures are wrapped into Externalizable classes
[
https://issues.apache.org/jira/browse/IGNITE-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2728:
Description: {{GridClosureProcessor}} wraps all closures into classes like
{{C1}, {{C2}}, etc., which are {{Externalizable}}. This means that even if
binary marshaller is used, the closure will be still serialized by optimized
marshaller and therefore all user's setting in binary configuration are ignored.
> User's closures are wrapped into Externalizable classes
> ---
>
> Key: IGNITE-2728
> URL: https://issues.apache.org/jira/browse/IGNITE-2728
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Reporter: Valentin Kulichenko
>Priority: Blocker
> Labels: community, customer, important
> Fix For: 1.6
>
>
> {{GridClosureProcessor}} wraps all closures into classes like {{C1}, {{C2}},
> etc., which are {{Externalizable}}. This means that even if binary marshaller
> is used, the closure will be still serialized by optimized marshaller and
> therefore all user's setting in binary configuration are ignored.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-2728) User's closures are wrapped into Externalizable classes
[
https://issues.apache.org/jira/browse/IGNITE-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko reassigned IGNITE-2728:
---
Assignee: Valentin Kulichenko
> User's closures are wrapped into Externalizable classes
> ---
>
> Key: IGNITE-2728
> URL: https://issues.apache.org/jira/browse/IGNITE-2728
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: community, customer, important
> Fix For: 1.6
>
>
> {{GridClosureProcessor}} wraps all closures into classes like {{C1}}, {{C2}},
> etc., which are {{Externalizable}}. This means that even if binary marshaller
> is used, the closure will be still serialized by optimized marshaller and
> therefore all user's setting in binary configuration are ignored.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2728) User's closures are wrapped into Externalizable classes
[
https://issues.apache.org/jira/browse/IGNITE-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2728:
Description: {{GridClosureProcessor}} wraps all closures into classes like
{{C1}}, {{C2}}, etc., which are {{Externalizable}}. This means that even if
binary marshaller is used, the closure will be still serialized by optimized
marshaller and therefore all user's setting in binary configuration are
ignored. (was: {{GridClosureProcessor}} wraps all closures into classes like
{{C1}, {{C2}}, etc., which are {{Externalizable}}. This means that even if
binary marshaller is used, the closure will be still serialized by optimized
marshaller and therefore all user's setting in binary configuration are
ignored.)
> User's closures are wrapped into Externalizable classes
> ---
>
> Key: IGNITE-2728
> URL: https://issues.apache.org/jira/browse/IGNITE-2728
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Reporter: Valentin Kulichenko
>Priority: Blocker
> Labels: community, customer, important
> Fix For: 1.6
>
>
> {{GridClosureProcessor}} wraps all closures into classes like {{C1}}, {{C2}},
> etc., which are {{Externalizable}}. This means that even if binary marshaller
> is used, the closure will be still serialized by optimized marshaller and
> therefore all user's setting in binary configuration are ignored.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2726) Visor shows zero size for OFFHEAP_TIERED cache
[
https://issues.apache.org/jira/browse/IGNITE-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2726:
Description:
To reproduce:
1. Change cache memory mode in {{CachePutGetExample}} to {{OFFHEAP_TIERED}}.
2. Run the example.
3. Connect with Visor and run {{cache -a}} command. See result below - number
of entries is zero. With {{ONHEAP_TIERED}} it shows the correct cache size.
{noformat}
visor> cache -a
Time of the snapshot: 02/25/16, 13:10:44
+==+
| Name(@) |Mode | Nodes | Entries |Hits|
Misses | Reads| Writes |
+==+
| CachePutGetExample(@c0) | PARTITIONED | 1 | min: 0| min: 40| min:
0| min: 40| min: 40|
| | | | avg: 0.00 | avg: 40.00 | avg:
0.00 | avg: 40.00 | avg: 40.00 |
| | | | max: 0| max: 40| max:
0| max: 40| max: 40|
+--+
{noformat}
was:
To reproduce:
1. Change cache memory mode in {{CachePutGetExample}} to {{OFFHEAP_TIERED}}.
2. Run the example.
3. Connect with Visor and run {{cache -a}} command. See result below - number
of entries is zero. With {{ONHEAP_TIERED}} is shows the correct cache size.
{noformat}
visor> cache -a
Time of the snapshot: 02/25/16, 13:10:44
+==+
| Name(@) |Mode | Nodes | Entries |Hits|
Misses | Reads| Writes |
+==+
| CachePutGetExample(@c0) | PARTITIONED | 1 | min: 0| min: 40| min:
0| min: 40| min: 40|
| | | | avg: 0.00 | avg: 40.00 | avg:
0.00 | avg: 40.00 | avg: 40.00 |
| | | | max: 0| max: 40| max:
0| max: 40| max: 40|
+--+
{noformat}
> Visor shows zero size for OFFHEAP_TIERED cache
> --
>
> Key: IGNITE-2726
> URL: https://issues.apache.org/jira/browse/IGNITE-2726
> Project: Ignite
> Issue Type: Bug
> Components: visor
>Reporter: Valentin Kulichenko
>Assignee: Vasiliy Sisko
>Priority: Critical
> Labels: community, customer
> Fix For: 1.6
>
>
> To reproduce:
> 1. Change cache memory mode in {{CachePutGetExample}} to {{OFFHEAP_TIERED}}.
> 2. Run the example.
> 3. Connect with Visor and run {{cache -a}} command. See result below - number
> of entries is zero. With {{ONHEAP_TIERED}} it shows the correct cache size.
> {noformat}
> visor> cache -a
> Time of the snapshot: 02/25/16, 13:10:44
> +==+
> | Name(@) |Mode | Nodes | Entries |Hits|
> Misses | Reads| Writes |
> +==+
> | CachePutGetExample(@c0) | PARTITIONED | 1 | min: 0| min: 40|
> min: 0| min: 40| min: 40|
> | | | | avg: 0.00 | avg: 40.00 |
> avg: 0.00 | avg: 40.00 | avg: 40.00 |
> | | | | max: 0| max: 40|
> max: 0| max: 40| max: 40|
> +--+
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-2455) SQL query fails if there are caches that were never used on this client
[
https://issues.apache.org/jira/browse/IGNITE-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko reassigned IGNITE-2455:
---
Assignee: Valentin Kulichenko (was: Sergi Vladykin)
> SQL query fails if there are caches that were never used on this client
> ---
>
> Key: IGNITE-2455
> URL: https://issues.apache.org/jira/browse/IGNITE-2455
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: important
> Fix For: 1.6
>
> Attachments: QueryTest.java
>
>
> Test attached.
> If SQL query contains caches that were never acquired on the current client,
> it fails with the following exception:
> {noformat}
> org.h2.jdbc.JdbcSQLException: Schema "cache2" not found;
> {noformat}
> We should automatically detect the list of required caches and create them
> before executing the query.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2455) SQL query fails if there are caches that were never used on this client
[
https://issues.apache.org/jira/browse/IGNITE-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169936#comment-15169936
]
Valentin Kulichenko commented on IGNITE-2455:
-
Made the simple fix: catch exception and try to create all client caches that
are currently missing.
Running TC.
> SQL query fails if there are caches that were never used on this client
> ---
>
> Key: IGNITE-2455
> URL: https://issues.apache.org/jira/browse/IGNITE-2455
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: important
> Fix For: 1.6
>
> Attachments: QueryTest.java
>
>
> Test attached.
> If SQL query contains caches that were never acquired on the current client,
> it fails with the following exception:
> {noformat}
> org.h2.jdbc.JdbcSQLException: Schema "cache2" not found;
> {noformat}
> We should automatically detect the list of required caches and create them
> before executing the query.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-2455) SQL query fails if there are caches that were never used on this client
[
https://issues.apache.org/jira/browse/IGNITE-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko resolved IGNITE-2455.
-
Resolution: Fixed
TC passed, code reviewed by Alex G.
Merged to master.
> SQL query fails if there are caches that were never used on this client
> ---
>
> Key: IGNITE-2455
> URL: https://issues.apache.org/jira/browse/IGNITE-2455
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: important
> Fix For: 1.6
>
> Attachments: QueryTest.java
>
>
> Test attached.
> If SQL query contains caches that were never acquired on the current client,
> it fails with the following exception:
> {noformat}
> org.h2.jdbc.JdbcSQLException: Schema "cache2" not found;
> {noformat}
> We should automatically detect the list of required caches and create them
> before executing the query.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-2455) SQL query fails if there are caches that were never used on this client
[
https://issues.apache.org/jira/browse/IGNITE-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko closed IGNITE-2455.
---
> SQL query fails if there are caches that were never used on this client
> ---
>
> Key: IGNITE-2455
> URL: https://issues.apache.org/jira/browse/IGNITE-2455
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: important
> Fix For: 1.6
>
> Attachments: QueryTest.java
>
>
> Test attached.
> If SQL query contains caches that were never acquired on the current client,
> it fails with the following exception:
> {noformat}
> org.h2.jdbc.JdbcSQLException: Schema "cache2" not found;
> {noformat}
> We should automatically detect the list of required caches and create them
> before executing the query.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-2728) User's closures are wrapped into Externalizable classes
[
https://issues.apache.org/jira/browse/IGNITE-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko resolved IGNITE-2728.
-
Resolution: Duplicate
Duplicate of IGNITE-2700
> User's closures are wrapped into Externalizable classes
> ---
>
> Key: IGNITE-2728
> URL: https://issues.apache.org/jira/browse/IGNITE-2728
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: community, customer, important
> Fix For: 1.6
>
>
> {{GridClosureProcessor}} wraps all closures into classes like {{C1}}, {{C2}},
> etc., which are {{Externalizable}}. This means that even if binary marshaller
> is used, the closure will be still serialized by optimized marshaller and
> therefore all user's setting in binary configuration are ignored.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-2728) User's closures are wrapped into Externalizable classes
[
https://issues.apache.org/jira/browse/IGNITE-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko closed IGNITE-2728.
---
> User's closures are wrapped into Externalizable classes
> ---
>
> Key: IGNITE-2728
> URL: https://issues.apache.org/jira/browse/IGNITE-2728
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: community, customer, important
> Fix For: 1.6
>
>
> {{GridClosureProcessor}} wraps all closures into classes like {{C1}}, {{C2}},
> etc., which are {{Externalizable}}. This means that even if binary marshaller
> is used, the closure will be still serialized by optimized marshaller and
> therefore all user's setting in binary configuration are ignored.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2748) Service proxy makes remote call for methods declared in java.lang.Object
Valentin Kulichenko created IGNITE-2748:
---
Summary: Service proxy makes remote call for methods declared in
java.lang.Object
Key: IGNITE-2748
URL: https://issues.apache.org/jira/browse/IGNITE-2748
Project: Ignite
Issue Type: Bug
Components: managed services
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
Priority: Critical
Fix For: 1.6
To reproduce the issue, get a service proxy and call one of
{{java.lang.Object}} methods (e.g., {{hashCode}}). It will make a remote call,
which is not needed and can cause issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2748) Service proxy makes remote call for methods declared in java.lang.Object
[
https://issues.apache.org/jira/browse/IGNITE-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2748:
Description:
To reproduce the issue, get a service proxy and call one of
{{java.lang.Object}} methods (e.g., {{hashCode}}). It will make a remote call,
which is not needed and can cause issues.
In addition, we should block the gateway on proxy invocation.
was:To reproduce the issue, get a service proxy and call one of
{{java.lang.Object}} methods (e.g., {{hashCode}}). It will make a remote call,
which is not needed and can cause issues.
> Service proxy makes remote call for methods declared in java.lang.Object
>
>
> Key: IGNITE-2748
> URL: https://issues.apache.org/jira/browse/IGNITE-2748
> Project: Ignite
> Issue Type: Bug
> Components: managed services
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.6
>
>
> To reproduce the issue, get a service proxy and call one of
> {{java.lang.Object}} methods (e.g., {{hashCode}}). It will make a remote
> call, which is not needed and can cause issues.
> In addition, we should block the gateway on proxy invocation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2748) Service proxy makes remote call for methods declared in java.lang.Object
[
https://issues.apache.org/jira/browse/IGNITE-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2748:
Attachment: master_d2d5d24_ignite-2748.patch
> Service proxy makes remote call for methods declared in java.lang.Object
>
>
> Key: IGNITE-2748
> URL: https://issues.apache.org/jira/browse/IGNITE-2748
> Project: Ignite
> Issue Type: Bug
> Components: managed services
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.6
>
> Attachments: master_d2d5d24_ignite-2748.patch
>
>
> To reproduce the issue, get a service proxy and call one of
> {{java.lang.Object}} methods (e.g., {{hashCode}}). It will make a remote
> call, which is not needed and can cause issues.
> In addition, we should block the gateway on proxy invocation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2748) Service proxy makes remote call for methods declared in java.lang.Object
[
https://issues.apache.org/jira/browse/IGNITE-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2748:
Attachment: (was: master_d2d5d24_ignite-2748.patch)
> Service proxy makes remote call for methods declared in java.lang.Object
>
>
> Key: IGNITE-2748
> URL: https://issues.apache.org/jira/browse/IGNITE-2748
> Project: Ignite
> Issue Type: Bug
> Components: managed services
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.6
>
> Attachments: master_d2d5d24_ignite-2748.patch
>
>
> To reproduce the issue, get a service proxy and call one of
> {{java.lang.Object}} methods (e.g., {{hashCode}}). It will make a remote
> call, which is not needed and can cause issues.
> In addition, we should block the gateway on proxy invocation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2748) Service proxy makes remote call for methods declared in java.lang.Object
[
https://issues.apache.org/jira/browse/IGNITE-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2748:
Attachment: master_d2d5d24_ignite-2748.patch
> Service proxy makes remote call for methods declared in java.lang.Object
>
>
> Key: IGNITE-2748
> URL: https://issues.apache.org/jira/browse/IGNITE-2748
> Project: Ignite
> Issue Type: Bug
> Components: managed services
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.6
>
> Attachments: master_d2d5d24_ignite-2748.patch
>
>
> To reproduce the issue, get a service proxy and call one of
> {{java.lang.Object}} methods (e.g., {{hashCode}}). It will make a remote
> call, which is not needed and can cause issues.
> In addition, we should block the gateway on proxy invocation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-2748) Service proxy makes remote call for methods declared in java.lang.Object
[
https://issues.apache.org/jira/browse/IGNITE-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko closed IGNITE-2748.
---
> Service proxy makes remote call for methods declared in java.lang.Object
>
>
> Key: IGNITE-2748
> URL: https://issues.apache.org/jira/browse/IGNITE-2748
> Project: Ignite
> Issue Type: Bug
> Components: managed services
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.6
>
> Attachments: master_d2d5d24_ignite-2748.patch
>
>
> To reproduce the issue, get a service proxy and call one of
> {{java.lang.Object}} methods (e.g., {{hashCode}}). It will make a remote
> call, which is not needed and can cause issues.
> In addition, we should block the gateway on proxy invocation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1267) JobStealingCollisionSpi never sends jobs to a node that joined after task was executed
[
https://issues.apache.org/jira/browse/IGNITE-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176971#comment-15176971
]
Valentin Kulichenko commented on IGNITE-1267:
-
Removing the check completely is wrong, because in this case a job can be
stealed by (or failed over to) a node that is not included in the cluster group
specified when the task or closure was executed.
I think the best fix is to include the cluster group along with the list of
nodes into the task session. Refer to any method in {{IgniteCompute}} and
{{TC_SUBGRID}} context key. Once we have it, all such checks can be properly
fixed.
> JobStealingCollisionSpi never sends jobs to a node that joined after task was
> executed
> --
>
> Key: IGNITE-1267
> URL: https://issues.apache.org/jira/browse/IGNITE-1267
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
> Labels: user-request
>
> Corresponding user thread (contains detailed description of the scenario that
> doesn't work):
> http://apache-ignite-users.70518.x6.nabble.com/Dynamic-ComputeTask-distribution-with-new-nodes-td997.html
> Essentially, {{JobStealingCollisionSpi}} always skips jobs that are not in
> task topology (see line 713). Task topology is static and created when task
> is executed, so newly joined node can't steal jobs. I think it should be able
> to do this if it satisfies initial cluster group predicate.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2710) Session not unbind from current request after invoking request.getSession().invalidate()
[ https://issues.apache.org/jira/browse/IGNITE-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176995#comment-15176995 ] Valentin Kulichenko commented on IGNITE-2710: - Roman, Sorry for the delay. I will take a look at this today or tomorrow. > Session not unbind from current request after invoking > request.getSession().invalidate() > > > Key: IGNITE-2710 > URL: https://issues.apache.org/jira/browse/IGNITE-2710 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.5.0.final > Environment: java8, tomcat8 >Reporter: YuxuanWang >Assignee: Roman Shtykh > Labels: community, session, user > Fix For: 1.6 > > > System.out.println(request.getSession().getId()); > request.getSession().invalidate(); > System.out.println(request.getSession().getId()); > getSession() although return the same session after the invalidation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2749) Web session clustering works incorrectly with WebLogic
Valentin Kulichenko created IGNITE-2749:
---
Summary: Web session clustering works incorrectly with WebLogic
Key: IGNITE-2749
URL: https://issues.apache.org/jira/browse/IGNITE-2749
Project: Ignite
Issue Type: Bug
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
Priority: Critical
Fix For: 1.6
{{WebSessionFilter}} has a special processing for the session ID generated by
WebLogic. The issue is that this processing is not applied in all required
cases. E.g., session ID is transformed when new session is saved in cache (see
{{createSession}} method, but not transformed when it's fetched from cache (see
{{doFilter0}}.
Need to go through the code, locate incorrect places and fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2749) Web session clustering works incorrectly with WebLogic
[
https://issues.apache.org/jira/browse/IGNITE-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2749:
Attachment: master_ee01b61_ignite-2749.patch
> Web session clustering works incorrectly with WebLogic
> --
>
> Key: IGNITE-2749
> URL: https://issues.apache.org/jira/browse/IGNITE-2749
> Project: Ignite
> Issue Type: Bug
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.6
>
> Attachments: master_ee01b61_ignite-2749.patch
>
>
> {{WebSessionFilter}} has a special processing for the session ID generated by
> WebLogic. The issue is that this processing is not applied in all required
> cases. E.g., session ID is transformed when new session is saved in cache
> (see {{createSession}} method, but not transformed when it's fetched from
> cache (see {{doFilter0}}.
> Need to go through the code, locate incorrect places and fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2753) Binary object might be deserialized unexpectedly when cache store is enabled.
[
https://issues.apache.org/jira/browse/IGNITE-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2753:
Flags: Important
> Binary object might be deserialized unexpectedly when cache store is enabled.
> -
>
> Key: IGNITE-2753
> URL: https://issues.apache.org/jira/browse/IGNITE-2753
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Dmitry Karachentsev
>Priority: Blocker
> Labels: community, customer, important
> Fix For: 1.6
>
>
> *Problem*
> See {{GridCacheMapEntry}} class. There are lots of calls to store like this:
> {code}
> cctx.store().put(null, keyValue(false), CU.value(val, cctx, false), ver);
> {code}
> When {{keyValue()}} is called, it might force object deserialization. And if
> there is no class on the server, the following exception might appear:
> {code}
> g.apache.ignite.binary.BinaryInvalidTypeException: XXX
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:558)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1442)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:542)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:117)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.keyValue(GridCacheMapEntry.java:1261)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3326)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:1598)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:304)
> [ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
> [ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:79)
> [ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:822)
> [ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
> [ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:785)
> [ignite-core-1.5.7.jar:1.5.7]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [?:1.8.0_51]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [?:1.8.0_51]
> {code}
> *Proposed solution*
> Pass key and value directly to store manager. It should already handle
> everything correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2753) Binary object might be deserialized unexpectedly when cache store is enabled.
[
https://issues.apache.org/jira/browse/IGNITE-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2753:
Labels: community customer important (was: )
> Binary object might be deserialized unexpectedly when cache store is enabled.
> -
>
> Key: IGNITE-2753
> URL: https://issues.apache.org/jira/browse/IGNITE-2753
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Dmitry Karachentsev
>Priority: Blocker
> Labels: community, customer, important
> Fix For: 1.6
>
>
> *Problem*
> See {{GridCacheMapEntry}} class. There are lots of calls to store like this:
> {code}
> cctx.store().put(null, keyValue(false), CU.value(val, cctx, false), ver);
> {code}
> When {{keyValue()}} is called, it might force object deserialization. And if
> there is no class on the server, the following exception might appear:
> {code}
> g.apache.ignite.binary.BinaryInvalidTypeException: XXX
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:558)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1442)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:542)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:117)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.keyValue(GridCacheMapEntry.java:1261)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3326)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:1598)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:304)
> [ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
> [ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:79)
> [ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:822)
> [ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
> [ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:785)
> [ignite-core-1.5.7.jar:1.5.7]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [?:1.8.0_51]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [?:1.8.0_51]
> {code}
> *Proposed solution*
> Pass key and value directly to store manager. It should already handle
> everything correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2753) Binary object might be deserialized unexpectedly when cache store is enabled.
[
https://issues.apache.org/jira/browse/IGNITE-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2753:
Description:
*Problem*
See {{GridCacheMapEntry}} class. There are lots of calls to store like this:
{code}
cctx.store().put(null, keyValue(false), CU.value(val, cctx, false), ver);
{code}
When {{keyValue()}} is called, it might force object deserialization. And if
there is no class on the server, the following exception might appear:
{code}
g.apache.ignite.binary.BinaryInvalidTypeException: XXX
at
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:558)
~[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1442)
~[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:542)
~[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:117)
~[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.keyValue(GridCacheMapEntry.java:1261)
~[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3326)
~[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:1598)
~[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
~[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:304)
[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:79)
[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:822)
[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:785)
[ignite-core-1.5.7.jar:1.5.7]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[?:1.8.0_51]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[?:1.8.0_51]
{code}
*Proposed solution*
Pass key and value directly to store manager. It should already handle
everything correctly.
was:
*Problem*
See {{GridCacheMapEntry}} class. There are lots of calls to store like this:
{code}
cctx.store().put(null, keyValue(false), CU.value(val, cctx, false), ver);
{code}
When {{keyValue()}} is called, it might force object deserialization. And if
there is no class on the server, the following exception might appear:
{code}
g.apache.ignite.binary.BinaryInvalidTypeException:
com.jefco.portfoliotrading.gets.common.CurrencyKey
at
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:558)
~[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1442)
~[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:542)
~[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:117)
~[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.keyValue(GridCacheMapEntry.java:1261)
~[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3326)
~[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:1598)
~[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
~[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:304)
[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
[ignite-core-1.5.7.jar:1.5.7]
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.on
[jira] [Updated] (IGNITE-2753) Binary object might be deserialized unexpectedly when cache store is enabled.
[
https://issues.apache.org/jira/browse/IGNITE-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2753:
Priority: Blocker (was: Critical)
> Binary object might be deserialized unexpectedly when cache store is enabled.
> -
>
> Key: IGNITE-2753
> URL: https://issues.apache.org/jira/browse/IGNITE-2753
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Dmitry Karachentsev
>Priority: Blocker
> Labels: community, customer, important
> Fix For: 1.6
>
>
> *Problem*
> See {{GridCacheMapEntry}} class. There are lots of calls to store like this:
> {code}
> cctx.store().put(null, keyValue(false), CU.value(val, cctx, false), ver);
> {code}
> When {{keyValue()}} is called, it might force object deserialization. And if
> there is no class on the server, the following exception might appear:
> {code}
> g.apache.ignite.binary.BinaryInvalidTypeException: XXX
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:558)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1442)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:542)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:117)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.keyValue(GridCacheMapEntry.java:1261)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3326)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:1598)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
> ~[ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:304)
> [ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
> [ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:79)
> [ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:822)
> [ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
> [ignite-core-1.5.7.jar:1.5.7]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:785)
> [ignite-core-1.5.7.jar:1.5.7]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [?:1.8.0_51]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [?:1.8.0_51]
> {code}
> *Proposed solution*
> Pass key and value directly to store manager. It should already handle
> everything correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2758) IGNITE_HOME/libs/ignite-aws/aws-java-sdk-1.10.29.jar doesn't contain any classes
Valentin Kulichenko created IGNITE-2758:
---
Summary: IGNITE_HOME/libs/ignite-aws/aws-java-sdk-1.10.29.jar
doesn't contain any classes
Key: IGNITE-2758
URL: https://issues.apache.org/jira/browse/IGNITE-2758
Project: Ignite
Issue Type: Bug
Components: build
Affects Versions: 1.5.0.final
Reporter: Valentin Kulichenko
Priority: Blocker
Fix For: 1.6
To observe the issue do this:
* Build the fabric ZIP file.
* Go to {{ignite-aws}} module folder.
* Unzip {{aws-java-sdk-1.10.29.jar}}.
* JAR file contains only pom.xml, no classes.
We need to make sure that all required AWS SDK components are included. At
least we need these ones:
* aws-java-sdk-core
* aws-java-sdk-s3
* joda-time
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2758) IGNITE_HOME/libs/ignite-aws/aws-java-sdk-1.10.29.jar doesn't contain any classes
[
https://issues.apache.org/jira/browse/IGNITE-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180376#comment-15180376
]
Valentin Kulichenko commented on IGNITE-2758:
-
Ilya,
Sorry, I was unclear :) {{aws-java-sdk}} artifact is just a set of
dependencies, this is how they distribute the SDK via Maven. So this is correct
that it doesn't have any classes inside. I don't actually think that we need
this JAR file in the ZIP at all, it doesn't add any value. What we need is the
set of JARs required for out AWS-related functionality. Can you check that
nodes can be started on Amazon using {{ignite.sh}} with S3 IP finder?
> IGNITE_HOME/libs/ignite-aws/aws-java-sdk-1.10.29.jar doesn't contain any
> classes
>
>
> Key: IGNITE-2758
> URL: https://issues.apache.org/jira/browse/IGNITE-2758
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: community, customer, important
> Fix For: 1.6
>
>
> To observe the issue do this:
> * Build the fabric ZIP file.
> * Go to {{ignite-aws}} module folder.
> * Unzip {{aws-java-sdk-1.10.29.jar}}.
> * JAR file contains only pom.xml, no classes.
> We need to make sure that all required AWS SDK components are included. At
> least we need these ones:
> * aws-java-sdk-core
> * aws-java-sdk-s3
> * joda-time
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2758) IGNITE_HOME/libs/ignite-aws/aws-java-sdk-1.10.29.jar doesn't contain any classes
[
https://issues.apache.org/jira/browse/IGNITE-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2758:
Assignee: Ilya Suntsov (was: Valentin Kulichenko)
> IGNITE_HOME/libs/ignite-aws/aws-java-sdk-1.10.29.jar doesn't contain any
> classes
>
>
> Key: IGNITE-2758
> URL: https://issues.apache.org/jira/browse/IGNITE-2758
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Ilya Suntsov
>Priority: Blocker
> Labels: community, customer, important
> Fix For: 1.6
>
>
> To observe the issue do this:
> * Build the fabric ZIP file.
> * Go to {{ignite-aws}} module folder.
> * Unzip {{aws-java-sdk-1.10.29.jar}}.
> * JAR file contains only pom.xml, no classes.
> We need to make sure that all required AWS SDK components are included. At
> least we need these ones:
> * aws-java-sdk-core
> * aws-java-sdk-s3
> * joda-time
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-2758) IGNITE_HOME/libs/ignite-aws/aws-java-sdk-1.10.29.jar doesn't contain any classes
[
https://issues.apache.org/jira/browse/IGNITE-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180376#comment-15180376
]
Valentin Kulichenko edited comment on IGNITE-2758 at 3/4/16 6:59 PM:
-
Ilya,
Sorry, I was unclear :) {{aws-java-sdk}} artifact is just a set of
dependencies, this is how they distribute the SDK via Maven. So this is correct
that it doesn't have any classes inside, and I don't actually think that we
need this JAR file in the ZIP at all, because it doesn't add any value. What we
need is the set of JARs required for out AWS-related functionality. Can you
check that nodes can be started on Amazon using {{ignite.sh}} with S3 IP finder?
was (Author: vkulichenko):
Ilya,
Sorry, I was unclear :) {{aws-java-sdk}} artifact is just a set of
dependencies, this is how they distribute the SDK via Maven. So this is correct
that it doesn't have any classes inside. I don't actually think that we need
this JAR file in the ZIP at all, it doesn't add any value. What we need is the
set of JARs required for out AWS-related functionality. Can you check that
nodes can be started on Amazon using {{ignite.sh}} with S3 IP finder?
> IGNITE_HOME/libs/ignite-aws/aws-java-sdk-1.10.29.jar doesn't contain any
> classes
>
>
> Key: IGNITE-2758
> URL: https://issues.apache.org/jira/browse/IGNITE-2758
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: community, customer, important
> Fix For: 1.6
>
>
> To observe the issue do this:
> * Build the fabric ZIP file.
> * Go to {{ignite-aws}} module folder.
> * Unzip {{aws-java-sdk-1.10.29.jar}}.
> * JAR file contains only pom.xml, no classes.
> We need to make sure that all required AWS SDK components are included. At
> least we need these ones:
> * aws-java-sdk-core
> * aws-java-sdk-s3
> * joda-time
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2765) WebSessionFilter doesn't survive client reconnect
[
https://issues.apache.org/jira/browse/IGNITE-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2765:
Description:
If a {{WebSessionFilter}} is started with an embedded client, it is not
functional after the client disconnects and reconnects. Any operation throws
the exception below.
{noformat}
java.lang.IllegalStateException: Cache has been closed or destroyed: WebCache
at
org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:160)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.onEnter(IgniteCacheProxy.java:1958)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:855)
at
org.apache.ignite.cache.websession.WebSessionFilter.doFilter0(WebSessionFilter.java:341)
{noformat}
was:
If a {{WebSessionFilter}} is started with an embedded client, it is not
functional after the client disconnects and reconnects. Any operation throws
the exception below.
{noformat}
java.lang.IllegalStateException: Cache has been closed or destroyed: WebCache
at
org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:160)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.onEnter(IgniteCacheProxy.java:1958)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:855)
at
org.apache.ignite.cache.websession.WebSessionFilter.doFilter0(WebSessionFilter.java:341)
> WebSessionFilter doesn't survive client reconnect
> -
>
> Key: IGNITE-2765
> URL: https://issues.apache.org/jira/browse/IGNITE-2765
> Project: Ignite
> Issue Type: Bug
> Components: websession
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Labels: community, customer, important
> Fix For: 1.6
>
>
> If a {{WebSessionFilter}} is started with an embedded client, it is not
> functional after the client disconnects and reconnects. Any operation throws
> the exception below.
> {noformat}
> java.lang.IllegalStateException: Cache has been closed or destroyed: WebCache
> at
> org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:160)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.onEnter(IgniteCacheProxy.java:1958)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:855)
> at
> org.apache.ignite.cache.websession.WebSessionFilter.doFilter0(WebSessionFilter.java:341)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2765) WebSessionFilter doesn't survive client reconnect
Valentin Kulichenko created IGNITE-2765:
---
Summary: WebSessionFilter doesn't survive client reconnect
Key: IGNITE-2765
URL: https://issues.apache.org/jira/browse/IGNITE-2765
Project: Ignite
Issue Type: Bug
Components: websession
Affects Versions: 1.5.0.final
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
Priority: Critical
Fix For: 1.6
If a {{WebSessionFilter}} is started with an embedded client, it is not
functional after the client disconnects and reconnects. Any operation throws
the exception below.
{noformat}
java.lang.IllegalStateException: Cache has been closed or destroyed: WebCache
at
org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:160)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.onEnter(IgniteCacheProxy.java:1958)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:855)
at
org.apache.ignite.cache.websession.WebSessionFilter.doFilter0(WebSessionFilter.java:341)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2765) WebSessionFilter doesn't survive client reconnect
[
https://issues.apache.org/jira/browse/IGNITE-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2765:
Description:
If a {{WebSessionFilter}} is started with an embedded client, it is not
functional after the client disconnects and reconnects. Any operation throws
the exception below.
{noformat}
java.lang.IllegalStateException: Cache has been closed or destroyed: WebCache
at
org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:160)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.onEnter(IgniteCacheProxy.java:1958)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:855)
at
org.apache.ignite.cache.websession.WebSessionFilter.doFilter0(WebSessionFilter.java:341)
{noformat}
We should get a new instance of the cache when the exception is thrown.
was:
If a {{WebSessionFilter}} is started with an embedded client, it is not
functional after the client disconnects and reconnects. Any operation throws
the exception below.
{noformat}
java.lang.IllegalStateException: Cache has been closed or destroyed: WebCache
at
org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:160)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.onEnter(IgniteCacheProxy.java:1958)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:855)
at
org.apache.ignite.cache.websession.WebSessionFilter.doFilter0(WebSessionFilter.java:341)
{noformat}
> WebSessionFilter doesn't survive client reconnect
> -
>
> Key: IGNITE-2765
> URL: https://issues.apache.org/jira/browse/IGNITE-2765
> Project: Ignite
> Issue Type: Bug
> Components: websession
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Labels: community, customer, important
> Fix For: 1.6
>
>
> If a {{WebSessionFilter}} is started with an embedded client, it is not
> functional after the client disconnects and reconnects. Any operation throws
> the exception below.
> {noformat}
> java.lang.IllegalStateException: Cache has been closed or destroyed: WebCache
> at
> org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:160)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.onEnter(IgniteCacheProxy.java:1958)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:855)
> at
> org.apache.ignite.cache.websession.WebSessionFilter.doFilter0(WebSessionFilter.java:341)
> {noformat}
> We should get a new instance of the cache when the exception is thrown.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2766) Cache instance is closed when client disconnects
Valentin Kulichenko created IGNITE-2766: --- Summary: Cache instance is closed when client disconnects Key: IGNITE-2766 URL: https://issues.apache.org/jira/browse/IGNITE-2766 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 1.5.0.final Reporter: Valentin Kulichenko Fix For: 1.6 In case client disconnects and reconnects after network timeout (i.e., with a new ID), all cache instances acquired by this client are closed and are not functional. User has to create a special logic to handle this case. Cache proxy should be able to handle this automatically. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2765) WebSessionFilter doesn't survive client reconnect
[
https://issues.apache.org/jira/browse/IGNITE-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180668#comment-15180668
]
Valentin Kulichenko commented on IGNITE-2765:
-
This issue will be fixed automatically when IGNITE-2766 is fixed. But probably
it's better to apply quick and easy fix here, because it seems to be more
critical (there is no workaround for {{WebSessionFilter}}).
> WebSessionFilter doesn't survive client reconnect
> -
>
> Key: IGNITE-2765
> URL: https://issues.apache.org/jira/browse/IGNITE-2765
> Project: Ignite
> Issue Type: Bug
> Components: websession
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Labels: community, customer, important
> Fix For: 1.6
>
>
> If a {{WebSessionFilter}} is started with an embedded client, it is not
> functional after the client disconnects and reconnects. Any operation throws
> the exception below.
> {noformat}
> java.lang.IllegalStateException: Cache has been closed or destroyed: WebCache
> at
> org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:160)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.onEnter(IgniteCacheProxy.java:1958)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:855)
> at
> org.apache.ignite.cache.websession.WebSessionFilter.doFilter0(WebSessionFilter.java:341)
> {noformat}
> We should get a new instance of the cache when the exception is thrown.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2766) Cache instance is closed when client disconnects
[
https://issues.apache.org/jira/browse/IGNITE-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180674#comment-15180674
]
Valentin Kulichenko commented on IGNITE-2766:
-
{{IgniteClientDisconnectedException}} should also behave consistently,
regardless of whether the client was reconnected within network timeout or
after it with a new ID.
> Cache instance is closed when client disconnects
>
>
> Key: IGNITE-2766
> URL: https://issues.apache.org/jira/browse/IGNITE-2766
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
> Fix For: 1.6
>
>
> In case client disconnects and reconnects after network timeout (i.e., with a
> new ID), all cache instances acquired by this client are closed and are not
> functional. User has to create a special logic to handle this case.
> Cache proxy should be able to handle this automatically.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2735) Interrupt all acquires on local node after ignite.close
[
https://issues.apache.org/jira/browse/IGNITE-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181493#comment-15181493
]
Valentin Kulichenko commented on IGNITE-2735:
-
Hi Vladislav,
For such functionality we have {{GridKernalGateway}}, which guards all public
API calls from being invoked after node is stopped. It should be used here as
well. Store a reference of {{GridKernalContext}} in the semaphore when it's
created and surround public method implementations with
{{ctx.gateway().readLock()}} and {{ctx.gateway().readUnlock()}}. As an example
you can refer to {{GridExecutorService}}.
Also I believe this fix should be applied to all data structures, not only the
semaphore.
Thanks!
> Interrupt all acquires on local node after ignite.close
> ---
>
> Key: IGNITE-2735
> URL: https://issues.apache.org/jira/browse/IGNITE-2735
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 1.6
>Reporter: Vladisav Jelisavcic
>Assignee: Vladisav Jelisavcic
> Fix For: 1.5.0.final
>
>
> "acquire" method should throw an exception when semaphore is no longer
> accessible when node is stopped.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2710) Session not unbind from current request after invoking request.getSession().invalidate()
[
https://issues.apache.org/jira/browse/IGNITE-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181497#comment-15181497
]
Valentin Kulichenko commented on IGNITE-2710:
-
Changes make sense to me. Couple of questions though:
* Why not all methods are guarded by {{if (!isValid)}} check? Is it on purpose?
* Why the test doesn't work in transactional cache?
> Session not unbind from current request after invoking
> request.getSession().invalidate()
>
>
> Key: IGNITE-2710
> URL: https://issues.apache.org/jira/browse/IGNITE-2710
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.5.0.final
> Environment: java8, tomcat8
>Reporter: YuxuanWang
>Assignee: Roman Shtykh
> Labels: community, session, user
> Fix For: 1.6
>
>
> System.out.println(request.getSession().getId());
> request.getSession().invalidate();
> System.out.println(request.getSession().getId());
> getSession() although return the same session after the invalidation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2767) Cont. query remote filter requires to be in client nodes class path
[
https://issues.apache.org/jira/browse/IGNITE-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181569#comment-15181569
]
Valentin Kulichenko commented on IGNITE-2767:
-
Denis,
As far as I know we only print out the error without stopping the join process.
Probably this can be improved form usability standpoint, but it doesn't break
anything, right?
> Cont. query remote filter requires to be in client nodes class path
> ---
>
> Key: IGNITE-2767
> URL: https://issues.apache.org/jira/browse/IGNITE-2767
> Project: Ignite
> Issue Type: Bug
> Components: community, important
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
> Fix For: 1.6
>
>
> Cont. query remote filter has to be placed to class path of all client nodes
> otherwise the following exception happens
> {noformat}
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas [ ] [1]
> [tcp-disco-msg-worker-#2%cas-grid%] : Failed to unmarshal discovery data for
> component: 0 [TcpDiscoverySpi]
> 2016-03-04T15:08:24.259Z ERR cas org.apache.ignite.IgniteCheckedException:
> Failed to find class with given class loader for unmarshalling (make sure
> same versions of all classes are available
> on all nodes or enable peer-class-loading):
> sun.misc.Launcher$AppClassLoader@18b4aac2
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:108)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMarshaller.java:78)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1717)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddedMessage(ServerImpl.java:3685)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2252)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5789)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2161)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas Caused by:
> java.lang.ClassNotFoundException:
> com.ringcentral.tap_api.ha.RemoteFilterWrapper
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> java.lang.Class.forName0(Native Method)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> java.lang.Class.forName(Class.java:348)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8195)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> org.apache.ignite.marshaller.jdk.JdkMarshallerObjectInputStream.resolveClass(JdkMarshallerObjectInputStream.java:54)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1613)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1518)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1774)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
> 2016-03-04T15:08:24.259Z rms01-t01-rcs01.lab.nordigy.ru ERR cas at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.readExternal(CacheContinuousQueryHandler.java:1077)
> 2016-03-04T
[jira] [Commented] (IGNITE-2710) Session not unbind from current request after invoking request.getSession().invalidate()
[ https://issues.apache.org/jira/browse/IGNITE-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181570#comment-15181570 ] Valentin Kulichenko commented on IGNITE-2710: - OK, I think it can be merged then. > Session not unbind from current request after invoking > request.getSession().invalidate() > > > Key: IGNITE-2710 > URL: https://issues.apache.org/jira/browse/IGNITE-2710 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.5.0.final > Environment: java8, tomcat8 >Reporter: YuxuanWang >Assignee: Roman Shtykh > Labels: community, session, user > Fix For: 1.6 > > > System.out.println(request.getSession().getId()); > request.getSession().invalidate(); > System.out.println(request.getSession().getId()); > getSession() although return the same session after the invalidation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2765) WebSessionFilter and SpringCache don't survive client reconnect
[
https://issues.apache.org/jira/browse/IGNITE-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2765:
Summary: WebSessionFilter and SpringCache don't survive client reconnect
(was: WebSessionFilter doesn't survive client reconnect)
> WebSessionFilter and SpringCache don't survive client reconnect
> ---
>
> Key: IGNITE-2765
> URL: https://issues.apache.org/jira/browse/IGNITE-2765
> Project: Ignite
> Issue Type: Bug
> Components: websession
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Labels: community, customer, important
> Fix For: 1.6
>
>
> If a {{WebSessionFilter}} is started with an embedded client, it is not
> functional after the client disconnects and reconnects. Any operation throws
> the exception below.
> {noformat}
> java.lang.IllegalStateException: Cache has been closed or destroyed: WebCache
> at
> org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:160)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.onEnter(IgniteCacheProxy.java:1958)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:855)
> at
> org.apache.ignite.cache.websession.WebSessionFilter.doFilter0(WebSessionFilter.java:341)
> {noformat}
> We should get a new instance of the cache when the exception is thrown.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2765) WebSessionFilter doesn't survive client reconnect
[
https://issues.apache.org/jira/browse/IGNITE-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181813#comment-15181813
]
Valentin Kulichenko commented on IGNITE-2765:
-
The same issue exists in {{SpringCache}}.
Hibernate L2 cache should be also checked.
> WebSessionFilter doesn't survive client reconnect
> -
>
> Key: IGNITE-2765
> URL: https://issues.apache.org/jira/browse/IGNITE-2765
> Project: Ignite
> Issue Type: Bug
> Components: websession
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Labels: community, customer, important
> Fix For: 1.6
>
>
> If a {{WebSessionFilter}} is started with an embedded client, it is not
> functional after the client disconnects and reconnects. Any operation throws
> the exception below.
> {noformat}
> java.lang.IllegalStateException: Cache has been closed or destroyed: WebCache
> at
> org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:160)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.onEnter(IgniteCacheProxy.java:1958)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:855)
> at
> org.apache.ignite.cache.websession.WebSessionFilter.doFilter0(WebSessionFilter.java:341)
> {noformat}
> We should get a new instance of the cache when the exception is thrown.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-2322) Downloads page lists incorrect maven version/maven central has not been updated
[ https://issues.apache.org/jira/browse/IGNITE-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-2322. --- > Downloads page lists incorrect maven version/maven central has not been > updated > --- > > Key: IGNITE-2322 > URL: https://issues.apache.org/jira/browse/IGNITE-2322 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: James Bench > Labels: documentation, maven > > The downloads page lists the latest version from Maven as 1.5.0.final - the > latest version available from Maven Central is 1.5.0-b1. > https://ignite.apache.org/download.cgi#maven > http://mvnrepository.com/artifact/org.apache.ignite/ignite-core -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-2322) Downloads page lists incorrect maven version/maven central has not been updated
[ https://issues.apache.org/jira/browse/IGNITE-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-2322. - Resolution: Not A Problem > Downloads page lists incorrect maven version/maven central has not been > updated > --- > > Key: IGNITE-2322 > URL: https://issues.apache.org/jira/browse/IGNITE-2322 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: James Bench > Labels: documentation, maven > > The downloads page lists the latest version from Maven as 1.5.0.final - the > latest version available from Maven Central is 1.5.0-b1. > https://ignite.apache.org/download.cgi#maven > http://mvnrepository.com/artifact/org.apache.ignite/ignite-core -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2770) Document custom SQL functions
Valentin Kulichenko created IGNITE-2770: --- Summary: Document custom SQL functions Key: IGNITE-2770 URL: https://issues.apache.org/jira/browse/IGNITE-2770 Project: Ignite Issue Type: Task Components: documentation Reporter: Valentin Kulichenko Assignee: Valentin Kulichenko -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2769) Document store session listeners
Valentin Kulichenko created IGNITE-2769: --- Summary: Document store session listeners Key: IGNITE-2769 URL: https://issues.apache.org/jira/browse/IGNITE-2769 Project: Ignite Issue Type: Task Components: documentation Reporter: Valentin Kulichenko Assignee: Valentin Kulichenko -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2771) Document machine safety
Valentin Kulichenko created IGNITE-2771: --- Summary: Document machine safety Key: IGNITE-2771 URL: https://issues.apache.org/jira/browse/IGNITE-2771 Project: Ignite Issue Type: Task Components: documentation Reporter: Valentin Kulichenko Assignee: Valentin Kulichenko -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2772) Document plugin development
Valentin Kulichenko created IGNITE-2772: --- Summary: Document plugin development Key: IGNITE-2772 URL: https://issues.apache.org/jira/browse/IGNITE-2772 Project: Ignite Issue Type: Task Components: documentation Reporter: Valentin Kulichenko -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2770) Document custom SQL functions
[ https://issues.apache.org/jira/browse/IGNITE-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2770: Fix Version/s: 1.6 > Document custom SQL functions > - > > Key: IGNITE-2770 > URL: https://issues.apache.org/jira/browse/IGNITE-2770 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Valentin Kulichenko >Assignee: Valentin Kulichenko > Fix For: 1.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2196) Broken links in the documentation
[ https://issues.apache.org/jira/browse/IGNITE-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2196: Issue Type: Task (was: Bug) > Broken links in the documentation > -- > > Key: IGNITE-2196 > URL: https://issues.apache.org/jira/browse/IGNITE-2196 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 1.5.0.final > Environment: Apache Ignite 1.5.0-final build #45 >Reporter: Vasilisa Sidorova >Assignee: Anton Vinogradov > Fix For: 1.6 > > > There is two broken links in the binary package documentation: > # IGNITE_HOME/docs/javadoc/org/apache/ignite/cache/store/CacheStore.html > (click on the CacheHibarnateBlobStore link -> go to nonexistent page > IGNITE_HOME/docs/javadoc/org/apache/ignite/cache/store/hibernate/CacheHibernateBlobStore.html) > # > IGNITE_HOME/docs/javadoc/org/apache/ignite/cache/store/CacheStoreSessionListener.html > (click on the CacheHibernateStoreSessionListener link -> go to nonexistent > page > IGNITE_HOME/docs/javadoc/org/apache/ignite/cache/store/hibernate/CacheHibernateStoreSessionListener.html) > Please, fix it -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2180) Javadocs for some modules are missing from Maven repository
[ https://issues.apache.org/jira/browse/IGNITE-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2180: Issue Type: Task (was: Bug) > Javadocs for some modules are missing from Maven repository > - > > Key: IGNITE-2180 > URL: https://issues.apache.org/jira/browse/IGNITE-2180 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 1.5.0.final > Environment: Apache Ignite 1.5.0-b2 build #112 >Reporter: Vasilisa Sidorova > Fix For: 1.6 > > > Javadocs are missing from Maven repository for following modules: > * ignite-clients > * ignite-extdata-uri > * ignite-osgi-karaf > * ignite-osgi-paxlogging > * ignite-scalar > * ignite-scalar_2.10 > * ignite-spark > * ignite-spark_2.10 > * ignite-visor-console > * ignite-visor-console_2.10 > Please, fix it -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2421) EventTypes are badly documented
[
https://issues.apache.org/jira/browse/IGNITE-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2421:
Issue Type: Task (was: Bug)
> EventTypes are badly documented
> ---
>
> Key: IGNITE-2421
> URL: https://issues.apache.org/jira/browse/IGNITE-2421
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
> Labels: important
> Fix For: 1.6
>
>
> We have to go through all the {{EventTypes}} and document them well:
> - in which conditions they are fired;
> - what kind of nodes (primary, backups or both) will receive and update;
> - etc.
> As an example.
> From {{EVT_CACHE_ENTRY_CREATED}} is not clear when it's fired at all. However
> it's fired when an entry is loaded from a storage, or when it's initially
> created due to a cache put.
> The same situation is around {{EVT_CACHE_OBJECT_PUT}}. There is no info
> saying that it's fired on both primary and backup nodes. That it's not fired
> due to a loading from a cache, etc.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2771) Document machine safety
[ https://issues.apache.org/jira/browse/IGNITE-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2771: Fix Version/s: 1.6 > Document machine safety > --- > > Key: IGNITE-2771 > URL: https://issues.apache.org/jira/browse/IGNITE-2771 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Valentin Kulichenko >Assignee: Valentin Kulichenko > Fix For: 1.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2773) Document swap space
Valentin Kulichenko created IGNITE-2773: --- Summary: Document swap space Key: IGNITE-2773 URL: https://issues.apache.org/jira/browse/IGNITE-2773 Project: Ignite Issue Type: Task Components: documentation Reporter: Valentin Kulichenko -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2731) Cache metrics documentation on readme.io
[ https://issues.apache.org/jira/browse/IGNITE-2731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2731: Issue Type: Task (was: Bug) > Cache metrics documentation on readme.io > > > Key: IGNITE-2731 > URL: https://issues.apache.org/jira/browse/IGNITE-2731 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 1.5.0.final >Reporter: Denis Magda > Fix For: 1.6 > > > Cache metrics related topic is becoming hot on the user list. > 1) > http://apache-ignite-users.70518.x6.nabble.com/Monitoring-Cache-Data-counters-Cache-Data-Size-td3203.html#a3211 > 2) > http://apache-ignite-users.70518.x6.nabble.com/Is-there-a-way-to-get-cache-metrics-for-all-the-nodes-in-cluster-combined-td2674.html > 3) > http://apache-ignite-users.70518.x6.nabble.com/Metrics-for-backup-caches-td2689.html#a2692 > The time to add a specific article for this topic has come. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2413) Twitter streamer documentation is missing on readme.io
[ https://issues.apache.org/jira/browse/IGNITE-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2413: Issue Type: Task (was: Bug) > Twitter streamer documentation is missing on readme.io > -- > > Key: IGNITE-2413 > URL: https://issues.apache.org/jira/browse/IGNITE-2413 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 1.5.0.final >Reporter: Denis Magda >Priority: Blocker > Fix For: 1.5.0.final > > > Twitter streamer was released as a part of 1.5. However there is no > documentation available on readme.io describing the new streaming > functionality. > Following documentation can be used as a reference > https://apacheignite.readme.io/docs/jms-data-streamer > https://apacheignite.readme.io/docs/flume-data-streamer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2511) Missing docs on readme.io for Zookeeper-based cluster discovery
[ https://issues.apache.org/jira/browse/IGNITE-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2511: Issue Type: Task (was: Bug) > Missing docs on readme.io for Zookeeper-based cluster discovery > --- > > Key: IGNITE-2511 > URL: https://issues.apache.org/jira/browse/IGNITE-2511 > Project: Ignite > Issue Type: Task > Components: documentation, ignite-zookeeper >Reporter: Roman Shtykh > Labels: documentation > Fix For: 1.6 > > > Nothing is said on how to use ZookeeperIpFinder on > https://apacheignite.readme.io/docs/cluster-config -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2769) Document store session listeners
[ https://issues.apache.org/jira/browse/IGNITE-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2769: Fix Version/s: 1.6 > Document store session listeners > > > Key: IGNITE-2769 > URL: https://issues.apache.org/jira/browse/IGNITE-2769 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Valentin Kulichenko >Assignee: Valentin Kulichenko > Fix For: 1.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2096) AtomicConfiguration and CollectionConfiguration should be properly checked for consistency
[
https://issues.apache.org/jira/browse/IGNITE-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2096:
Labels: usability (was: newbie)
> AtomicConfiguration and CollectionConfiguration should be properly checked
> for consistency
> --
>
> Key: IGNITE-2096
> URL: https://issues.apache.org/jira/browse/IGNITE-2096
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Labels: usability
> Fix For: 1.6
>
>
> Currently {{AtomicConfiguration}} and {{CollectionConfiguration}} are mapped
> to system caches configuration and consistency is checked like for any other
> cache. This leads to unintuitive errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2774) Add JPA-based store session listener
Valentin Kulichenko created IGNITE-2774: --- Summary: Add JPA-based store session listener Key: IGNITE-2774 URL: https://issues.apache.org/jira/browse/IGNITE-2774 Project: Ignite Issue Type: Improvement Components: cache Reporter: Valentin Kulichenko Assignee: Valentin Kulichenko Fix For: 1.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2735) Interrupt all acquires on local node after ignite.close
[
https://issues.apache.org/jira/browse/IGNITE-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183850#comment-15183850
]
Valentin Kulichenko commented on IGNITE-2735:
-
Vladislav,
I meant that if gateway is used, everything is handled automatically. You don't
need {{stop()} callback on the semaphore as well as {{if(isBroken())}} all over
the place. Can these unnecessary changes be removed?
Let me know if I'm missing something.
> Interrupt all acquires on local node after ignite.close
> ---
>
> Key: IGNITE-2735
> URL: https://issues.apache.org/jira/browse/IGNITE-2735
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 1.6
>Reporter: Vladisav Jelisavcic
>Assignee: Vladisav Jelisavcic
> Fix For: 1.5.0.final
>
>
> "acquire" method should throw an exception when semaphore is no longer
> accessible when node is stopped.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-2735) Interrupt all acquires on local node after ignite.close
[
https://issues.apache.org/jira/browse/IGNITE-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183850#comment-15183850
]
Valentin Kulichenko edited comment on IGNITE-2735 at 3/7/16 10:22 PM:
--
Vladislav,
I meant that if gateway is used, everything is handled automatically. You don't
need {{stop()}} callback on the semaphore as well as {{if(isBroken())}} all
over the place. Can these unnecessary changes be removed?
Let me know if I'm missing something.
was (Author: vkulichenko):
Vladislav,
I meant that if gateway is used, everything is handled automatically. You don't
need {{stop()} callback on the semaphore as well as {{if(isBroken())}} all over
the place. Can these unnecessary changes be removed?
Let me know if I'm missing something.
> Interrupt all acquires on local node after ignite.close
> ---
>
> Key: IGNITE-2735
> URL: https://issues.apache.org/jira/browse/IGNITE-2735
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 1.6
>Reporter: Vladisav Jelisavcic
>Assignee: Vladisav Jelisavcic
> Fix For: 1.5.0.final
>
>
> "acquire" method should throw an exception when semaphore is no longer
> accessible when node is stopped.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-2735) Interrupt all acquires on local node after ignite.close
[
https://issues.apache.org/jira/browse/IGNITE-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183850#comment-15183850
]
Valentin Kulichenko edited comment on IGNITE-2735 at 3/7/16 10:22 PM:
--
Vladislav,
I meant that if gateway is used, everything is handled automatically. You don't
need {{stop()}} callback on the semaphore as well as {{if(isBroken())}} checks
all over the place. Can these unnecessary changes be removed?
Let me know if I'm missing something.
was (Author: vkulichenko):
Vladislav,
I meant that if gateway is used, everything is handled automatically. You don't
need {{stop()}} callback on the semaphore as well as {{if(isBroken())}} all
over the place. Can these unnecessary changes be removed?
Let me know if I'm missing something.
> Interrupt all acquires on local node after ignite.close
> ---
>
> Key: IGNITE-2735
> URL: https://issues.apache.org/jira/browse/IGNITE-2735
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 1.6
>Reporter: Vladisav Jelisavcic
>Assignee: Vladisav Jelisavcic
> Fix For: 1.5.0.final
>
>
> "acquire" method should throw an exception when semaphore is no longer
> accessible when node is stopped.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2749) Web session clustering works incorrectly with WebLogic
[
https://issues.apache.org/jira/browse/IGNITE-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2749:
Assignee: Anton Vinogradov (was: Valentin Kulichenko)
> Web session clustering works incorrectly with WebLogic
> --
>
> Key: IGNITE-2749
> URL: https://issues.apache.org/jira/browse/IGNITE-2749
> Project: Ignite
> Issue Type: Bug
>Reporter: Valentin Kulichenko
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.6
>
> Attachments: master_ee01b61_ignite-2749.patch
>
>
> {{WebSessionFilter}} has a special processing for the session ID generated by
> WebLogic. The issue is that this processing is not applied in all required
> cases. E.g., session ID is transformed when new session is saved in cache
> (see {{createSession}} method, but not transformed when it's fetched from
> cache (see {{doFilter0}}.
> Need to go through the code, locate incorrect places and fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2776) Need to support JTA transactions via synchronization callback
Valentin Kulichenko created IGNITE-2776:
---
Summary: Need to support JTA transactions via synchronization
callback
Key: IGNITE-2776
URL: https://issues.apache.org/jira/browse/IGNITE-2776
Project: Ignite
Issue Type: Improvement
Affects Versions: 1.5.0.final
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
Priority: Critical
Fix For: 1.6
Need to add an option to enlist transaction as
{{javax.transaction.Synchronization}} instead of XA resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-2776) Need to support JTA transactions via synchronization callback
[
https://issues.apache.org/jira/browse/IGNITE-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko closed IGNITE-2776.
---
> Need to support JTA transactions via synchronization callback
> -
>
> Key: IGNITE-2776
> URL: https://issues.apache.org/jira/browse/IGNITE-2776
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Labels: community, customer, important
> Fix For: 1.6
>
>
> Need to add an option to enlist transaction as
> {{javax.transaction.Synchronization}} instead of XA resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-2776) Need to support JTA transactions via synchronization callback
[
https://issues.apache.org/jira/browse/IGNITE-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko resolved IGNITE-2776.
-
Resolution: Fixed
Done in master.
Added {{TransactionConfiguration.setUseJtaSynchronization()}} configuration
flag.
> Need to support JTA transactions via synchronization callback
> -
>
> Key: IGNITE-2776
> URL: https://issues.apache.org/jira/browse/IGNITE-2776
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Labels: community, customer, important
> Fix For: 1.6
>
>
> Need to add an option to enlist transaction as
> {{javax.transaction.Synchronization}} instead of XA resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2758) IGNITE_HOME/libs/ignite-aws/aws-java-sdk-1.10.29.jar doesn't contain any classes
[
https://issues.apache.org/jira/browse/IGNITE-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188433#comment-15188433
]
Valentin Kulichenko commented on IGNITE-2758:
-
Vasilisa,
I made another fix in master, can you please recheck?
> IGNITE_HOME/libs/ignite-aws/aws-java-sdk-1.10.29.jar doesn't contain any
> classes
>
>
> Key: IGNITE-2758
> URL: https://issues.apache.org/jira/browse/IGNITE-2758
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: community, customer, important
> Fix For: 1.6
>
>
> To observe the issue do this:
> * Build the fabric ZIP file.
> * Go to {{ignite-aws}} module folder.
> * Unzip {{aws-java-sdk-1.10.29.jar}}.
> * JAR file contains only pom.xml, no classes.
> We need to make sure that all required AWS SDK components are included. At
> least we need these ones:
> * aws-java-sdk-core
> * aws-java-sdk-s3
> * joda-time
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2758) IGNITE_HOME/libs/ignite-aws/aws-java-sdk-1.10.29.jar doesn't contain any classes
[
https://issues.apache.org/jira/browse/IGNITE-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2758:
Assignee: Vasilisa Sidorova (was: Valentin Kulichenko)
> IGNITE_HOME/libs/ignite-aws/aws-java-sdk-1.10.29.jar doesn't contain any
> classes
>
>
> Key: IGNITE-2758
> URL: https://issues.apache.org/jira/browse/IGNITE-2758
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Vasilisa Sidorova
>Priority: Blocker
> Labels: community, customer, important
> Fix For: 1.6
>
>
> To observe the issue do this:
> * Build the fabric ZIP file.
> * Go to {{ignite-aws}} module folder.
> * Unzip {{aws-java-sdk-1.10.29.jar}}.
> * JAR file contains only pom.xml, no classes.
> We need to make sure that all required AWS SDK components are included. At
> least we need these ones:
> * aws-java-sdk-core
> * aws-java-sdk-s3
> * joda-time
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2756) StreamVisitorExample returns empty result set
[
https://issues.apache.org/jira/browse/IGNITE-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2756:
Assignee: Sergey Kozlov
> StreamVisitorExample returns empty result set
> -
>
> Key: IGNITE-2756
> URL: https://issues.apache.org/jira/browse/IGNITE-2756
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.6
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>
> 1. Start {{ExampleNodeStartup}}
> 2. Start {{StreamVisitorExample}}
> {noformat}
> [15:31:22] Ignite node started OK (id=4395613e)
> [15:31:22] Topology snapshot [ver=2, servers=1, clients=1, CPUs=8, heap=7.1GB]
> Number of tuples streamed into Ignite: 50
> Number of tuples streamed into Ignite: 100
> ...
> Number of tuples streamed into Ignite: 950
> Number of tuples streamed into Ignite: 1000
> Top performing financial instruments:
> Query result set is empty.
> [15:31:47] Ignite node stopped OK [uptime=00:00:25:209]
> Process finished with exit code 0
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2756) StreamVisitorExample returns empty result set
[
https://issues.apache.org/jira/browse/IGNITE-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188565#comment-15188565
]
Valentin Kulichenko commented on IGNITE-2756:
-
Sergey,
I fixed the example in master. Can you please verify?
> StreamVisitorExample returns empty result set
> -
>
> Key: IGNITE-2756
> URL: https://issues.apache.org/jira/browse/IGNITE-2756
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.6
>Reporter: Sergey Kozlov
>
> 1. Start {{ExampleNodeStartup}}
> 2. Start {{StreamVisitorExample}}
> {noformat}
> [15:31:22] Ignite node started OK (id=4395613e)
> [15:31:22] Topology snapshot [ver=2, servers=1, clients=1, CPUs=8, heap=7.1GB]
> Number of tuples streamed into Ignite: 50
> Number of tuples streamed into Ignite: 100
> ...
> Number of tuples streamed into Ignite: 950
> Number of tuples streamed into Ignite: 1000
> Top performing financial instruments:
> Query result set is empty.
> [15:31:47] Ignite node stopped OK [uptime=00:00:25:209]
> Process finished with exit code 0
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-2749) Web session clustering works incorrectly with WebLogic
[
https://issues.apache.org/jira/browse/IGNITE-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko reassigned IGNITE-2749:
---
Assignee: Valentin Kulichenko (was: Anton Vinogradov)
> Web session clustering works incorrectly with WebLogic
> --
>
> Key: IGNITE-2749
> URL: https://issues.apache.org/jira/browse/IGNITE-2749
> Project: Ignite
> Issue Type: Bug
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.6
>
> Attachments: master_ee01b61_ignite-2749.patch
>
>
> {{WebSessionFilter}} has a special processing for the session ID generated by
> WebLogic. The issue is that this processing is not applied in all required
> cases. E.g., session ID is transformed when new session is saved in cache
> (see {{createSession}} method, but not transformed when it's fetched from
> cache (see {{doFilter0}}.
> Need to go through the code, locate incorrect places and fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-2749) Web session clustering works incorrectly with WebLogic
[
https://issues.apache.org/jira/browse/IGNITE-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko closed IGNITE-2749.
---
> Web session clustering works incorrectly with WebLogic
> --
>
> Key: IGNITE-2749
> URL: https://issues.apache.org/jira/browse/IGNITE-2749
> Project: Ignite
> Issue Type: Bug
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.6
>
> Attachments: master_ee01b61_ignite-2749.patch
>
>
> {{WebSessionFilter}} has a special processing for the session ID generated by
> WebLogic. The issue is that this processing is not applied in all required
> cases. E.g., session ID is transformed when new session is saved in cache
> (see {{createSession}} method, but not transformed when it's fetched from
> cache (see {{doFilter0}}.
> Need to go through the code, locate incorrect places and fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2785) Improve test coverage for web session clustering
Valentin Kulichenko created IGNITE-2785:
---
Summary: Improve test coverage for web session clustering
Key: IGNITE-2785
URL: https://issues.apache.org/jira/browse/IGNITE-2785
Project: Ignite
Issue Type: Improvement
Components: websession
Affects Versions: 1.5.0.final
Reporter: Valentin Kulichenko
Assignee: Anton Vinogradov
Fix For: 1.6
Web session clustering is not very well covered with tests. What should be done:
* Add more unit tests for different cases.
* Test with different cache configurations.
* Make {{ignite-weblogic-test}} more verbose and use it to check functionality
on a "real" app with different app servers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2786) SpringCache doesn't survive client reconnect
Valentin Kulichenko created IGNITE-2786: --- Summary: SpringCache doesn't survive client reconnect Key: IGNITE-2786 URL: https://issues.apache.org/jira/browse/IGNITE-2786 Project: Ignite Issue Type: Improvement Components: cache Affects Versions: 1.5.0.final Reporter: Valentin Kulichenko Assignee: Valentin Kulichenko Fix For: 1.6 After a client disconnects and reconnects with new ID, Spring caching can't be used, because existing cache instance are closed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2765) WebSessionFilter doesn't survive client reconnect
[
https://issues.apache.org/jira/browse/IGNITE-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2765:
Summary: WebSessionFilter doesn't survive client reconnect (was:
WebSessionFilter and SpringCache don't survive client reconnect)
> WebSessionFilter doesn't survive client reconnect
> -
>
> Key: IGNITE-2765
> URL: https://issues.apache.org/jira/browse/IGNITE-2765
> Project: Ignite
> Issue Type: Bug
> Components: websession
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Labels: community, customer, important
> Fix For: 1.6
>
>
> If a {{WebSessionFilter}} is started with an embedded client, it is not
> functional after the client disconnects and reconnects. Any operation throws
> the exception below.
> {noformat}
> java.lang.IllegalStateException: Cache has been closed or destroyed: WebCache
> at
> org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:160)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.onEnter(IgniteCacheProxy.java:1958)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:855)
> at
> org.apache.ignite.cache.websession.WebSessionFilter.doFilter0(WebSessionFilter.java:341)
> {noformat}
> We should get a new instance of the cache when the exception is thrown.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-2786) SpringCache doesn't survive client reconnect
[ https://issues.apache.org/jira/browse/IGNITE-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko reassigned IGNITE-2786: --- Assignee: Valentin Kulichenko > SpringCache doesn't survive client reconnect > > > Key: IGNITE-2786 > URL: https://issues.apache.org/jira/browse/IGNITE-2786 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 1.5.0.final >Reporter: Valentin Kulichenko >Assignee: Valentin Kulichenko > Fix For: 1.6 > > > After a client disconnects and reconnects with new ID, Spring caching can't > be used, because existing cache instance are closed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2787) Hibernate L2 cache doesn't survive client reconnect
Valentin Kulichenko created IGNITE-2787: --- Summary: Hibernate L2 cache doesn't survive client reconnect Key: IGNITE-2787 URL: https://issues.apache.org/jira/browse/IGNITE-2787 Project: Ignite Issue Type: Improvement Components: cache Affects Versions: 1.5.0.final Reporter: Valentin Kulichenko Assignee: Valentin Kulichenko Fix For: 1.6 After a client disconnects and reconnects with new ID, Hibernate L2 cache can't be used, because existing cache instance are closed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2786) SpringCache doesn't survive client reconnect
[ https://issues.apache.org/jira/browse/IGNITE-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2786: Assignee: (was: Valentin Kulichenko) > SpringCache doesn't survive client reconnect > > > Key: IGNITE-2786 > URL: https://issues.apache.org/jira/browse/IGNITE-2786 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 1.5.0.final >Reporter: Valentin Kulichenko > Fix For: 1.6 > > > After a client disconnects and reconnects with new ID, Spring caching can't > be used, because existing cache instance are closed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2765) WebSessionFilter doesn't survive client reconnect
[
https://issues.apache.org/jira/browse/IGNITE-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188670#comment-15188670
]
Valentin Kulichenko commented on IGNITE-2765:
-
Created separate tickets for Spring cache and Hibernate L2 cache:
https://issues.apache.org/jira/browse/IGNITE-2786
https://issues.apache.org/jira/browse/IGNITE-2787
> WebSessionFilter doesn't survive client reconnect
> -
>
> Key: IGNITE-2765
> URL: https://issues.apache.org/jira/browse/IGNITE-2765
> Project: Ignite
> Issue Type: Bug
> Components: websession
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Labels: community, customer, important
> Fix For: 1.6
>
>
> If a {{WebSessionFilter}} is started with an embedded client, it is not
> functional after the client disconnects and reconnects. Any operation throws
> the exception below.
> {noformat}
> java.lang.IllegalStateException: Cache has been closed or destroyed: WebCache
> at
> org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:160)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.onEnter(IgniteCacheProxy.java:1958)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:855)
> at
> org.apache.ignite.cache.websession.WebSessionFilter.doFilter0(WebSessionFilter.java:341)
> {noformat}
> We should get a new instance of the cache when the exception is thrown.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2775) HttpRequest.changeSessionId() won't change session id
[
https://issues.apache.org/jira/browse/IGNITE-2775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188682#comment-15188682
]
Valentin Kulichenko commented on IGNITE-2775:
-
Looks good to me.
> HttpRequest.changeSessionId() won't change session id
> -
>
> Key: IGNITE-2775
> URL: https://issues.apache.org/jira/browse/IGNITE-2775
> Project: Ignite
> Issue Type: Bug
> Components: websession
>Affects Versions: 1.5.0.final
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
> Fix For: 1.6
>
>
> After
> {code}
> request.changeSessionId();
> {code}
> {code}
> request.getSession().getId();
> {code}
> returns the old session id.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2795) Cache query cursor do not create value copy
Valentin Kulichenko created IGNITE-2795: --- Summary: Cache query cursor do not create value copy Key: IGNITE-2795 URL: https://issues.apache.org/jira/browse/IGNITE-2795 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 1.5.0.final Reporter: Valentin Kulichenko Priority: Critical Fix For: 1.6 If entries returned from SQL query are modified, these changes are reflected in the cache. Test attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2795) Cache query cursor do not create value copy
[ https://issues.apache.org/jira/browse/IGNITE-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2795: Attachment: QueryTest.java > Cache query cursor do not create value copy > --- > > Key: IGNITE-2795 > URL: https://issues.apache.org/jira/browse/IGNITE-2795 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.5.0.final >Reporter: Valentin Kulichenko >Priority: Critical > Fix For: 1.6 > > Attachments: QueryTest.java > > > If entries returned from SQL query are modified, these changes are reflected > in the cache. > Test attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1071) IgniteCache.metrics() method returns local metrics
[
https://issues.apache.org/jira/browse/IGNITE-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190035#comment-15190035
]
Valentin Kulichenko commented on IGNITE-1071:
-
Semen, I think we should check other MBeans as well. From what I see in the
code, non-cache metrics are also node-local in MBeans.
> IgniteCache.metrics() method returns local metrics
> --
>
> Key: IGNITE-1071
> URL: https://issues.apache.org/jira/browse/IGNITE-1071
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>Priority: Minor
> Labels: Usability
> Fix For: 1.6
>
>
> To get metrics for the whole cluster user needs to use
> {{cache.metrics(ignite.cluster())}}, which is counterintuitive and
> inconsistent with other APIs. {{IgniteCache.metrics()}} w/o parameters should
> return metrics for the whole cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
