March 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8892) RestStore should only implement CacheLoader

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8892?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-8892: ------------------------------------- This is deprecated for 9.3 and will be removed in 10.0. > RestStore should only implement CacheLoader > ------------------------------------------- > > Key: ISPN-8892 > URL: https://issues.jboss.org/browse/ISPN-8892 > Project: Infinispan > Issue Type: Task > Components: Loaders and Stores > Reporter: William Burns > Assignee: William Burns > Fix For: 10.0.0.Final > > > The RestStore is redundant since a user could just use the RemoteStore which performs better for pretty much every operation. The only real usage for RestStore is if you wanted to pull data from an existing server and wanted to cache that data. As such we should change RestStore to just implement the CacheLoader interface. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8892) RestStore should only implement CacheLoader

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8892?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8892: -------------------------------- Fix Version/s: 10.0.0.Final (was: 9.3.0.Final) > RestStore should only implement CacheLoader > ------------------------------------------- > > Key: ISPN-8892 > URL: https://issues.jboss.org/browse/ISPN-8892 > Project: Infinispan > Issue Type: Task > Components: Loaders and Stores > Reporter: William Burns > Assignee: William Burns > Fix For: 10.0.0.Final > > > The RestStore is redundant since a user could just use the RemoteStore which performs better for pretty much every operation. The only real usage for RestStore is if you wanted to pull data from an existing server and wanted to cache that data. As such we should change RestStore to just implement the CacheLoader interface. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8900) Sockets might be left open if server unreachable on creation

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8900?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8900: ----------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/5808 > Sockets might be left open if server unreachable on creation > ------------------------------------------------------------ > > Key: ISPN-8900 > URL: https://issues.jboss.org/browse/ISPN-8900 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 9.1.6.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.1.7.Final > > > Seems to affect pre-netty client but not sure yet whether it affects netty version: > In 9.1.x and before, TcpTransport.destroy/release not called if TcpTransport constructor fails to connect socket. This might be leaving the socket file descriptor open. If an exception, socket and socketChannel should be closed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8902) Client hangs forever when IP address not accessible

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8902?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-8902: ---------------------------------------- Actually, does not hang forever but it's very slow getting through the servers. 60 second connection timeout? Shouldn't the address be resolved via DNS or something to unknown host? {code} 2018-03-01 18:02:39,038 DEBUG [org.infinispan.client.hotrod.impl.transport.netty.ChannelFactory] (main:[]) Statically configured servers: [127.0.0.1:11222, 127.0.0.2:11222, 127.0.0.2:11222, 127.0.0.3:11222, 127.0.0.4:11222] 2018-03-01 18:02:39,040 DEBUG [org.infinispan.client.hotrod.impl.transport.netty.ChannelFactory] (main:[]) Load balancer class: org.infinispan.client.hotrod.impl.transport.tcp.RoundRobinBalancingStrategy 2018-03-01 18:02:39,040 DEBUG [org.infinispan.client.hotrod.impl.transport.netty.ChannelFactory] (main:[]) Tcp no delay = true; client socket timeout = 60000 ms; connect timeout = 60000 ms 2018-03-01 18:02:39,042 TRACE [org.infinispan.client.hotrod.impl.transport.tcp.RoundRobinBalancingStrategy] (main:[]) New server list is: [127.0.0.1:11222, 127.0.0.2:11222, 127.0.0.2:11222, 127.0.0.3:11222, 127.0.0.4:11222] 2018-03-01 18:02:39,046 DEBUG [org.infinispan.client.hotrod.impl.transport.netty.ChannelFactory] (main:[]) Creating new channel pool for 127.0.0.1:11222 2018-03-01 18:02:39,202 TRACE [org.infinispan.client.hotrod.impl.transport.netty.ChannelInitializer] (HotRod-client-async-pool-0:[]) Created channel [id: 0xe5361eed] 2018-03-01 18:02:39,227 TRACE [org.infinispan.client.hotrod.impl.transport.netty.ChannelFactory] (main:[]) Ignoring exception pinging configured servers [127.0.0.1:11222, 127.0.0.2:11222, 127.0.0.2:11222, 127.0.0.3:11222, 127.0.0.4:11222] to establish a connection org.infinispan.client.hotrod.exceptions.TransportException: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /127.0.0.1:11222 at org.infinispan.client.hotrod.impl.Util.rewrap(Util.java:46) ~[classes/:?] at org.infinispan.client.hotrod.impl.Util.await(Util.java:23) ~[classes/:?] at org.infinispan.client.hotrod.impl.transport.netty.ChannelFactory.pingServersIgnoreException(ChannelFactory.java:199) [classes/:?] at org.infinispan.client.hotrod.impl.transport.netty.ChannelFactory.start(ChannelFactory.java:146) [classes/:?] at org.infinispan.client.hotrod.RemoteCacheManager.start(RemoteCacheManager.java:217) [classes/:?] at org.infinispan.client.hotrod.RemoteCacheManager.<init>(RemoteCacheManager.java:105) [classes/:?] at org.infinispan.client.hotrod.RemoteCacheManager.<init>(RemoteCacheManager.java:90) [classes/:?] at org.infinispan.client.hotrod.UnknownHosts.main(UnknownHosts.java:12) [test-classes/:?] Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /127.0.0.1:11222 at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[?:1.8.0_144] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) ~[?:1.8.0_144] at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:325) ~[netty-transport-4.1.21.Final.jar:4.1.21.Final] at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:340) ~[netty-transport-4.1.21.Final.jar:4.1.21.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:633) ~[netty-transport-4.1.21.Final.jar:4.1.21.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:580) ~[netty-transport-4.1.21.Final.jar:4.1.21.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:497) ~[netty-transport-4.1.21.Final.jar:4.1.21.Final] at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:459) ~[netty-transport-4.1.21.Final.jar:4.1.21.Final] at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886) ~[netty-common-4.1.21.Final.jar:4.1.21.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_144] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_144] at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_144] Caused by: java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[?:1.8.0_144] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) ~[?:1.8.0_144] at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:325) ~[netty-transport-4.1.21.Final.jar:4.1.21.Final] at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:340) ~[netty-transport-4.1.21.Final.jar:4.1.21.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:633) ~[netty-transport-4.1.21.Final.jar:4.1.21.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:580) ~[netty-transport-4.1.21.Final.jar:4.1.21.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:497) ~[netty-transport-4.1.21.Final.jar:4.1.21.Final] at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:459) ~[netty-transport-4.1.21.Final.jar:4.1.21.Final] at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886) ~[netty-common-4.1.21.Final.jar:4.1.21.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_144] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_144] at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_144] 2018-03-01 18:02:39,234 DEBUG [org.infinispan.client.hotrod.impl.transport.netty.ChannelFactory] (main:[]) Creating new channel pool for 127.0.0.2:11222 2018-03-01 18:02:39,234 TRACE [org.infinispan.client.hotrod.impl.transport.netty.ChannelInitializer] (HotRod-client-async-pool-1:[]) Created channel [id: 0xc6eedcd6] 2018-03-01 18:03:39,238 TRACE [org.infinispan.client.hotrod.impl.transport.netty.ChannelFactory] (main:[]) Ignoring exception pinging configured servers [127.0.0.1:11222, 127.0.0.2:11222, 127.0.0.2:11222, 127.0.0.3:11222, 127.0.0.4:11222] to establish a connection org.infinispan.client.hotrod.exceptions.TransportException: io.netty.channel.ConnectTimeoutException: connection timed out: /127.0.0.2:11222 at org.infinispan.client.hotrod.impl.Util.rewrap(Util.java:46) ~[classes/:?] at org.infinispan.client.hotrod.impl.Util.await(Util.java:23) ~[classes/:?] at org.infinispan.client.hotrod.impl.transport.netty.ChannelFactory.pingServersIgnoreException(ChannelFactory.java:199) [classes/:?] at org.infinispan.client.hotrod.impl.transport.netty.ChannelFactory.start(ChannelFactory.java:146) [classes/:?] at org.infinispan.client.hotrod.RemoteCacheManager.start(RemoteCacheManager.java:217) [classes/:?] at org.infinispan.client.hotrod.RemoteCacheManager.<init>(RemoteCacheManager.java:105) [classes/:?] at org.infinispan.client.hotrod.RemoteCacheManager.<init>(RemoteCacheManager.java:90) [classes/:?] at org.infinispan.client.hotrod.UnknownHosts.main(UnknownHosts.java:12) [test-classes/:?] Caused by: io.netty.channel.ConnectTimeoutException: connection timed out: /127.0.0.2:11222 at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:267) ~[netty-transport-4.1.21.Final.jar:4.1.21.Final] at io.netty.util.concurrent.PromiseTask$RunnableAdapter.call(PromiseTask.java:38) ~[netty-common-4.1.21.Final.jar:4.1.21.Final] at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:125) ~[netty-common-4.1.21.Final.jar:4.1.21.Final] at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163) ~[netty-common-4.1.21.Final.jar:4.1.21.Final] at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404) ~[netty-common-4.1.21.Final.jar:4.1.21.Final] at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:463) ~[netty-transport-4.1.21.Final.jar:4.1.21.Final] at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886) ~[netty-common-4.1.21.Final.jar:4.1.21.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_144] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_144] at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_144] 2018-03-01 18:03:39,240 TRACE [org.infinispan.client.hotrod.impl.transport.netty.ChannelInitializer] (HotRod-client-async-pool-2:[]) Created channel [id: 0x30dc0122] {code} > Client hangs forever when IP address not accessible > --------------------------------------------------- > > Key: ISPN-8902 > URL: https://issues.jboss.org/browse/ISPN-8902 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 9.2.0.Final > Reporter: Galder Zamarreño > Assignee: Radim Vansa > Fix For: 9.2.1.Final > > > Can be replicated with code [here|https://github.com/galderz/jdg-sandbox/blob/master/client/src/main/j...] > Thread dump is [here|https://gist.github.com/galderz/89b387b9e8b644456c18653e7b3c3c38]. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8900) Sockets might be left open if server unreachable on creation

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8900?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8900: ----------------------------------- Fix Version/s: (was: 9.2.1.Final) > Sockets might be left open if server unreachable on creation > ------------------------------------------------------------ > > Key: ISPN-8900 > URL: https://issues.jboss.org/browse/ISPN-8900 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 9.1.6.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.1.7.Final > > > Seems to affect pre-netty client but not sure yet whether it affects netty version: > In 9.1.x and before, TcpTransport.destroy/release not called if TcpTransport constructor fails to connect socket. This might be leaving the socket file descriptor open. If an exception, socket and socketChannel should be closed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8900) Sockets might be left open if server unreachable on creation

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8900?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-8900: ---------------------------------------- Master does not have this issue, but does not behave well (ISPN-8902). > Sockets might be left open if server unreachable on creation > ------------------------------------------------------------ > > Key: ISPN-8900 > URL: https://issues.jboss.org/browse/ISPN-8900 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 9.1.6.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.1.7.Final > > > Seems to affect pre-netty client but not sure yet whether it affects netty version: > In 9.1.x and before, TcpTransport.destroy/release not called if TcpTransport constructor fails to connect socket. This might be leaving the socket file descriptor open. If an exception, socket and socketChannel should be closed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8900) Sockets might be left open if server unreachable on creation

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8900?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8900: ----------------------------------- Affects Version/s: (was: 9.2.0.Final) > Sockets might be left open if server unreachable on creation > ------------------------------------------------------------ > > Key: ISPN-8900 > URL: https://issues.jboss.org/browse/ISPN-8900 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 9.1.6.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.1.7.Final > > > Seems to affect pre-netty client but not sure yet whether it affects netty version: > In 9.1.x and before, TcpTransport.destroy/release not called if TcpTransport constructor fails to connect socket. This might be leaving the socket file descriptor open. If an exception, socket and socketChannel should be closed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8902) Client hangs forever when IP address not accessible

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8902?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-8902: ---------------------------------------- Btw, code does not behave like ISPN-8900. When the first node can't be reached, the socket is indeed closed. But the code hangs when trying to access 127.0.0.2. > Client hangs forever when IP address not accessible > --------------------------------------------------- > > Key: ISPN-8902 > URL: https://issues.jboss.org/browse/ISPN-8902 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 9.2.0.Final > Reporter: Galder Zamarreño > Assignee: Radim Vansa > Fix For: 9.2.1.Final > > > Can be replicated with code [here|https://github.com/galderz/jdg-sandbox/blob/master/client/src/main/j...] > Thread dump is [here|https://gist.github.com/galderz/89b387b9e8b644456c18653e7b3c3c38]. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8902) Client hangs forever when IP address not accessible

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-8902: -------------------------------------- Summary: Client hangs forever when IP address not accessible Key: ISPN-8902 URL: https://issues.jboss.org/browse/ISPN-8902 Project: Infinispan Issue Type: Bug Components: Remote Protocols Affects Versions: 9.2.0.Final Reporter: Galder Zamarreño Assignee: Radim Vansa Fix For: 9.2.1.Final Can be replicated with code [here|https://github.com/galderz/jdg-sandbox/blob/master/client/src/main/j...] Thread dump is [here|https://gist.github.com/galderz/89b387b9e8b644456c18653e7b3c3c38]. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8900) Sockets might be left open if server unreachable on creation

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8900?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-8900: ---------------------------------------- Use [this class|https://github.com/galderz/jdg-sandbox/blob/master/client/src/main/...] to replicate issue. > Sockets might be left open if server unreachable on creation > ------------------------------------------------------------ > > Key: ISPN-8900 > URL: https://issues.jboss.org/browse/ISPN-8900 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 9.1.6.Final, 9.2.0.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.2.1.Final, 9.1.7.Final > > > Seems to affect pre-netty client but not sure yet whether it affects netty version: > In 9.1.x and before, TcpTransport.destroy/release not called if TcpTransport constructor fails to connect socket. This might be leaving the socket file descriptor open. If an exception, socket and socketChannel should be closed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2018