May 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3132) Remove Metadata.read() method

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3132?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3132: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1830 > Remove Metadata.read() method > ----------------------------- > > Key: ISPN-3132 > URL: https://issues.jboss.org/browse/ISPN-3132 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 5.3.0.CR1 > > > As I started writing the documentation for Metadata, I came to the same conclusion that Mircea did WRT Metadata.read() method. It does not really make sense. Better to have a helper method that where needed, applies version information. Keeps interface clean and the helper method is always available. > I'm also moving Metadata and related metadata classes to org.infinispan.metadata package to avoid polluting root package. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3132) Remove Metadata.read() method

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-3132: -------------------------------------- Summary: Remove Metadata.read() method Key: ISPN-3132 URL: https://issues.jboss.org/browse/ISPN-3132 Project: Infinispan Issue Type: Enhancement Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.3.0.CR1 As I started writing the documentation for Metadata, I came to the same conclusion that Mircea did WRT Metadata.read() method. It does not really make sense. Better to have a helper method that where needed, applies version information. Keeps interface clean and the helper method is always available. I'm also moving Metadata and related metadata classes to org.infinispan.metadata package to avoid polluting root package. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3131) Calling forget() when not in a recovery-enabled cache should not throw a NPE

by Manik Surtani (JIRA)

Manik Surtani created ISPN-3131: ----------------------------------- Summary: Calling forget() when not in a recovery-enabled cache should not throw a NPE Key: ISPN-3131 URL: https://issues.jboss.org/browse/ISPN-3131 Project: Infinispan Issue Type: Feature Request Components: Transactions Affects Versions: 5.2.6.Final Reporter: Manik Surtani Assignee: Mircea Markus Fix For: 5.3.0.CR1, 5.3.0.Final In some cases, a cache may be configured not to have recovery enabled, but may run in an environment where a transaction manager may try and call forget(). This should *not* cause a {{NullPointerException}} which will propagate to the transaction manager and cause more issues. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3127) Shell scripts broken on AIX

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3127?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-3127: --------------------------------------- Well, in this case the requirement is a version of bash which doesn't break at that line in the script. You are using 3.2.16. I see the latest in the 3.2 series is 3.2.48, but I don't know how easy it is for you to upgrade. The script works fine here with bash 4.2. Does IBM provide a 4.2 for your version of AIX ? > Shell scripts broken on AIX > --------------------------- > > Key: ISPN-3127 > URL: https://issues.jboss.org/browse/ISPN-3127 > Project: Infinispan > Issue Type: Bug > Reporter: Kranti Deepak > Assignee: Tristan Tarrant > > Please specify infinispan system requirements. > I have deployed Infinispan on windows xp, windows7 and linux-redhat (all 32 bit) its working good. But unable to start on AIX 64bit version. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3127) Shell scripts broken on AIX

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3127?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3127: ---------------------------------- Summary: Shell scripts broken on AIX (was: Broken ) > Shell scripts broken on AIX > --------------------------- > > Key: ISPN-3127 > URL: https://issues.jboss.org/browse/ISPN-3127 > Project: Infinispan > Issue Type: Feature Request > Reporter: Kranti Deepak > Assignee: Tristan Tarrant > > Please specify infinispan system requirements. > I have deployed Infinispan on windows xp, windows7 and linux-redhat (all 32 bit) its working good. But unable to start on AIX 64bit version. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3127) Shell scripts broken on AIX

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3127?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3127: ---------------------------------- Issue Type: Bug (was: Feature Request) > Shell scripts broken on AIX > --------------------------- > > Key: ISPN-3127 > URL: https://issues.jboss.org/browse/ISPN-3127 > Project: Infinispan > Issue Type: Bug > Reporter: Kranti Deepak > Assignee: Tristan Tarrant > > Please specify infinispan system requirements. > I have deployed Infinispan on windows xp, windows7 and linux-redhat (all 32 bit) its working good. But unable to start on AIX 64bit version. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3127) Broken

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3127?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3127: ---------------------------------- Summary: Broken (was: Infinispan system requirements) > Broken > ------- > > Key: ISPN-3127 > URL: https://issues.jboss.org/browse/ISPN-3127 > Project: Infinispan > Issue Type: Feature Request > Reporter: Kranti Deepak > Assignee: Mircea Markus > > Please specify infinispan system requirements. > I have deployed Infinispan on windows xp, windows7 and linux-redhat (all 32 bit) its working good. But unable to start on AIX 64bit version. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3127) Broken

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3127?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3127: ------------------------------------- Assignee: Tristan Tarrant (was: Mircea Markus) > Broken > ------- > > Key: ISPN-3127 > URL: https://issues.jboss.org/browse/ISPN-3127 > Project: Infinispan > Issue Type: Feature Request > Reporter: Kranti Deepak > Assignee: Tristan Tarrant > > Please specify infinispan system requirements. > I have deployed Infinispan on windows xp, windows7 and linux-redhat (all 32 bit) its working good. But unable to start on AIX 64bit version. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1990) Preload sets the versions to null (repeatable read + write skew)

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-1990?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-1990: ----------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/1829 > Preload sets the versions to null (repeatable read + write skew) > ---------------------------------------------------------------- > > Key: ISPN-1990 > URL: https://issues.jboss.org/browse/ISPN-1990 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 5.1.3.FINAL > Environment: Java 6 (64bits) > Infinispan 5.2.0-SNAPSHOT > MacOS > Reporter: Pedro Ruivo > Assignee: Galder Zamarreño > Labels: preload, skew, versioning, write > Fix For: 5.3.0.Final > > > I think I've spotted a issue when I use repeatable read with write skew check and I preload the cache. > > I've made a test case to reproduce the bug. It can be found here [1]. > The problem is that each keys preloaded is put in the container with version = null. When I try to commit a transaction, I get this exception: > > {code} > java.lang.IllegalStateException: Entries cannot have null versions! > at org.infinispan.container.entries.ClusteredRepeatableReadEntry.performWriteSkewCheck(ClusteredRepeatableReadEntry.java:44) > at org.infinispan.transaction.WriteSkewHelper.performWriteSkewCheckAndReturnNewVersions(WriteSkewHelper.java:81) > at org.infinispan.interceptors.locking.ClusteringDependentLogic$AllNodesLogic.createNewVersionsAndCheckForWriteSkews(ClusteringDependentLogic.java:133) > at org.infinispan.interceptors.VersionedEntryWrappingInterceptor.visitPrepareCommand(VersionedEntryWrappingInterceptor.java:64) > {code} > > I think that all info is in the test case, but if you need something let > me know. > > Cheers, > Pedro > [1] > https://github.com/pruivo/infinispan/blob/issue_1/core/src/test/java/org/... -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3130) Cancelling an InboundTransferTask should be idempotent

by Dan Berindei (JIRA)

Dan Berindei created ISPN-3130: ---------------------------------- Summary: Cancelling an InboundTransferTask should be idempotent Key: ISPN-3130 URL: https://issues.jboss.org/browse/ISPN-3130 Project: Infinispan Issue Type: Bug Components: State transfer Affects Versions: 5.2.6.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 5.3.0.Final When installing a new topology, it's possible for the {{StateConsumerImpl.cancelSegments}} method to fail with an {{IllegalArgumentException}}: {code} 05:43:56,513 WARN [org.infinispan.topology.CacheTopologyControlCommand] (notification-thread-0) ISPN000071: Caught exception when handling command CacheTopologyControlCommand{cache=default-host/clusterbench, type=CH_UPDATE, sender=perf21/web, joinInfo=null, topologyId=23, currentCH=DefaultConsistentHash{numSegments=80, numOwners=2, members=[perf21/web, perf18/web, perf19/web]}, pendingCH=null, throwable=null, viewId=8}: java.lang.IllegalArgumentException: The task is already cancelled. at org.infinispan.statetransfer.InboundTransferTask.cancelSegments(InboundTransferTask.java:167) at org.infinispan.statetransfer.StateConsumerImpl.cancelTransfers(StateConsumerImpl.java:774) at org.infinispan.statetransfer.StateConsumerImpl.onTopologyUpdate(StateConsumerImpl.java:314) at org.infinispan.statetransfer.StateTransferManagerImpl.doTopologyUpdate(StateTransferManagerImpl.java:195) at org.infinispan.statetransfer.StateTransferManagerImpl.access$000(StateTransferManagerImpl.java:61) at org.infinispan.statetransfer.StateTransferManagerImpl$1.updateConsistentHash(StateTransferManagerImpl.java:121) at org.infinispan.topology.LocalTopologyManagerImpl.handleConsistentHashUpdate(LocalTopologyManagerImpl.java:202) at org.infinispan.topology.CacheTopologyControlCommand.doPerform(CacheTopologyControlCommand.java:165) at org.infinispan.topology.CacheTopologyControlCommand.perform(CacheTopologyControlCommand.java:137) at org.infinispan.topology.ClusterTopologyManagerImpl.executeOnClusterSync(ClusterTopologyManagerImpl.java:540) at org.infinispan.topology.ClusterTopologyManagerImpl.broadcastConsistentHashUpdate(ClusterTopologyManagerImpl.java:332) at org.infinispan.topology.ClusterTopologyManagerImpl.updateCacheStatusAfterMerge(ClusterTopologyManagerImpl.java:319) at org.infinispan.topology.ClusterTopologyManagerImpl.handleNewView(ClusterTopologyManagerImpl.java:236) at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener.handleViewChange(ClusterTopologyManagerImpl.java:579) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_43] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_43] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_43] at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_43] at org.infinispan.notifications.AbstractListenerImpl$ListenerInvocation$1.run(AbstractListenerImpl.java:212) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_43] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_43] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_43] {code} Instead, it should just log a message and ignore the cancel request. -- 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

12 years, 10 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 2013