October 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3556) When LockControlCommand fails on an owner, the rollback command is not sent

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3556?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3556: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > When LockControlCommand fails on an owner, the rollback command is not sent > --------------------------------------------------------------------------- > > Key: ISPN-3556 > URL: https://issues.jboss.org/browse/ISPN-3556 > Project: Infinispan > Issue Type: Bug > Components: Locking and Concurrency > Affects Versions: 5.2.7.Final, 5.3.0.Final, 6.0.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > > If a transaction starts with a {{lock()}} operation and the lock fails on one of the owners (e.g. because of a {{SuspectException}}), the rollback command should still be sent to all the live owners. > However, because a locked key is only registered in the {{affectedKeys}} collection after a successful lock operation (in {{PessimisticLockingInterceptor.acquireRemoteIfNeeded()}}, the rollback command is not sent to any owners. > This is in a pessimistic cache. However, looking at the {{OptimisticLockingInterceptor.acquireAllLocks()}} code I think I see a similar problem: it's possible that a key is locked, but the write skew check fails and the key is not added to the {{affectedKeys}} collection. We should always register the key first and attempt to lock it after. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3522) Upgrade to c3p0 version 0.9.2.1

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3522?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3522: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Upgrade to c3p0 version 0.9.2.1 > ------------------------------- > > Key: ISPN-3522 > URL: https://issues.jboss.org/browse/ISPN-3522 > Project: Infinispan > Issue Type: Component Upgrade > Affects Versions: 6.0.0.Alpha4 > Reporter: Dan Berindei > Assignee: Dan Berindei > > We are currently using c3p0 version 0.9.1.2, which is the last version with the {{c3p0}} group id. We should upgrade to the latest stable version, 0.9.2.1: http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22com.mchange%22%20AND%2... > AFAIK version 0.9.2.1 does not solve the concurrency issue in ISPN-3324, but it may solve other problems. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3512) Don't deserialize the cache loader entries needed by a remote node

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3512?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3512: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Don't deserialize the cache loader entries needed by a remote node > ------------------------------------------------------------------- > > Key: ISPN-3512 > URL: https://issues.jboss.org/browse/ISPN-3512 > Project: Infinispan > Issue Type: Feature Request > Reporter: Mircea Markus > Assignee: Mircea Markus > > the new API allows exposing the stored entries in serialized format. If an entry is fetched from persistent storage for the sole purpose of being sent remotely, we no longer need to deserialize it (when reading from the store) and serialize it back (when writing to the wire). Now we can write to the wire the serialized format as read fro the storage directly -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3589) StackOverflow in InternalMetadataImpl.Externalizer

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3589?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3589: -------------------------------- Fix Version/s: (was: 6.1.0.Final) (was: 6.0.0.Final) > StackOverflow in InternalMetadataImpl.Externalizer > -------------------------------------------------- > > Key: ISPN-3589 > URL: https://issues.jboss.org/browse/ISPN-3589 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.CR1 > Reporter: Pedro Ruivo > Assignee: Mircea Markus > > the implementation delegates to another metadata some methods. The result is a chain of InternalMetadataImpl as you can see in: > {code} > metadata=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=Inte > rnalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl > {actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=Internal > MetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{act > ual=InternalMetadataImpl [....] > {code} -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3559) TuningOptionsAppliedTest creates garbage in current dir

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3559?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3559: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > TuningOptionsAppliedTest creates garbage in current dir > ------------------------------------------------------- > > Key: ISPN-3559 > URL: https://issues.jboss.org/browse/ISPN-3559 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.Beta1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Minor > > Should create the index in a per-test temp dir and should not leave the dirs person.0 ... person.5 in current dir. There is also another such folder called 'null' but I could not identify who creates 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3586) Improve performance of Infinispan Lucene directory provider

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3586?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3586: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Improve performance of Infinispan Lucene directory provider > ----------------------------------------------------------- > > Key: ISPN-3586 > URL: https://issues.jboss.org/browse/ISPN-3586 > Project: Infinispan > Issue Type: Enhancement > Components: Lucene Directory > Affects Versions: 6.0.0.Beta2 > Reporter: Adrian Nistor > Assignee: Sanne Grinovero > > Currently in distributed mode it takes about 2 minutes to index 2000 entries. This was found in ISPN-3102. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3589) StackOverflow in InternalMetadataImpl.Externalizer

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3589?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-3589: ------------------------------------- This seems to be caused by an InternalMetadataImpl having set the "actual" field to itself. Hard to see how this can happen. Do you have any logs for this? > StackOverflow in InternalMetadataImpl.Externalizer > -------------------------------------------------- > > Key: ISPN-3589 > URL: https://issues.jboss.org/browse/ISPN-3589 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.CR1 > Reporter: Pedro Ruivo > Assignee: Mircea Markus > Fix For: 6.0.0.Final, 6.1.0.Final > > > the implementation delegates to another metadata some methods. The result is a chain of InternalMetadataImpl as you can see in: > {code} > metadata=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=Inte > rnalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl > {actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=Internal > MetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{actual=InternalMetadataImpl{act > ual=InternalMetadataImpl [....] > {code} -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3590) SingleFileStore can retry to create the folder

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3590?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-3590: ------------------------------------- reducing the prio as there is a workaround for this (use different locations). As a solution, we can retry in a loop... > SingleFileStore can retry to create the folder > ---------------------------------------------- > > Key: ISPN-3590 > URL: https://issues.jboss.org/browse/ISPN-3590 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 6.0.0.CR1 > Reporter: Pedro Ruivo > Assignee: Mircea Markus > Priority: Minor > > Sometimes, the SingleFileStore fails to create the directory even if it has permissions and enough disk space. It happens randomly when it starts multiple caches at the same time, with SingleFileStore and storage in the same location. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3596) LifecycleManager of query module should use the Provider mechanism instead of relying on brute class loading

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3596?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3596: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > LifecycleManager of query module should use the Provider mechanism instead of relying on brute class loading > ------------------------------------------------------------------------------------------------------------ > > Key: ISPN-3596 > URL: https://issues.jboss.org/browse/ISPN-3596 > Project: Infinispan > Issue Type: Bug > Components: Querying > Affects Versions: 6.0.0.CR1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > > This is used to customize the SearchFactory programmatic mappings only if remote query module is present in classpath. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3590) SingleFileStore can retry to create the folder

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3590?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3590: -------------------------------- Fix Version/s: (was: 6.1.0.Final) (was: 6.0.0.Final) > SingleFileStore can retry to create the folder > ---------------------------------------------- > > Key: ISPN-3590 > URL: https://issues.jboss.org/browse/ISPN-3590 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 6.0.0.CR1 > Reporter: Pedro Ruivo > Assignee: Mircea Markus > > Sometimes, the SingleFileStore fails to create the directory even if it has permissions and enough disk space. It happens randomly when it starts multiple caches at the same time, with SingleFileStore and storage in the same location. -- 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, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2013