December 2010 - infinispan-issues

[JBoss JIRA] Created: (ISPN-822) Allow retrieving coordinator address from EmbeddedCacheManager

by Tristan Tarrant (JIRA)

Allow retrieving coordinator address from EmbeddedCacheManager -------------------------------------------------------------- Key: ISPN-822 URL: https://jira.jboss.org/browse/ISPN-822 Project: Infinispan Issue Type: Feature Request Components: Core API Affects Versions: 4.2.0.CR3 Reporter: Tristan Tarrant Assignee: Manik Surtani Priority: Minor Fix For: 4.2.0.CR4 In order to get the coordinator's address I go through the following hoops: cache.getAdvancedCache().getRpcManager().getTransport().getCoordinator().getJGroupsAddress(). which requires obtaining a clustered cache first. the EmbeddedCacheManager interface exposes several methods to access the local address, the address of all members and whether the local address is also coordinator, but there is no method to get the cluster's coordinator address. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-736) Shipped jgroups files should be shipped in root of jar

by Galder Zamarreño (JIRA)

Shipped jgroups files should be shipped in root of jar ------------------------------------------------------ Key: ISPN-736 URL: https://jira.jboss.org/browse/ISPN-736 Project: Infinispan Issue Type: Task Components: Configuration, RPC Affects Versions: 4.2.0.ALPHA4 Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.BETA1, 5.0.0.Final 4.0.0.FINAL and 4.1.0.FINAL are shipping jgroups-*.xml files under config-samples/ directory. Instead, these files should be located on root so that people can apply configurations such as: <transport clusterName="infinispan-cluster" distributedSyncTimeout="50000" nodeName="Jalapeno"> <properties> <property name="configurationFile" value="jgroups-udp.xml"/> </properties> </transport> -- 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

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-821) Make Memcached flush_all consistent with other servers

by Galder Zamarreño (JIRA)

Make Memcached flush_all consistent with other servers ------------------------------------------------------ Key: ISPN-821 URL: https://jira.jboss.org/browse/ISPN-821 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 4.2.0.CR3, 4.1.0.Final Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 4.2.0.CR4, 4.2.0.Final REST and Hot Rod servers do a cluster wide clear when delete cache, or clear command is sent to them. Memcached should behave in the same way when flush_all is sent. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
4
0 / 0

[JBoss JIRA] Created: (ISPN-817) Maven Archetype for a skeleton Infinispan project

by Manik Surtani (JIRA)

Maven Archetype for a skeleton Infinispan project ------------------------------------------------- Key: ISPN-817 URL: https://jira.jboss.org/browse/ISPN-817 Project: Infinispan Issue Type: Feature Request Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.2.0.Final Maven archetypes can be used to create a skeleton project, complete with a pom with necessary dependencies and sample code, to get people started on building projects using Infinispan. http://maven.apache.org/guides/introduction/introduction-to-archetypes.html http://maven.apache.org/archetype/maven-archetype-plugin/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-818) Maven Archetype for a skeleton Infinispan unit test

by Manik Surtani (JIRA)

Maven Archetype for a skeleton Infinispan unit test --------------------------------------------------- Key: ISPN-818 URL: https://jira.jboss.org/browse/ISPN-818 Project: Infinispan Issue Type: Feature Request Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.2.0.Final Infinispan users tend to report bugs by submitting unit or functional tests, but these tests are often cumbersome and are not always easily migratable to Infinispan's own testsuite. An archetype for this can be created which would declare dependencies on Infinispan and necessary test helpers, and create a skeleton test in a format appropriate for potential inclusion into Infinispan. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (ISPN-816) Configdoc Javadoc link is incorrect

by Manik Surtani (JIRA)

Configdoc Javadoc link is incorrect ----------------------------------- Key: ISPN-816 URL: https://jira.jboss.org/browse/ISPN-816 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 4.2.0.CR2 Reporter: Manik Surtani Assignee: Vladimir Blagojevic Fix For: 4.2.0.CR3 E.g., http://docs.jboss.org/infinispan/4.2/apidocs/config.html#ce_default_trans... under useEagerLocking - the Javadoc link takes you to TransactionType#useEagerLocking which has no Javdocs on it! The programmatic way of setting this is to use Configuration#setUseEagerLocking(). So the link should go to http://docs.jboss.org/infinispan/4.2/apidocs/org/infinispan/config/Config... which has actual Javadocs on it. The bean already has a ref to this setter thanks to the @ConfigurationDocRef annotation so it should be easy. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-808) Provide programmatic access to RemoteCacheManager configuration data

by Richard Achmatowicz (JIRA)

Provide programmatic access to RemoteCacheManager configuration data -------------------------------------------------------------------- Key: ISPN-808 URL: https://jira.jboss.org/browse/ISPN-808 Project: Infinispan Issue Type: Bug Affects Versions: 4.1.0.Final, 4.2.0.CR2 Reporter: Richard Achmatowicz Assignee: Mircea Markus Fix For: 4.2.0.Final The javadoc for the interface org.infinispan.client.hotrod.RemoteCache incorrectly marks a number of operations as supported, whereas the code throws an UnsupportedOperationException when the se methods are invoked. The methods in question are: void evict() Configuration getConfiguration() void addListener() Set<Object> getListeners() void removeListener() -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (ISPN-790) Extract version info to a separate version.properties file

by Manik Surtani (JIRA)

Extract version info to a separate version.properties file ---------------------------------------------------------- Key: ISPN-790 URL: https://jira.jboss.org/browse/ISPN-790 Project: Infinispan Issue Type: Feature Request Components: Core API Affects Versions: 4.1.0.Final Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.2.0.CR1, 4.2.0.Final Makes it easier for release scripts to update. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
6
0 / 0

[JBoss JIRA] Created: (ISPN-815) Clone caches should be created and started much faster

by Galder Zamarreño (JIRA)

Clone caches should be created and started much faster ------------------------------------------------------ Key: ISPN-815 URL: https://jira.jboss.org/browse/ISPN-815 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 4.2.0.CR2 Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 4.2.0.Final We must be faster creating caches that are just simply copies of the same configuration. Creating 500 caches of the default cache configuration takes around 4 seconds. Creating 1000 caches takes around 10 seconds. This is too slow. As shown in the profiler screenshot, calling componentRegistry.registerComponent(spi, AdvancedCache.class); is quite expensive. The start procedure is also quite expensive, specially due to some reflection going on there. IMO, we need fast way to clone caches. IOW, if you create Cache A based on config default config, creating/starting Cache B based on default config should be extremely fast. Simply duplicate objects and set them in the right state. This is of particular importance in 2LC use cases where each entity/collection is stored in a separate cache and these are generally created on startup by the Hibernate Session Factory. Check the linked user forum post for some feedback from a 2LC user. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (ISPN-760) Provide meaningful Hot Rod exceptions to Java clients

by Galder Zamarreño (JIRA)

Provide meaningful Hot Rod exceptions to Java clients ----------------------------------------------------- Key: ISPN-760 URL: https://jira.jboss.org/browse/ISPN-760 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 4.2.0.BETA1 Reporter: Galder Zamarreño Assignee: Mircea Markus Fix For: 4.2.0.CR1 "I've got following exeception: HotRodServerException{messageId=2, errorStatusCode=133} org.infinispan.client.hotrod.exceptions.HotRodClientException: at org.infinispan.client.hotrod.impl.operations.HotRodOperation.checkForErrorsInResponseStatus(HotRodOperation.java:129) at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:98) at org.infinispan.client.hotrod.impl.operations.AbstractKeyOperation.sendKeyOperation(AbstractKeyOperation.java:48) at org.infinispan.client.hotrod.impl.operations.GetOperation.executeOperation(GetOperation.java:26) at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:38) at org.infinispan.client.hotrod.impl.RemoteCacheImpl.get(RemoteCacheImpl.java:283) at pl.carrierex.manager.DomainManager.getDomainData(DomainManager.java:166) ............... there is no information what is wrong, maybe you know where I can find description for errorStatusCode=133 ?" "In this example cache was not defined on HotRod server" The Java Hot Rod client should launder exceptions into something that's meaningful to the user. -- 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

13 years, 5 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2010