April 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3016) Rest server should optionally return owner information in a header

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3016?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-3016: --------------------------------------- Implementation: add a server configuration parameter, "returnMetadata" which can be configured as NEVER, ON_DEMAND, ALWAYS. In the case of ON_DEMAND, the GET/HEAD request must add a custom header to obtain the metadata. > Rest server should optionally return owner information in a header > ------------------------------------------------------------------ > > Key: ISPN-3016 > URL: https://issues.jboss.org/browse/ISPN-3016 > Project: Infinispan > Issue Type: Enhancement > Components: Remote protocols > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 5.3.0.Final > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2912) Drop server-compatibility configuration parser

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2912?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2912: ---------------------------------- Summary: Drop server-compatibility configuration parser (was: Move server-compatibility configuration parser to a separate module) Description: Drop the JDG/AS/EAP configuration parsers since it is safer to use a static configuration converter (was: The server configuration parsers don't really belong in core and the jdbc cachestore but should really be extracted to an external module) > Drop server-compatibility configuration parser > ---------------------------------------------- > > Key: ISPN-2912 > URL: https://issues.jboss.org/browse/ISPN-2912 > Project: Infinispan > Issue Type: Task > Components: Configuration > Affects Versions: 5.2.4.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 5.3.0.Final > > > Drop the JDG/AS/EAP configuration parsers since it is safer to use a static configuration converter -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2309) Support parsing of the AS7 threads configuration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2309?page=com.atlassian.jira.plugin.... ] Tristan Tarrant resolved ISPN-2309. ----------------------------------- Resolution: Won't Fix Not going to do this > Support parsing of the AS7 threads configuration > ------------------------------------------------ > > Key: ISPN-2309 > URL: https://issues.jboss.org/browse/ISPN-2309 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 5.3.0.Final > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2310) Support parsing of the AS7 jgroups configuration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2310?page=com.atlassian.jira.plugin.... ] Tristan Tarrant resolved ISPN-2310. ----------------------------------- Resolution: Won't Fix We won't do this > Support parsing of the AS7 jgroups configuration > ------------------------------------------------ > > Key: ISPN-2310 > URL: https://issues.jboss.org/browse/ISPN-2310 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 5.3.0.Final > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3025) NullMarkerEntry is singleton but can be changed - very error prone!

by Mircea Markus (JIRA)

Mircea Markus created ISPN-3025: ----------------------------------- Summary: NullMarkerEntry is singleton but can be changed - very error prone! Key: ISPN-3025 URL: https://issues.jboss.org/browse/ISPN-3025 Project: Infinispan Issue Type: Bug Affects Versions: 5.2.5.Final Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.3.0.Final, 5.3.0.Alpha1 NullMarkerEntry is singleton but almost all the flags it aggregates can be amended. this is dangerous as some code might read the e.g. isChanged() value in a total random manner. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3024) Removed entry not seen correctly within transaction's scope

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3024?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3024: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1772 > Removed entry not seen correctly within transaction's scope > ----------------------------------------------------------- > > Key: ISPN-3024 > URL: https://issues.jboss.org/browse/ISPN-3024 > Project: Infinispan > Issue Type: Bug > Reporter: Mircea Markus > Assignee: Mircea Markus > Priority: Critical > Labels: 5.2.x > Fix For: 5.3.0.Beta1, 5.3.0.Beta2 > > > for both replicated and distributed caches: > cache.put(k,v); > tm.begin(); > cache.remove(k); > assertNull(cache.get(k), "This fails!"); -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3024) Removed entry not seen correctly within transaction's scope

by Mircea Markus (JIRA)

Mircea Markus created ISPN-3024: ----------------------------------- Summary: Removed entry not seen correctly within transaction's scope Key: ISPN-3024 URL: https://issues.jboss.org/browse/ISPN-3024 Project: Infinispan Issue Type: Bug Reporter: Mircea Markus Assignee: Mircea Markus Priority: Critical for both replicated and distributed caches: cache.put(k,v); tm.begin(); cache.remove(k); assertNull(cache.get(k), "This fails!"); -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3024) Removed entry not seen correctly within transaction's scope

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3024?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3024: -------------------------------- Fix Version/s: 5.3.0.Beta1 5.3.0.Beta2 > Removed entry not seen correctly within transaction's scope > ----------------------------------------------------------- > > Key: ISPN-3024 > URL: https://issues.jboss.org/browse/ISPN-3024 > Project: Infinispan > Issue Type: Bug > Reporter: Mircea Markus > Assignee: Mircea Markus > Priority: Critical > Fix For: 5.3.0.Beta1, 5.3.0.Beta2 > > > for both replicated and distributed caches: > cache.put(k,v); > tm.begin(); > cache.remove(k); > assertNull(cache.get(k), "This fails!"); -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3024) Removed entry not seen correctly within transaction's scope

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3024?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3024: -------------------------------- Labels: 5.2.x (was: ) > Removed entry not seen correctly within transaction's scope > ----------------------------------------------------------- > > Key: ISPN-3024 > URL: https://issues.jboss.org/browse/ISPN-3024 > Project: Infinispan > Issue Type: Bug > Reporter: Mircea Markus > Assignee: Mircea Markus > Priority: Critical > Labels: 5.2.x > Fix For: 5.3.0.Beta1, 5.3.0.Beta2 > > > for both replicated and distributed caches: > cache.put(k,v); > tm.begin(); > cache.remove(k); > assertNull(cache.get(k), "This fails!"); -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3023) Re-implement BoundedConcurrentHashMap using CHMv8 designs

by Manik Surtani (JIRA)

Manik Surtani created ISPN-3023: ----------------------------------- Summary: Re-implement BoundedConcurrentHashMap using CHMv8 designs Key: ISPN-3023 URL: https://issues.jboss.org/browse/ISPN-3023 Project: Infinispan Issue Type: Feature Request Components: Core API, Eviction Affects Versions: 5.2.5.Final Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.3.0.Beta1, 5.3.0.Final This is better than the current segment-based approach, in terms of memory footprint as well as performance under high concurrency. -- 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, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2013