October 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2461) Upgrade to JGroups 3.2.0.Final

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2461: ----------------------------------- Summary: Upgrade to JGroups 3.2.0.Final Key: ISPN-2461 URL: https://issues.jboss.org/browse/ISPN-2461 Project: Infinispan Issue Type: Feature Request Affects Versions: 5.2.0.Beta3 Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.2.0.CR1 http://belaban.blogspot.co.uk/2012/10/jgroups-320final-released.html -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] (ISPN-2214) Dump marshalled and unmarshalled payloads for tracing

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2214: -------------------------------------- Summary: Dump marshalled and unmarshalled payloads for tracing Key: ISPN-2214 URL: https://issues.jboss.org/browse/ISPN-2214 Project: Infinispan Issue Type: Enhancement Components: Marshalling Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.2.0.ALPHA3, 5.2.0.FINAL Dump marshalled payloads in order to detect root cause of issues such as AS7-5393. -- 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, 2 months

2
7
0 / 0

[JBoss JIRA] (ISPN-2426) putForExternalRead() does not unlock if entry already exists

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2426?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-2426: ------------------------------------- Thanks [~j.boehm]! integrated in both master and 5.1.x > putForExternalRead() does not unlock if entry already exists > ------------------------------------------------------------ > > Key: ISPN-2426 > URL: https://issues.jboss.org/browse/ISPN-2426 > Project: Infinispan > Issue Type: Patch > Affects Versions: 5.1.6.FINAL > Reporter: Jan Boehm > Assignee: Manik Surtani > Priority: Blocker > Fix For: 5.2.0.CR1, 5.2.0.Final, 5.1.9.Final > > Attachments: ISPN-2426-Set-looked-up-key-in-InvocationContext-on-.patch > > > When performing a {{putForExternalRead()}} for an existing entry, the entry factory fails to provide the InvocationContext with the key for the entry. This makes it impossible for the locking interceptors to release the lock. > Note that this is only a problem when used in a non-transactional context. When transactions are used, no stale locks are observed. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2426) putForExternalRead() does not unlock if entry already exists

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2426?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2426: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > putForExternalRead() does not unlock if entry already exists > ------------------------------------------------------------ > > Key: ISPN-2426 > URL: https://issues.jboss.org/browse/ISPN-2426 > Project: Infinispan > Issue Type: Patch > Affects Versions: 5.1.6.FINAL > Reporter: Jan Boehm > Assignee: Manik Surtani > Priority: Blocker > Fix For: 5.2.0.CR1, 5.2.0.Final, 5.1.9.Final > > Attachments: ISPN-2426-Set-looked-up-key-in-InvocationContext-on-.patch > > > When performing a {{putForExternalRead()}} for an existing entry, the entry factory fails to provide the InvocationContext with the key for the entry. This makes it impossible for the locking interceptors to release the lock. > Note that this is only a problem when used in a non-transactional context. When transactions are used, no stale locks are observed. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-1263) Allow a type safe selection of the cache used by the JCache interceptors

by Kevin Pollet (JIRA)

Allow a type safe selection of the cache used by the JCache interceptors ------------------------------------------------------------------------ Key: ISPN-1263 URL: https://issues.jboss.org/browse/ISPN-1263 Project: Infinispan Issue Type: Feature Request Components: CDI integration Reporter: Kevin Pollet Assignee: Kevin Pollet Priority: Minor Currently the name of the cache which will be used by the JCache interceptors has to be specified in JCache annotations (e.g {{@CacheResult(cacheName="greeting-cache"}}). This can be error prone (typo, refactoring ...). The CDI integration module provides the possibility to associate a qualifier to a cache. This qualifier could be re-used to provide a type safe selection of the cache used by a JCache interceptor. Something like: {code} public class GreetingService { @CacheResult @GreetingCache public String greet(String name) { return "Hello" + name; } } {code} Here we need to be in sync with JCache specification. In my understanding of the spec the cache name is required for {{@CacheRemoveEntry}} and {{@CacheRemoveAll}} (but currently in the API there is a default value). For {{@CacheResult}} if no cache name is defined a default one is used. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (ISPN-1266) Add more integration tests with Arquillian

by Kevin Pollet (JIRA)

Add more integration tests with Arquillian ------------------------------------------ Key: ISPN-1266 URL: https://issues.jboss.org/browse/ISPN-1266 Project: Infinispan Issue Type: Task Components: CDI integration Reporter: Kevin Pollet Assignee: Kevin Pollet Fix For: 5.1.0.FINAL This extension should be tested with: * Open Web Beans * JBoss AS7 * GlassFish -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

5
13
0 / 0

[JBoss JIRA] Created: (ISPN-1253) Integrate the Tattletale Maven plugin into Infinispan.

by Navin Surtani (JIRA)

Integrate the Tattletale Maven plugin into Infinispan. ------------------------------------------------------ Key: ISPN-1253 URL: https://issues.jboss.org/browse/ISPN-1253 Project: Infinispan Issue Type: Task Components: Build process Reporter: Navin Surtani Assignee: Navin Surtani Priority: Minor Fix For: 5.0.0.FINAL Make use of the tattletale maven plugin for infinispan. This way there will not be issues similar to ISPN-1234 cropping up. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

6
7
0 / 0

[JBoss JIRA] (ISPN-1491) Provide methods to retrieve the CacheKey parameters

by Kevin Pollet (Created) (JIRA)

Provide methods to retrieve the CacheKey parameters --------------------------------------------------- Key: ISPN-1491 URL: https://issues.jboss.org/browse/ISPN-1491 Project: Infinispan Issue Type: Enhancement Components: CDI integration Reporter: Kevin Pollet Assignee: Kevin Pollet Fix For: 5.1.0.BETA4, 5.1.0.FINAL Currently, it's not possible to retrieve the parameter values composing the {{CacheKey}} (generated by JCache interceptors). For that, we could introduce two interfaces. * {{SimpleCacheKey<T>}} used when only one parameter is used as key. This interface could add the following method {{T getValue()}} * {{ComposedCacheKey}} used when the key is composed by more than one parameter. This interface could add the following method {{Object[] getValues()}} Here, we need to ensure that we are compliant with the specification. -- 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, 2 months

4
7
0 / 0

[JBoss JIRA] (ISPN-1627) Remove the deprecated OverrideDefault annotation

by Kevin Pollet (Created) (JIRA)

Remove the deprecated OverrideDefault annotation ------------------------------------------------ Key: ISPN-1627 URL: https://issues.jboss.org/browse/ISPN-1627 Project: Infinispan Issue Type: Task Components: CDI integration Reporter: Kevin Pollet Assignee: Kevin Pollet Fix For: 5.2.0.FINAL -- 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, 2 months

3
2
0 / 0

[JBoss JIRA] (ISPN-2427) Test hanging on StateTransferLockImpl.waitForTopology

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-2427: ------------------------------------- Summary: Test hanging on StateTransferLockImpl.waitForTopology Key: ISPN-2427 URL: https://issues.jboss.org/browse/ISPN-2427 Project: Infinispan Issue Type: Bug Components: State transfer Reporter: Sanne Grinovero Assignee: Dan Berindei Fix For: 5.2.0.CR1 Attachments: lockedStack.txt from a quick glance on the thread dump, I think _OOB-3,Infinispan-Query-Cluster,MultiNodeDistributedTest-NodeA-44306_ is the offender. (not sure!) I'm attaching the full dump as a text file. -- 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, 2 months

2
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2012