September 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3462) Unable to add custom interceptors declaratively to server config

by Riad Mohammed (JIRA)

Riad Mohammed created ISPN-3462: ----------------------------------- Summary: Unable to add custom interceptors declaratively to server config Key: ISPN-3462 URL: https://issues.jboss.org/browse/ISPN-3462 Project: Infinispan Issue Type: Bug Components: Server Affects Versions: 5.3.0.Final Reporter: Riad Mohammed Assignee: Tristan Tarrant Per Tristan Tarrant, creating jira ticket: I've upgraded from Infinispan 5.2.5 to Infinispan server 5.3 and it looks like the configuration file (urn:infinispan:server:core:5.3) doesn't support declaring custom interceptors as jboss-infinispan-core_5_3.xsd does not have the necessary elements. [I did try just adding the custom interceptor elements and got a parse error]. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3439) EHCache2InfinispanTransformerTest is failing randomly

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3439?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3439: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: (was: 6.0.0.Final) Resolution: Done > EHCache2InfinispanTransformerTest is failing randomly > ----------------------------------------------------- > > Key: ISPN-3439 > URL: https://issues.jboss.org/browse/ISPN-3439 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.Alpha3 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 6.0.0.Beta1 > > > http://ci.infinispan.org/viewLog.html?buildId=2868&buildTypeId=bt8&tab=bu... > http://ci.infinispan.org/viewLog.html?buildId=2868&buildTypeId=bt8&tab=bu... -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3389) Forwarded transactions can remain stale after state transfer

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3389?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3389: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 6.0.0.Beta1 (was: 6.0.0.CR1) Resolution: Done > Forwarded transactions can remain stale after state transfer > ------------------------------------------------------------ > > Key: ISPN-3389 > URL: https://issues.jboss.org/browse/ISPN-3389 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 5.2.7.Final > Reporter: Erik Salter > Assignee: Dan Berindei > Priority: Critical > Labels: 5.2.x > Fix For: 6.0.0.Beta1, 6.0.0.Final > > > There is a scenario where a tx started on one node, moved during state transfer, and committed on the originating node won't be removed from the new owner's tx table. > The chain of events is as follows: > 1. New topology comes in as part of a view change. > 2. Local transaction started with the new topology ID. This transaction was started due to a LockControlCommand and has no modifications. Also important, it only has local locks. > 3. Tx forwarded to new owner before the local lock is acquired and registered with the transaction. > 4. Since the tx has only local locks and no modifications, it is only removed locally. No TxCompletion or Rollback are broadcast to the new owners. > This key becomes unusable not due to stale locks, but because the waitForTransaction() code will see that the old tx can "potentially" lock the key. > This easily happens with pessimistic caches, though I have seen it happen with optimistic caches (there is a delta between the transaction being created and the lock registration). -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3433) Versioned L1 values don't expire

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3433?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3433: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Versioned L1 values don't expire > -------------------------------- > > Key: ISPN-3433 > URL: https://issues.jboss.org/browse/ISPN-3433 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 5.3.0.Final > Reporter: William Burns > Assignee: William Burns > > When versioned entries are enabled it doesn't properly apply the lifespan value to L1 entries causing them to never expire. > This requires a change in the ClusterDependentLogic class to apply the L1 lifespan to the passed in metadata as well. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3433) Versioned L1 values don't expire

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3433?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3433: ----------------------------------- Fix Version/s: 6.0.0.Beta1 6.0.0.Final > Versioned L1 values don't expire > -------------------------------- > > Key: ISPN-3433 > URL: https://issues.jboss.org/browse/ISPN-3433 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 5.3.0.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 6.0.0.Beta1, 6.0.0.Final > > > When versioned entries are enabled it doesn't properly apply the lifespan value to L1 entries causing them to never expire. > This requires a change in the ClusterDependentLogic class to apply the L1 lifespan to the passed in metadata as well. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3461) Quickstarts: Modify GAV to use org.jboss.quickstarts.jdg

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-3461?page=com.atlassian.jira.plugin.... ] Martin Gencur reassigned ISPN-3461: ----------------------------------- Assignee: Martin Gencur (was: Mircea Markus) > Quickstarts: Modify GAV to use org.jboss.quickstarts.jdg > -------------------------------------------------------- > > Key: ISPN-3461 > URL: https://issues.jboss.org/browse/ISPN-3461 > Project: Infinispan > Issue Type: Bug > Components: Demos and Tutorials > Reporter: Sande Gilda > Assignee: Martin Gencur > > As part of the BOM, Stacks, Archetypes, and Quickstarts reorganization process, we are standardizing on the quickstarts GAV to use 'org.jboss.quickstarts.<product-name>. > Could you change the Infinispan quickstarts GAV from 'com.jboss.datagrid.quickstart' to 'org.jboss.quickstarts.jdg'? > This can be done at a time that works best with your release schedule. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3461) Quickstarts: Modify GAV to use org.jboss.quickstarts.jdg

by Sande Gilda (JIRA)

Sande Gilda created ISPN-3461: --------------------------------- Summary: Quickstarts: Modify GAV to use org.jboss.quickstarts.jdg Key: ISPN-3461 URL: https://issues.jboss.org/browse/ISPN-3461 Project: Infinispan Issue Type: Bug Components: Demos and Tutorials Reporter: Sande Gilda Assignee: Mircea Markus As part of the BOM, Stacks, Archetypes, and Quickstarts reorganization process, we are standardizing on the quickstarts GAV to use 'org.jboss.quickstarts.<product-name>. Could you change the Infinispan quickstarts GAV from 'com.jboss.datagrid.quickstart' to 'org.jboss.quickstarts.jdg'? This can be done at a time that works best with your release schedule. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2898) Web Cache fails to start when multiple apps are trying to create it

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2898?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2898: ----------------------------------------------- Paul Ferraro <paul.ferraro(a)redhat.com> made a comment on [bug 918791|https://bugzilla.redhat.com/show_bug.cgi?id=918791] https://github.com/jbossas/jboss-eap/pull/327 > Web Cache fails to start when multiple apps are trying to create it > ------------------------------------------------------------------- > > Key: ISPN-2898 > URL: https://issues.jboss.org/browse/ISPN-2898 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.1.7.Final > Reporter: Shay Matasaro > Assignee: Dan Berindei > Fix For: 6.0.0.Final > > > When multiple apps are trying to create/connect to the web cache , the fist one get a lock on the cache manager, and prevents the others from starting it in a timely 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2898) Web Cache fails to start when multiple apps are trying to create it

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2898?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2898: ----------------------------------------------- Paul Ferraro <paul.ferraro(a)redhat.com> changed the Status of [bug 918791|https://bugzilla.redhat.com/show_bug.cgi?id=918791] from NEW to POST > Web Cache fails to start when multiple apps are trying to create it > ------------------------------------------------------------------- > > Key: ISPN-2898 > URL: https://issues.jboss.org/browse/ISPN-2898 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.1.7.Final > Reporter: Shay Matasaro > Assignee: Dan Berindei > Fix For: 6.0.0.Final > > > When multiple apps are trying to create/connect to the web cache , the fist one get a lock on the cache manager, and prevents the others from starting it in a timely 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3459) Add support for Cache-Control http header to REST server

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-3459?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-3459: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2044 > Add support for Cache-Control http header to REST server > -------------------------------------------------------- > > Key: ISPN-3459 > URL: https://issues.jboss.org/browse/ISPN-3459 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Reporter: Martin Gencur > Assignee: Martin Gencur > Fix For: 6.0.0.CR1 > > > Apart from "Expires", the REST server should return also "Cache-Control" http header for entries that have lifespan defined. -- 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

10 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2013