March 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5327) EventSocketTimeoutTest fails randomly

by Vojtech Juranek (JIRA)

Vojtech Juranek created ISPN-5327: ------------------------------------- Summary: EventSocketTimeoutTest fails randomly Key: ISPN-5327 URL: https://issues.jboss.org/browse/ISPN-5327 Project: Infinispan Issue Type: Bug Components: Test Suite - Core Reporter: Vojtech Juranek Assignee: Vojtech Juranek {{EventSocketTimeoutTest#testSocketTimeoutWithEvent}} fails randomly with {{SocketTimeoutException}}: {noformat} org.infinispan.client.hotrod.exceptions.TransportException:: java.net.SocketTimeoutException at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.readByte(TcpTransport.java:184) at org.infinispan.client.hotrod.impl.protocol.Codec20.readMagic(Codec20.java:282) at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:94) at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56) at org.infinispan.client.hotrod.impl.operations.AbstractKeyValueOperation.sendPutOperation(AbstractKeyValueOperation.java:50) at org.infinispan.client.hotrod.impl.operations.PutOperation.executeOperation(PutOperation.java:30) at org.infinispan.client.hotrod.impl.operations.PutOperation.executeOperation(PutOperation.java:19) at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:52) at org.infinispan.client.hotrod.impl.RemoteCacheImpl.put(RemoteCacheImpl.java:237) at org.infinispan.client.hotrod.impl.RemoteCacheSupport.put(RemoteCacheSupport.java:79) at org.infinispan.client.hotrod.event.EventSocketTimeoutTest$1.call(EventSocketTimeoutTest.java:60) at org.infinispan.client.hotrod.test.HotRodClientTestingUtil.withClientListener(HotRodClientTestingUtil.java:145) at org.infinispan.client.hotrod.event.EventSocketTimeoutTest.testSocketTimeoutWithEvent(EventSocketTimeoutTest.java:47) {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5325) Upgrade to protostream-3.0.1.Final

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5325?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5325: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.2.0.Final Resolution: Done > Upgrade to protostream-3.0.1.Final > ---------------------------------- > > Key: ISPN-5325 > URL: https://issues.jboss.org/browse/ISPN-5325 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Querying > Affects Versions: 7.2.0.Beta1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.Beta2, 7.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5304) WildFly module "/org/infinispan/client/hotrod/jdg-6.4" is different if installed with library or HR-client

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5304?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5304: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > WildFly module "/org/infinispan/client/hotrod/jdg-6.4" is different if installed with library or HR-client > ---------------------------------------------------------------------------------------------------------- > > Key: ISPN-5304 > URL: https://issues.jboss.org/browse/ISPN-5304 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 7.2.0.Alpha1, 7.1.1.Final > Environment: Infinispan as WildFly module > Reporter: Wolf-Dieter Fink > Assignee: Adrian Nistor > Fix For: 7.2.0.Beta2, 7.2.0.Final, 7.1.2.Final > > > If Infinispan is used inside WildFly applications there are two WF modules for Infinispan. > One for Library mode > One for HotRod remote client mode > Both modules contain > modules/org/infinispan/client/hotrod/jdg-6.4/infinispan-client-hotrod-6.2.0.Final-redhat-4.jar > modules/org/infinispan/client/hotrod/jdg-6.4/module.xml > BUT > the module.xml is different: > < <module name="org.infinispan" slot="jdg-6.4"/> > --- > > <module name="org.infinispan.commons" slot="jdg-6.4"/> > > <module name="org.infinispan.protostream" slot="jdg-6.4"/> > > <module name="org.infinispan.query.dsl" slot="jdg-6.4"/> > > <module name="org.infinispan.query.remote.client" slot="jdg-6.4"/> > This mean it is not possible to use both modules if there are applications with library mode and others with HR remote client mode. > Also it is odd because it depends on the installation order what dependencies are installed. > It should be possible to install both modules and use it at the same time from different applicaitons. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5315) Tight loop on ClientListenerNotifier

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5315?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5315: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.2.0.Beta2 7.2.0.Final Resolution: Done > Tight loop on ClientListenerNotifier > ------------------------------------ > > Key: ISPN-5315 > URL: https://issues.jboss.org/browse/ISPN-5315 > Project: Infinispan > Issue Type: Bug > Components: Listeners > Affects Versions: 7.2.0.Beta1, 7.1.1.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Minor > Fix For: 7.2.0.Beta2, 7.2.0.Final > > Attachments: stackTrace > > > Sometimes the {{ClientListenerNotifier}} keeps printing extremely high number of warning and quickly fill GBs of disk space: > {code} > 11:28:16,805 WARN [ClientListenerNotifier] (Client-Listener-aacb322ffc60405e) ISPN004039: Unable to complete reading event from server null > java.nio.channels.IllegalBlockingModeException > at sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:201) > at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) > at java.io.BufferedInputStream.read(BufferedInputStream.java:254) > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.readByte(TcpTransport.java:179) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readMagic(Codec20.java:282) > at org.infinispan.client.hotrod^C.impl.protocol.Codec20.readEvent(Codec20.java:126) > at org.infinispan.client.hotrod.event.ClientListenerNotifier$EventDispatcher.run(ClientListenerNotifier.java:237) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > {code} > This can be reproduced when running the server test suite, more specifically the test {{ExampleConfigsIT}}. Right after the server is started the above warning is logged in a loop for the duration of the tests. > I've started to observe this after commit (1), which changed the behaviour to retry on SocketTimeouts. > Before the aforementioned commit, log were printing: > {code} > 10:49:56,361 ERROR [ClientListenerNotifier] (Client-Listener-b53963d5ab2b4234) ISPN004043: Unrecoverable error reading event from server null, exiting event reader thread > org.infinispan.client.hotrod.exceptions.TransportException:: java.net.SocketTimeoutException > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.readByte(TcpTransport.java:184) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readMagic(Codec20.java:282) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readEvent(Codec20.java:126) > at org.infinispan.client.hotrod.event.ClientListenerNotifier$EventDispatcher.run(ClientListenerNotifier.java:236) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.net.SocketTimeoutException > at sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:229) > at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) > at java.io.BufferedInputStream.read(BufferedInputStream.java:254) > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.readByte(TcpTransport.java:179) > ... 8 more > {code} > And thus the listener thread was exiting, > (1) https://github.com/infinispan/infinispan/commit/1a03a0a84307ae8b95c06b398... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5315) Tight loop on ClientListenerNotifier

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5315?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5315: ----------------------------------- Affects Version/s: 7.1.1.Final 7.2.0.Beta1 > Tight loop on ClientListenerNotifier > ------------------------------------ > > Key: ISPN-5315 > URL: https://issues.jboss.org/browse/ISPN-5315 > Project: Infinispan > Issue Type: Bug > Components: Listeners > Affects Versions: 7.2.0.Beta1, 7.1.1.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Minor > Fix For: 7.2.0.Beta2, 7.2.0.Final > > Attachments: stackTrace > > > Sometimes the {{ClientListenerNotifier}} keeps printing extremely high number of warning and quickly fill GBs of disk space: > {code} > 11:28:16,805 WARN [ClientListenerNotifier] (Client-Listener-aacb322ffc60405e) ISPN004039: Unable to complete reading event from server null > java.nio.channels.IllegalBlockingModeException > at sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:201) > at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) > at java.io.BufferedInputStream.read(BufferedInputStream.java:254) > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.readByte(TcpTransport.java:179) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readMagic(Codec20.java:282) > at org.infinispan.client.hotrod^C.impl.protocol.Codec20.readEvent(Codec20.java:126) > at org.infinispan.client.hotrod.event.ClientListenerNotifier$EventDispatcher.run(ClientListenerNotifier.java:237) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > {code} > This can be reproduced when running the server test suite, more specifically the test {{ExampleConfigsIT}}. Right after the server is started the above warning is logged in a loop for the duration of the tests. > I've started to observe this after commit (1), which changed the behaviour to retry on SocketTimeouts. > Before the aforementioned commit, log were printing: > {code} > 10:49:56,361 ERROR [ClientListenerNotifier] (Client-Listener-b53963d5ab2b4234) ISPN004043: Unrecoverable error reading event from server null, exiting event reader thread > org.infinispan.client.hotrod.exceptions.TransportException:: java.net.SocketTimeoutException > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.readByte(TcpTransport.java:184) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readMagic(Codec20.java:282) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readEvent(Codec20.java:126) > at org.infinispan.client.hotrod.event.ClientListenerNotifier$EventDispatcher.run(ClientListenerNotifier.java:236) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.net.SocketTimeoutException > at sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:229) > at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) > at java.io.BufferedInputStream.read(BufferedInputStream.java:254) > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.readByte(TcpTransport.java:179) > ... 8 more > {code} > And thus the listener thread was exiting, > (1) https://github.com/infinispan/infinispan/commit/1a03a0a84307ae8b95c06b398... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4741) ConsistentHashV1IntegrationTest.testCorrectBalancingOfKeysAfterNodeKill randomly fails on RHEL

by Vitalii Chepeliuk (JIRA)

[ https://issues.jboss.org/browse/ISPN-4741?page=com.atlassian.jira.plugin.... ] Vitalii Chepeliuk updated ISPN-4741: ------------------------------------ Description: {{ConsistentHashV1IntegrationTest.testCorrectBalancingOfKeysAfterNodeKill}} randomly fails (spot on RHEL6, IBM java 6) with ([see details|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FU...]): {noformat} java.lang.AssertionError: expected:<ConsistentHashV1IntegrationTest-NodeA-42275> but was:<ConsistentHashV1IntegrationTest-NodeE-19755> at org.testng.AssertJUnit.fail(AssertJUnit.java:59) at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:88) at org.infinispan.client.hotrod.ConsistentHashV1IntegrationTest.runTest(ConsistentHashV1IntegrationTest.java:124) at org.infinispan.client.hotrod.ConsistentHashV1IntegrationTest.testCorrectBalancingOfKeysAfterNodeKill(ConsistentHashV1IntegrationTest.java:155) {noformat} was: {{ConsistentHashV1IntegrationTest.testCorrectBalancingOfKeysAfterNodeKill}} randomly fails (spot on RHEL6, IMB java 6) with ([see details|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FU...]): {noformat} java.lang.AssertionError: expected:<ConsistentHashV1IntegrationTest-NodeA-42275> but was:<ConsistentHashV1IntegrationTest-NodeE-19755> at org.testng.AssertJUnit.fail(AssertJUnit.java:59) at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:88) at org.infinispan.client.hotrod.ConsistentHashV1IntegrationTest.runTest(ConsistentHashV1IntegrationTest.java:124) at org.infinispan.client.hotrod.ConsistentHashV1IntegrationTest.testCorrectBalancingOfKeysAfterNodeKill(ConsistentHashV1IntegrationTest.java:155) {noformat} > ConsistentHashV1IntegrationTest.testCorrectBalancingOfKeysAfterNodeKill randomly fails on RHEL > ---------------------------------------------------------------------------------------------- > > Key: ISPN-4741 > URL: https://issues.jboss.org/browse/ISPN-4741 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Reporter: Vojtech Juranek > Labels: testsuite_stability > > {{ConsistentHashV1IntegrationTest.testCorrectBalancingOfKeysAfterNodeKill}} randomly fails (spot on RHEL6, IBM java 6) with ([see details|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FU...]): > {noformat} > java.lang.AssertionError: expected:<ConsistentHashV1IntegrationTest-NodeA-42275> but was:<ConsistentHashV1IntegrationTest-NodeE-19755> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:88) > at org.infinispan.client.hotrod.ConsistentHashV1IntegrationTest.runTest(ConsistentHashV1IntegrationTest.java:124) > at org.infinispan.client.hotrod.ConsistentHashV1IntegrationTest.testCorrectBalancingOfKeysAfterNodeKill(ConsistentHashV1IntegrationTest.java:155) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5326) JSR-107 Support for exception-handling annotation properties

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5326?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5326: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1205705 > JSR-107 Support for exception-handling annotation properties > ------------------------------------------------------------ > > Key: ISPN-5326 > URL: https://issues.jboss.org/browse/ISPN-5326 > Project: Infinispan > Issue Type: Enhancement > Components: JCache > Reporter: Matej Čimbora > > The following JSR-107 annotation properties are currently not yet supported. > CacheResult - cachedExceptions, exceptionCacheName, nonCachedExceptions > CachePut - cacheFor, noCacheFor > CacheRemove - evictFor, noEvictFor > CacheRemoveAll - evictFor, noEvictFor > Note: Not covered by TCK tests. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5326) JSR-107 Support for exception-handling annotation properties

by Matej Čimbora (JIRA)

Matej Čimbora created ISPN-5326: ----------------------------------- Summary: JSR-107 Support for exception-handling annotation properties Key: ISPN-5326 URL: https://issues.jboss.org/browse/ISPN-5326 Project: Infinispan Issue Type: Enhancement Components: JCache Reporter: Matej Čimbora The following JSR-107 annotation properties are currently not yet supported. CacheResult - cachedExceptions, exceptionCacheName, nonCachedExceptions CachePut - cacheFor, noCacheFor CacheRemove - evictFor, noEvictFor CacheRemoveAll - evictFor, noEvictFor Note: Not covered by TCK tests. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5325) Upgrade to protostream-3.0.1.Final

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5325?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5325: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3336 > Upgrade to protostream-3.0.1.Final > ---------------------------------- > > Key: ISPN-5325 > URL: https://issues.jboss.org/browse/ISPN-5325 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Querying > Affects Versions: 7.2.0.Beta1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5325) Upgrade to protostream-3.0.1.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5325?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5325: ----------------------------------------------- Adrian Nistor <anistor(a)redhat.com> changed the Status of [bug 1205679|https://bugzilla.redhat.com/show_bug.cgi?id=1205679] from NEW to POST > Upgrade to protostream-3.0.1.Final > ---------------------------------- > > Key: ISPN-5325 > URL: https://issues.jboss.org/browse/ISPN-5325 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Querying > Affects Versions: 7.2.0.Beta1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2015