June 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6644) Use externalizer directly to serialize CommandInvocationId

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-6644?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-6644: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Alpha3 9.0.0.Final Resolution: Done > Use externalizer directly to serialize CommandInvocationId > ---------------------------------------------------------- > > Key: ISPN-6644 > URL: https://issues.jboss.org/browse/ISPN-6644 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 9.0.0.Alpha1 > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.0.0.Alpha3, 9.0.0.Final > > > CommandInvocationId serialization can be improved by using the externalizer directly, instead of invoking {{output.writeObject(commandInvocationId)}} and {{input.readObject()}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6790) Distribution interceptors re-compute key location after remote get

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6790?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6790: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Final Resolution: Done > Distribution interceptors re-compute key location after remote get > ------------------------------------------------------------------ > > Key: ISPN-6790 > URL: https://issues.jboss.org/browse/ISPN-6790 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Alpha2, 8.2.2.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.0.0.Alpha3, 9.0.0.Final > > > If the distribution interceptors don't find a key remotely, they try again to retrieve it from the local data container. Before reading the local value, though, they compute the key's ownership again, to make sure they don't read a stale value that was previously owned by the local node. > Most of the time, the topology doesn't change during the invocation through the interceptor chain, so there's no need to look up the value locally again, or to re-compute the key's location. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6683) LevelDB ConfigurationTest#testXmlConfig fails on Windows

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6683?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6683: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > LevelDB ConfigurationTest#testXmlConfig fails on Windows > -------------------------------------------------------- > > Key: ISPN-6683 > URL: https://issues.jboss.org/browse/ISPN-6683 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Environment: Apache Maven 3.3.9 > Java version: 1.8.0_91, vendor: Oracle Corporation > Default locale: pl_PL, platform encoding: Cp1250 > OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "dos" > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Labels: windows > Fix For: 9.0.0.Alpha3, 9.0.0.Final > > > LevelDB tests operate on the same directory. Windows someones reports deleting file to the JVM but the file is still there. > The easiest way to workaround this problem is to use different directories for all the tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6796) Administration console - improve error messages when executing script

by Roman Macor (JIRA)

Roman Macor created ISPN-6796: --------------------------------- Summary: Administration console - improve error messages when executing script Key: ISPN-6796 URL: https://issues.jboss.org/browse/ISPN-6796 Project: Infinispan Issue Type: Enhancement Components: JMX, reporting and management Reporter: Roman Macor Priority: Minor When executing javascript which results in error, the error message displayed by Administration console is not very helpful: Error Some unexpected problem happened when launching the task: DGISPN0118: Failed to invoke operation: ISPN026003: Script execution error Executing the same script through hotrod client throws more descriptive exception: ReferenceError: "console" is not defined in <eval> at line number 4 The script is: console.debug("test"); -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6758) JDBC DB Major/Minor Versions not exposed by the server

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6758?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6758: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Alpha3 9.0.0.Final Resolution: Done > JDBC DB Major/Minor Versions not exposed by the server > ------------------------------------------------------ > > Key: ISPN-6758 > URL: https://issues.jboss.org/browse/ISPN-6758 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores, Server > Affects Versions: 9.0.0.Alpha2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.0.0.Alpha3, 9.0.0.Final > > > The ability for the user to configure the Major and Minor versions of the underlying DB that JDBC connects was added as part of ISPN-20, however the ability to read/configure these values via the server was omitted. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6768) CommandAwareRpcDispatcher channel listener can cause classloader leaks

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6768?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6768: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > CommandAwareRpcDispatcher channel listener can cause classloader leaks > ---------------------------------------------------------------------- > > Key: ISPN-6768 > URL: https://issues.jboss.org/browse/ISPN-6768 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Alpha2, 8.1.4.Final, 8.2.2.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 8.1.5.Final, 9.0.0.Alpha3, 8.2.3.Final > > > CommandAwareRpcDispatcher registers a listener with the channel in its constructor, but never unregisters it. Thus, if the channel persists following shutdown of the CommandAwareRpcDispatcher (e.g. in WildFly), this will cause a classloader leak. > See linked issue for details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6751) Backports for 8.1.5.Final

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6751?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6751: ---------------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Radoslav Husar Resolution: Done > Backports for 8.1.5.Final > ------------------------- > > Key: ISPN-6751 > URL: https://issues.jboss.org/browse/ISPN-6751 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.1.4.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Priority: Blocker > Fix For: 8.1.5.Final > > > Tracking Jira for issues to be backported to 8.1.5.Final. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-4) Nested message type definitions should not be allowed in 'extend' declarations

by Adrian Nistor (JIRA)

Adrian Nistor created IPROTO-4: ---------------------------------- Summary: Nested message type definitions should not be allowed in 'extend' declarations Key: IPROTO-4 URL: https://issues.jboss.org/browse/IPROTO-4 Project: Infinispan ProtoStream Issue Type: Bug Reporter: Adrian Nistor The test DescriptorsTest.testNestedMessageInExtend demonstrates these declarations are ignored. But the correct way to handle this is to throw a parsing error similar to protoc. In proto3 we should ban extend declarations completely. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4390) CHMv8 leaks ThreadLocal

by Mathieu Lachance (JIRA)

[ https://issues.jboss.org/browse/ISPN-4390?page=com.atlassian.jira.plugin.... ] Mathieu Lachance commented on ISPN-4390: ---------------------------------------- Any news and/or ETA around that issue? Anything I could do to help out to try getting this one resolved? Thanks, > CHMv8 leaks ThreadLocal > ----------------------- > > Key: ISPN-4390 > URL: https://issues.jboss.org/browse/ISPN-4390 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Sanne Grinovero > Assignee: William Burns > Fix For: 8.1.5.Final, 9.0.0.Final, 8.2.3.Final > > > As discussed on: http://lists.jboss.org/pipermail/infinispan-dev/2014-June/015055.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6795) ClusteredGetResponseValidityFilter swallows exceptions

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-6795?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-6795: ------------------------------ Affects Version/s: 9.0.0.Alpha2 > ClusteredGetResponseValidityFilter swallows exceptions > ------------------------------------------------------ > > Key: ISPN-6795 > URL: https://issues.jboss.org/browse/ISPN-6795 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Alpha2 > Reporter: Radim Vansa > Priority: Minor > > ClusteredGetValidityFilter does not accept exceptional responses. Therefore, if there's a exception on the remote side when executing ClusteredGetCommand, it's swallowed and TimeoutException is thrown instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2016