July 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7991) Compatibility between Rest and HotRod not working on both ways

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-7991?page=com.atlassian.jira.plugin.... ] Martin Gencur edited comment on ISPN-7991 at 7/10/17 4:10 AM: -------------------------------------------------------------- I've tried option 1) and it worked for me. Steps to reproduce my behavior: 1) add no-arg constructor to org.infinispan.commons.marshall.StringMarshaller: {code} public StringMarshaller() { this.charset = Charset.forName("UTF-8"); } {code} 2) deploy the compiled marshaller to the server and register it via {code} <compatibility enabled="true" marshaller="org.infinispan.commons.marshall.StringMarshaller"/> {code} 3) register the marshaller in HotRod client: {code} builder.marshaller(org.infinispan.commons.marshall.StringMarshaller.class) {code} 4) put the data via {code} curl -v -u test:test -X POST -H 'Content-type: application/xml' -d @file.xml http://localhost:8080/rest/compat/1 {code} 5) read the data a via HotRod: {code} cache.get("1") {code} I really get what I stored there, i.e. the XML. was (Author: mgencur): I've tried option 1) and it worked for me. Steps to reproduce my behavior: 1) add no-arg constructor to org.infinispan.commons.marshall.StringMarshaller 2) deploy the compiled marshaller to the server and register it via {code} <compatibility enabled="true" marshaller="org.infinispan.commons.marshall.StringMarshaller"/> {code} 3) register the marshaller in HotRod client: {code} builder.marshaller(org.infinispan.commons.marshall.StringMarshaller.class) {code} 4) put the data via {code} curl -v -u test:test -X POST -H 'Content-type: application/xml' -d @file.xml http://localhost:8080/rest/compat/1 {code} 5) read the data a via HotRod: {code} cache.get("1") {code} I really get what I stored there, i.e. the XML. > Compatibility between Rest and HotRod not working on both ways > -------------------------------------------------------------- > > Key: ISPN-7991 > URL: https://issues.jboss.org/browse/ISPN-7991 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.2.7.Final, 9.1.0.Beta1, 9.0.3.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > Writing via Hot Rod and reading via Rest works fine, but not the other way around -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7991) Compatibility between Rest and HotRod not working on both ways

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-7991?page=com.atlassian.jira.plugin.... ] Martin Gencur commented on ISPN-7991: ------------------------------------- I've tried option 1) and it worked for me. Steps to reproduce my behavior: 1) add no-arg constructor to org.infinispan.commons.marshall.StringMarshaller 2) deploy the compiled marshaller to the server and register it via {code} <compatibility enabled="true" marshaller="org.infinispan.commons.marshall.StringMarshaller"/> {code} 3) register the marshaller in HotRod client: {code} builder.marshaller(org.infinispan.commons.marshall.StringMarshaller.class) {code} 4) put the data via {code} curl -v -u test:test -X POST -H 'Content-type: application/xml' -d @file.xml http://localhost:8080/rest/compat/1 {code} 5) read the data a via HotRod: {code} cache.get("1") {code} I really get what I stored there, i.e. the XML. > Compatibility between Rest and HotRod not working on both ways > -------------------------------------------------------------- > > Key: ISPN-7991 > URL: https://issues.jboss.org/browse/ISPN-7991 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.2.7.Final, 9.1.0.Beta1, 9.0.3.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > Writing via Hot Rod and reading via Rest works fine, but not the other way around -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7948) ComponentMetadataPersister should not create dat files in src/main/resources

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7948?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7948: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > ComponentMetadataPersister should not create dat files in src/main/resources > ---------------------------------------------------------------------------- > > Key: ISPN-7948 > URL: https://issues.jboss.org/browse/ISPN-7948 > Project: Infinispan > Issue Type: Bug > Components: Build process > Affects Versions: 9.1.0.Beta1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.1.0.Final > > > Generated files should go in target/classes; src/main/resources should be immutable -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7991) Compatibility between Rest and HotRod not working on both ways

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7991?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-7991: ------------------------------------------- I think the approach #2 can be the easiest thing to add (it just requires adding {{StringMarshaller}} in the cache on the REST side). > Compatibility between Rest and HotRod not working on both ways > -------------------------------------------------------------- > > Key: ISPN-7991 > URL: https://issues.jboss.org/browse/ISPN-7991 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.2.7.Final, 9.1.0.Beta1, 9.0.3.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > Writing via Hot Rod and reading via Rest works fine, but not the other way around -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8032) Add hibernate-cache module to bom

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8032?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8032: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add hibernate-cache module to bom > --------------------------------- > > Key: ISPN-8032 > URL: https://issues.jboss.org/browse/ISPN-8032 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.1.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8036) TestResourceTracker keeps cache managers alive after they are stopped

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8036?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8036: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5275 > TestResourceTracker keeps cache managers alive after they are stopped > --------------------------------------------------------------------- > > Key: ISPN-8036 > URL: https://issues.jboss.org/browse/ISPN-8036 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.1.0.CR1, 9.0.3.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 9.1.0.Final > > > {{TestCacheManagerFactory.newDefaultCacheManager()}} adds the manager to {{TestResourceTracker}} so if the test doesn't stop it explicitly, {{TestResourceTracker}} will. > When a test uses {{@CleanupAfterMethod}}, however, the cache managers are stopped and recreated after each method, but the list of resources is only cleared at the end of the test class. If a test has lots of methods, like {{LocalDistributedExecutorTest}} and its subclasses, the stopped managers can use a lot of memory (250KB for each {{ComponentMetadataRepo}}). > I believe the extra memory usage is causing longer GC pauses, and in turn leads to intermittent test failures in test methods that use short timeouts: > {noformat} > 16:58:34,801 ERROR (testng-ReplSyncDistributedExecutorTest:[]) [TestSuiteProgress] Test failed: org.infinispan.distexec.ReplSyncDistributedExecutorTest.testInvokeAnyTimedSleepingTasks > java.lang.AssertionError: Should have thrown an class java.util.concurrent.TimeoutException > at org.infinispan.test.Exceptions.assertException(Exceptions.java:21) ~[test-classes/:?] > at org.infinispan.test.Exceptions.expectException(Exceptions.java:92) ~[test-classes/:?] > at org.infinispan.distexec.LocalDistributedExecutorTest.testInvokeAnyTimedSleepingTasks(LocalDistributedExecutorTest.java:269) ~[test-classes/:?] > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8036) TestResourceTracker keeps cache managers alive after they are stopped

by Dan Berindei (JIRA)

Dan Berindei created ISPN-8036: ---------------------------------- Summary: TestResourceTracker keeps cache managers alive after they are stopped Key: ISPN-8036 URL: https://issues.jboss.org/browse/ISPN-8036 Project: Infinispan Issue Type: Bug Components: Test Suite - Core Affects Versions: 9.0.3.Final, 9.1.0.CR1 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 9.1.0.Final {{TestCacheManagerFactory.newDefaultCacheManager()}} adds the manager to {{TestResourceTracker}} so if the test doesn't stop it explicitly, {{TestResourceTracker}} will. When a test uses {{@CleanupAfterMethod}}, however, the cache managers are stopped and recreated after each method, but the list of resources is only cleared at the end of the test class. If a test has lots of methods, like {{LocalDistributedExecutorTest}} and its subclasses, the stopped managers can use a lot of memory (250KB for each {{ComponentMetadataRepo}}). I believe the extra memory usage is causing longer GC pauses, and in turn leads to intermittent test failures in test methods that use short timeouts: {noformat} 16:58:34,801 ERROR (testng-ReplSyncDistributedExecutorTest:[]) [TestSuiteProgress] Test failed: org.infinispan.distexec.ReplSyncDistributedExecutorTest.testInvokeAnyTimedSleepingTasks java.lang.AssertionError: Should have thrown an class java.util.concurrent.TimeoutException at org.infinispan.test.Exceptions.assertException(Exceptions.java:21) ~[test-classes/:?] at org.infinispan.test.Exceptions.expectException(Exceptions.java:92) ~[test-classes/:?] at org.infinispan.distexec.LocalDistributedExecutorTest.testInvokeAnyTimedSleepingTasks(LocalDistributedExecutorTest.java:269) ~[test-classes/:?] {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8036) TestResourceTracker keeps cache managers alive after they are stopped

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8036?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8036: ------------------------------- Status: Open (was: New) > TestResourceTracker keeps cache managers alive after they are stopped > --------------------------------------------------------------------- > > Key: ISPN-8036 > URL: https://issues.jboss.org/browse/ISPN-8036 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.1.0.CR1, 9.0.3.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 9.1.0.Final > > > {{TestCacheManagerFactory.newDefaultCacheManager()}} adds the manager to {{TestResourceTracker}} so if the test doesn't stop it explicitly, {{TestResourceTracker}} will. > When a test uses {{@CleanupAfterMethod}}, however, the cache managers are stopped and recreated after each method, but the list of resources is only cleared at the end of the test class. If a test has lots of methods, like {{LocalDistributedExecutorTest}} and its subclasses, the stopped managers can use a lot of memory (250KB for each {{ComponentMetadataRepo}}). > I believe the extra memory usage is causing longer GC pauses, and in turn leads to intermittent test failures in test methods that use short timeouts: > {noformat} > 16:58:34,801 ERROR (testng-ReplSyncDistributedExecutorTest:[]) [TestSuiteProgress] Test failed: org.infinispan.distexec.ReplSyncDistributedExecutorTest.testInvokeAnyTimedSleepingTasks > java.lang.AssertionError: Should have thrown an class java.util.concurrent.TimeoutException > at org.infinispan.test.Exceptions.assertException(Exceptions.java:21) ~[test-classes/:?] > at org.infinispan.test.Exceptions.expectException(Exceptions.java:92) ~[test-classes/:?] > at org.infinispan.distexec.LocalDistributedExecutorTest.testInvokeAnyTimedSleepingTasks(LocalDistributedExecutorTest.java:269) ~[test-classes/:?] > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8034) Support and document the new `local_heap` configuration property for Query configuration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8034?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8034: ---------------------------------- Fix Version/s: 9.1.0.Final (was: 9.1.0.CR2) > Support and document the new `local_heap` configuration property for Query configuration > ---------------------------------------------------------------------------------------- > > Key: ISPN-8034 > URL: https://issues.jboss.org/browse/ISPN-8034 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Embedded Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 9.1.0.Final > > > The "ram" short name to use Lucene's {{RAMDirectory}} implementation was renamed to "local_heap" in Hibernate Search to make its function clearer in the context of Infinispan as there are many kinds of _ram_. > The "ram" keyword was hardcoded into the Infinispan project though, so this needs to be updated and documented. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8035) Query module using several deprecated configuration methods from Infinispan core

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-8035?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-8035: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5274 > Query module using several deprecated configuration methods from Infinispan core > -------------------------------------------------------------------------------- > > Key: ISPN-8035 > URL: https://issues.jboss.org/browse/ISPN-8035 > Project: Infinispan > Issue Type: Task > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Optional > Fix For: 9.1.0.CR2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 July 2017