[JBoss JIRA] Resolved: (ISPN-47) Pre-release checklist
by Manik Surtani (JIRA)
[ https://jira.jboss.org/jira/browse/ISPN-47?page=com.atlassian.jira.plugin... ]
Manik Surtani resolved ISPN-47.
-------------------------------
Fix Version/s: (was: 4.0.0.CR2)
Resolution: Done
> Pre-release checklist
> ---------------------
>
> Key: ISPN-47
> URL: https://jira.jboss.org/jira/browse/ISPN-47
> Project: Infinispan
> Issue Type: Task
> Reporter: Manik Surtani
> Assignee: Manik Surtani
> Fix For: 4.0.0.GA
>
>
> * Import tests from JBC core 3.x to make sure we haven't lost any features
> * Text search for all comments, Strings, log messages, Javadocs that refer to (Node, TreeCache, Region, Starobrno, JBossCache) and replace with proper wording pertaining to Horizon.
> * Ensure all TODOs in the code is dealt with
> * Update documentation
> * Benchmark + tune
> * Feature comparison with Coherence, Terracotta and gigaspaces
> * TestSuite - try to use testNg @Factory to avoid inheritance
> * TestSuite - if async replication is in use, make sure that all the test are *forced* to wait for all replication messages
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (ISPN-240) Removals not working as expected when L1 is disabled
by Galder Zamarreno (JIRA)
Removals not working as expected when L1 is disabled
----------------------------------------------------
Key: ISPN-240
URL: https://jira.jboss.org/jira/browse/ISPN-240
Project: Infinispan
Issue Type: Bug
Components: Distributed Cache
Affects Versions: 4.0.0.CR1
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Fix For: 4.0.0.CR2
The following is what happens when L1 is not enabled for distribution:
Let's say you call put on 5 keys [k1-k5] on node A of a two node cluster [A,B] and the distribution should be something like: A[k1,k2,k5] and B[k3,k4].
What really happens is that A *stores all keys* [k1,k2,k3,k4,k5] and B stores [k3,k4]. So, if you now call remove[k1-k5] from B, all the keys in B will be deleted and only the keys that should have belonged to A would be deleted, so the result is that A will still contain [k3,k4].
With L1, this is not an issue cos whenever there's a write on that key, the L1 is invalidated, so the above test would result on both A and B not containing any keys.
I'm in the process of replicating this in a smaller unit test. I'm not sure yet what the fix for this would be.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Updated: (ISPN-47) Pre-release checklist
by Manik Surtani (JIRA)
[ https://jira.jboss.org/jira/browse/ISPN-47?page=com.atlassian.jira.plugin... ]
Manik Surtani updated ISPN-47:
------------------------------
Fix Version/s: 4.0.0.CR2
(was: 4.0.0.CR1)
> Pre-release checklist
> ---------------------
>
> Key: ISPN-47
> URL: https://jira.jboss.org/jira/browse/ISPN-47
> Project: Infinispan
> Issue Type: Task
> Reporter: Manik Surtani
> Assignee: Manik Surtani
> Fix For: 4.0.0.CR2, 4.0.0.GA
>
>
> * Import tests from JBC core 3.x to make sure we haven't lost any features
> * Text search for all comments, Strings, log messages, Javadocs that refer to (Node, TreeCache, Region, Starobrno, JBossCache) and replace with proper wording pertaining to Horizon.
> * Ensure all TODOs in the code is dealt with
> * Update documentation
> * Benchmark + tune
> * Feature comparison with Coherence, Terracotta and gigaspaces
> * TestSuite - try to use testNg @Factory to avoid inheritance
> * TestSuite - if async replication is in use, make sure that all the test are *forced* to wait for all replication messages
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (ISPN-234) Serialization exception thrown if objects in distibuted cache do not implement the serializiable interface
by Noel O'Connor (JIRA)
Serialization exception thrown if objects in distibuted cache do not implement the serializiable interface
-----------------------------------------------------------------------------------------------------------
Key: ISPN-234
URL: https://jira.jboss.org/jira/browse/ISPN-234
Project: Infinispan
Issue Type: Bug
Components: Distributed Cache
Affects Versions: 4.0.0.BETA2
Reporter: Noel O'Connor
Assignee: Manik Surtani
When running a cache in distributed mode with but with just one instance running. NumOwners set to two or more.
Insert objects which do not implement the serializable interface.
Bring up a second cache instance and upon the join even the following exception is thrown
[java] 6585 [main] DEBUG org.infinispan.jmx.ResourceDMBean - @MBean description set - Component that handles distribution of content across a cluster
[java] 6587 [main] DEBUG org.infinispan.jmx.ResourceDMBean - @MBean description set - Manager that handles MVCC locks for entries
[java] 6588 [main] DEBUG org.infinispan.jmx.ResourceDMBean - @MBean description set - General statistics such as timings, hit/miss ratio, etc.
[java] 6590 [main] DEBUG org.infinispan.jmx.ResourceDMBean - @MBean description set - Manages all remote calls to remote cache instances in the cluster.
[java] 6594 [main] DEBUG org.infinispan.jmx.ResourceDMBean - @MBean description set - Component that manages the cache's participation in JTA transactions.
[java] 6595 [main] INFO org.infinispan.jmx.CacheJmxRegistration - MBeans were successfully registered to the platform mbean server.
[java] 6595 [Rehasher-redlappie-1032] DEBUG org.infinispan.distribution.JoinTask - Commencing
[java] 6597 [main] INFO org.infinispan.factories.ComponentRegistry - Infinispan version: Infinispan 'Starobrno' 4.0.0.BETA2
[java] 6742 [Rehasher-redlappie-1032] DEBUG org.infinispan.distribution.JoinTask - Retrieved old consistent hash address list [redlappie-23510]
[java] 6742 [Rehasher-redlappie-1032] DEBUG org.infinispan.distribution.JoinTask - Retrieved old consistent hash address list [redlappie-23510]
[java] 6766 [Rehasher-redlappie-1032] DEBUG org.infinispan.distribution.JoinTask - Retrieved old consistent hash address list [redlappie-23510]
[java] 8421 [Rehasher-redlappie-1032] INFO org.infinispan.distribution.JoinTask - Completed in 2.04 seconds!
[java] 8533 [Rehasher-redlappie-1032] INFO org.infinispan.distribution.JoinTask - Completed in 1.94 seconds!
[java] 9640 [Rehasher-redlappie-1032] ERROR org.infinispan.remoting.rpc.RpcManagerImpl - unexpected error while replicating
[java] java.lang.ClassCastException: java.io.NotSerializableException cannot be cast to org.infinispan.remoting.responses.Response
[java] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:378)
[java] at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:87)
[java] at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:106)
[java] at org.infinispan.distribution.JoinTask.performRehash(JoinTask.java:118)
[java] at org.infinispan.distribution.RehashTask.call(RehashTask.java:52)
[java] at org.infinispan.distribution.RehashTask.call(RehashTask.java:30)
[java] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
[java] at java.util.concurrent.FutureTask.run(FutureTask.java:138)
[java] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[java] at java.lang.Thread.run(Thread.java:619)
[java] 9641 [Rehasher-redlappie-1032] ERROR org.infinispan.distribution.JoinTask - Caught exception!
[java] org.infinispan.CacheException: java.lang.ClassCastException: java.io.NotSerializableException cannot be cast to org.infinispan.remoting.responses.Response
[java] at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:100)
[java] at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:106)
[java] at org.infinispan.distribution.JoinTask.performRehash(JoinTask.java:118)
[java] at org.infinispan.distribution.RehashTask.call(RehashTask.java:52)
[java] at org.infinispan.distribution.RehashTask.call(RehashTask.java:30)
[java] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
[java] at java.util.concurrent.FutureTask.run(FutureTask.java:138)
[java] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[java] at java.lang.Thread.run(Thread.java:619)
[java] Caused by: java.lang.ClassCastException: java.io.NotSerializableException cannot be cast to org.infinispan.remoting.responses.Response
[java] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:378)
[java] at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:87)
[java] ... 9 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months