October 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4915) Support flags for REST endpoint

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-4915?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-4915: ------------------------------------- Assignee: Gustavo Fernandes > Support flags for REST endpoint > ------------------------------- > > Key: ISPN-4915 > URL: https://issues.jboss.org/browse/ISPN-4915 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Tristan Tarrant > Assignee: Gustavo Fernandes > Priority: Major > Labels: hackathon > > For protocol symmetry, we should add support for the operation flags (e.g. SKIP_CACHE_LOAD, SKIP_INDEXING, etc) on the REST operations using some form of custom header -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7385) Number of REST tests fail on Solaris Sparc

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7385?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-7385. --------------------------------- Resolution: Out of Date > Number of REST tests fail on Solaris Sparc > ------------------------------------------ > > Key: ISPN-7385 > URL: https://issues.jboss.org/browse/ISPN-7385 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.0.0.Beta1 > Reporter: Roman Macor > Priority: Major > Labels: testsuite_stability > > Affected tests: > org.infinispan.rest.IntegrationTest* > org.infinispan.server.test.client.rest.REST* > org.infinispan.rest.TwoServerTest* > org.infinispan.persistence.rest.RestStore* > They fail with: (the logs differ slightly e.g. dataGET instead of dataPUT) > javax.ws.rs.NotAllowedException: RESTEASY003650: No resource method found for dataPUT, return 405 with Allow header > Standard Output > 03:45:36,766 ERROR (nioEventLoopGroup-3-1) [i18n] RESTEASY002010: Failed to execute > javax.ws.rs.NotAllowedException: RESTEASY003650: No resource method found for dataPUT, return 405 with Allow header > at org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:382) > at org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:121) > at org.jboss.resteasy.core.registry.RootNode.match(RootNode.java:43) > at org.jboss.resteasy.core.registry.RootClassNode.match(RootClassNode.java:48) > at org.jboss.resteasy.core.ResourceMethodRegistry.getResourceInvoker(ResourceMethodRegistry.java:445) > at org.jboss.resteasy.core.SynchronousDispatcher.getInvoker(SynchronousDispatcher.java:264) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:201) > at org.jboss.resteasy.plugins.server.netty.RequestDispatcher.service(RequestDispatcher.java:83) > at org.jboss.resteasy.plugins.server.netty.RequestHandler.channelRead0(RequestHandler.java:55)[UnitTestTestNGListener] Test testPutReplication(org.infinispan.rest.TwoServerTest) failed. > 03:45:36,770 ERROR (testng-TwoServerTest) [UnitTestTestNGListener] Test testPutReplication(org.infinispan.rest.TwoServerTest) failed. > java.lang.AssertionError: expected:<405> but was:<200> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at org.infinispan.rest.TwoServerTest.testPutReplication(TwoServerTest.java:78) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[UnitTestTestNGListener] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5992) REST server does not set value equivalence properly

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-5992?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-5992. --------------------------------- Resolution: Out of Date > REST server does not set value equivalence properly > --------------------------------------------------- > > Key: ISPN-5992 > URL: https://issues.jboss.org/browse/ISPN-5992 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.0.2.Final > Reporter: Radim Vansa > Priority: Major > > REST server uses String-based keys; therefore AnyEquivalence works on keys. However, the data accepted are byte[], and value equivalence is set to AnyEquivalence, too. This means that replace() command which is used in {{Server.putOrReplace}} does not work when the write is executed on non-owner. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6534) REST endpoint page doesn't work

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-6534?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-6534. --------------------------------- Resolution: Out of Date > REST endpoint page doesn't work > ------------------------------- > > Key: ISPN-6534 > URL: https://issues.jboss.org/browse/ISPN-6534 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.2.1.Final > Reporter: Roman Macor > Priority: Major > > - start infinispan standalone server > - in web browser go to localhost:8080 > Result: > Nothing is displayed in the browser > Server log: > 12:58:55,882 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (nioEventLoopGroup-7-1) RESTEASY002010: Failed to execute: javax.ws.rs.NotFoundException: RESTEASY003210: Could not find resource for full path: http://localhost:8080/ > at org.jboss.resteasy.core.registry.ClassNode.match(ClassNode.java:75) > at org.jboss.resteasy.core.registry.RootClassNode.match(RootClassNode.java:48) > at org.jboss.resteasy.core.ResourceMethodRegistry.getResourceInvoker(ResourceMethodRegistry.java:445) > at org.jboss.resteasy.core.SynchronousDispatcher.getInvoker(SynchronousDispatcher.java:257) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:194) > at org.jboss.resteasy.plugins.server.netty.RequestDispatcher.service(RequestDispatcher.java:83) > at org.jboss.resteasy.plugins.server.netty.RequestHandler.channelRead0(RequestHandler.java:53) > at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308) > at io.netty.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:32) > at io.netty.channel.AbstractChannelHandlerContext$7.run(AbstractChannelHandlerContext.java:299) > at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:380) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357) > at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116) > at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137) > at java.lang.Thread.run(Thread.java:745) > Expected result: > Rest console should be displayed -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

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

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-5086?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-5086. --------------------------------- Resolution: Out of Date Superseded by the HTTP/2 implementation > 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 > Priority: Major > > Once our REST server is based on Netty, explore the possibility of enabling SPDY. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8535) Rest API redesign

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8535?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8535: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1 > Rest API redesign > ----------------- > > Key: ISPN-8535 > URL: https://issues.jboss.org/browse/ISPN-8535 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 9.2.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.0.0.Final > > > Infinispan REST API deals with only one resource, (the cache) and maps all operations on the cache using HTTP verbs and request parameters. The API assumes the URI is related to the cache making it hard to add new kinds of resources without causing ambiguous references. > Since we now have other types of entities, such as counters, scripts, templates, etc, and each one of them can involve different operations, we should make the API more "Restful" by using more than one resource and collections of resources, plus HTTP verbs and operations on them. Examples: > * Create a cache: POST /rest/caches > * Delete a cache: DELETE /rest/caches/myCache > * Create a template: POST /rest/templates > * Delete a template: DELETE /rest/templates/myTemplate > * Create an entry: POST /rest/caches/myCache/1 > * Create a counter: POST /rest/counters > * Get a counter value: GET /rest/counters/mycounter > * Increment a counter: GET /rest/counters/mycounter?action=increment > * Search a cache: GET /rest/caches/myCache?action=search > * Create a script: POST /rest/scripts/ > * Get a script source: GET /rest/scritps/myScript > * Execute a script: GET /rest/scripts/myScript?action=execute&param1=foo > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8124) Create Lean Infinispan Server

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8124?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8124: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1 > Create Lean Infinispan Server > ----------------------------- > > Key: ISPN-8124 > URL: https://issues.jboss.org/browse/ISPN-8124 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Affects Versions: 9.1.0.Final > Reporter: Ryan Emerson > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Final > > > We need to create an infinispan server that utilises the minimum number of dependencies during run time. This is in order to reduce the server's memory footprint as much as possible. The resulting server will have the following characteristics: > * Based upon jboss-modules > * Mostly compatible with existing standalone configuration > * Expose management operations via Jolokia -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8124) Create Lean Infinispan Server

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8124?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8124: ---------------------------------- Parent: (was: ISPN-8123) Issue Type: Feature Request (was: Sub-task) > Create Lean Infinispan Server > ----------------------------- > > Key: ISPN-8124 > URL: https://issues.jboss.org/browse/ISPN-8124 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Affects Versions: 9.1.0.Final > Reporter: Ryan Emerson > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Final > > > We need to create an infinispan server that utilises the minimum number of dependencies during run time. This is in order to reduce the server's memory footprint as much as possible. The resulting server will have the following characteristics: > * Based upon jboss-modules > * Mostly compatible with existing standalone configuration > * Expose management operations via Jolokia -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8124) Create Lean Infinispan Server

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8124?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8124: ---------------------------------- Status: Open (was: New) > Create Lean Infinispan Server > ----------------------------- > > Key: ISPN-8124 > URL: https://issues.jboss.org/browse/ISPN-8124 > Project: Infinispan > Issue Type: Sub-task > Components: Server > Affects Versions: 9.1.0.Final > Reporter: Ryan Emerson > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Final > > > We need to create an infinispan server that utilises the minimum number of dependencies during run time. This is in order to reduce the server's memory footprint as much as possible. The resulting server will have the following characteristics: > * Based upon jboss-modules > * Mostly compatible with existing standalone configuration > * Expose management operations via Jolokia -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7095) JCache remote CacheManger needs to be aware of current server state

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7095?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-7095. --------------------------------- Resolution: Out of Date > JCache remote CacheManger needs to be aware of current server state > ------------------------------------------------------------------- > > Key: ISPN-7095 > URL: https://issues.jboss.org/browse/ISPN-7095 > Project: Infinispan > Issue Type: Bug > Components: JCache > Affects Versions: 9.0.0.Alpha3 > Reporter: Zdenek Hostasa > Priority: Major > > As per ISPN-6574 the JCache API needs to reflect correctly on caches created from outside of this API (in server config for example). This issue was addressed for the {{getCache(...)}} method, but remains unfixed for other three methods mentioned in previous request: {{getCacheNames()}}, {{enableManagement(..)}} and {{enableStatistics(...)}} > *Note:* During test creation I found out that invoking CacheManager.getCache will refresh that particular caches reference in the manager and the rest of the methods work correctly afterwards (for that one cache). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 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 October 2018