[JBoss JIRA] (ISPN-10692) WildFly 18.0.0.Beta1
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10692?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10692:
------------------------------------------
Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> WildFly 18.0.0.Beta1
> --------------------
>
> Key: ISPN-10692
> URL: https://issues.redhat.com/browse/ISPN-10692
> Project: Infinispan
> Issue Type: Component Upgrade
> Components: Build, WildFly modules
> Affects Versions: 10.0.0.CR2
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.CR3
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (ISPN-10672) Server default configs issues
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10672?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10672:
------------------------------------------
Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> Server default configs issues
> -----------------------------
>
> Key: ISPN-10672
> URL: https://issues.redhat.com/browse/ISPN-10672
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.0.0.CR2
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.CR3
>
>
> The default server configuration is affected by the following issues:
> * it does not set the global state shared persistent location
> * they assume that user property files will use plain text password, but the user tool defaults to hashed passwords
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (ISPN-10718) Ensure protobuf metadata cache is predictably started when the cache manager has finished initializing
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10718?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10718:
------------------------------------------
Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> Ensure protobuf metadata cache is predictably started when the cache manager has finished initializing
> ------------------------------------------------------------------------------------------------------
>
> Key: ISPN-10718
> URL: https://issues.redhat.com/browse/ISPN-10718
> Project: Infinispan
> Issue Type: Enhancement
> Components: Remote Querying
> Affects Versions: 10.0.0.CR2
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> Casual code browsing led me to ProtobufMetadataCacheStartedTest where I see we actually assert that protobuf metadata cache is not started on cache manager start, it is actually started lazily, when first non-internal cache starts. And the code is written as if this is a (happy) accident. That's very dangerous. We should start it predictably, when the cache manager has finished startup.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (ISPN-10714) Batch support in the CLI
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10714?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10714:
------------------------------------------
Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> Batch support in the CLI
> ------------------------
>
> Key: ISPN-10714
> URL: https://issues.redhat.com/browse/ISPN-10714
> Project: Infinispan
> Issue Type: Enhancement
> Components: CLI
> Affects Versions: 10.0.0.CR2
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.CR3
>
>
> The CLI should support batch mode
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (ISPN-10707) Jcache: loaded entries should use ExpiryPolicy.getExpiryForCreation()
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10707?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10707:
------------------------------------------
Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> Jcache: loaded entries should use ExpiryPolicy.getExpiryForCreation()
> ---------------------------------------------------------------------
>
> Key: ISPN-10707
> URL: https://issues.redhat.com/browse/ISPN-10707
> Project: Infinispan
> Issue Type: Bug
> Components: Core, JCache
> Affects Versions: 10.0.0.CR2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> {{MVCCEntry.isLoaded()}} is not used in the core, but JCache uses it do decide whether to call {{ExpiryPolicy.getExpiryForCreation()}} or {{ExpiryPolicy.getExpiryForAccess()}}.
> ISPN-8086 accidentally removed the {{ReadCommittedEntry}} implementation along with {{CacheEntry.isLoaded()}}, but the {{CacheExpiryTest}} test failure got ignored because Jenkins ignores the TCK test suite results (ISPN-10379).
> {noformat}
> [OK: 14, KO: 1, SKIP: 0] Test failed: CacheExpiryTest.invokeAllReadThroughEnabledGetOnNonExistentEntry
> java.lang.AssertionError:
> Expected: is <0>
> but: was <5>
> at org.jsr107.tck.expiry.CacheExpiryTest.invokeAllReadThroughEnabledGetOnNonExistentEntry(CacheExpiryTest.java:1202)
> [OK: 15, KO: 2, SKIP: 0] Test failed: CacheExpiryTest.invokeGetValueWithReadThroughForNonExistentEntryShouldCallGetExpiryForCreatedEntry
> java.lang.AssertionError:
> Expected: is <0>
> but: was <1>
> at org.jsr107.tck.expiry.CacheExpiryTest.invokeGetValueWithReadThroughForNonExistentEntryShouldCallGetExpiryForCreatedEntry(CacheExpiryTest.java:1110)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (ISPN-10655) REST operation to return a list of counters
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10655?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10655:
------------------------------------------
Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> REST operation to return a list of counters
> -------------------------------------------
>
> Key: ISPN-10655
> URL: https://issues.redhat.com/browse/ISPN-10655
> Project: Infinispan
> Issue Type: Bug
> Components: Clustered Counter, REST
> Affects Versions: 10.0.0.CR2
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.CR3
>
>
> GET /v2/counters/
> should return a list of available counter names
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (ISPN-10686) JGroups property replacement failure warnings on startup
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-10686?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated ISPN-10686:
------------------------------------------
Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
> JGroups property replacement failure warnings on startup
> --------------------------------------------------------
>
> Key: ISPN-10686
> URL: https://issues.redhat.com/browse/ISPN-10686
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 10.0.0.CR2
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.CR3
>
>
> On startup, Infinispan prints a number of warnings related to property substitutions failing in the built-in JGroups stacks even when they are not being used.
> These should be initialized lazily, so that such substitutions only happen when a stack is effectively initialized.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months