[JBoss JIRA] (ISPN-12177) Persist IRAC version during shutdown
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12177?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12177:
-----------------------------------
Sprint: DataGrid Sprint #47, DataGrid Sprint #48, DataGrid Sprint #49 (was: DataGrid Sprint #47, DataGrid Sprint #48)
> Persist IRAC version during shutdown
> ------------------------------------
>
> Key: ISPN-12177
> URL: https://issues.redhat.com/browse/ISPN-12177
> Project: Infinispan
> Issue Type: Bug
> Components: Cross-Site Replication
> Affects Versions: 11.0.1.Final
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> The IRAC version is reset after a complete shutdown. It should be persisted in the global state to avoid unnecessary conflicts and/or data inconsistency.
> If the global state is disabled, the users have to deal with it.
> Also, make it possible to "compute" the version if the data is persisted and when receiving state from the remote site.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (ISPN-12184) Implicit authentication config stomps on explicit config
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12184?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12184:
-----------------------------------
Sprint: DataGrid Sprint #47, DataGrid Sprint #48, DataGrid Sprint #49 (was: DataGrid Sprint #47, DataGrid Sprint #48)
> Implicit authentication config stomps on explicit config
> --------------------------------------------------------
>
> Key: ISPN-12184
> URL: https://issues.redhat.com/browse/ISPN-12184
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration, Server
> Affects Versions: 12.0.0.Dev01
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 12.0.0.Dev04
>
>
> The server overwrites any explicit security configuration set on the individual protocols, including realm and mechanisms.
> If these are set explicitly, they should be respected.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (IPROTO-144) Upgrade to log4j2 ver. 2.13.2 and make it a test dependency only
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/IPROTO-144?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated IPROTO-144:
-----------------------------------
Sprint: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48, DataGrid Sprint #49 (was: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48)
> Upgrade to log4j2 ver. 2.13.2 and make it a test dependency only
> ----------------------------------------------------------------
>
> Key: IPROTO-144
> URL: https://issues.redhat.com/browse/IPROTO-144
> Project: Infinispan ProtoStream
> Issue Type: Component Upgrade
> Affects Versions: 4.3.3.Final
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 4.4.0.Alpha1, 4.3.4.Final
>
>
> The real logging dependency is on jboss logging, log4j is just a back end that does not need to be exposed. Also, we need to upgrade to log4j2.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (ISPN-12261) Protocol server transport management
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12261?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12261:
-----------------------------------
Sprint: DataGrid Sprint #48, DataGrid Sprint #49 (was: DataGrid Sprint #48)
> Protocol server transport management
> -------------------------------------
>
> Key: ISPN-12261
> URL: https://issues.redhat.com/browse/ISPN-12261
> Project: Infinispan
> Issue Type: Feature Request
> Components: CLI, JMX, reporting and management, Server
> Affects Versions: 12.0.0.Dev02
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 12.0.0.Dev04
>
>
> the WF-server had the ability to stop/start a transport via the CLI (ISPN-11240).
> The new server should have a similar capability.
> Aside from start/stop, we should also leverage netty's ipfilter handler which allows filtering based on subnet so that traffic can be blocked selectively.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (ISPN-12005) Store purge should ignore errors
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12005?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12005:
-----------------------------------
Sprint: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48, DataGrid Sprint #49 (was: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48)
> Store purge should ignore errors
> --------------------------------
>
> Key: ISPN-12005
> URL: https://issues.redhat.com/browse/ISPN-12005
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Loaders and Stores
> Affects Versions: 10.1.5.Final, 11.0.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 12.0.0.Final, 11.0.4.Final
>
>
> Purging of expired entries from stores is a pretty involved process, especially with {{RocksDBStore}}. When there's a problem unmarshalling the expired bucket or deleting an expired key, the purge task bails out immediately, without processing the remaining keys. To make matters worse, the exception it not logged anywhere. The only sign that something is wrong is a growing store (in the case of {{RocksDBStore}}, a growing number of SST files).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (ISPN-11978) Java ScriptEngine
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11978?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11978:
-----------------------------------
Sprint: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48, DataGrid Sprint #49 (was: DataGrid Sprint #46, DataGrid Sprint #47, DataGrid Sprint #48)
> Java ScriptEngine
> -----------------
>
> Key: ISPN-11978
> URL: https://issues.redhat.com/browse/ISPN-11978
> Project: Infinispan
> Issue Type: Enhancement
> Components: Tasks
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> Since Java 11 the Nashorn script engine has been deprecated and marked for removal.
> We can use either the Java compiler API or JShell to implement a ScriptEngine for Java.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months