November 2019 - infinispan-issues

[JBoss JIRA] (ISPN-10908) Client timeout Exception should log the connection additional to the key

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-10908: --------------------------------------- Summary: Client timeout Exception should log the connection additional to the key Key: ISPN-10908 URL: https://issues.jboss.org/browse/ISPN-10908 Project: Infinispan Issue Type: Enhancement Components: Hot Rod Affects Versions: 10.0.0.Final Environment: HotRod client Reporter: Wolf-Dieter Fink Assignee: Will Burns In case of communication timeout with the server the client should log the connection details as the key will not give enough to analyse the issue. ~~~ ERROR [stderr] (pool-12-thread-3) org.infinispan.client.hotrod.exceptions.TransportException:: java.net.SocketTimeoutException: GetOperation{TestCache, key=[B0x800127656A6B2F6C..[103], flags=0} timed out after 60000 ms ERROR [stderr] (pool-12-thread-3) at org.infinispan.client.hotrod.impl.Util.rewrap(Util.java:54) ERROR [stderr] (pool-12-thread-3) at org.infinispan.client.hotrod.impl.Util.await(Util.java:27) ERROR [stderr] (pool-12-thread-3) at org.infinispan.client.hotrod.impl.RemoteCacheImpl.get(RemoteCacheImpl.java:418) ... ERROR [stderr] (pool-12-thread-3) Caused by: java.net.SocketTimeoutException: GetOperation{TestCache, key=[B0x800127656A6B2F6C..[103], flags=0} timed out after 60000 ms ERROR [stderr] (pool-12-thread-3) at org.infinispan.client.hotrod.impl.operations.HotRodOperation.run(HotRodOperation.java:172) ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.PromiseTask$RunnableAdapter.call(PromiseTask.java:38) ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:127) ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163) ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404) ERROR [stderr] (pool-12-thread-3) at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:322) ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884) ERROR [stderr] (pool-12-thread-3) ... 3 more ~~~ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7912) Prevent RocksDBStore writes blocking on full expiry queue

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-7912?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-7912: -------------------------------- Status: Open (was: New) > Prevent RocksDBStore writes blocking on full expiry queue > --------------------------------------------------------- > > Key: ISPN-7912 > URL: https://issues.jboss.org/browse/ISPN-7912 > Project: Infinispan > Issue Type: Sub-task > Components: Loaders and Stores > Affects Versions: 9.1.0.Alpha1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.1.0.Final > > > Currently you can only insert 10000 elements into the rocks db store until you will block a thread until the expiration reaper is ran. Instead we should offer elements to the queue and upon failure utilise the persistence executors to run purge. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7912) Prevent RocksDBStore writes blocking on full expiry queue

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-7912?page=com.atlassian.jira.plugin.... ] Work on ISPN-7912 started by Diego Lovison. ------------------------------------------- > Prevent RocksDBStore writes blocking on full expiry queue > --------------------------------------------------------- > > Key: ISPN-7912 > URL: https://issues.jboss.org/browse/ISPN-7912 > Project: Infinispan > Issue Type: Sub-task > Components: Loaders and Stores > Affects Versions: 9.1.0.Alpha1 > Reporter: Ryan Emerson > Assignee: Diego Lovison > Priority: Major > Fix For: 10.1.0.Final > > > Currently you can only insert 10000 elements into the rocks db store until you will block a thread until the expiration reaper is ran. Instead we should offer elements to the queue and upon failure utilise the persistence executors to run purge. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10893) Avoid sending HTTP date headers for entries that don't contain metadata

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-10893?page=com.atlassian.jira.plugin... ] Katia Aresti updated ISPN-10893: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Avoid sending HTTP date headers for entries that don't contain metadata > ----------------------------------------------------------------------- > > Key: ISPN-10893 > URL: https://issues.jboss.org/browse/ISPN-10893 > Project: Infinispan > Issue Type: Bug > Components: REST > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > > Currently, the REST server returns date headers like "Thu, 1 Jan 1970 01:00:00 +0100" for entries that don't contain metadata. > It should not return those headers if the server doesn't store those informations (e.g. for immortal cache entries) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10907) Add TCP_KEEPIDLE TCP_KEEPINTVL and TCP_KEEPCNT to the Hot Rod client

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-10907: -------------------------------------- Summary: Add TCP_KEEPIDLE TCP_KEEPINTVL and TCP_KEEPCNT to the Hot Rod client Key: ISPN-10907 URL: https://issues.jboss.org/browse/ISPN-10907 Project: Infinispan Issue Type: Enhancement Components: Hot Rod Reporter: Tristan Tarrant Assignee: Tristan Tarrant Netty's epoll channel offers additional socket options that we could support https://netty.io/4.1/api/io/netty/channel/epoll/EpollChannelOption.html -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10906) JGroupsTransport instance is reused in tests

by Dan Berindei (Jira)

Dan Berindei created ISPN-10906: ----------------------------------- Summary: JGroupsTransport instance is reused in tests Key: ISPN-10906 URL: https://issues.jboss.org/browse/ISPN-10906 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 10.0.1.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 10.1.0.Beta1 The {{TRANSPORT}} {{AttributeDefinition}} uses {{IdentityAttributeCopier}}, which means that when a test uses {{GlobalConfigurationBuilder.read()}} to make a clone of the global configuration it keeps using the same {{JGroupsTransport}} instance. Both cache managers sort of work, but usually not as intended. We should detect when {{JGroupsTransport}}'s dependencies are injected twice and throw an exception. We should also consider changing the {{TRANSPORT}} copier to {{SimpleInstanceAttributeCopier}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10906) JGroupsTransport instance is reused in tests

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10906?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10906: -------------------------------- Status: Open (was: New) > JGroupsTransport instance is reused in tests > -------------------------------------------- > > Key: ISPN-10906 > URL: https://issues.jboss.org/browse/ISPN-10906 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.0.Beta1 > > > The {{TRANSPORT}} {{AttributeDefinition}} uses {{IdentityAttributeCopier}}, which means that when a test uses {{GlobalConfigurationBuilder.read()}} to make a clone of the global configuration it keeps using the same {{JGroupsTransport}} instance. Both cache managers sort of work, but usually not as intended. > We should detect when {{JGroupsTransport}}'s dependencies are injected twice and throw an exception. We should also consider changing the {{TRANSPORT}} copier to {{SimpleInstanceAttributeCopier}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10905) Hot Rod client should not use JmxUtil (no PrivilegedActions needed by client)

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10905?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10905: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7534 > Hot Rod client should not use JmxUtil (no PrivilegedActions needed by client) > ----------------------------------------------------------------------------- > > Key: ISPN-10905 > URL: https://issues.jboss.org/browse/ISPN-10905 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management, Remote Protocols > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10905) Hot Rod client should not use JmxUtil (no PrivilegedActions needed by client)

by Nistor Adrian (Jira)

Nistor Adrian created ISPN-10905: ------------------------------------ Summary: Hot Rod client should not use JmxUtil (no PrivilegedActions needed by client) Key: ISPN-10905 URL: https://issues.jboss.org/browse/ISPN-10905 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management, Remote Protocols Reporter: Nistor Adrian Assignee: Nistor Adrian Fix For: 10.1.0.Beta1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10905) Hot Rod client should not use JmxUtil (no PrivilegedActions needed by client)

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10905?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10905: --------------------------------- Status: Open (was: New) > Hot Rod client should not use JmxUtil (no PrivilegedActions needed by client) > ----------------------------------------------------------------------------- > > Key: ISPN-10905 > URL: https://issues.jboss.org/browse/ISPN-10905 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management, Remote Protocols > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 November 2019