February 2014 - infinispan-issues

[JBoss JIRA] (ISPN-3840) Test suite should continue when a test hasn't closed its cache managers

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3840?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3840: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > Test suite should continue when a test hasn't closed its cache managers > ----------------------------------------------------------------------- > > Key: ISPN-3840 > URL: https://issues.jboss.org/browse/ISPN-3840 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Core > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 7.0.0.Alpha2 > > > The test listener has access to the cache managers that are still open, so it could fail the test and still close the cache managers. > Especially now that the server tests are back into the main project, the server tests should run even if a test in another module failed to close its cache managers. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3787) Upgrade to c3p0 0.9.5-pre4

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3787?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3787: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > Upgrade to c3p0 0.9.5-pre4 > -------------------------- > > Key: ISPN-3787 > URL: https://issues.jboss.org/browse/ISPN-3787 > Project: Infinispan > Issue Type: Component Upgrade > Components: Loaders and Stores > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 7.0.0.Alpha2 > > > Version 0.9.5-pre4 has a fix for http://sourceforge.net/p/c3p0/bugs/119/ (ISPN-3324). -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3824) Upgrade to JBoss Transactions 4.17.17

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3824?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3824: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > Upgrade to JBoss Transactions 4.17.17 > ------------------------------------- > > Key: ISPN-3824 > URL: https://issues.jboss.org/browse/ISPN-3824 > Project: Infinispan > Issue Type: Component Upgrade > Components: Transactions > Reporter: Sanne Grinovero > Assignee: Mircea Markus > Fix For: 7.0.0.Alpha2 > > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3727) intermittent test failure AsyncReplExtendedStatisticTest.testReplaceWithOldVal

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3727?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3727: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > intermittent test failure AsyncReplExtendedStatisticTest.testReplaceWithOldVal > ------------------------------------------------------------------------------ > > Key: ISPN-3727 > URL: https://issues.jboss.org/browse/ISPN-3727 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 6.0.0.Final > Reporter: Mircea Markus > Assignee: Pedro Ruivo > Labels: testsuite_stability > Fix For: 7.0.0.Alpha2 > > > Failed tests: > AsyncReplExtendedStatisticTest>BaseClusteredExtendedStatisticTest.testReplaceWithOldVal:190->BaseClusteredExtendedStatisticTest.assertCacheValue:253->MultipleCacheManagersTest.assertEventuallyEquals:554->AbstractInfinispanTest.eventually:173->AbstractInfinispanTest.eventually:45->AbstractInfinispanTest.eventually:62 > expected [true] but found [false] -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3843) Remove broadcast/unicast optimization in JGroupsTransport

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3843?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3843: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > Remove broadcast/unicast optimization in JGroupsTransport > --------------------------------------------------------- > > Key: ISPN-3843 > URL: https://issues.jboss.org/browse/ISPN-3843 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 7.0.0.Alpha2 > > > The broadcast/unicast optimization in JGroupsTransport can break the message ordering for regular messages, because NAKACK[2] and UNICAST[2|3] have their own ordering. > We should test if this optimization really brings any performance benefits and eliminate it, at least for asynchronous commands. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3891) Tune for batching without transactions

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3891?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3891: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > Tune for batching without transactions > -------------------------------------- > > Key: ISPN-3891 > URL: https://issues.jboss.org/browse/ISPN-3891 > Project: Infinispan > Issue Type: Enhancement > Components: Transactions > Reporter: Sanne Grinovero > Assignee: Mircea Markus > Fix For: 7.0.0.Final, 7.0.0.Alpha2 > > > The usage of batching is a critically important feature, widely used to improve performance in many common scenarios, but while documentation makes it clear that it's built on transactions, it's unclear how these transactions should be configured. > Also, I would challenge the decision of building batching on top of transactions and see if there are opportunities for further optimization. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3906) Do not place ProtobufValueWrapper instances in the cache

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3906?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3906: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > Do not place ProtobufValueWrapper instances in the cache > -------------------------------------------------------- > > Key: ISPN-3906 > URL: https://issues.jboss.org/browse/ISPN-3906 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Final, 7.0.0.Alpha2 > > > ProtobufValueWrapper is only needed in order to provide a classbridge so we can integrate with Hibernate Search. Still, we should not need to wrap the protobuf encoded byte array put in the cache with this class. It should only be created as a temporary wrapper just before we feed the data to Hibernate Search. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3936) State transfer should not modify shared cache stores

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3936?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3936: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > State transfer should not modify shared cache stores > ---------------------------------------------------- > > Key: ISPN-3936 > URL: https://issues.jboss.org/browse/ISPN-3936 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.0.0.Final, 7.0.0.Alpha2 > > > When installing a new topology, we invalidate the cache entries that are no longer mapped to the local node. We also iterate over the entries in the cache stores and delete the ones that are no longer local, but this should only happen if the cache store is not shared. > We had similar issues in the past, but this seems to be related to the new cache store API introduced in 6.0. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3851) Write tests for REST server using timeToLiveSeconds=0

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3851?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3851: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > Write tests for REST server using timeToLiveSeconds=0 > ----------------------------------------------------- > > Key: ISPN-3851 > URL: https://issues.jboss.org/browse/ISPN-3851 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Fix For: 7.0.0.Final, 7.0.0.Alpha2 > > > ISPN-3786 fixed an issue with timeToLiveSeconds=0 being treated inconsistently, but more tests are needed. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3907) Define a Protobuf custom option for defining numeric IDs for types

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3907?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3907: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > Define a Protobuf custom option for defining numeric IDs for types > ------------------------------------------------------------------ > > Key: ISPN-3907 > URL: https://issues.jboss.org/browse/ISPN-3907 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Final, 7.0.0.Alpha2 > > > Currently the wire format of all Protobuf encoded keys and values contains a header/envelope that has some metadata information, like the fully qualified type name (that is protobuf type name, not java) of the object encoded in the message. This information is needed so that the other end can decode the message. And we added it because the Protobuf spec assumes both ends are aware of the message type, which is not the case most of the time. > While this approach solves the problem nicely, it becomes very inefficient is the FQN is long, which is usually the case, as people tend to stick the domain name of their company + package app name into it. > Solution: provide alternative unique numeric IDs to all types. The IDs can be added to message type definitions in the protobuf schema and the user is in charge of guaranteeing their uniqueness while the system must check and enforce the uniqueness when a schema is registered ib the ProtobufMetadataManager. To do this we define a custom Protobuf Message type option that accepts a numeric value. If such a numeric ID was assigned to the type then when it is serialized in protobuf the system has to use this id in the header rather that the FQN string. > This option should not be mandatory. Existing apps should work without requiring source code changes or recompiling providing that the relevant jars are upgraded in both client and server to support the new header encoding. -- 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, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2014