[JBoss JIRA] (ISPN-9893) New Reactive API
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-9893?page=com.atlassian.jira.plugin.... ]
Pedro Zapata Fernandez updated ISPN-9893:
-----------------------------------------
Sprint: DataGrid Sprint #29, DataGrid Sprint #30, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #36 (was: DataGrid Sprint #29, DataGrid Sprint #30, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34)
> New Reactive API
> ----------------
>
> Key: ISPN-9893
> URL: https://issues.jboss.org/browse/ISPN-9893
> Project: Infinispan
> Issue Type: Enhancement
> Components: API
> Reporter: Katia Aresti
> Assignee: Katia Aresti
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> See sub-talks. This is an umbrella issue
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-10781) Expose ComponentRef.isAlias()
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-10781?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-10781:
------------------------------------------
Sprint: DataGrid Sprint #35, DataGrid Sprint #36 (was: DataGrid Sprint #35)
> Expose ComponentRef.isAlias()
> -----------------------------
>
> Key: ISPN-10781
> URL: https://issues.jboss.org/browse/ISPN-10781
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Reporter: Nistor Adrian
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> This will help distinguish ComponentRefs whenever we need too. For example JMX registration currently fails (and sadly, the error is hidden due to other problems) because of CacheJmxRegistration attempting to create MBeans twice for the Cache because it encounters two ComponentRefs when scanning the registry. Would be good to know which one is just an alias and ignore it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-10859) Change site status only after failures
by Pedro Ruivo (Jira)
Pedro Ruivo created ISPN-10859:
----------------------------------
Summary: Change site status only after failures
Key: ISPN-10859
URL: https://issues.jboss.org/browse/ISPN-10859
Project: Infinispan
Issue Type: Enhancement
Components: Cross-Site Replication
Affects Versions: 9.4.16.Final, 10.0.0.CR3
Reporter: Pedro Ruivo
Assignee: Pedro Ruivo
Currently, the site status is checked and updates before sending each write request.
However, it would be better to update the site's status only after a failure.
If the cluster becomes idle and the last cross-site requests fail, the site will be taken offline. Changing this, will keep the site online and only updates the status after it sent the request.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (ISPN-10858) Fix Spring Integration in Remote
by Katia Aresti (Jira)
Katia Aresti created ISPN-10858:
-----------------------------------
Summary: Fix Spring Integration in Remote
Key: ISPN-10858
URL: https://issues.jboss.org/browse/ISPN-10858
Project: Infinispan
Issue Type: Bug
Components: Spring Integration
Affects Versions: 10.0.0.Final
Reporter: Katia Aresti
The spring integration in remote needs to add to the white list the `org.infinispan.spring.common.provider.NullValue` class to work properly
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months