December 2014 - infinispan-issues

[JBoss JIRA] (ISPN-3353) AsyncReplExtendedStatisticTest.testReplace intermittent failure

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3353?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3353: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > AsyncReplExtendedStatisticTest.testReplace intermittent failure > --------------------------------------------------------------- > > Key: ISPN-3353 > URL: https://issues.jboss.org/browse/ISPN-3353 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 6.0.0.Alpha1 > Reporter: Mircea Markus > Assignee: Pedro Ruivo > Priority: Blocker > Labels: testsuite_stability > Fix For: 7.1.0.Beta1 > > > http://ci.infinispan.org/viewLog.html?buildId=2583&tab=buildResultsDiv&bu... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5087) CacheContainerStatsMBeanTest.testClusterStats() is failing

by Pedro Ruivo (JIRA)

Pedro Ruivo created ISPN-5087: --------------------------------- Summary: CacheContainerStatsMBeanTest.testClusterStats() is failing Key: ISPN-5087 URL: https://issues.jboss.org/browse/ISPN-5087 Project: Infinispan Issue Type: Feature Request Components: Test Suite - Core Affects Versions: 7.1.0.Alpha1 Reporter: Pedro Ruivo Assignee: Vladimir Blagojevic Priority: Blocker The test is always failing: {code} testClusterStats(org.infinispan.jmx.CacheContainerStatsMBeanTest) Time elapsed: 0.017 sec <<< FAILURE! java.lang.AssertionError: expecting 0 for AverageWriteTime, to be greater than0 at org.infinispan.jmx.CacheContainerStatsMBeanTest.assertAttributeValueGreaterThan(CacheContainerStatsMBeanTest.java:100) at org.infinispan.jmx.CacheContainerStatsMBeanTest.testClusterStats(CacheContainerStatsMBeanTest.java:86) {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5053) Modules inheriting directly from the BOM use Java 1.5

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5053?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5053: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.1.0.Beta1 Resolution: Done > Modules inheriting directly from the BOM use Java 1.5 > ----------------------------------------------------- > > Key: ISPN-5053 > URL: https://issues.jboss.org/browse/ISPN-5053 > Project: Infinispan > Issue Type: Bug > Components: Build process > Affects Versions: 7.1.0.Alpha1 > Reporter: Ion Savin > Assignee: Ion Savin > Fix For: 7.1.0.Beta1 > > > Modules inheriting directly from the BOM use Java 1.5 > Affected modules: > infinispan-embedded-it > infinispan-embedded-query-it > infinispan-remote-it -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5086) Add SPDY support to the REST server

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-5086: ------------------------------------- Summary: Add SPDY support to the REST server Key: ISPN-5086 URL: https://issues.jboss.org/browse/ISPN-5086 Project: Infinispan Issue Type: Feature Request Components: Remote Protocols, Server Affects Versions: 7.1.0.Alpha1 Reporter: Tristan Tarrant Assignee: Gustavo Fernandes Once our REST server is based on Netty, explore the possibility of enabling SPDY. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5085) Convert REST server to using Netty instead of RESTEasy

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-5085: -------------------------------------- Summary: Convert REST server to using Netty instead of RESTEasy Key: ISPN-5085 URL: https://issues.jboss.org/browse/ISPN-5085 Project: Infinispan Issue Type: Enhancement Components: Remote Protocols Reporter: Galder Zamarreño Fix For: 7.1.0.Final REST server is currently based on RESTEasy. We should instead use Netty. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5084) Eclipse compilation errors for modules dependent on uberjars

by Ion Savin (JIRA)

Ion Savin created ISPN-5084: ------------------------------- Summary: Eclipse compilation errors for modules dependent on uberjars Key: ISPN-5084 URL: https://issues.jboss.org/browse/ISPN-5084 Project: Infinispan Issue Type: Bug Components: Build process Affects Versions: 7.1.0.Alpha1 Reporter: Ion Savin Assignee: Ion Savin Some modules (e.g. demos) have the uberjars defined as dependency but since the dependencies of the uberjars are all optional and the shade plugin doesn't have a m2e correspondent to generate the jar compilation fails for them. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4393) Separate Memcached and Hot Rod protocol decoders

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4393?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-4393: ---------------------------------------- Also, consider using a different base Netty decoder, e.g. ByteToMessageDecoder. See rationale: http://netty.io/4.0/api/io/netty/handler/codec/ReplayingDecoder.html > Separate Memcached and Hot Rod protocol decoders > ------------------------------------------------ > > Key: ISPN-4393 > URL: https://issues.jboss.org/browse/ISPN-4393 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > This is for 7.1, for the first alpha. In 7.0, we've focused on creating Hot Rod 2.0 protocol which adds a lot of enhancements and capabilities in a backwards compatible way. > In 7.1, a big focus should be on refactoring the protocol decoders for Memcached and Hot Rod which are very entangled and are hindering development of Hot Rod. Essentially, each should have a fully async decoder that focuses purely on the protocol at hand and makes the most of it. > This should also enable to improve performance of each protocol decoder. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4359) Provide an annotation driven way of declaring protobuf metadata

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4359?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4359: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/protostream/pull/14 > Provide an annotation driven way of declaring protobuf metadata > --------------------------------------------------------------- > > Key: ISPN-4359 > URL: https://issues.jboss.org/browse/ISPN-4359 > Project: Infinispan > Issue Type: Feature Request > Components: Marshalling > Affects Versions: 7.0.0.Alpha4 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: jdg > > The main goal of this is to simply marshalling of java objects to protobuf using the Protostream library. > Instead of providing a Protostream MessageMarshaller implementation and a proto schema file it would be nice to have an alternative way of just adding minimal annotations to a Java class (and its fields) to assist on the fly generation (via reflection) of the proto schema. The Protostream library should also infer the marshaller so it would not require a manually implemented one. The annotation should require minimal info (tag number) and the rest should be inferred based on common sense defaults (protobuf type, java collection type, collection element type ...) but should be possible to override. The auto-generated schema should be available to users and they should be able then to use it as reference if they need it to implement domain model classes and marshallers for other languages. > The user should still be able to specify a manually created schema (besides the annotated classes) and in that case the Protostream library should check the auto-inferred schema against the provided one and ensure they match. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5083) Hot Rod decoder should use async Cache operations

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-5083: -------------------------------------- Summary: Hot Rod decoder should use async Cache operations Key: ISPN-5083 URL: https://issues.jboss.org/browse/ISPN-5083 Project: Infinispan Issue Type: Enhancement Components: Remote Protocols Reporter: Galder Zamarreño Assignee: Gustavo Fernandes Fix For: 7.1.0.Final Hot Rod decoder is currently tying up Netty threads as a result of calling up to Infinispan sync operations. Instead, Hot Rod decoder should call up async operations, convert the Notifying Futures to Scala Futures, and write up the reply when it's received. This should increase performance specially under heavy load. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5082) Separate Memcached and Hot Rod decoders

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5082?page=com.atlassian.jira.plugin.... ] Galder Zamarreño resolved ISPN-5082. ------------------------------------ Resolution: Duplicate Issue > Separate Memcached and Hot Rod decoders > --------------------------------------- > > Key: ISPN-5082 > URL: https://issues.jboss.org/browse/ISPN-5082 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Gustavo Fernandes > Fix For: 7.1.0.Final > > > The current AbstractProtocolDecoder makes it difficult to expand Hot Rod protocol. Separate each protocol decoder in order to be as efficient as possible. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 December 2014