[JBoss JIRA] (ISPN-10489) Deploy ServerNG distribution zip with SNAPSHOT builds
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10489?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10489:
-----------------------------------
Sprint: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36)
> Deploy ServerNG distribution zip with SNAPSHOT builds
> -----------------------------------------------------
>
> Key: ISPN-10489
> URL: https://issues.jboss.org/browse/ISPN-10489
> Project: Infinispan
> Issue Type: Enhancement
> Components: Build
> Affects Versions: 10.0.0.Beta5
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.CR1
>
>
> In order to facilitate nightly builds of the infinispan image, it's necessary for the ServerNG zip to be deployed as part of our snapshot releases.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10500) Remove javassist 3.24.1-GA dependency
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10500?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10500:
-----------------------------------
Sprint: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36)
> 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.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10504) Deprecate ProtostreamSerializationContextInitializer in favour of SerializationContextInitializer
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10504?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10504:
-----------------------------------
Sprint: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36)
> 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.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10520) Move Version class to commons
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10520?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10520:
-----------------------------------
Sprint: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36)
> Move Version class to commons
> -----------------------------
>
> Key: ISPN-10520
> URL: https://issues.jboss.org/browse/ISPN-10520
> Project: Infinispan
> Issue Type: Task
> Components: Core
> Affects Versions: 10.0.0.CR1
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.CR2
>
>
> The Version class should be moved to commons so that it can be used by the client as well.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10528) Server cannot start when authorization is enabled
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10528?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10528:
-----------------------------------
Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36)
> Server cannot start when authorization is enabled
> -------------------------------------------------
>
> Key: ISPN-10528
> URL: https://issues.jboss.org/browse/ISPN-10528
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.0.0.CR1
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.CR2
>
>
> The cachemanager and protocolserver start/stop calls must be wrapped in security actions.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10529) Netty 4.1.39
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10529?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10529:
-----------------------------------
Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36)
> Netty 4.1.39
> ------------
>
> Key: ISPN-10529
> URL: https://issues.jboss.org/browse/ISPN-10529
> Project: Infinispan
> Issue Type: Component Upgrade
> Components: Server
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.CR2, 9.4.17.Final
>
>
> Upgrade to Netty 4.1.39
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10422) Deprecate MediaType::parse in favour of MediaType::fromString
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10422?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10422:
-----------------------------------
Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36)
> Deprecate MediaType::parse in favour of MediaType::fromString
> -------------------------------------------------------------
>
> Key: ISPN-10422
> URL: https://issues.jboss.org/browse/ISPN-10422
> Project: Infinispan
> Issue Type: Enhancement
> Components: API
> Affects Versions: 10.0.0.Beta4
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta5
>
>
> Currently {{org.infinispan.commons.dataconversion.MediaType}} exposes both {{fromString}} and {{parse}} methods to create an instance from a String. We should deprecate the latter in favour of the former and update all internal code references.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10419) RocksDB purge should not utilise ArrayList to store multiple expired keys
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10419?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10419:
-----------------------------------
Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36)
> RocksDB purge should not utilise ArrayList to store multiple expired keys
> -------------------------------------------------------------------------
>
> Key: ISPN-10419
> URL: https://issues.jboss.org/browse/ISPN-10419
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores
> Affects Versions: 10.0.0.Beta4
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.CR1
>
>
> Currently the RocksDB purge method stores multiple keys that expire at the same time in a ArrayList associated with the expiry time. This is currently marshallable because ArrayList is serializable and we utilise Jboss-marshalling, however ISPN-10354 means this is no longer possible in embedded mode when `infinispan-jboss-marshalling` is not present. Therefore, we should create a `ExpiryBucket` that can be marshalled via the persistence marshaller i.e. protobuf based.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10423) RocksDB ReadOptions memory leak
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10423?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10423:
-----------------------------------
Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36)
> RocksDB ReadOptions memory leak
> -------------------------------
>
> Key: ISPN-10423
> URL: https://issues.jboss.org/browse/ISPN-10423
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 10.0.0.Beta4, 9.4.15.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta5, 9.4.16.Final
>
>
> Currently our rocksdb store impl creates a new ReadOptions instance per iterator created. As per the RocksDB we should be calling {{dispose()}} on this once it goes out of scope, so that the c++ underlying impl can free the memory. Currently we're not doing this, resulting in a memory leak.
> As we only ever use the same ReadOptions for all iterators, we should simply re-use a singleton for all iterators and then dispose of this on shutdown.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months