May 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3109) Define(reuse) a language independent serialisation protocol for storing data in the cache

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3109?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3109: -------------------------------- Description: The basic requirement is: write a Person object from a C++ hotrod client and read it from a Java/C# client, or in embedded mode. Analysis: https://docs.google.com/spreadsheet/ccc?key=0Ag5RGdzR_GsldDdOVnpwbDUyT20x... was:The basic requirement is: write a Person object from a C++ hotrod client and read it from a Java/C# client, or in embedded mode. > Define(reuse) a language independent serialisation protocol for storing data in the cache > ----------------------------------------------------------------------------------------- > > Key: ISPN-3109 > URL: https://issues.jboss.org/browse/ISPN-3109 > Project: Infinispan > Issue Type: Task > Reporter: Mircea Markus > Assignee: Adrian Nistor > > The basic requirement is: write a Person object from a C++ hotrod client and read it from a Java/C# client, or in embedded mode. > Analysis: https://docs.google.com/spreadsheet/ccc?key=0Ag5RGdzR_GsldDdOVnpwbDUyT20x... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3109) Define(reuse) a language independent serialisation protocol for storing data in the cache

by Mircea Markus (JIRA)

Mircea Markus created ISPN-3109: ----------------------------------- Summary: Define(reuse) a language independent serialisation protocol for storing data in the cache Key: ISPN-3109 URL: https://issues.jboss.org/browse/ISPN-3109 Project: Infinispan Issue Type: Task Reporter: Mircea Markus Assignee: Adrian Nistor The basic requirement is: write a Person object from a C++ hotrod client and read it from a Java/C# client, or in embedded mode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3046) Add WebSocket endpoint to server

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-3046?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-3046: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add WebSocket endpoint to server > -------------------------------- > > Key: ISPN-3046 > URL: https://issues.jboss.org/browse/ISPN-3046 > Project: Infinispan > Issue Type: Task > Components: Server > Affects Versions: 5.3.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 5.3.0.Beta2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3108) Server endpoint compatibility enhancements

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3108?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3108: ----------------------------------- Description: Several TODOs: - Transaction's lookedUpEntries, affected and lockedKeys should use equivalent collections - Change equivalent hash set to be based on JSR-166 - Make CollectionFactory a per cache component and contain references to key/value equivalence - figure out a way to have comparable ByteArrayEquivalence implementation and uncomment tests - MetadataMortalCacheValue should extend MortalCacheValue, check others... - EntryFactoryImpl.extractMetadata: "this is invoked from wrapEntryForPut and wrapEntryForReplace. Better make these two methods receive the metadata object directly from the caller, which is aware of these commands being MetadataAwareCommand, in order to avoid the not-so-nice instanceOf." - Have `Builder lifespan(long time);` in Metadata builder interface and same for maxIdle. was: Several TODOs: - Transaction's lookedUpEntries, affected and lockedKeys should use equivalent collections - Change equivalent hash set to be based on JSR-166 - Make CollectionFactory a per cache component and contain references to key/value equivalence - figure out a way to have comparable ByteArrayEquivalence implementation and uncomment tests - MetadataMortalCacheValue should extend MortalCacheValue, check others... - EntryFactoryImpl.extractMetadata: "this is invoked from wrapEntryForPut and wrapEntryForReplace. Better make these two methods receive the metadata object directly from the caller, which is aware of these commands being MetadataAwareCommand, in order to avoid the not-so-nice instanceOf." > Server endpoint compatibility enhancements > ------------------------------------------ > > Key: ISPN-3108 > URL: https://issues.jboss.org/browse/ISPN-3108 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 5.3.0.Final > > > Several TODOs: > - Transaction's lookedUpEntries, affected and lockedKeys should use equivalent collections > - Change equivalent hash set to be based on JSR-166 > - Make CollectionFactory a per cache component and contain references to key/value equivalence > - figure out a way to have comparable ByteArrayEquivalence implementation and uncomment tests > - MetadataMortalCacheValue should extend MortalCacheValue, check others... > - EntryFactoryImpl.extractMetadata: "this is invoked from wrapEntryForPut and wrapEntryForReplace. Better make these two methods receive the metadata object directly from the caller, which is aware of these commands being MetadataAwareCommand, in order to avoid the not-so-nice instanceOf." > - Have `Builder lifespan(long time);` in Metadata builder interface and same for maxIdle. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3108) Server endpoint compatibility enhancements

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-3108: -------------------------------------- Summary: Server endpoint compatibility enhancements Key: ISPN-3108 URL: https://issues.jboss.org/browse/ISPN-3108 Project: Infinispan Issue Type: Enhancement Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.3.0.Final Several TODOs: - Transaction's lookedUpEntries, affected and lockedKeys should use equivalent collections - Change equivalent hash set to be based on JSR-166 - Make CollectionFactory a per cache component and contain references to key/value equivalence - figure out a way to have comparable ByteArrayEquivalence implementation and uncomment tests - MetadataMortalCacheValue should extend MortalCacheValue, check others... - EntryFactoryImpl.extractMetadata: "this is invoked from wrapEntryForPut and wrapEntryForReplace. Better make these two methods receive the metadata object directly from the caller, which is aware of these commands being MetadataAwareCommand, in order to avoid the not-so-nice instanceOf." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2896) org.infinispan.lucene.DirectoryOnMultipleCachesTest.verifyIntendedLockCachesUsage fails randomly

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2896?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2896: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > org.infinispan.lucene.DirectoryOnMultipleCachesTest.verifyIntendedLockCachesUsage fails randomly > ------------------------------------------------------------------------------------------------ > > Key: ISPN-2896 > URL: https://issues.jboss.org/browse/ISPN-2896 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Affects Versions: 5.2.2.Final > Reporter: Anna Manukyan > Assignee: Sanne Grinovero > Labels: stable_embedded_query > Fix For: 5.3.0.CR1 > > > org.infinispan.lucene.DirectoryOnMultipleCachesTest.verifyIntendedLockCachesUsage fails randomly. The error message is: > {code} > java.lang.AssertionError > at org.infinispan.lucene.DirectoryOnMultipleCachesTest.verifyIntendedLockCachesUsage(DirectoryOnMultipleCachesTest.java:96) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:715) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3083) Recovery parser always enable it

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3083?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3083: -------------------------------- Fix Version/s: 5.3.0.Beta2 > Recovery parser always enable it > -------------------------------- > > Key: ISPN-3083 > URL: https://issues.jboss.org/browse/ISPN-3083 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 5.3.0.Beta1 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Minor > Fix For: 5.3.0.Beta2, 5.3.0.Final > > > in TransactionConfigurationBuilder: > {code:java} > public RecoveryConfigurationBuilder recovery() { > recovery.enable(); > return recovery; > } > {code} > This will enable the Recovery in configurations like this: > {code:xml} > <namedCache name="noRecovery"> > <transaction (...) transactionMode="NON_TRANSACTIONAL"> > <recovery enabled="false" recoveryInfoCacheName="someName"/> > </transaction> > </namedCache> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3063) Data Inconsistency when Recovery + syncCommitPhase=false

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3063?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3063: -------------------------------- Fix Version/s: 5.3.0.Beta2 5.3.0.Final > Data Inconsistency when Recovery + syncCommitPhase=false > -------------------------------------------------------- > > Key: ISPN-3063 > URL: https://issues.jboss.org/browse/ISPN-3063 > Project: Infinispan > Issue Type: Bug > Components: Transactions > Affects Versions: 5.2.5.Final, 5.3.0.Alpha1 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Minor > Labels: recovery, transaction > Fix For: 5.3.0.Beta2, 5.3.0.Final > > > with syncCommitPhase=false, the CommitCommand is sent asynchronously. the TransactionCoordinator sends immediately the TxCompletionNotificationCommand that can be deliver first than the CommitCommand. The CommitCommand fails silently: > {code} > if (transaction == null) { > if (trace) log.tracef("Did not find a RemoteTransaction for %s", globalTx); > return invalidRemoteTxReturnValue(); > } > } > {code} > This bug affects the 5.3 and 5.2.5. I've made one test case to catch this bug: > 5.3 => https://github.com/pruivo/infinispan/blob/rec-async/core/src/test/java/or... > 5.2 => https://github.com/pruivo/infinispan/blob/rec-async-5.2/core/src/test/jav... > Note: this bug may happen if you use async communication (prepare in 1PC) > Note2: this may be related to https://issues.jboss.org/browse/ISPN-2719 > Possible solutions: > * do not allow to configure the cache with syncCommitPhase=false && recovery enabled; > * force syncCommitPhase=true when recovery is enabled; > * send the CommitCommand and the TxCompletionNotificationCommand as Regular Messages (they will be deliver in FIFO order) > Thanks to Diego Didona that spotted this bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3063) Data Inconsistency when Recovery + syncCommitPhase=false

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3063?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3063: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Data Inconsistency when Recovery + syncCommitPhase=false > -------------------------------------------------------- > > Key: ISPN-3063 > URL: https://issues.jboss.org/browse/ISPN-3063 > Project: Infinispan > Issue Type: Bug > Components: Transactions > Affects Versions: 5.2.5.Final, 5.3.0.Alpha1 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Minor > Labels: recovery, transaction > Fix For: 5.3.0.Beta2, 5.3.0.Final > > > with syncCommitPhase=false, the CommitCommand is sent asynchronously. the TransactionCoordinator sends immediately the TxCompletionNotificationCommand that can be deliver first than the CommitCommand. The CommitCommand fails silently: > {code} > if (transaction == null) { > if (trace) log.tracef("Did not find a RemoteTransaction for %s", globalTx); > return invalidRemoteTxReturnValue(); > } > } > {code} > This bug affects the 5.3 and 5.2.5. I've made one test case to catch this bug: > 5.3 => https://github.com/pruivo/infinispan/blob/rec-async/core/src/test/java/or... > 5.2 => https://github.com/pruivo/infinispan/blob/rec-async-5.2/core/src/test/jav... > Note: this bug may happen if you use async communication (prepare in 1PC) > Note2: this may be related to https://issues.jboss.org/browse/ISPN-2719 > Possible solutions: > * do not allow to configure the cache with syncCommitPhase=false && recovery enabled; > * force syncCommitPhase=true when recovery is enabled; > * send the CommitCommand and the TxCompletionNotificationCommand as Regular Messages (they will be deliver in FIFO order) > Thanks to Diego Didona that spotted this bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3083) Recovery parser always enable it

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3083?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3083: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Recovery parser always enable it > -------------------------------- > > Key: ISPN-3083 > URL: https://issues.jboss.org/browse/ISPN-3083 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 5.3.0.Beta1 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Minor > Fix For: 5.3.0.Beta2, 5.3.0.Final > > > in TransactionConfigurationBuilder: > {code:java} > public RecoveryConfigurationBuilder recovery() { > recovery.enable(); > return recovery; > } > {code} > This will enable the Recovery in configurations like this: > {code:xml} > <namedCache name="noRecovery"> > <transaction (...) transactionMode="NON_TRANSACTIONAL"> > <recovery enabled="false" recoveryInfoCacheName="someName"/> > </transaction> > </namedCache> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2013