August 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10504) Deprecate ProtostreamSerializationContextInitializer in favour of SerializationContextInitializer

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10504?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10504: -------------------------------- Status: Open (was: New) > Deprecate ProtostreamSerializationContextInitializer in favour of SerializationContextInitializer > ------------------------------------------------------------------------------------------------- > > Key: ISPN-10504 > URL: https://issues.jboss.org/browse/ISPN-10504 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying > Affects Versions: 10.0.0.Beta5 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.CR1 > > > Now that the protostream library provides the SerializationContextInitializer interface, we should deprecate ProtostreamSerializationContextInitializer and just allow users to provide the former via the ServiceLoader. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10504) Deprecate ProtostreamSerializationContextInitializer in favour of SerializationContextInitializer

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10504?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10504: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7205 > Deprecate ProtostreamSerializationContextInitializer in favour of SerializationContextInitializer > ------------------------------------------------------------------------------------------------- > > Key: ISPN-10504 > URL: https://issues.jboss.org/browse/ISPN-10504 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying > Affects Versions: 10.0.0.Beta5 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.CR1 > > > Now that the protostream library provides the SerializationContextInitializer interface, we should deprecate ProtostreamSerializationContextInitializer and just allow users to provide the former via the ServiceLoader. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10504) Deprecate ProtostreamSerializationContextInitializer in favour of SerializationContextInitializer

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10504?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10504: -------------------------------- Summary: Deprecate ProtostreamSerializationContextInitializer in favour of SerializationContextInitializer (was: Deprecate ProtostreamSerializationContextInitializer in favour SerializationContextInitializer) > Deprecate ProtostreamSerializationContextInitializer in favour of SerializationContextInitializer > ------------------------------------------------------------------------------------------------- > > Key: ISPN-10504 > URL: https://issues.jboss.org/browse/ISPN-10504 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying > Affects Versions: 10.0.0.Beta5 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.CR1 > > > Now that the protostream library provides the SerializationContextInitializer interface, we should deprecate ProtostreamSerializationContextInitializer and just allow users to provide the former via the ServiceLoader. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10504) Deprecate ProtostreamSerializationContextInitializer in favour SerializationContextInitializer

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-10504: ----------------------------------- Summary: Deprecate ProtostreamSerializationContextInitializer in favour SerializationContextInitializer Key: ISPN-10504 URL: https://issues.jboss.org/browse/ISPN-10504 Project: Infinispan Issue Type: Enhancement Components: Remote Querying Affects Versions: 10.0.0.Beta5 Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 10.0.0.CR1 Now that the protostream library provides the SerializationContextInitializer interface, we should deprecate ProtostreamSerializationContextInitializer and just allow users to provide the former via the ServiceLoader. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10500) Remove javassist 3.24.1-GA dependency

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10500?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated ISPN-10500: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Remove javassist 3.24.1-GA dependency > ------------------------------------- > > Key: ISPN-10500 > URL: https://issues.jboss.org/browse/ISPN-10500 > Project: Infinispan > Issue Type: Enhancement > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.CR1 > > > There are two versions used in Infinispan's pom: 3.23.1-GA used by hibernate-search and 3.24.1-GA apparently used by protostream. But protostream is an uberjar that shades that dependency (although it declares it in pom), so this is not really needed. also, in the past javassist was used by the tools modules for RHQ plugin, but this is no longer the case. I'm tempted to try to remove it for good. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10503) jgroups config not getting stack name

by Gustavo Lira e Silva (Jira)

Gustavo Lira e Silva created ISPN-10503: ------------------------------------------- Summary: jgroups config not getting stack name Key: ISPN-10503 URL: https://issues.jboss.org/browse/ISPN-10503 Project: Infinispan Issue Type: Bug Components: Configuration, Server Affects Versions: 10.0.0.Beta5 Reporter: Gustavo Lira e Silva If I use a jgroups configuration like this: {code:xml} <jgroups> <stack-file name='image-tcp' path='jgroups-tcp.xml'/> </jgroups> <cache-container> <transport cluster='infinispan' stack='image-tcp'/> </cache-container> {code} Everything works fine, but I use a configuration like this: {code:xml} xi:include href="server-configuration/jgroups/default-tcp.xml"/> {code} default-tcp.xml file {code:xml} <infinispan xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:infinispan:config:10.0 http://www.infinispan.org/schemas/infinispan-config-10.0.xsd urn:org:jgroups http://www.jgroups.org/schema/jgroups-4.0.xsd" xmlns="urn:infinispan:config:10.0" xmlns:ispn="urn:infinispan:config:10.0"> <jgroups> <stack name="image-tcp"> <MERGE3 min_interval="1000" max_interval="5000"/> <TCP_NIO2 bind_addr="${jgroups.tcp.address:127.0.0.1}" bind_port="${jgroups.tcp.port:7800}" port_range="30" recv_buf_size="20m" send_buf_size="640k" enable_diagnostics="false" bundler_type="no-bundler" thread_naming_pattern="pl" thread_pool.min_threads="0" thread_pool.max_threads="8" thread_pool.keep_alive_time="60000" /> <MPING bind_addr="${jgroups.tcp.address:127.0.0.1}" mcast_addr="${jgroups.mping.mcast_addr:228.2.4.6}" mcast_port="${jgroups.mping.mcast_port:43366}" ip_ttl="${jgroups.udp.ip_ttl:2}" /> </stack> </jgroups> </infinispan> {code} I'm receiving the following exception {noformat} FATAL [org.infinispan.SERVER] (main) Error: org.infinispan.commons.CacheConfigurationException: ISPN000539: Duplicate JGroups stack 'tcp' {noformat} Looks like the *name* attribute of the <stack> are not working as expected -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10502) @TopologyChanged post events fired too soon

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/ISPN-10502?page=com.atlassian.jira.plugin... ] Paul Ferraro closed ISPN-10502. ------------------------------- Resolution: Rejected > @TopologyChanged post events fired too soon > ------------------------------------------- > > Key: ISPN-10502 > URL: https://issues.jboss.org/browse/ISPN-10502 > Project: Infinispan > Issue Type: Bug > Components: State Transfer > Affects Versions: 10.0.0.Beta5, 9.4.16.Final > Reporter: Paul Ferraro > Priority: Critical > > It used to be the case that @TopologyChanged post events were fired after state transfer completes. However, since this commit: > https://github.com/infinispan/infinispan/commit/bbbfda8c5868b6a9f7b1da337... > The event is sent after transfer is initiated instead of when it completes. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10502) @TopologyChanged post events fired too soon

by Paul Ferraro (Jira)

Paul Ferraro created ISPN-10502: ----------------------------------- Summary: @TopologyChanged post events fired too soon Key: ISPN-10502 URL: https://issues.jboss.org/browse/ISPN-10502 Project: Infinispan Issue Type: Bug Components: State Transfer Affects Versions: 9.4.16.Final, 10.0.0.Beta5 Reporter: Paul Ferraro It used to be the case that @TopologyChanged post events were fired after state transfer completes. However, since this commit: https://github.com/infinispan/infinispan/commit/bbbfda8c5868b6a9f7b1da337... The event is sent after transfer is initiated instead of when it completes. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-110) Protostream should not expose dependencies on the artifacts it already includes in the uberjar

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-110?page=com.atlassian.jira.plugin... ] Nistor Adrian updated IPROTO-110: --------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/protostream/pull/79 > Protostream should not expose dependencies on the artifacts it already includes in the uberjar > ---------------------------------------------------------------------------------------------- > > Key: IPROTO-110 > URL: https://issues.jboss.org/browse/IPROTO-110 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.2.3.Final, 4.3.0.Alpha10 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.2.4.Final, 4.3.0.Alpha11 > > > Javassit, protobuf-java, protoparser are such examples. Marking them provide + optional should be nicer -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-110) Protostream should not expose dependencies on the artifacts it already includes in the uberjar

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-110?page=com.atlassian.jira.plugin... ] Nistor Adrian updated IPROTO-110: --------------------------------- Description: Javassist, protobuf-java, protoparser are such examples. Marking them provided + optional should be nicer (was: Javassit, protobuf-java, protoparser are such examples. Marking them provide + optional should be nicer) > Protostream should not expose dependencies on the artifacts it already includes in the uberjar > ---------------------------------------------------------------------------------------------- > > Key: IPROTO-110 > URL: https://issues.jboss.org/browse/IPROTO-110 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.2.3.Final, 4.3.0.Alpha10 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.2.4.Final, 4.3.0.Alpha11 > > > Javassist, protobuf-java, protoparser are such examples. Marking them provided + optional should be nicer -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2019