November 2019 - infinispan-issues

[JBoss JIRA] (ISPN-10833) Client ProtoStreamMarshaller intitialization should happen on RemoteCacheManager start

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10833?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10833: ----------------------------------- Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #35, DataGrid Sprint #36) > Client ProtoStreamMarshaller intitialization should happen on RemoteCacheManager start > -------------------------------------------------------------------------------------- > > Key: ISPN-10833 > URL: https://issues.jboss.org/browse/ISPN-10833 > Project: Infinispan > Issue Type: Bug > Components: CLI, Hot Rod > Affects Versions: 10.0.0.CR3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Final > > > Currently intiialisation happens in the ConfigurationBuilder::create method, however this should be delayed until the RemoteCacheManager startsup. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10834) Client ConfigurationBuilder contextInitializer methods should be consistent with core

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10834?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10834: ----------------------------------- Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #35, DataGrid Sprint #36) > Client ConfigurationBuilder contextInitializer methods should be consistent with core > ------------------------------------------------------------------------------------- > > Key: ISPN-10834 > URL: https://issues.jboss.org/browse/ISPN-10834 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 10.0.0.CR3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Final > > > Currently the client ConfigurationBuilder uses ConfigurationBuilder::contextInitializer whereas core uses ConfigurationBuilder::addContextInitializer. We should make these the same for consistency. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10848) Change site status only after failures

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10848?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10848: ----------------------------------- Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36) > Change site status only after failures > --------------------------------------- > > Key: ISPN-10848 > URL: https://issues.jboss.org/browse/ISPN-10848 > Project: Infinispan > Issue Type: Enhancement > Components: Cross-Site Replication > Affects Versions: 9.4.16.Final, 10.0.0.CR3 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.1.0.Beta1 > > > Currently, the site status is checked and updates before sending each write request. > However, it would be better to update the site's status only after a failure. > If the cluster becomes idle and the last cross-site requests fail, the site will be taken offline. Changing this, will keep the site online and only updates the status after it sent the request. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10602) Lazily register clustered listener for counters

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10602?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10602: ----------------------------------- Sprint: DataGrid Sprint #34, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #34, DataGrid Sprint #36) > Lazily register clustered listener for counters > ----------------------------------------------- > > Key: ISPN-10602 > URL: https://issues.jboss.org/browse/ISPN-10602 > Project: Infinispan > Issue Type: Enhancement > Components: Clustered Counter > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.1.0.Final > > > We can register the clustered-listeners only when needed instead of eagerly. Should save some resources in our test suite too. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9394) Getting java.lang.ClassCastException after calling XSiteAdmin.status()

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9394?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9394: ---------------------------------- Sprint: DataGrid Sprint #34, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #34, DataGrid Sprint #36) > Getting java.lang.ClassCastException after calling XSiteAdmin.status() > ---------------------------------------------------------------------- > > Key: ISPN-9394 > URL: https://issues.jboss.org/browse/ISPN-9394 > Project: Infinispan > Issue Type: Bug > Components: Cross-Site Replication > Reporter: Jared Blashka > Assignee: Pedro Ruivo > Priority: Minor > Fix For: 10.1.0.Beta1 > > Attachments: clustered.xml > > > I've got a cross-site cluster set up with 4 hosts (a,b) <-> (c,d). If I stop a particular cache on 'a' and then call XSiteAdmin.status() for that cache on 'b' I get "java.lang.ClassCastException: org.infinispan.remoting.responses.CacheNotFoundResponse cannot be cast to org.infinispan.remoting.responses.SuccessfulResponse". > XSiteAdmin.status() still works without any issues on 'c' and 'd' however -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10855) MultipleCacheManagersTest factory issues are ignored

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10855?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10855: ----------------------------------- Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #35, DataGrid Sprint #36) > MultipleCacheManagersTest factory issues are ignored > ---------------------------------------------------- > > Key: ISPN-10855 > URL: https://issues.jboss.org/browse/ISPN-10855 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 9.4.16.Final, 10.0.0.Final > Reporter: dan.berindei > Assignee: dan.berindei > Priority: Major > Fix For: 10.1.0.Beta1 > > > TestNG doesn't like exceptions being thrown from {{@Factory}} methods, so when {{MultipleCacheManager.defaultFactory()}} finds a problem with the concrete {{factory()}} implementation or with the annotations it replaces the test instance with a {{TestFrameworkFailure}}. > Turns out that doesn't actually work: TestNG ignores the {{TestFrameworkFailure}} instance and runs the tests on a "default instance" of the test class. This is ok when the problem is the concrete class didn't override {{factory()}} and very likely the test author wanted a single test instance, but it's not ok for other errors like {{factory()}} being copy-pasted from super with the wrong class name. > We can make TestNG report our factory failures if we implement {{IInstanceInfo}} and mock all the test/configuration methods to throw our exception. We just need to make all configuration methods non-final so we can mock them. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10806) Default semantic configurations for the server

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10806?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10806: ----------------------------------- Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #35, DataGrid Sprint #36) > Default semantic configurations for the server > ---------------------------------------------- > > Key: ISPN-10806 > URL: https://issues.jboss.org/browse/ISPN-10806 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Server > Affects Versions: 10.0.0.CR3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.0.Final > > > org.infinispan.VOLATILE (same as DIST_SYNC) > org.infinispan.PERSISTENT (VOLATILE + soft index store) > org.infinispan.INDEXED (PERSISTENT + indexed) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10807) Don't include Narayana in the server

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10807?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10807: ----------------------------------- Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #35, DataGrid Sprint #36) > Don't include Narayana in the server > ------------------------------------ > > Key: ISPN-10807 > URL: https://issues.jboss.org/browse/ISPN-10807 > Project: Infinispan > Issue Type: Feature Request > Components: Server, Transactions > Affects Versions: 10.0.0.CR3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Final > > > The Hot Rod tx implementation uses the embedded TM only. Including Narayana in the server distribution is therefore pointless. It should be removed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10815) Javadoc missing jboss-marshalling dependency

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10815?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10815: ----------------------------------- Sprint: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #35, DataGrid Sprint #36) > Javadoc missing jboss-marshalling dependency > -------------------------------------------- > > Key: ISPN-10815 > URL: https://issues.jboss.org/browse/ISPN-10815 > Project: Infinispan > Issue Type: Bug > Components: Documentation > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Final > > > Caused by ISPN-10591 which removed the {{infinispan-jboss-marshalling}} dependency from the persistence-remote jar, which was transitively pulling in the dependency to the documentation module. > The solution is to add an explicit dependency on {{infinispan-jboss-marshalling}} to the javadoc pom. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[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)

6 years, 4 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 November 2019