October 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2370) Quickstarts use wrong package in documentation

by Joseph Ottinger (JIRA)

Joseph Ottinger created ISPN-2370: ------------------------------------- Summary: Quickstarts use wrong package in documentation Key: ISPN-2370 URL: https://issues.jboss.org/browse/ISPN-2370 Project: Infinispan Issue Type: Enhancement Components: Demos and Tutorials Reporter: Joseph Ottinger Assignee: Mircea Markus Priority: Minor https://github.com/infinispan/infinispan-quickstart/tree/master/clustered... Note that there are multiple quickstarts, yet the documentation addresses only one; also, the one quickstart mentioned has no explanation of expected results, and ignores the package name required for invocation. Other quickstarts show the same issues, although I've not done an exhaustive search. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2365) Tx with no modifications can be replicated to a remote site.

by Erik Salter (JIRA)

Erik Salter created ISPN-2365: --------------------------------- Summary: Tx with no modifications can be replicated to a remote site. Key: ISPN-2365 URL: https://issues.jboss.org/browse/ISPN-2365 Project: Infinispan Issue Type: Feature Request Components: Cross-Site Replication Affects Versions: 5.2.0.Alpha4 Reporter: Erik Salter Assignee: Mircea Markus If a tx has no modifications, but has acquired remote locks (which can be the case of an aggregate lock), the tx will still attempt to be replicated across the wire. This will result in an IllegalStateException on the receiving sites, as there are no modifications to replay. -- 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, 3 months

2
2
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

12 years, 3 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

12 years, 3 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

12 years, 3 months

4
9
0 / 0

[JBoss JIRA] Created: (ISPN-1103) Soft schema-based storage

by Manik Surtani (JIRA)

Soft schema-based storage ------------------------- Key: ISPN-1103 URL: https://issues.jboss.org/browse/ISPN-1103 Project: Infinispan Issue Type: Feature Request Components: Core API Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.1.0.BETA1, 5.1.0.Final This JIRA is about storing metadata alongside values. Perhaps encapsulating values as SchematicValues, which could be described as: {code} class SchematicValue { String jsonMetadata; String jsonObject; } {code} Metadata would allow for a few interesting features: * Extracting of lifespan and timestamp data if manipulated over a remote protocol (REST, HotRod, etc) * Content type for REST responses * Timestamps for REST headers, will affect HTTP content caches * Validation information (may not be processed by Infinispan, but can be used by client libs) * Classloader/marshaller/classdef version info * General structure of the information stored -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

8
22
0 / 0

[JBoss JIRA] (ISPN-2351) Operate the Query MassIndexer via JMX

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2351?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2351: -------------------------------- Fix Version/s: 5.2.0.CR1 (was: 5.2.0.Beta1) > Operate the Query MassIndexer via JMX > ------------------------------------- > > Key: ISPN-2351 > URL: https://issues.jboss.org/browse/ISPN-2351 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management, Querying > Reporter: Sanne Grinovero > Assignee: Galder Zamarreño > Fix For: 5.2.0.CR1 > > > The MassIndexer is not exposed on JMX, we should expose it. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2363) Allow overriding of JMX port in startServer script

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2363: ------------------------------------- Summary: Allow overriding of JMX port in startServer script Key: ISPN-2363 URL: https://issues.jboss.org/browse/ISPN-2363 Project: Infinispan Issue Type: Enhancement Components: JMX, reporting and management Reporter: Tristan Tarrant Assignee: Tristan Tarrant Priority: Minor Fix For: 5.2.0.Final We can use an environment variable for this -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] (ISPN-2357) New coordinator installs old CH containing crashed members

by Erik Salter (JIRA)

Erik Salter created ISPN-2357: --------------------------------- Summary: New coordinator installs old CH containing crashed members Key: ISPN-2357 URL: https://issues.jboss.org/browse/ISPN-2357 Project: Infinispan Issue Type: Feature Request Components: State transfer Affects Versions: 5.2.0.Alpha4 Reporter: Erik Salter Assignee: Mircea Markus After merging the round of pull requests today (including ISPN-2349), there still is an issue where a killed node can appear in the CH even after JGroups passes up the new view. This appears to happen when the old coordinator was killed. Obviously, if the CH contains the old member, writes that map to the segments previously owned by the dead node will fail. Here are ISPN trace logs. You are looking for erm-cluster. http://dl.dropbox.com/u/50401510/5.2.0.ALPHA4/relay2/10.30.12.83/server.l... (phl-dg1) http://dl.dropbox.com/u/50401510/5.2.0.ALPHA4/relay2/10.30.12.84/server.l... (phl-dg2) http://dl.dropbox.com/u/50401510/5.2.0.ALPHA4/relay2/10.30.12.83/server.l... (phl-dg3, the node that was killed) -- 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, 3 months

4
6
0 / 0

[JBoss JIRA] (ISPN-2364) Store fluency changes break some stores

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2364: ------------------------------------- Summary: Store fluency changes break some stores Key: ISPN-2364 URL: https://issues.jboss.org/browse/ISPN-2364 Project: Infinispan Issue Type: Bug Reporter: Tristan Tarrant Assignee: Tristan Tarrant Priority: Blocker Fix For: 5.2.0.Beta1 -- 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, 3 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2012