[Red Hat JIRA] (ISPN-12664) Change redirect of login for ok response
by Katia Aresti (Jira)
Katia Aresti created ISPN-12664:
-----------------------------------
Summary: Change redirect of login for ok response
Key: ISPN-12664
URL: https://issues.redhat.com/browse/ISPN-12664
Project: Infinispan
Issue Type: Feature Request
Components: Server
Affects Versions: 12.0.0.Final
Reporter: Katia Aresti
Assignee: Katia Aresti
In order to implement the login with the form, the login must return ok and not a redirect
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 11 months
[Red Hat JIRA] (ISPN-12663) LocalIndexSyncStateTransferTest random failures
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-12663?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-12663:
-------------------------------------
Status: Open (was: New)
> LocalIndexSyncStateTransferTest random failures
> -----------------------------------------------
>
> Key: ISPN-12663
> URL: https://issues.redhat.com/browse/ISPN-12663
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 12.0.0.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> {noformat}
> java.lang.AssertionError: On node LocalIndexSyncStateTransferTest-NodeA index contains 10 entries for entity org.infinispan.query.test.Person, but data container has 8
> at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:226)
> at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:205)
> at org.infinispan.query.blackbox.LocalIndexSyncStateTransferTest.lambda$assertIndexesSynced$2(LocalIndexSyncStateTransferTest.java:54)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 11 months
[Red Hat JIRA] (ISPN-12663) LocalIndexSyncStateTransferTest random failures
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-12663?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-12663:
-------------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/9015
Status: Pull Request Sent (was: Open)
> LocalIndexSyncStateTransferTest random failures
> -----------------------------------------------
>
> Key: ISPN-12663
> URL: https://issues.redhat.com/browse/ISPN-12663
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 12.0.0.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> {noformat}
> java.lang.AssertionError: On node LocalIndexSyncStateTransferTest-NodeA index contains 10 entries for entity org.infinispan.query.test.Person, but data container has 8
> at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:226)
> at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:205)
> at org.infinispan.query.blackbox.LocalIndexSyncStateTransferTest.lambda$assertIndexesSynced$2(LocalIndexSyncStateTransferTest.java:54)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 11 months
[Red Hat JIRA] (ISPN-12663) LocalIndexSyncStateTransferTest random failures
by Gustavo Fernandes (Jira)
Gustavo Fernandes created ISPN-12663:
----------------------------------------
Summary: LocalIndexSyncStateTransferTest random failures
Key: ISPN-12663
URL: https://issues.redhat.com/browse/ISPN-12663
Project: Infinispan
Issue Type: Bug
Components: Embedded Querying
Affects Versions: 12.0.0.Final
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
{noformat}
java.lang.AssertionError: On node LocalIndexSyncStateTransferTest-NodeA index contains 10 entries for entity org.infinispan.query.test.Person, but data container has 8
at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:226)
at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:205)
at org.infinispan.query.blackbox.LocalIndexSyncStateTransferTest.lambda$assertIndexesSynced$2(LocalIndexSyncStateTransferTest.java:54)
{noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 11 months
[Red Hat JIRA] (ISPN-12662) Functional commands break in replicated caches on zero-capacity nodes
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-12662?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-12662:
--------------------------------
Description:
In replicated embedded caches, {{BaseDistributionInterceptor}} on the primary owner sends write commands (including functional write commands) to all the other cache members, using {{RpcManager.invokeCommandOnAll()}}. The write commands will execute on all the cache members, including zero-capacity nodes, and an exception response from any cache member will fail the operation.
Functional commands like {{ReadWriteKeyCommand}} assume they can read the previous value for the affected key on any node where they execute. A zero-capacity node doesn't have the previous value, so it should ignore the command and pretend it was applied, but instead it wraps a {{null}} value in the invocation context and tries to invoke the lambda anyway.
Clustered locks are affected by this issue, but it's hidden because of ISPN-12548.
was:
In replicated embedded caches, {{BaseDistributionInterceptor}} on the primary owner sends write commands (including functional write commands) to all the other cache members, using {{RpcManager.invokeCommandOnAll()}}. The write commands will execute on all the cache members, including zero-capacity nodes, and an exception response from any cache member will fail the operation.
Functional commands like {{ReadWriteKeyCommand}} assume they can read the previous value for the affected key on any node where they execute. A zero-capacity node doesn't have the previous value, so it should ignore the command and pretend it was applied, but instead it wraps a {{null}} value in the invocation context and tries to invoke the lambda anyway.
Clustered locks are affected by this issue, but only after fixing ISPN-12548.
> Functional commands break in replicated caches on zero-capacity nodes
> ---------------------------------------------------------------------
>
> Key: ISPN-12662
> URL: https://issues.redhat.com/browse/ISPN-12662
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 12.0.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 12.1.0.Final, 12.0.1.Final
>
>
> In replicated embedded caches, {{BaseDistributionInterceptor}} on the primary owner sends write commands (including functional write commands) to all the other cache members, using {{RpcManager.invokeCommandOnAll()}}. The write commands will execute on all the cache members, including zero-capacity nodes, and an exception response from any cache member will fail the operation.
> Functional commands like {{ReadWriteKeyCommand}} assume they can read the previous value for the affected key on any node where they execute. A zero-capacity node doesn't have the previous value, so it should ignore the command and pretend it was applied, but instead it wraps a {{null}} value in the invocation context and tries to invoke the lambda anyway.
> Clustered locks are affected by this issue, but it's hidden because of ISPN-12548.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 11 months
[Red Hat JIRA] (ISPN-12662) Functional commands break in replicated caches on zero-capacity nodes
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-12662?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-12662:
--------------------------------
Status: Open (was: New)
> Functional commands break in replicated caches on zero-capacity nodes
> ---------------------------------------------------------------------
>
> Key: ISPN-12662
> URL: https://issues.redhat.com/browse/ISPN-12662
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 12.0.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 12.1.0.Final, 12.0.1.Final
>
>
> In replicated embedded caches, {{BaseDistributionInterceptor}} on the primary owner sends write commands (including functional write commands) to all the other cache members, using {{RpcManager.invokeCommandOnAll()}}. The write commands will execute on all the cache members, including zero-capacity nodes, and an exception response from any cache member will fail the operation.
> Functional commands like {{ReadWriteKeyCommand}} assume they can read the previous value for the affected key on any node where they execute. A zero-capacity node doesn't have the previous value, so it should ignore the command and pretend it was applied, but instead it wraps a {{null}} value in the invocation context and tries to invoke the lambda anyway.
> Clustered locks are affected by this issue, but it's hidden because of ISPN-12548.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 11 months
[Red Hat JIRA] (ISPN-12662) Functional commands break in replicated caches on zero-capacity nodes
by Dan Berindei (Jira)
Dan Berindei created ISPN-12662:
-----------------------------------
Summary: Functional commands break in replicated caches on zero-capacity nodes
Key: ISPN-12662
URL: https://issues.redhat.com/browse/ISPN-12662
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 12.0.0.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 12.1.0.Final, 12.0.1.Final
In replicated embedded caches, {{BaseDistributionInterceptor}} on the primary owner sends write commands (including functional write commands) to all the other cache members, using {{RpcManager.invokeCommandOnAll()}}. The write commands will execute on all the cache members, including zero-capacity nodes, and an exception response from any cache member will fail the operation.
Functional commands like {{ReadWriteKeyCommand}} assume they can read the previous value for the affected key on any node where they execute. A zero-capacity node doesn't have the previous value, so it should ignore the command and pretend it was applied, but instead it wraps a {{null}} value in the invocation context and tries to invoke the lambda anyway.
Clustered locks are affected by this issue, but only after fixing ISPN-12548.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 11 months
[Red Hat JIRA] (ISPN-12661) Licenses are not properly generated in console
by Pedro Ruivo (Jira)
[ https://issues.redhat.com/browse/ISPN-12661?page=com.atlassian.jira.plugi... ]
Pedro Ruivo updated ISPN-12661:
-------------------------------
Status: Open (was: New)
> Licenses are not properly generated in console
> ----------------------------------------------
>
> Key: ISPN-12661
> URL: https://issues.redhat.com/browse/ISPN-12661
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 11.0.9.Final, 12.0.0.Final
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 11.0.10.Final, 12.0.1.Final
>
>
> The {{license-reporter}} needs to have {{node}} executable available in PATH.
> It isn't the case for CI & PNC and the build process does not include the {{licenses-console.xml}}.
> It must use the {{node}} executable downloaded by the frontend-plugin
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 11 months
[Red Hat JIRA] (ISPN-12661) Licenses are not properly generated in console
by Pedro Ruivo (Jira)
Pedro Ruivo created ISPN-12661:
----------------------------------
Summary: Licenses are not properly generated in console
Key: ISPN-12661
URL: https://issues.redhat.com/browse/ISPN-12661
Project: Infinispan
Issue Type: Bug
Components: Console
Affects Versions: 12.0.0.Final, 11.0.9.Final
Reporter: Pedro Ruivo
Assignee: Pedro Ruivo
Fix For: 11.0.10.Final, 12.0.1.Final
The {{license-reporter}} needs to have {{node}} executable available in PATH.
It isn't the case for CI & PNC and the build process does not include the {{licenses-console.xml}}.
It must use the {{node}} executable downloaded by the frontend-plugin
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 11 months