September 2012 - infinispan-issues

[JBoss JIRA] (ISPN-2203) Test AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle is unstable

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2203: -------------------------------------- Summary: Test AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle is unstable Key: ISPN-2203 URL: https://issues.jboss.org/browse/ISPN-2203 Project: Infinispan Issue Type: Feature Request Reporter: Galder Zamarreño Assignee: Tomas Sykora Fix For: 5.2.0.ALPHA3 Test being disabled as part of ISPN-2196 cos it's unstable. -- 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

11 years, 7 months

4
7
0 / 0

[JBoss JIRA] (ISPN-2249) Fix test failures introduced with NBST

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2249: ----------------------------------- Summary: Fix test failures introduced with NBST Key: ISPN-2249 URL: https://issues.jboss.org/browse/ISPN-2249 Project: Infinispan Issue Type: Bug Components: State transfer Affects Versions: 5.2.0.Alpha3 Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.2.0.Alpha4 -- 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, 7 months

4
18
0 / 0

[JBoss JIRA] (ISPN-2301) DefaultConsistentHash does not use group annotation.

by Erik Salter (JIRA)

Erik Salter created ISPN-2301: --------------------------------- Summary: DefaultConsistentHash does not use group annotation. Key: ISPN-2301 URL: https://issues.jboss.org/browse/ISPN-2301 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 5.2.0.Alpha3 Reporter: Erik Salter Assignee: Mircea Markus Part of my design pattern is to use the Group API to group like-minded keys to the same segment. The DefaultConsistentHash impl, in returning the primary owner of a key, uses the key's hash code instead of the Group annotation value. According to TRACE logs, this results in remote LockControlCommand. See the comments for ISPN-2291 for logs associated with such keys. (These keys use "edgeDeviceId=" as the group 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, 7 months

5
7
0 / 0

[JBoss JIRA] (ISPN-2326) c3p0 not part of the release

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-2326: ---------------------------------- Summary: c3p0 not part of the release Key: ISPN-2326 URL: https://issues.jboss.org/browse/ISPN-2326 Project: Infinispan Issue Type: Feature Request Components: Build process Affects Versions: 5.2.0.Alpha4 Reporter: Thomas Fromm Assignee: Mircea Markus According infinispan-5.2.0.Alpha4-all/modules/cachestores/jdbc/runtime-classpath.txt c3p0 lib should be part of the release. -- 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, 7 months

3
6
0 / 0

[JBoss JIRA] (ISPN-2355) Flag for local affine key at put

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-2355: ---------------------------------- Summary: Flag for local affine key at put Key: ISPN-2355 URL: https://issues.jboss.org/browse/ISPN-2355 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 5.2.0.Alpha4 Reporter: Thomas Fromm Assignee: Mircea Markus Problem: I store data based upon a known key (I can't use key generator) in the distributed cache. Shortly after storing the data will be read/deleted. In case store is used, the data are only held on 2 nodes which migh not be the same node, where its created and needed next. What I need is some kind of withFlags(Flag.LOCAL_AFFINE).put(...) to make sure, that at least the local node gets owner. -- 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, 7 months

3
5
0 / 0

[JBoss JIRA] (ISPN-2341) event.isPre has a counter intuitive behaviour

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2341: ----------------------------------- Summary: event.isPre has a counter intuitive behaviour Key: ISPN-2341 URL: https://issues.jboss.org/browse/ISPN-2341 Project: Infinispan Issue Type: Feature Request Components: Listeners Affects Versions: 5.1.7.Final Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 6.0.0.Final When the listener is notified with (event.isPre == false), the change that triggered the event is not visible to the user[1] as the notification happens before exiting the EntryWrappingInterceptor. For all types of notifications, when event.isPre==false, the modification should be visible into the cache. OTHO when event.isPre == true the modification shouldn't be visible. -- 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, 7 months

2
5
0 / 0

[JBoss JIRA] (ISPN-2336) Allow endpoints to be configured as read-only

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2336: ------------------------------------- Summary: Allow endpoints to be configured as read-only Key: ISPN-2336 URL: https://issues.jboss.org/browse/ISPN-2336 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Tristan Tarrant Assignee: Galder Zamarreño Priority: Minor It would be nice to configure endpoints to be read-only. This can be done reasonably easily with REST by disabling certain methods, but a common method would be welcome -- 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, 7 months

3
3
0 / 0

[JBoss JIRA] (ISPN-1842) Configuration schema is not included at expected location

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-1842: ------------------------------------- Summary: Configuration schema is not included at expected location Key: ISPN-1842 URL: https://issues.jboss.org/browse/ISPN-1842 Project: Infinispan Issue Type: Bug Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 5.2.0.ALPHA1, 5.2.0.FINAL Just found these messages in my logs: {quote} 17:04:43,731 (main) DEBUG FileLookup:57 - Unable to find file schema/infinispan-config-5.1.xsd in classpath; searching for this file on the filesystem instead. 17:04:43,731 (main) DEBUG InfinispanConfiguration:389 - Could not find schema on path schema/infinispan-config-5.1.xsd, resolving infinispan.config.schema to http://www.infinispan.org/schemas/infinispan-config-5.1.xsd 17:04:43,911 (main) DEBUG InfinispanConfiguration:396 - Using schema http://www.infinispan.org/schemas/infinispan-config-5.1.xsd {quote} Indeed the schema is included in the jar, but is in the root of the jar, while it's searched for in *schema/infinispan-config-5.1.xsd* -- 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

11 years, 7 months

5
13
0 / 0

[JBoss JIRA] (ISPN-2289) Server endpoints should report number of active connections as a JMX operation

by Manik Surtani (JIRA)

Manik Surtani created ISPN-2289: ----------------------------------- Summary: Server endpoints should report number of active connections as a JMX operation Key: ISPN-2289 URL: https://issues.jboss.org/browse/ISPN-2289 Project: Infinispan Issue Type: Feature Request Components: Cache Server, JMX, reporting and management Affects Versions: 5.1.7.Final Reporter: Manik Surtani Assignee: Galder Zamarreño Fix For: 5.2.0.Alpha4, 5.2.0.Final Even if JMX statistics are disabled, as a JMX operation, the server endpoints should expose the number of active connections on the endpoint. Two operations should be exposed. 1. {{numberOfLocalConnections()}}, reporting a count of active connections on the node invoked. 2. {{numberOfGlobalConnections()}}, so that if invoked, it launches a distributed executor task to the entire cluster which does a count on *each* node and aggregates the result. The second operation would allow a sysadmin to query a *single* node to get the number of open connections to the entire cluster. -- 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, 7 months

4
7
0 / 0

[JBoss JIRA] (ISPN-2332) Update xsite configuration file

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2332: ----------------------------------- Summary: Update xsite configuration file Key: ISPN-2332 URL: https://issues.jboss.org/browse/ISPN-2332 Project: Infinispan Issue Type: Feature Request Components: Cross-Site Replication Affects Versions: 5.2.0.Alpha4 Reporter: Mircea Markus Assignee: Mircea Markus Priority: Blocker Fix For: 5.2.0.Beta1 Update configuration file after feedback: {code:xml} <sites local="LON"> <site name="SFO"/> <site name="NYC"/> <site name="LON"/> </sites> {code} The sites element above are not used and should be dropped. Also the local configuration should look like: {code:xml} <global> <sites> <localSite="${site:LON}" backupSites="${backup-sites:SFO,NYC}" /> <backups> <backup site="NYC" backupFailurePolicy="WARN" strategy="SYNC" timeout="12000"/> <backup site="SFO" backupFailurePolicy="IGNORE" strategy="ASYNC"/> <backup site="LON" backupFailurePolicy="IGNORE" strategy="ASYNC"/> </backups> </sites> </global> {code} This would allow re-using of configuration files between sites. -- 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, 7 months

4
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2012