October 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4046) New query dsl does not support isNull filters for non-string properties

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4046?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4046: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > New query dsl does not support isNull filters for non-string properties > ----------------------------------------------------------------------- > > Key: ISPN-4046 > URL: https://issues.jboss.org/browse/ISPN-4046 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 6.0.1.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: 630 > Fix For: 7.0.0.CR2, 7.0.0.Final > > > String properties can be supported because of Hibernate Search null token, but HSearch only offers this for strings and not for other types. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4159?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4159: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > 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.CR2, 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.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4136) Declarative config for REST rawValues

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4136?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4136: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > Declarative config for REST rawValues > ------------------------------------- > > Key: ISPN-4136 > URL: https://issues.jboss.org/browse/ISPN-4136 > Project: Infinispan > Issue Type: Task > Components: Configuration > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.CR2, 7.0.0.Final > > > Once ISPN-3514 is in we can add support for the REST rawValues boolean in the new 7.0 parser -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4182?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4182: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > 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.CR2, 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.3.1#6329)

11 years, 6 months

1
0
0 / 0

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4176?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4176: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > 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.CR2 > > > {{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.3.1#6329)

11 years, 6 months

1
0
0 / 0

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4167?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4167: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > 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.CR2 > > > 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.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4166) useSynchronization should be disabled by default

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4166?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4166: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > useSynchronization should be disabled by default > ------------------------------------------------ > > Key: ISPN-4166 > URL: https://issues.jboss.org/browse/ISPN-4166 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration, Transactions > Affects Versions: 6.0.2.Final > Reporter: Dan Berindei > Assignee: Ion Savin > Priority: Critical > Fix For: 7.0.0.CR2, 7.0.0.Final > > > When Infinispan registers with the transaction manager as a synchronization, failures during commit are not reported to the user. > Even if registering as a synchronization is faster in some cases, the default should be the safe version. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4262) Rolling back a transaction after commit timeout should release locks in two phases

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4262?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4262: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > Rolling back a transaction after commit timeout should release locks in two phases > ---------------------------------------------------------------------------------- > > Key: ISPN-4262 > URL: https://issues.jboss.org/browse/ISPN-4262 > 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.CR2 > > > This is related to ISPN-4137. > When a commit command times out, we send a rollback command to release locks. The problem is that the node that timed out might still execute commit command, before the rollback command reaching the backup but after it released the locks on the primary owner. > The solution is to not release any locks during the rollback command's execution, but send an asynchronous TxCompletionNotification afterwards - just like for commit commands. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4289) Provide a user friendly error for not being able to parse 6.0 configuration files

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4289?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4289: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > Provide a user friendly error for not being able to parse 6.0 configuration files > --------------------------------------------------------------------------------- > > Key: ISPN-4289 > URL: https://issues.jboss.org/browse/ISPN-4289 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Sanne Grinovero > Assignee: Dan Berindei > Fix For: 7.0.0.CR2, 7.0.0.Final > > > When failing to parse a configuration file in XML format from Infinispan 6.0 (apparently now unsupported) the error message should be improved. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4190?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4190: ------------------------------- Fix Version/s: 7.0.0.CR2 (was: 7.0.0.CR1) > 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.CR2 > > > 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.3.1#6329)

11 years, 6 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 October 2014