October 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10776) The new ServerNG doesn't support scripts execution

by Anna Manukyan (Jira)

Anna Manukyan created ISPN-10776: ------------------------------------ Summary: The new ServerNG doesn't support scripts execution Key: ISPN-10776 URL: https://issues.jboss.org/browse/ISPN-10776 Project: Infinispan Issue Type: Bug Components: Server Affects Versions: 10.0.0.CR3 Reporter: Anna Manukyan The new server doesn't support the script execution. When trying to add and execute a script, the following response is got on nodejs-client side: {code} org.infinispan.server.hotrod.CacheNotFoundException: Cache with name '___script_cache' not found amongst the configured caches {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10772) RemoteListener doesn't work with StorageType.BINARY/StorageType.OFF_HEAP

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10772?page=com.atlassian.jira.plugin... ] Work on ISPN-10772 started by Gustavo Fernandes. ------------------------------------------------ > RemoteListener doesn't work with StorageType.BINARY/StorageType.OFF_HEAP > ------------------------------------------------------------------------ > > Key: ISPN-10772 > URL: https://issues.jboss.org/browse/ISPN-10772 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod, Listeners > Affects Versions: 9.4.16.Final > Environment: RHDG 7.3.2 > Reporter: Will Burns > Assignee: Gustavo Fernandes > Priority: Major > > Customer has a cache configuration that uses nearCache builder. When try to get the value using cache.get(KEY), get the following message before get the value: > ------------------------------------------------------------- > --- [Retrieve Bean] Retrieve key='KEY' --- > Sep 20, 2019 7:15:28 PM org.infinispan.client.hotrod.impl.transport.netty.HeaderDecoder decode > WARN: ISPN004039: Unable to complete reading event from server 192.168.1.5/192.168.1.5:11222 > org.infinispan.client.hotrod.exceptions.HotRodClientException:: ISPN004034: Unable to unmarshall bytes 01012905033E034B4559 > at org.infinispan.client.hotrod.marshall.MarshallerUtil.bytes2obj(MarshallerUtil.java:47) > at org.infinispan.client.hotrod.DataFormat.keyToObj(DataFormat.java:103) > at org.infinispan.client.hotrod.impl.protocol.Codec21.readCacheEvent(Codec21.java:79) > at org.infinispan.client.hotrod.impl.transport.netty.HeaderDecoder.decode(HeaderDecoder.java:153) > at org.infinispan.client.hotrod.impl.transport.netty.HintedReplayingDecoder.callDecode(HintedReplayingDecoder.java:98) > at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:265) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) > at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) > at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:286) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) > at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) > at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1434) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) > at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:965) > at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:808) > at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:417) > at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:317) > at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.io.IOException: Unsupported protocol version 1 > at org.jboss.marshalling.river.RiverUnmarshaller.start(RiverUnmarshaller.java:1349) > at org.infinispan.commons.marshall.jboss.AbstractJBossMarshaller.startObjectInput(AbstractJBossMarshaller.java:129) > at org.infinispan.commons.marshall.jboss.AbstractJBossMarshaller.objectFromByteBuffer(AbstractJBossMarshaller.java:110) > at org.infinispan.commons.marshall.AbstractMarshaller.objectFromByteBuffer(AbstractMarshaller.java:82) > at org.infinispan.client.hotrod.marshall.MarshallerUtil.bytes2obj(MarshallerUtil.java:31) > ... 23 more > --- [Retrieve Bean] Value is 'VALUE' --- > ------------------------------------------------------------- > That doesn't impact the process of getting the stored value, but gets the WARN message with every query to that cache. The message is only generated when uses nearCahche -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10772) RemoteListener doesn't work with StorageType.BINARY/StorageType.OFF_HEAP

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10772?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-10772: ------------------------------------- Summary: RemoteListener doesn't work with StorageType.BINARY/StorageType.OFF_HEAP (was: Cache put generates WARN message "ISPN004034: Unable to unmarshall bytes" when uses near cache) > RemoteListener doesn't work with StorageType.BINARY/StorageType.OFF_HEAP > ------------------------------------------------------------------------ > > Key: ISPN-10772 > URL: https://issues.jboss.org/browse/ISPN-10772 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod, Listeners > Affects Versions: 9.4.16.Final > Environment: RHDG 7.3.2 > Reporter: Will Burns > Assignee: Gustavo Fernandes > Priority: Major > > Customer has a cache configuration that uses nearCache builder. When try to get the value using cache.get(KEY), get the following message before get the value: > ------------------------------------------------------------- > --- [Retrieve Bean] Retrieve key='KEY' --- > Sep 20, 2019 7:15:28 PM org.infinispan.client.hotrod.impl.transport.netty.HeaderDecoder decode > WARN: ISPN004039: Unable to complete reading event from server 192.168.1.5/192.168.1.5:11222 > org.infinispan.client.hotrod.exceptions.HotRodClientException:: ISPN004034: Unable to unmarshall bytes 01012905033E034B4559 > at org.infinispan.client.hotrod.marshall.MarshallerUtil.bytes2obj(MarshallerUtil.java:47) > at org.infinispan.client.hotrod.DataFormat.keyToObj(DataFormat.java:103) > at org.infinispan.client.hotrod.impl.protocol.Codec21.readCacheEvent(Codec21.java:79) > at org.infinispan.client.hotrod.impl.transport.netty.HeaderDecoder.decode(HeaderDecoder.java:153) > at org.infinispan.client.hotrod.impl.transport.netty.HintedReplayingDecoder.callDecode(HintedReplayingDecoder.java:98) > at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:265) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) > at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) > at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:286) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) > at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) > at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1434) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) > at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:965) > at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:808) > at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:417) > at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:317) > at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.io.IOException: Unsupported protocol version 1 > at org.jboss.marshalling.river.RiverUnmarshaller.start(RiverUnmarshaller.java:1349) > at org.infinispan.commons.marshall.jboss.AbstractJBossMarshaller.startObjectInput(AbstractJBossMarshaller.java:129) > at org.infinispan.commons.marshall.jboss.AbstractJBossMarshaller.objectFromByteBuffer(AbstractJBossMarshaller.java:110) > at org.infinispan.commons.marshall.AbstractMarshaller.objectFromByteBuffer(AbstractMarshaller.java:82) > at org.infinispan.client.hotrod.marshall.MarshallerUtil.bytes2obj(MarshallerUtil.java:31) > ... 23 more > --- [Retrieve Bean] Value is 'VALUE' --- > ------------------------------------------------------------- > That doesn't impact the process of getting the stored value, but gets the WARN message with every query to that cache. The message is only generated when uses nearCahche -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10748) Rest endpoint is not able to reach a preconfigured cache

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10748?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10748. --------------------------------- Fix Version/s: 10.0.0.Final Resolution: Done > Rest endpoint is not able to reach a preconfigured cache > -------------------------------------------------------- > > Key: ISPN-10748 > URL: https://issues.jboss.org/browse/ISPN-10748 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.CR3 > Reporter: Diego Lovison > Assignee: Gustavo Fernandes > Priority: Blocker > Fix For: 10.0.0.Final > > > infinispan.xml > {code:xml} > <cache-container name="default"> > <transport cluster="${infinispan.cluster.name}" stack="${infinispan.cluster.stack:tcp}"/> > <distributed-cache name="rest"/> > </cache-container> > {code} > {code:java} > public static void main(String[] args) throws IOException { > String key = "k1"; > String value = "v1"; > OkHttpClient client = new OkHttpClient(); > String url = "http://%s:%s/rest/v2/caches/%s/%s"; > //String url = "http://%s:%s/rest/%s/%s"; > Request request = new Request.Builder() > .url(String.format(url, "localhost", 11222, "rest", key)) > .put(RequestBody.create(TEXT_PLAIN, value)) > .build(); > Response response = client.newCall(request).execute(); > assertEquals(200, response.code()); > } > {code} > A few notes: > * When created via rest, it works. > * When using the v2 rest endpoint, it works. > * It is only failing with the legacy endpoint. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10774) kill-server Ant task kills clients too

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10774?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10774. --------------------------------- Resolution: Done > kill-server Ant task kills clients too > -------------------------------------- > > Key: ISPN-10774 > URL: https://issues.jboss.org/browse/ISPN-10774 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 10.0.0.CR3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Final > > > {{kill-server}} uses multiple sources to find the pid of the running server(s), among them {{lsof}} to find processes listening on the HotRod port. > The {{lsof}} command line is imprecise and it also finds clients that have leaked a connection to the server, killing the failsafe fork too early and preventing failsafe from reporting the test results. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10773) RestClientConfigurationBuilder timeout configuration must be a long value

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-10773?page=com.atlassian.jira.plugin... ] Diego Lovison updated ISPN-10773: --------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/7441 > RestClientConfigurationBuilder timeout configuration must be a long value > ------------------------------------------------------------------------- > > Key: ISPN-10773 > URL: https://issues.jboss.org/browse/ISPN-10773 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.CR3 > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Major > > The JavaAPI by default uses long when dealing with timeouts. > CompletableFuture.java > public T get(long timeout, TimeUnit unit) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10773) RestClientConfigurationBuilder timeout configuration must be a long value

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-10773?page=com.atlassian.jira.plugin... ] Work on ISPN-10773 started by Diego Lovison. -------------------------------------------- > RestClientConfigurationBuilder timeout configuration must be a long value > ------------------------------------------------------------------------- > > Key: ISPN-10773 > URL: https://issues.jboss.org/browse/ISPN-10773 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.CR3 > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Major > > The JavaAPI by default uses long when dealing with timeouts. > CompletableFuture.java > public T get(long timeout, TimeUnit unit) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10773) RestClientConfigurationBuilder timeout configuration must be a long value

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-10773?page=com.atlassian.jira.plugin... ] Diego Lovison reassigned ISPN-10773: ------------------------------------ Assignee: Diego Lovison > RestClientConfigurationBuilder timeout configuration must be a long value > ------------------------------------------------------------------------- > > Key: ISPN-10773 > URL: https://issues.jboss.org/browse/ISPN-10773 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.CR3 > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Major > > The JavaAPI by default uses long when dealing with timeouts. > CompletableFuture.java > public T get(long timeout, TimeUnit unit) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10773) RestClientConfigurationBuilder timeout configuration must be a long value

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-10773?page=com.atlassian.jira.plugin... ] Diego Lovison updated ISPN-10773: --------------------------------- Status: Open (was: New) > RestClientConfigurationBuilder timeout configuration must be a long value > ------------------------------------------------------------------------- > > Key: ISPN-10773 > URL: https://issues.jboss.org/browse/ISPN-10773 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.CR3 > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Major > > The JavaAPI by default uses long when dealing with timeouts. > CompletableFuture.java > public T get(long timeout, TimeUnit unit) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10745) infinispan-jcache-remote does not support CDI caching annotations

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10745?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10745: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7420 > infinispan-jcache-remote does not support CDI caching annotations > ----------------------------------------------------------------- > > Key: ISPN-10745 > URL: https://issues.jboss.org/browse/ISPN-10745 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.4.16.Final, 10.0.0.CR3 > Reporter: Dan Berindei > Priority: Major > > {{infinispan-jcache-remote}} does not have CDI interceptors for the JCache annotations like {{@CacheResult}}, so the annotations are ignored. > The JCache TCK has tests for the annotations (e.g. {{InterceptionCacheNameOnEachMethodTest}}), but those tests used to pass by accident: a Weld dependency ({{slf4j-api}}) was missing in the {{tck-remote}} maven-failsafe-plugin execution, and {{AbstractInterceptionTest}} was automatically excluding them. > Weld 2.3.4.Final removed the {{slf4j-api}} dependency and the {{tck-remote}} interception tests started failing after the upgrade, but we did not notice because of ISPN-10379. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 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 2019