November 2019 - infinispan-issues

[JBoss JIRA] (ISPN-10819) GracefulShutdownRestartIT Failure

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10819?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10819: ----------------------------------- Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #35, DataGrid Sprint #36) > GracefulShutdownRestartIT Failure > --------------------------------- > > Key: ISPN-10819 > URL: https://issues.jboss.org/browse/ISPN-10819 > Project: Infinispan > Issue Type: Bug > Components: Server, Test Suite > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Final > > > The GlobalMarshaller is unable to marshall {{Server.ShutdownRunnable}} as it does not have an externalizer defined. This wasn't an issue when jboss-marshalling was used in the Server as the class was marshalled via Serialization, however now that the default user marshaller is Protostream based this is not possible. The solution is to enable the GlobalMarshaller to be able to marshall the class directly. This can be achieved by defining an Externalizer for the class. > {code:java}_emphasized text_ > [0] STDOUT: 19:05:14,244 WARN [org.infinispan.PERSISTENCE] (SINGLE_PORT-ServerIO-7-2) ISPN000559: Cannot marshall 'class org.infinispan.server.Server$ShutdownRunnable': java.lang.IllegalArgumentException: No marshaller registered for Java type org.infinispan.server.Server$ShutdownRunnable > [0] STDOUT: at org.infinispan.protostream.impl.SerializationContextImpl.getMarshallerDelegate(SerializationContextImpl.java:279) > [0] STDOUT: at org.infinispan.protostream.WrappedMessage.writeMessage(WrappedMessage.java:240) > [0] STDOUT: at org.infinispan.protostream.ProtobufUtil.toWrappedStream(ProtobufUtil.java:196) > [0] STDOUT: at org.infinispan.marshall.persistence.impl.PersistenceMarshallerImpl.objectToBuffer(PersistenceMarshallerImpl.java:157) > [0] STDOUT: at org.infinispan.marshall.persistence.impl.PersistenceMarshallerImpl.objectToByteBuffer(PersistenceMarshallerImpl.java:137) > [0] STDOUT: at org.infinispan.marshall.persistence.impl.PersistenceMarshallerImpl.objectToByteBuffer(PersistenceMarshallerImpl.java:145) > [0] STDOUT: at org.infinispan.marshall.core.GlobalMarshaller.writeRawUnknown(GlobalMarshaller.java:638) > [0] STDOUT: at org.infinispan.marshall.core.GlobalMarshaller.writeUnknown(GlobalMarshaller.java:627) > [0] STDOUT: at org.infinispan.marshall.core.GlobalMarshaller.writeUnknown(GlobalMarshaller.java:618) > [0] STDOUT: at org.infinispan.marshall.core.GlobalMarshaller.writeNonNullableObject(GlobalMarshaller.java:384) > [0] STDOUT: at org.infinispan.marshall.core.GlobalMarshaller.writeNullableObject(GlobalMarshaller.java:352) > [0] STDOUT: at org.infinispan.marshall.core.BytesObjectOutput.writeObject(BytesObjectOutput.java:26) > [0] STDOUT: at org.infinispan.manager.impl.ReplicableManagerFunctionCommand.writeTo(ReplicableManagerFunctionCommand.java:54) > [0] STDOUT: at org.infinispan.marshall.exts.ReplicableCommandExternalizer.writeCommandParameters(ReplicableCommandExternalizer.java:70) > [0] STDOUT: at org.infinispan.marshall.exts.ReplicableCommandExternalizer.writeObject(ReplicableCommandExternalizer.java:66) > [0] STDOUT: at org.infinispan.marshall.exts.ReplicableCommandExternalizer.writeObject(ReplicableCommandExternalizer.java:54) > [0] STDOUT: at org.infinispan.marshall.core.GlobalMarshaller.writeInternal(GlobalMarshaller.java:656) > [0] STDOUT: at org.infinispan.marshall.core.GlobalMarshaller.writeNonNullableObject(GlobalMarshaller.java:371) > [0] STDOUT: at org.infinispan.marshall.core.GlobalMarshaller.writeNullableObject(GlobalMarshaller.java:352) > [0] STDOUT: at org.infinispan.marshall.core.GlobalMarshaller.writeObjectOutput(GlobalMarshaller.java:181) > [0] STDOUT: at org.infinispan.marshall.core.GlobalMarshaller.writeObjectOutput(GlobalMarshaller.java:174) > [0] STDOUT: at org.infinispan.marshall.core.GlobalMarshaller.objectToBuffer(GlobalMarshaller.java:302)+underlined text+ > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10824) Hanged tests are ignored by Jenkins

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10824?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10824: ----------------------------------- Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #35, DataGrid Sprint #36) > Hanged tests are ignored by Jenkins > ----------------------------------- > > Key: ISPN-10824 > URL: https://issues.jboss.org/browse/ISPN-10824 > Project: Infinispan > Issue Type: Bug > Components: Build, Test Suite > Affects Versions: 9.4.16.Final, 10.0.0.CR3 > Reporter: dan.berindei > Assignee: dan.berindei > Priority: Major > Fix For: 10.0.0.Final > > > ISPN-10161 was supposed to add a custom JUnit report in {{RunningTestsRegistry}} just before killing the JVM. Unfortunately it only calls {{TestSuiteProgress.fakeTestFailure()}}, which sounds like it should do it, but actually only writes a {{Test failed:}} messsage to the console, which Jenkins ignores. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10821) Decrease GMS join_timeout and increase xPING num_discovery_runs

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10821?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10821: ----------------------------------- Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #35, DataGrid Sprint #36) > Decrease GMS join_timeout and increase xPING num_discovery_runs > --------------------------------------------------------------- > > Key: ISPN-10821 > URL: https://issues.jboss.org/browse/ISPN-10821 > Project: Infinispan > Issue Type: Task > Components: Configuration > Affects Versions: 9.4.16.Final, 10.0.0.CR3 > Reporter: dan.berindei > Assignee: dan.berindei > Priority: Major > Fix For: 10.0.0.Final > > > Our default JGroups configurations have a GMS {{join_timeout="5000"}}, meaning the first node to start will always wait for 5 seconds before becoming coordinator. It should be safe to use the JGroups default of 2 seconds. > To make it even more safe, we could configure the discovery protocol's {{num_discovery_runs="3"}}, so that it makes multiple attempts to contact existing nodes during those 2 seconds of waiting. {{num_discovery_runs}} is only used for the initial discovery, so there's no danger of creating additional traffic while the node is up. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10820) Upgrade to JGroups 4.1.6.Final

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10820?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10820: ----------------------------------- Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #35, DataGrid Sprint #36) > Upgrade to JGroups 4.1.6.Final > ------------------------------ > > Key: ISPN-10820 > URL: https://issues.jboss.org/browse/ISPN-10820 > Project: Infinispan > Issue Type: Component Upgrade > Components: Dependency > Affects Versions: 10.0.0.CR3 > Reporter: dan.berindei > Assignee: dan.berindei > Priority: Major > Fix For: 10.0.0.Final > > > [4.1.5.Final|https://issues.jboss.org/projects/JGRP/versions/12342765] added support for UDP and PING on Quarkus and fixed some issues with LOCAL_PING > [4.1.6.Final|https://issues.jboss.org/projects/JGRP/versions/12342864] fixes a recurring warning message from FD_ALL -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10804) JCache tck-runner does not run interception tests

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10804?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10804: ----------------------------------- Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #35, DataGrid Sprint #36) > JCache tck-runner does not run interception tests > ------------------------------------------------- > > Key: ISPN-10804 > URL: https://issues.jboss.org/browse/ISPN-10804 > Project: Infinispan > Issue Type: Bug > Components: JCache, Test Suite > Affects Versions: 9.4.16.Final, 10.0.0.CR3 > Reporter: dan.berindei > Assignee: dan.berindei > Priority: Major > Fix For: 10.1.0.Final > > > Initially I thought the only way to make the interception TCK tests run was to add a {{@Priority}} annotation, which is not a good idea because even our tests expect to be able to switch between the managed or the managed interceptors. > But it turns out if we revert ISPN-10721 and unpack the TCK tests in our build output directory, we can override {{beans.xml}} and make the interception tests run. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10798) JCache annotations attribute cacheResolverFactory is ignored

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10798?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10798: ----------------------------------- Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #35, DataGrid Sprint #36) > JCache annotations attribute cacheResolverFactory is ignored > ------------------------------------------------------------ > > Key: ISPN-10798 > URL: https://issues.jboss.org/browse/ISPN-10798 > Project: Infinispan > Issue Type: Bug > Components: JCache > Affects Versions: 9.4.16.Final, 10.0.0.CR3 > Reporter: dan.berindei > Assignee: dan.berindei > Priority: Major > Fix For: 10.1.0.Final > > > The JCache TCK doesn't seem to require support for {{cacheResolverFactory}}, but having it would allow us to have an alternative to the managed interceptors {{InjectedCache*Interceptor}} and to deprecate them. > We can then move the default interceptors to the jcache-commons module, so they support both embedded and remote caches. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10759) Upgrade to WildFly 18.0.0.Final

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10759?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10759: ----------------------------------- Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #35, DataGrid Sprint #36) > Upgrade to WildFly 18.0.0.Final > ------------------------------- > > Key: ISPN-10759 > URL: https://issues.jboss.org/browse/ISPN-10759 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10764) Clustered Graceful Shutdown for server

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10764?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10764: ----------------------------------- Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #35, DataGrid Sprint #36) > Clustered Graceful Shutdown for server > -------------------------------------- > > Key: ISPN-10764 > URL: https://issues.jboss.org/browse/ISPN-10764 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 10.0.0.CR3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Final > > > * Allow the server to shutdown any other node as well as the whole cluster > * Add REST APIs for specific node shutdown and clustered shutdown > * Add corresponding CLI commands -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10774) kill-server Ant task kills clients too

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10774?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10774: ----------------------------------- Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #35, DataGrid Sprint #36) > kill-server Ant task kills clients too > -------------------------------------- > > Key: ISPN-10774 > URL: https://issues.jboss.org/browse/ISPN-10774 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 10.0.0.CR3 > Reporter: dan.berindei > Assignee: dan.berindei > Priority: Major > Fix For: 10.0.0.Final > > > {{kill-server}} uses multiple sources to find the pid of the running server(s), among them {{lsof}} to find processes listening on the HotRod port. > The {{lsof}} command line is imprecise and it also finds clients that have leaked a connection to the server, killing the failsafe fork too early and preventing failsafe from reporting the test results. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10779) RestConnectorTest.testUrlWithSSL failure

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10779?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10779: ----------------------------------- Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #35, DataGrid Sprint #36) > RestConnectorTest.testUrlWithSSL failure > ---------------------------------------- > > Key: ISPN-10779 > URL: https://issues.jboss.org/browse/ISPN-10779 > Project: Infinispan > Issue Type: Bug > Components: CLI > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Final > > > IllegalStateException thrown by SSLConfigurationBuilder::validate as no TrustManager set -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2019