April 2014 - infinispan-issues - Jboss List Archives

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

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-4177?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-4177: -------------------------------- Fix Version/s: 7.0.0.Alpha4 (was: 7.0.0.Alpha3) > 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.Alpha4, 7.0.0.Final > > -- 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, 12 months

1
0
0 / 0

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

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-4167?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-4167: -------------------------------- Fix Version/s: 7.0.0.Alpha4 (was: 7.0.0.Alpha3) > 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.Alpha4 > > > 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 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4174) Pluggable Audit logging for authentication and authorization

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-4174?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-4174: -------------------------------- Fix Version/s: 7.0.0.Alpha4 (was: 7.0.0.Alpha3) > Pluggable Audit logging for authentication and authorization > ------------------------------------------------------------ > > Key: ISPN-4174 > URL: https://issues.jboss.org/browse/ISPN-4174 > Project: Infinispan > Issue Type: Sub-task > Components: Core, Remote Protocols, Security, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.Alpha4, 7.0.0.Final > > -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4203) Update clustered cache quickstart to remove the cluster validation

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-4203?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-4203: -------------------------------- Fix Version/s: 7.0.0.Alpha4 (was: 7.0.0.Alpha3) > Update clustered cache quickstart to remove the cluster validation > ------------------------------------------------------------------ > > Key: ISPN-4203 > URL: https://issues.jboss.org/browse/ISPN-4203 > Project: Infinispan > Issue Type: Task > Components: Demos and Tutorials, Documentation-Core > Affects Versions: 6.0.2.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 7.0.0.Alpha4 > > > The clustered cache quickstart has a utility ClusteredValidation class, which waits for to see that the node has fully joined the cluster. This has not been necessary for quite a while, as {{getCache()}} does not return before the cache has finished joining. -- 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, 12 months

1
0
0 / 0

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

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-4195?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-4195: -------------------------------- Fix Version/s: 7.0.0.Alpha4 (was: 7.0.0.Alpha3) > 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.Alpha4 > > > See http://lists.jboss.org/pipermail/infinispan-dev/2014-April/014840.html -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4203) Update clustered cache quickstart to remove the cluster validation

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4203?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4203: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-quickstart/pull/13 > Update clustered cache quickstart to remove the cluster validation > ------------------------------------------------------------------ > > Key: ISPN-4203 > URL: https://issues.jboss.org/browse/ISPN-4203 > Project: Infinispan > Issue Type: Task > Components: Demos and Tutorials, Documentation-Core > Affects Versions: 6.0.2.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 7.0.0.Alpha3 > > > The clustered cache quickstart has a utility ClusteredValidation class, which waits for to see that the node has fully joined the cluster. This has not been necessary for quite a while, as {{getCache()}} does not return before the cache has finished joining. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4203) Update clustered cache quickstart to remove the cluster validation

by Dan Berindei (JIRA)

Dan Berindei created ISPN-4203: ---------------------------------- Summary: Update clustered cache quickstart to remove the cluster validation Key: ISPN-4203 URL: https://issues.jboss.org/browse/ISPN-4203 Project: Infinispan Issue Type: Task Components: Demos and Tutorials, Documentation-Core Affects Versions: 6.0.2.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 7.0.0.Alpha3 The clustered cache quickstart has a utility ClusteredValidation class, which waits for to see that the node has fully joined the cluster. This has not been necessary for quite a while, as {{getCache()}} does not return before the cache has finished joining. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4025) Cross-Site State Transfer: failure scenarios

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4025?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4025: ------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/2495 > Cross-Site State Transfer: failure scenarios > -------------------------------------------- > > Key: ISPN-4025 > URL: https://issues.jboss.org/browse/ISPN-4025 > Project: Infinispan > Issue Type: Sub-task > Components: Cross-Site Replication > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 7.0.0.Final > > > Needs to handle the following scenarios (at least): > * join/leave in the consumer site (i.e. site that receives the the state) > I think NBST will handle most of join scenario. However, the leave scenario needs to be handle carefully or we can loose some key chunks. (easy solution: resend all the chunk?) > * join/leave in the producer site (i.e. site that sends the state) > trick scenario. we have to be sure that all keys are really sent! (naive solution: restart the state transfer) > * state transfer coordinator dies > the coordinator node is the one that receives the acks when all members has finished sending the keys. Or we replicate its state or we restart the state transfer... > * site master dies in consumer site > No idea which keys was already applied or not. need to resend the chunks... -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4160) Do not allow the state transfer chunk size to be <= 0

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-4160?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-4160: -------------------------------------- Fix Version/s: 7.0.0.Alpha4 (was: 7.0.0.Alpha3) > Do not allow the state transfer chunk size to be <= 0 > ----------------------------------------------------- > > Key: ISPN-4160 > URL: https://issues.jboss.org/browse/ISPN-4160 > Project: Infinispan > Issue Type: Task > Components: Configuration, State Transfer > Affects Versions: 7.0.0.Alpha1 > Reporter: Dan Berindei > Assignee: Vladimir Blagojevic > Fix For: 7.0.0.Alpha4 > > > The state transfer chunk size is used in other places as well, and the case of {{chunkSize <= 0}} has to be handled everywhere independently. StateTransferConfigurationBuilder should validate that {{chunkSize > 0}}, so that users of the chunk size setting don't need a default value. > The users will still be able to force state transfer to transfer everything at once with {{chunkSize == Integer.MAX_VALUE}}. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2148) Improve lock timeout exception details

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-2148?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-2148: -------------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/2492 > Improve lock timeout exception details > -------------------------------------- > > Key: ISPN-2148 > URL: https://issues.jboss.org/browse/ISPN-2148 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Transactions > Affects Versions: 5.1.5.FINAL > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Minor > Fix For: 7.0.0.Alpha4 > > > I found it much easier to debug locking issues if we log the call originator in TimeoutException raised in LockingManagerImpl.java. Node that sent the call is readily available in InvocationContext#getOrigin() -- 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, 12 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 April 2014