August 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6930) ERROR logged when consuming events with SSL

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6930?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6930: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4491 > ERROR logged when consuming events with SSL > ------------------------------------------- > > Key: ISPN-6930 > URL: https://issues.jboss.org/browse/ISPN-6930 > Project: Infinispan > Issue Type: Bug > Reporter: Gustavo Fernandes > > When closing the remote cache manager that has an event listener and connects via SSL, the Hot Rod client logs an ERROR > {noformat} > 2016-08-05 12:14:53 [Client-Listener-org.infinispan.spark.suites.JavaStreamApiSecureSuite-3219f3f2007a4ba4] ERROR ClientListenerNotifier:278 - ISPN004043: Unrecoverable error reading event from server localhost/127.0.0.1:11222, exiting event reader thread > org.infinispan.client.hotrod.exceptions.TransportException:: java.net.SocketException: Socket closed > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.readByte(TcpTransport.java:207) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readMagic(Codec20.java:305) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readEvent(Codec20.java:147) > at org.infinispan.client.hotrod.event.ClientListenerNotifier$EventDispatcher.run(ClientListenerNotifier.java:262) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at org.infinispan.client.hotrod.event.ClientListenerNotifier.lambda$null$0(ClientListenerNotifier.java:78) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.net.SocketException: Socket closed > at java.net.SocketInputStream.read(SocketInputStream.java:203) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.read(InputRecord.java:503) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read(BufferedInputStream.java:265) > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.readByte(TcpTransport.java:202) > ... 9 more > {noformat} > The error is not throw when not using SSL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6910) Random failures due to MagicKey

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6910?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6910: ---------------------------------- Status: Open (was: New) > Random failures due to MagicKey > ------------------------------- > > Key: ISPN-6910 > URL: https://issues.jboss.org/browse/ISPN-6910 > Project: Infinispan > Issue Type: Enhancement > Components: Test Suite - Core > Affects Versions: 9.0.0.Alpha3 > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.0.0.Beta1, 9.0.0.Final > > > There is a fixed 1000-iteration loop to find out proper key. In tests that create many magic keys, the cumulative probability of failing one of the keys' generation is going up and this is causing random failures in the testsuite. > Moreover, the equality of magic keys is based only on the hashCode - with many keys, there is a non-trivial chance that the hashcodes will make two logically different keys equal. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6910) Random failures due to MagicKey

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6910?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6910: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4487 > Random failures due to MagicKey > ------------------------------- > > Key: ISPN-6910 > URL: https://issues.jboss.org/browse/ISPN-6910 > Project: Infinispan > Issue Type: Enhancement > Components: Test Suite - Core > Affects Versions: 9.0.0.Alpha3 > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.0.0.Beta1, 9.0.0.Final > > > There is a fixed 1000-iteration loop to find out proper key. In tests that create many magic keys, the cumulative probability of failing one of the keys' generation is going up and this is causing random failures in the testsuite. > Moreover, the equality of magic keys is based only on the hashCode - with many keys, there is a non-trivial chance that the hashcodes will make two logically different keys equal. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6910) Random failures due to MagicKey

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6910?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6910: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Beta1 9.0.0.Final Resolution: Done > Random failures due to MagicKey > ------------------------------- > > Key: ISPN-6910 > URL: https://issues.jboss.org/browse/ISPN-6910 > Project: Infinispan > Issue Type: Enhancement > Components: Test Suite - Core > Affects Versions: 9.0.0.Alpha3 > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.0.0.Beta1, 9.0.0.Final > > > There is a fixed 1000-iteration loop to find out proper key. In tests that create many magic keys, the cumulative probability of failing one of the keys' generation is going up and this is causing random failures in the testsuite. > Moreover, the equality of magic keys is based only on the hashCode - with many keys, there is a non-trivial chance that the hashcodes will make two logically different keys equal. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6614) [8.2.x] JCacheConfigurationPropertiesFileTest.testPropertiesConfiguration always fails

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6614?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-6614: ------------------------------------- Assignee: Tristan Tarrant (was: Galder Zamarreño) > [8.2.x] JCacheConfigurationPropertiesFileTest.testPropertiesConfiguration always fails > --------------------------------------------------------------------------------------- > > Key: ISPN-6614 > URL: https://issues.jboss.org/browse/ISPN-6614 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 8.2.1.Final > Reporter: Dan Berindei > Assignee: Tristan Tarrant > Labels: testsuite_stability > Fix For: 8.2.4.Final > > > Class {{SomeCustomConsistentHashV2}} appears to be missing on the 8.2.x branch: > {noformat} > org.infinispan.commons.CacheConfigurationException: Unable to instantiate class org.infinispan.client.hotrod.SomeCustomConsistentHashV2 > at org.infinispan.commons.util.Util.loadClass(Util.java:103) > at org.infinispan.client.hotrod.configuration.ConfigurationBuilder.consistentHashImpl(ConfigurationBuilder.java:171) > at org.infinispan.client.hotrod.configuration.ConfigurationBuilder.withProperties(ConfigurationBuilder.java:291) > at org.infinispan.jcache.remote.JCacheManager.getConfigurationBuilder(JCacheManager.java:60) > at org.infinispan.jcache.remote.JCacheManager.<init>(JCacheManager.java:38) > at org.infinispan.jcache.remote.JCachingProvider.createCacheManager(JCachingProvider.java:37) > at org.infinispan.jcache.AbstractJCachingProvider.getCacheManager(AbstractJCachingProvider.java:67) > at org.infinispan.jcache.AbstractJCachingProvider.getCacheManager(AbstractJCachingProvider.java:80) > at org.infinispan.jcache.remote.JCacheConfigurationPropertiesFileTest.testPropertiesConfiguration(JCacheConfigurationPropertiesFileTest.java:24) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6647) DecoratedCache.putForExternalRead method with Metadata ignores Metadata

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6647?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6647: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 (was: 9.0.0.Beta1) > DecoratedCache.putForExternalRead method with Metadata ignores Metadata > ----------------------------------------------------------------------- > > Key: ISPN-6647 > URL: https://issues.jboss.org/browse/ISPN-6647 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 8.2.2.Final > Reporter: Karl von Randow > Assignee: Karl von Randow > Priority: Minor > Fix For: 9.0.0.Alpha3, 8.2.3.Final > > > The implementation of the {{putForExternalRead}} method ignores the {{Metadata}} parameter, instead of passing it on to the {{putForExternalRead}} method in the cache implementation. This is no doubt because the cache implementation previously didn't support {{Metadata}} for {{putForExternalRead}}. > I will prepare a PR and attach it to this ticket shortly. It was a gargantuan effort to patch this up, as you'll see! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6647) DecoratedCache.putForExternalRead method with Metadata ignores Metadata

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6647?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6647: ---------------------------------- Fix Version/s: 8.2.3.Final (was: 8.2.4.Final) > DecoratedCache.putForExternalRead method with Metadata ignores Metadata > ----------------------------------------------------------------------- > > Key: ISPN-6647 > URL: https://issues.jboss.org/browse/ISPN-6647 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 8.2.2.Final > Reporter: Karl von Randow > Assignee: Karl von Randow > Priority: Minor > Fix For: 9.0.0.Beta1, 8.2.3.Final > > > The implementation of the {{putForExternalRead}} method ignores the {{Metadata}} parameter, instead of passing it on to the {{putForExternalRead}} method in the cache implementation. This is no doubt because the cache implementation previously didn't support {{Metadata}} for {{putForExternalRead}}. > I will prepare a PR and attach it to this ticket shortly. It was a gargantuan effort to patch this up, as you'll see! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6647) DecoratedCache.putForExternalRead method with Metadata ignores Metadata

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6647?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6647: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > DecoratedCache.putForExternalRead method with Metadata ignores Metadata > ----------------------------------------------------------------------- > > Key: ISPN-6647 > URL: https://issues.jboss.org/browse/ISPN-6647 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 8.2.2.Final > Reporter: Karl von Randow > Assignee: Karl von Randow > Priority: Minor > Fix For: 9.0.0.Beta1, 8.2.4.Final > > > The implementation of the {{putForExternalRead}} method ignores the {{Metadata}} parameter, instead of passing it on to the {{putForExternalRead}} method in the cache implementation. This is no doubt because the cache implementation previously didn't support {{Metadata}} for {{putForExternalRead}}. > I will prepare a PR and attach it to this ticket shortly. It was a gargantuan effort to patch this up, as you'll see! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6907) Repl/Dist cache with Transactions doesn't respect shared store semantics

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6907?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6907: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Repl/Dist cache with Transactions doesn't respect shared store semantics > ------------------------------------------------------------------------ > > Key: ISPN-6907 > URL: https://issues.jboss.org/browse/ISPN-6907 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 9.0.0.Alpha3, 8.2.3.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.0.0.Beta1, 8.2.4.Final > > > When running a replicated or distributed cache with different transaction modes and a shared cache store, it is possible for more than one node to write the store. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6907) Repl/Dist cache with Transactions doesn't respect shared store semantics

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6907?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6907: ---------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/infinispan/infinispan/pull/4480, https://github.com/infinispan/infinispan/pull/4481 (was: https://github.com/infinispan/infinispan/pull/4480) > Repl/Dist cache with Transactions doesn't respect shared store semantics > ------------------------------------------------------------------------ > > Key: ISPN-6907 > URL: https://issues.jboss.org/browse/ISPN-6907 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 9.0.0.Alpha3, 8.2.3.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.0.0.Beta1, 8.2.4.Final > > > When running a replicated or distributed cache with different transaction modes and a shared cache store, it is possible for more than one node to write the store. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 August 2016