October 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-1947) Automate staging repository step in release script

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-1947: ------------------------------------- Summary: Automate staging repository step in release script Key: ISPN-1947 URL: https://issues.jboss.org/browse/ISPN-1947 Project: Infinispan Issue Type: Task Components: Build process Reporter: Sanne Grinovero Assignee: Manik Surtani Priority: Optional Fix For: 5.2.0.ALPHA1 The following plugin can be used to control the staging repository from command line (including authenticating with your account as set in your settings file) {code:xml} <plugin> <groupId>org.sonatype.plugins</groupId> <artifactId>nexus-maven-plugin</artifactId> <configuration> <nexusUrl>https://repository.jboss.org/nexus</nexusUrl> <automatic>true</automatic> </configuration> </plugin> {code} Goals are described at: https://repository.sonatype.org/content/sites/maven-sites/nexus-maven-plu... -- 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

11 years, 7 months

4
9
0 / 0

[JBoss JIRA] (ISPN-2189) Compact buffers of ExpandableMarshalledValueByteStream to save memory on long term storage

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-2189: ------------------------------------- Summary: Compact buffers of ExpandableMarshalledValueByteStream to save memory on long term storage Key: ISPN-2189 URL: https://issues.jboss.org/browse/ISPN-2189 Project: Infinispan Issue Type: Enhancement Affects Versions: 5.1.5.FINAL Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 5.2.0.ALPHA3 Buffers allocated by org.infinispan.io.ExpandableMarshalledValueByteStream grow by approximation, but in {code}org.infinispan.marshall.MarshalledValue.serialize0(){code} we know when the buffer won't grow any longer as it's going to be treated as effectively immutable. At this point we should shrink the buffer to potentially save memory on each entry in the datagrid. This likely needs to be optional as depending on configuration the buffer might be used for a temporary operation, in which case the effort of resizing should be avoided. -- 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

11 years, 7 months

3
3
0 / 0

[JBoss JIRA] (ISPN-2133) Provide a context for object de-serialization

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-2133: ------------------------------------- Summary: Provide a context for object de-serialization Key: ISPN-2133 URL: https://issues.jboss.org/browse/ISPN-2133 Project: Infinispan Issue Type: Feature Request Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 5.2.0.FINAL See proposal description at http://lists.jboss.org/pipermail/infinispan-dev/2012-June/010925.html -- 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

11 years, 7 months

2
1
0 / 0

[JBoss JIRA] (ISPN-2331) Add documentation describing rolling upgrades of a live cluster

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2331: ----------------------------------- Summary: Add documentation describing rolling upgrades of a live cluster Key: ISPN-2331 URL: https://issues.jboss.org/browse/ISPN-2331 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Mircea Markus Priority: Critical Fix For: 5.2.0.Final Once the issues under ISPN-1410 are resolved we should add a user manual page describing how rolling upgrades can be performed. A video with a demo would also be awesome. -- 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, 7 months

1
4
0 / 0

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

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-2426?page=com.atlassian.jira.plugin.... ] Manik Surtani updated ISPN-2426: -------------------------------- Description: 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. was: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. > 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2353) Allow non-emitting Mapper

by Vladimir Blagojevic (JIRA)

Vladimir Blagojevic created ISPN-2353: ----------------------------------------- Summary: Allow non-emitting Mapper Key: ISPN-2353 URL: https://issues.jboss.org/browse/ISPN-2353 Project: Infinispan Issue Type: Bug Components: Distributed Execution and Map/Reduce Affects Versions: 5.2.0.Alpha4 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 5.2.0.Beta1, 5.2.0.Final In some cases Mapper being executed on remote nodes might not produce any intermediate KOut/VOut pairs and we should allow/account for that possibility. Currently such tasks fail with NPE. -- 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, 7 months

2
12
0 / 0

[JBoss JIRA] Created: (ISPN-761) Cache.keySet(), entrySet(), values(), size() ignore contents of cache loader

by Paul Ferraro (JIRA)

Cache.keySet(),entrySet(),values(),size() ignore contents of cache loader ------------------------------------------------------------------------- Key: ISPN-761 URL: https://jira.jboss.org/browse/ISPN-761 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 4.2.0.BETA1 Reporter: Paul Ferraro Assignee: Manik Surtani Passivated cache entries are not represented in values returned by the keySet(), entrySet(), values(), and size() Cache methods. This results in inconsistent behavior, since it is possible that a given cache key may not be contained in keySet() even though Cache.get(...) would return a non-null value if the entry was previously passivated. I think CacheLoaderInterceptor needs to implement the following methods: Object visitSizeCommand(InvocationContext ctx, SizeCommand command) throws Throwable Object visitValuesCommand(InvocationContext ctx, ValuesCommand command) throws Throwable Object visitEntrySetCommand(InvocationContext ctx, EntrySetCommand command) throws Throwable Object visitKeySetCommand(InvocationContext ctx, KeySetCommand command) throws Throwable -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

3
14
0 / 0

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

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-2426?page=com.atlassian.jira.plugin.... ] Manik Surtani updated ISPN-2426: -------------------------------- Fix Version/s: 5.1.9.Final > 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. -- 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, 7 months

1
0
0 / 0

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

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-2426?page=com.atlassian.jira.plugin.... ] Manik Surtani updated ISPN-2426: -------------------------------- Priority: Blocker (was: Major) > 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 > > 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. -- 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, 7 months

1
0
0 / 0

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

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-2426?page=com.atlassian.jira.plugin.... ] Manik Surtani updated ISPN-2426: -------------------------------- Summary: putForExternalRead() does not unlock if entry already exists (was: putIfAbsent with PUT_FOR_EXTERNAL_READ does not unlock if entry already exists) > 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 > Fix For: 5.2.0.CR1, 5.2.0.Final > > Attachments: ISPN-2426-Set-looked-up-key-in-InvocationContext-on-.patch > > > When performing a putIfAbsent for an existing entry with the flag PUT_FOR_EXTERNAL_READ set, 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. -- 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, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2012