March 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-1790) Release script should not rip off comments from XML files

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-1790: ------------------------------------- Summary: Release script should not rip off comments from XML files Key: ISPN-1790 URL: https://issues.jboss.org/browse/ISPN-1790 Project: Infinispan Issue Type: Bug Components: Build process Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 5.1.0.FINAL Comparing the git commit which was used to release 5.1.0.Final to the final tag of the released version, reveals some changes which are likely unintended: * All Copyright statements removed * All comments removed (useful and unuseful) * In some way changed the inlined scripts for Google analytics - not sure if it's still working -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
4
0 / 0

[JBoss JIRA] (ISPN-1947) Automate staging repository step in release script

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-1947: ------------------------------------- Summary: Automate staging repository step in release script Key: ISPN-1947 URL: https://issues.jboss.org/browse/ISPN-1947 Project: Infinispan Issue Type: Task Components: Build process Reporter: Sanne Grinovero Assignee: Manik Surtani Priority: Optional Fix For: 5.2.0.ALPHA1 The following plugin can be used to control the staging repository from command line (including authenticating with your account as set in your settings file) {code:xml} <plugin> <groupId>org.sonatype.plugins</groupId> <artifactId>nexus-maven-plugin</artifactId> <configuration> <nexusUrl>https://repository.jboss.org/nexus</nexusUrl> <automatic>true</automatic> </configuration> </plugin> {code} Goals are described at: https://repository.sonatype.org/content/sites/maven-sites/nexus-maven-plu... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
9
0 / 0

[JBoss JIRA] Created: (ISPN-761) Cache.keySet(), entrySet(), values(), size() ignore contents of cache loader

by Paul Ferraro (JIRA)

Cache.keySet(),entrySet(),values(),size() ignore contents of cache loader ------------------------------------------------------------------------- Key: ISPN-761 URL: https://jira.jboss.org/browse/ISPN-761 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 4.2.0.BETA1 Reporter: Paul Ferraro Assignee: Manik Surtani Passivated cache entries are not represented in values returned by the keySet(), entrySet(), values(), and size() Cache methods. This results in inconsistent behavior, since it is possible that a given cache key may not be contained in keySet() even though Cache.get(...) would return a non-null value if the entry was previously passivated. I think CacheLoaderInterceptor needs to implement the following methods: Object visitSizeCommand(InvocationContext ctx, SizeCommand command) throws Throwable Object visitValuesCommand(InvocationContext ctx, ValuesCommand command) throws Throwable Object visitEntrySetCommand(InvocationContext ctx, EntrySetCommand command) throws Throwable Object visitKeySetCommand(InvocationContext ctx, KeySetCommand command) throws Throwable -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
14
0 / 0

[JBoss JIRA] (ISPN-1951) Use MERGE3 in the default UDP configuration

by Dan Berindei (JIRA)

Dan Berindei created ISPN-1951: ---------------------------------- Summary: Use MERGE3 in the default UDP configuration Key: ISPN-1951 URL: https://issues.jboss.org/browse/ISPN-1951 Project: Infinispan Issue Type: Task Components: Configuration Affects Versions: 5.1.3.CR1, 5.1.2.FINAL Reporter: Dan Berindei Assignee: Dan Berindei Priority: Critical Fix For: 5.1.3.FINAL, 5.2.0.ALPHA1 Bela recommends using MERGE3 instead of MERGE2 in UDP clusters. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
9
0 / 0

[JBoss JIRA] (ISPN-1896) ClusteredGetCommands should never fail with a SuspectException

by Dan Berindei (JIRA)

Dan Berindei created ISPN-1896: ---------------------------------- Summary: ClusteredGetCommands should never fail with a SuspectException Key: ISPN-1896 URL: https://issues.jboss.org/browse/ISPN-1896 Project: Infinispan Issue Type: Bug Components: RPC Affects Versions: 5.1.2.CR1 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 5.1.2.FINAL I have seen this exception in the core test suite logs: {noformat} 2012-03-02 15:07:19,718 ERROR (testng-VersionedDistStateTransferTest) [org.infinispan.test.fwk.UnitTestTestNGListener] Method testStateTransfer(org.infinispan.container.versioning.VersionedDistStateTransferTest) threw an exceptionorg.infinispan.CacheException: SuspectedException at org.infinispan.util.Util.rewrapAsCacheException(Util.java:524) at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:168) at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:478) at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:148) at org.infinispan.distribution.DistributionManagerImpl.retrieveFromRemoteSource(DistributionManagerImpl.java:169) at org.infinispan.interceptors.DistributionInterceptor.realRemoteGet(DistributionInterceptor.java:212) at org.infinispan.interceptors.DistributionInterceptor.remoteGetAndStoreInL1(DistributionInterceptor.java:194) at org.infinispan.interceptors.DistributionInterceptor.remoteGetBeforeWrite(DistributionInterceptor.java:440) at org.infinispan.interceptors.DistributionInterceptor.handleWriteCommand(DistributionInterceptor.java:455) at org.infinispan.interceptors.DistributionInterceptor.visitPutKeyValueCommand(DistributionInterceptor.java:274) ... Caused by: SuspectedException at org.jgroups.blocks.MessageDispatcher.sendMessage(MessageDispatcher.java:349) at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.processSingleCall(CommandAwareRpcDispatcher.java:263) at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:163) ... 60 more {noformat} The remote get command should return null instead of failing, even if it had a single target node. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
8
0 / 0

[JBoss JIRA] (ISPN-1956) Create a Forge plugin for bootstrapping Infinispan projects

by Manik Surtani (JIRA)

Manik Surtani created ISPN-1956: ----------------------------------- Summary: Create a Forge plugin for bootstrapping Infinispan projects Key: ISPN-1956 URL: https://issues.jboss.org/browse/ISPN-1956 Project: Infinispan Issue Type: Feature Request Affects Versions: 5.1.3.FINAL Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.2.0.ALPHA1, 5.2.0.FINAL Follow the plugin creation guide, and email the forge-dev(a)lists.jboss.org mail list with any questions and the Forge team will help out :) There are plenty of examples to go on. https://docs.jboss.org/author/display/FORGE/Developing+a+Plugin -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
24
0 / 0

[JBoss JIRA] Created: (ISPN-470) HotRod client in C++

by Manik Surtani (JIRA)

HotRod client in C++ -------------------- Key: ISPN-470 URL: https://jira.jboss.org/browse/ISPN-470 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.0.0.BETA1, 5.0.0.Final .NET client impl for HotRod. Protocol is documented here: http://community.jboss.org/wiki/HotRodProtocol Could be based off the Java reference impl client: http://fisheye.jboss.org/browse/Infinispan/trunk/client/hotrod-client -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-791) On node startup, ensure all peers have compatible configurations

by Manik Surtani (JIRA)

On node startup, ensure all peers have compatible configurations ---------------------------------------------------------------- Key: ISPN-791 URL: https://jira.jboss.org/browse/ISPN-791 Project: Infinispan Issue Type: Feature Request Components: Configuration Affects Versions: 4.1.0.Final Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.0.0.BETA1, 5.0.0.Final This is to prevent caches that are supposed to be symmetric/identical from being misconfigured. Some elements are allowed to be unique, of course, such as bind addresses in JGroups as well as node names, server hints, certain props passed to cache stores, etc. A simple test could be a hash (MD5 or SHA1?) of the config XML (or a serial form of the generated Configuration bean) which is exchanged as a part of the join method. On failure of the hash check, the entire object could be checked, and if that fails as well, an appropriate ConfigurationException could be thrown. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

5
10
0 / 0

[JBoss JIRA] Created: (ISPN-1117) Make use of JGroups Exclusion Lists where possible

by Manik Surtani (JIRA)

Make use of JGroups Exclusion Lists where possible -------------------------------------------------- Key: ISPN-1117 URL: https://issues.jboss.org/browse/ISPN-1117 Project: Infinispan Issue Type: Feature Request Components: RPC Affects Versions: 5.0.0.FINAL Reporter: Manik Surtani Assignee: Vladimir Blagojevic Fix For: 5.1.0.BETA1, 5.1.0.Final See JGRP-1192 - this can be used to minimise the messages on the wire. Should only be used if UDP multicast is available though. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-201) make JDBC cache store use DB transactions for commit/rollback

by Mircea Markus (JIRA)

make JDBC cache store use DB transactions for commit/rollback ------------------------------------------------------------- Key: ISPN-201 URL: https://jira.jboss.org/jira/browse/ISPN-201 Project: Infinispan Issue Type: Feature Request Components: Loaders and Stores Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.0.0.GA current impl of JDBC cache store does not use DB transaction (nor local transactions/Connection.setAutocommit(false)) for storing the modifications created within a transaction. This might leave the store in an inconsistent state one operation fails during commit. This should be changed to either 1. use local transactions or 2. register the driver as an XAResource and rely on the TM to manage the boundaries. I would go for 1, as it would be more consistent with other CStore implementation (different cache store interceptor should be used for managing the 2'nd approach). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2012