May 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4159) DefaultTwoWayKey2StringMapper encodes objects to strings in a manner that is incompatible with string handling of some databases

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4159?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4159: ------------------------------ Fix Version/s: 7.0.0.Beta1 (was: 7.0.0.Alpha4) > DefaultTwoWayKey2StringMapper encodes objects to strings in a manner that is incompatible with string handling of some databases > -------------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-4159 > URL: https://issues.jboss.org/browse/ISPN-4159 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Beta1, 7.0.0.Final > > > DefaultTwoWayKey2StringMapper uses two neat tricks. > 1. it does not encode all supported types, it only encodes non-Strings. Strings are kept unmodified. > 2. it uses a special prefix (unicode char 0xfeff) to mark which strings were encoded and which are plain. > Unfortunately some databases, notably MySql, interpret the endianness mark (0xfeff, 0xfffe), convert to native byte order and then drop it. > This leaves us with no clue the string is not an actual String but an encoded representation of another type. This misinterpretation leads later to ClassCastExceptions in various places in core and user code. > Proposed fix: get rid of #1 and #2 optimisations. Encode all objects, including Strings and always use the ?n prefix (where n stands for the original type). Drop the 0xFEFF marker prefix. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4180) Configuration parsing incorrectly logs that the cache name is ignored

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4180?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4180: ------------------------------ Fix Version/s: 7.0.0.Beta1 (was: 7.0.0.Alpha4) > Configuration parsing incorrectly logs that the cache name is ignored > --------------------------------------------------------------------- > > Key: ISPN-4180 > URL: https://issues.jboss.org/browse/ISPN-4180 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Reporter: Jakub Markos > Assignee: Galder Zamarreño > Priority: Minor > Fix For: 7.0.0.Beta1 > > > Here: > https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... > If you configure a cache name, you get: > {code} > INFO [org.infinispan.configuration.parsing.Parser70] (ServerService Thread Pool -- 15) ISPN000293: Ignoring XML attribute NAME, please remove from configuration file > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4177) Upgrade server base to WildFly 8

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4177?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4177: ------------------------------ Fix Version/s: 7.0.0.Beta1 (was: 7.0.0.Alpha4) > Upgrade server base to WildFly 8 > -------------------------------- > > Key: ISPN-4177 > URL: https://issues.jboss.org/browse/ISPN-4177 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.Beta1, 7.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4176) Forcing a commit via recovery RecoveryAdminOperations may create a duplicate GlobalTransaction

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4176?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4176: ------------------------------ Fix Version/s: 7.0.0.Beta1 (was: 7.0.0.Alpha4) > Forcing a commit via recovery RecoveryAdminOperations may create a duplicate GlobalTransaction > ---------------------------------------------------------------------------------------------- > > Key: ISPN-4176 > URL: https://issues.jboss.org/browse/ISPN-4176 > Project: Infinispan > Issue Type: Bug > Components: Core, Transactions > Affects Versions: 6.0.2.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 7.0.0.Beta1 > > > {{RecoveryManagerImpl.forceTransactionCompletion()}} modifies the {{GlobalTransaction.address}} of the transaction being committed so that the local node is the originator. But the {{GlobalTransaction.id}} stays the same, we could have two transactions with the same {{GlobalTransaction}} - which shouldn't be possible. > We can't remove the code that changes the {{GlobalTransaction.address}}, because we use it as the originator in other parts of the code. So the only option is to generate a new id as well. > But there is another problem: RecoveryAwareTransactionTable.cleanupStaleTransactions() doesn't release the locks acquired by that transaction on the primary node. So forcing a commit with a different GlobalTransaction will not be able to acquire the locks that were held by the original transaction. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4167) DummyBaseTransactionManager doesn't clean up when rollback fails

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4167?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4167: ------------------------------ Fix Version/s: 7.0.0.Beta1 (was: 7.0.0.Alpha4) > DummyBaseTransactionManager doesn't clean up when rollback fails > ---------------------------------------------------------------- > > Key: ISPN-4167 > URL: https://issues.jboss.org/browse/ISPN-4167 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.2.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 7.0.0.Beta1 > > > If the rollback fails, the thread local holding the current transaction is not cleared, and it becomes impossible to start a new transaction on the same thread. > One way this can happen is when Infinispan registers as a XA transaction, but DummyTransactionManager is not configured to use XA Xids: > {noformat} > 12:47:57,169 ERROR (testng-ReplicationExceptionTest:) [DummyTransaction] ISPN000098: Exception while rollback > java.lang.UnsupportedOperationException > at org.infinispan.transaction.tm.DummyNoXaXid.getBranchQualifier(DummyNoXaXid.java:30) > at org.infinispan.transaction.xa.recovery.SerializableXid.<init>(SerializableXid.java:37) > at org.infinispan.transaction.xa.TransactionXaAdapter.convertXid(TransactionXaAdapter.java:251) > at org.infinispan.transaction.xa.TransactionXaAdapter.rollback(TransactionXaAdapter.java:122) > at org.infinispan.transaction.tm.DummyTransaction.runRollback(DummyTransaction.java:281) > at org.infinispan.transaction.tm.DummyTransaction.rollback(DummyTransaction.java:88) > at org.infinispan.transaction.tm.DummyBaseTransactionManager.rollback(DummyBaseTransactionManager.java:104) > at org.infinispan.CacheImpl.tryRollback(CacheImpl.java:1442) > at org.infinispan.CacheImpl.executeCommandAndCommitIfNeeded(CacheImpl.java:1418) > at org.infinispan.CacheImpl.putInternal(CacheImpl.java:894) > at org.infinispan.CacheImpl.put(CacheImpl.java:886) > at org.infinispan.CacheImpl.put(CacheImpl.java:1461) > at org.infinispan.CacheImpl.put(CacheImpl.java:225) > at org.infinispan.tx.synchronisation.ReplicationExceptionTest.testSyncReplTimeout(ReplicationExceptionTest.java:54) > {noformat} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4190) Use Message.Flag.DONT_LOOPBACK instead of RequestOptions.setExclusionList

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4190?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4190: ------------------------------ Fix Version/s: 7.0.0.Beta1 (was: 7.0.0.Alpha4) > Use Message.Flag.DONT_LOOPBACK instead of RequestOptions.setExclusionList > ------------------------------------------------------------------------- > > Key: ISPN-4190 > URL: https://issues.jboss.org/browse/ISPN-4190 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.0.0.Alpha2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 7.0.0.Beta1 > > > We are currently using {{RequestOptions.setExclusionList(channel.getAddress())}} in CommandAwareRpcDispatcher, to prevent the sender of an RPC to receive that message. We can't use {{Channel.setDiscardOwnMessages(true)}}, because TO requires messages to be delivered to self. > JGroups 3.5.0.Beta2 has added a {{DONT_LOOPBACK}} flag, which should be a lot more efficient than using the exclusion list. We should start using it. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4182) ClusteredCacheWithAsyncDirTest does not properly ensure each db url is unique for parallel tests

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4182?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4182: ------------------------------ Fix Version/s: 7.0.0.Beta1 (was: 7.0.0.Alpha4) > ClusteredCacheWithAsyncDirTest does not properly ensure each db url is unique for parallel tests > ------------------------------------------------------------------------------------------------ > > Key: ISPN-4182 > URL: https://issues.jboss.org/browse/ISPN-4182 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 7.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: 630 > Fix For: 7.0.0.Beta1, 7.0.0.Final > > > The test should ensure the db url is not the same across nodes of all parallel tests because they all run in the same jvm and the H2 instances might collide. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4197) Replace batching="true|false" with <transaction mode="BATCH"/> in infinispan subsystem schema/model

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4197?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4197: ------------------------------ Fix Version/s: 7.0.0.Beta1 (was: 7.0.0.Alpha4) > Replace batching="true|false" with <transaction mode="BATCH"/> in infinispan subsystem schema/model > --------------------------------------------------------------------------------------------------- > > Key: ISPN-4197 > URL: https://issues.jboss.org/browse/ISPN-4197 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.0.Beta1 > > > Suggested by Paul in https://issues.jboss.org/browse/WFLY-3227, makes sense. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4195) Clarify how L1 is enabled in XSD and configuration with new parser

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4195?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4195: ------------------------------ Fix Version/s: 7.0.0.Beta1 (was: 7.0.0.Alpha4) > Clarify how L1 is enabled in XSD and configuration with new parser > ------------------------------------------------------------------ > > Key: ISPN-4195 > URL: https://issues.jboss.org/browse/ISPN-4195 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.0.Beta1 > > > See http://lists.jboss.org/pipermail/infinispan-dev/2014-April/014840.html -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4193) StateSequencer: state machine-based utility for synchronizing multi-threaded tests

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4193?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4193: ------------------------------ Fix Version/s: 7.0.0.Beta1 (was: 7.0.0.Alpha4) > StateSequencer: state machine-based utility for synchronizing multi-threaded tests > ---------------------------------------------------------------------------------- > > Key: ISPN-4193 > URL: https://issues.jboss.org/browse/ISPN-4193 > Project: Infinispan > Issue Type: Feature Request > Components: Test Suite - Core > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 7.0.0.Beta1 > > > I've previously written a {{CheckPoint}} class for the same purpose, but while the logs are a little clearer, it's still pretty hard to reason about the expected ordering of events with a CheckPoint-based test. > StateSequencer-based tests should make it clear what the expected order of states should be from the beginning of the test: > {code:java} > sequencer.logicalThread("t1", "t1:block", "t1:resume"); > sequencer.logicalThread("t2", "t2:do_stuff"); > sequencer.order("t1:block", "t2:do_stuff", "t1:resume"); > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2014