April 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10123) SecureServerFailureRetryTest random failures

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10123?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10123: -------------------------------- Attachment: threaddump-org_infinispan_client_hotrod_retry_SecureServerFailureRetryTest_testRetryCacheStopped-2019-04-04-22303.log.xz > SecureServerFailureRetryTest random failures > -------------------------------------------- > > Key: ISPN-10123 > URL: https://issues.jboss.org/browse/ISPN-10123 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.4.12.Final > Reporter: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.0.0.Beta4 > > Attachments: threaddump-org_infinispan_client_hotrod_retry_SecureServerFailureRetryTest_testRetryCacheStopped-2019-04-04-22303.log.xz > > > {noformat} > 06:32:49,516 DEBUG (testng-SecureServerFailureRetryTest:[]) [CacheImpl] Stopping cache ___defaultcache on SecureServerFailureRetryTest-NodeC-46394 > 06:32:49,524 WARN (SecureServerFailureRetryTest-Client-Async-111-1:[]) [ChannelFactory] ISPN004015: Failed adding new server 127.0.0.1:35206 > org.infinispan.client.hotrod.exceptions.RemoteIllegalLifecycleStateException: org.infinispan.IllegalLifecycleStateException: Cannot wire or start components while the registry is not running > at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:344) ~[classes/:?] > at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:177) ~[classes/:?] > at org.infinispan.client.hotrod.impl.transport.netty.HeaderDecoder.decode(HeaderDecoder.java:138) ~[classes/:?] > at org.infinispan.client.hotrod.impl.transport.netty.HintedReplayingDecoder.callDecode(HintedReplayingDecoder.java:98) ~[classes/:?] > at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:265) ~[netty-codec-4.1.28.Final.jar:4.1.28.Final] > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-transport-4.1.28.Final.jar:4.1.28.Final] > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-transport-4.1.28.Final.jar:4.1.28.Final] > at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) [netty-transport-4.1.28.Final.jar:4.1.28.Final] > at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:286) [netty-handler-4.1.28.Final.jar:4.1.28.Final] > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-transport-4.1.28.Final.jar:4.1.28.Final] > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-transport-4.1.28.Final.jar:4.1.28.Final] > at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) [netty-transport-4.1.28.Final.jar:4.1.28.Final] > at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1434) [netty-transport-4.1.28.Final.jar:4.1.28.Final] > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-transport-4.1.28.Final.jar:4.1.28.Final] > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-transport-4.1.28.Final.jar:4.1.28.Final] > at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:965) [netty-transport-4.1.28.Final.jar:4.1.28.Final] > at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:808) [netty-transport-native-epoll-4.1.28.Final-linux-x86_64.jar:4.1.28.Final] > at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:417) [netty-transport-native-epoll-4.1.28.Final-linux-x86_64.jar:4.1.28.Final] > at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:317) [netty-transport-native-epoll-4.1.28.Final-linux-x86_64.jar:4.1.28.Final] > [ERROR] Test org.infinispan.client.hotrod.retry.SecureServerFailureRetryTest.testRetryCacheStopped has been running for more than 300 seconds. Interrupting the test thread and dumping threads of the test suite process and its children. > Dumping thread stacks of process 22303 to /home/infinispan/workspace/Infinispan_PR-6833/client/hotrod-client/threaddump-org_infinispan_client_hotrod_retry_SecureServerFailureRetryTest_testRetryCacheStopped-2019-04-04-22303.log > Interrupted thread testng-SecureServerFailureRetryTest (21). > [OK: 4016, KO: 1, SKIP: 0] Test failed: org.infinispan.client.hotrod.retry.SecureServerFailureRetryTest.testRetryCacheStopped > org.infinispan.client.hotrod.exceptions.HotRodClientException:: java.lang.InterruptedException > at org.infinispan.client.hotrod.impl.Util.await(Util.java:25) > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.put(RemoteCacheImpl.java:335) > at org.infinispan.client.hotrod.impl.RemoteCacheSupport.put(RemoteCacheSupport.java:79) > at org.infinispan.client.hotrod.retry.ServerFailureRetryTest.testRetryCacheStopped(ServerFailureRetryTest.java:63) > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10123) SecureServerFailureRetryTest random failures

by Dan Berindei (Jira)

Dan Berindei created ISPN-10123: ----------------------------------- Summary: SecureServerFailureRetryTest random failures Key: ISPN-10123 URL: https://issues.jboss.org/browse/ISPN-10123 Project: Infinispan Issue Type: Bug Components: Test Suite - Server Affects Versions: 9.4.12.Final Reporter: Dan Berindei Fix For: 10.0.0.Beta4 {noformat} 06:32:49,516 DEBUG (testng-SecureServerFailureRetryTest:[]) [CacheImpl] Stopping cache ___defaultcache on SecureServerFailureRetryTest-NodeC-46394 06:32:49,524 WARN (SecureServerFailureRetryTest-Client-Async-111-1:[]) [ChannelFactory] ISPN004015: Failed adding new server 127.0.0.1:35206 org.infinispan.client.hotrod.exceptions.RemoteIllegalLifecycleStateException: org.infinispan.IllegalLifecycleStateException: Cannot wire or start components while the registry is not running at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:344) ~[classes/:?] at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:177) ~[classes/:?] at org.infinispan.client.hotrod.impl.transport.netty.HeaderDecoder.decode(HeaderDecoder.java:138) ~[classes/:?] at org.infinispan.client.hotrod.impl.transport.netty.HintedReplayingDecoder.callDecode(HintedReplayingDecoder.java:98) ~[classes/:?] at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:265) ~[netty-codec-4.1.28.Final.jar:4.1.28.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-transport-4.1.28.Final.jar:4.1.28.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-transport-4.1.28.Final.jar:4.1.28.Final] at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) [netty-transport-4.1.28.Final.jar:4.1.28.Final] at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:286) [netty-handler-4.1.28.Final.jar:4.1.28.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-transport-4.1.28.Final.jar:4.1.28.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-transport-4.1.28.Final.jar:4.1.28.Final] at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) [netty-transport-4.1.28.Final.jar:4.1.28.Final] at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1434) [netty-transport-4.1.28.Final.jar:4.1.28.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-transport-4.1.28.Final.jar:4.1.28.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-transport-4.1.28.Final.jar:4.1.28.Final] at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:965) [netty-transport-4.1.28.Final.jar:4.1.28.Final] at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:808) [netty-transport-native-epoll-4.1.28.Final-linux-x86_64.jar:4.1.28.Final] at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:417) [netty-transport-native-epoll-4.1.28.Final-linux-x86_64.jar:4.1.28.Final] at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:317) [netty-transport-native-epoll-4.1.28.Final-linux-x86_64.jar:4.1.28.Final] [ERROR] Test org.infinispan.client.hotrod.retry.SecureServerFailureRetryTest.testRetryCacheStopped has been running for more than 300 seconds. Interrupting the test thread and dumping threads of the test suite process and its children. Dumping thread stacks of process 22303 to /home/infinispan/workspace/Infinispan_PR-6833/client/hotrod-client/threaddump-org_infinispan_client_hotrod_retry_SecureServerFailureRetryTest_testRetryCacheStopped-2019-04-04-22303.log Interrupted thread testng-SecureServerFailureRetryTest (21). [OK: 4016, KO: 1, SKIP: 0] Test failed: org.infinispan.client.hotrod.retry.SecureServerFailureRetryTest.testRetryCacheStopped org.infinispan.client.hotrod.exceptions.HotRodClientException:: java.lang.InterruptedException at org.infinispan.client.hotrod.impl.Util.await(Util.java:25) at org.infinispan.client.hotrod.impl.RemoteCacheImpl.put(RemoteCacheImpl.java:335) at org.infinispan.client.hotrod.impl.RemoteCacheSupport.put(RemoteCacheSupport.java:79) at org.infinispan.client.hotrod.retry.ServerFailureRetryTest.testRetryCacheStopped(ServerFailureRetryTest.java:63) {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10113) Cluster description properties should be under `spec` field

by Vittorio Rigamonti (Jira)

[ https://issues.jboss.org/browse/ISPN-10113?page=com.atlassian.jira.plugin... ] Vittorio Rigamonti reopened ISPN-10113: --------------------------------------- This issue refers to the "config" field which should be under spec if we want to consider it part of the desired state of the object. > Cluster description properties should be under `spec` field > ----------------------------------------------------------- > > Key: ISPN-10113 > URL: https://issues.jboss.org/browse/ISPN-10113 > Project: Infinispan > Issue Type: Feature Request > Components: Operator > Affects Versions: 0.2.1 > Reporter: Vittorio Rigamonti > Assignee: Vittorio Rigamonti > Priority: Major > > As specified in [k8s doc|https://github.com/kubernetes/community/blob/master/contributors/deve...] desired status of an object must be under `spec` field. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10118) Add status field to Operator custom resource

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-10118?page=com.atlassian.jira.plugin... ] Galder Zamarreño updated ISPN-10118: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-operator/pull/37 > Add status field to Operator custom resource > -------------------------------------------- > > Key: ISPN-10118 > URL: https://issues.jboss.org/browse/ISPN-10118 > Project: Infinispan > Issue Type: Enhancement > Components: Operator > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Major > > Operator scorecard warning > {code} > SUGGESTION: Add a 'status' field to your Custom Resource > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10118) Add status field to Operator custom resource

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-10118?page=com.atlassian.jira.plugin... ] Galder Zamarreño updated ISPN-10118: ------------------------------------ Status: Open (was: New) > Add status field to Operator custom resource > -------------------------------------------- > > Key: ISPN-10118 > URL: https://issues.jboss.org/browse/ISPN-10118 > Project: Infinispan > Issue Type: Enhancement > Components: Operator > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Major > > Operator scorecard warning > {code} > SUGGESTION: Add a 'status' field to your Custom Resource > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10113) Cluster description properties should be under `spec` field

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-10113?page=com.atlassian.jira.plugin... ] Galder Zamarreño resolved ISPN-10113. ------------------------------------- Resolution: Duplicate Issue > Cluster description properties should be under `spec` field > ----------------------------------------------------------- > > Key: ISPN-10113 > URL: https://issues.jboss.org/browse/ISPN-10113 > Project: Infinispan > Issue Type: Feature Request > Components: Operator > Affects Versions: 0.2.1 > Reporter: Vittorio Rigamonti > Assignee: Vittorio Rigamonti > Priority: Major > > As specified in [k8s doc|https://github.com/kubernetes/community/blob/master/contributors/deve...] desired status of an object must be under `spec` field. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10113) Cluster description properties should be under `spec` field

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-10113?page=com.atlassian.jira.plugin... ] Galder Zamarreño commented on ISPN-10113: ----------------------------------------- This is not completely. An operator is supposed to expose a status object, but that's independent of the `spec` field. This has already been caught by the operator scorecard, see ISPN-10118. > Cluster description properties should be under `spec` field > ----------------------------------------------------------- > > Key: ISPN-10113 > URL: https://issues.jboss.org/browse/ISPN-10113 > Project: Infinispan > Issue Type: Feature Request > Components: Operator > Affects Versions: 0.2.1 > Reporter: Vittorio Rigamonti > Assignee: Vittorio Rigamonti > Priority: Major > > As specified in [k8s doc|https://github.com/kubernetes/community/blob/master/contributors/deve...] desired status of an object must be under `spec` field. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10118) Add status field to Operator custom resource

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-10118?page=com.atlassian.jira.plugin... ] Galder Zamarreño commented on ISPN-10118: ----------------------------------------- Status not shown: {code} $ kubectl get infinispan example-infinispan -n local-operators -o yaml apiVersion: infinispan.org/v1 config: {} kind: Infinispan metadata: ... spec: image: jboss/infinispan-server:latest size: 3 {code} After fix: {code} $ kubectl get infinispan example-infinispan -n local-operators -o yaml apiVersion: infinispan.org/v1 config: {} kind: Infinispan metadata: ... spec: image: jboss/infinispan-server:latest size: 3 status: nodes: - example-infinispan-0 - example-infinispan-1 - example-infinispan-2 {code} > Add status field to Operator custom resource > -------------------------------------------- > > Key: ISPN-10118 > URL: https://issues.jboss.org/browse/ISPN-10118 > Project: Infinispan > Issue Type: Enhancement > Components: Operator > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Major > > Operator scorecard warning > {code} > SUGGESTION: Add a 'status' field to your Custom Resource > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10121) Docs: Spring Boot Dependency

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10121?page=com.atlassian.jira.plugin... ] Donald Naro closed ISPN-10121. ------------------------------ Fix Version/s: (was: 9.4.13.Final) Resolution: Rejected > Docs: Spring Boot Dependency > ---------------------------- > > Key: ISPN-10121 > URL: https://issues.jboss.org/browse/ISPN-10121 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Minor > > This issue affects the RHDG product docs even though the source is in the upstream repo. The downstream docs got out of sync with upstream. > :sb_starter: 1.0.5.Final-redhat-00001 > :sb2_starter: 2.1.3.Final-redhat-00001 > should be: > :sb_starter: 1.0.5.Final-redhat-00002 > :sb2_starter: 2.1.3.Final-redhat-00002 > https://access.redhat.com/documentation/en-us/red_hat_data_grid/7.3/html-... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10122) Unable to start application using Infinispan on Client/Server mode with JMX enabled

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-10122?page=com.atlassian.jira.plugin... ] Katia Aresti updated ISPN-10122: -------------------------------- Status: Open (was: New) > Unable to start application using Infinispan on Client/Server mode with JMX enabled > ----------------------------------------------------------------------------------- > > Key: ISPN-10122 > URL: https://issues.jboss.org/browse/ISPN-10122 > Project: Infinispan > Issue Type: Bug > Components: Spring Integration > Affects Versions: 2.1.4.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > A Spring-Boot application using Infinispan Client/Server with JMX enabled for the Infinispan Client won't start, unless you disable jmx spring.jmx.enabled=false. > Infinispan already registers a bean that is registered by Spring, so we get the following exception on start: > {code} > org.springframework.jmx.export.UnableToRegisterMBeanException: Unable to register MBean [org.infinispan.client.hotrod.RemoteCacheManager@1d67f4e9] with key 'remoteCacheManager'; nested exception is javax.management.InstanceAlreadyExistsException: MXBean already registered with name org.infinispan:type=HotRodClient,name=Default > at org.springframework.jmx.export.MBeanExporter.registerBeanNameOrInstance(MBeanExporter.java:625) ~[spring-context-5.1.6.RELEASE.jar:5.1.6.RELEASE] > at org.springframework.jmx.export.MBeanExporter.lambda$registerBeans$2(MBeanExporter.java:551) ~[spring-context-5.1.6.RELEASE.jar:5.1.6.RELEASE] > at java.base/java.util.HashMap.forEach(HashMap.java:1336) ~[na:na] > at org. > {code} > https://github.com/spring-projects/spring-boot/issues/16482 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2019