[JBoss JIRA] (ISPN-10268) Cluster Resource
by Gustavo Fernandes (Jira)
Gustavo Fernandes created ISPN-10268:
----------------------------------------
Summary: Cluster Resource
Key: ISPN-10268
URL: https://issues.jboss.org/browse/ISPN-10268
Project: Infinispan
Issue Type: Sub-task
Components: REST
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
Expose information about the cluster. Currently it is handled by JMX backed by org.infinispan.health.ClusterHealth
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 10 months
[JBoss JIRA] (ISPN-10166) Unnecessary String wrapping when converting to JSON
by Gustavo Fernandes (Jira)
[ https://issues.jboss.org/browse/ISPN-10166?page=com.atlassian.jira.plugin... ]
Gustavo Fernandes commented on ISPN-10166:
------------------------------------------
Could you provide more details? How is the cache configured? Which client is this (Hot rod, node.js)?
> Unnecessary String wrapping when converting to JSON
> ---------------------------------------------------
>
> Key: ISPN-10166
> URL: https://issues.jboss.org/browse/ISPN-10166
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.4.12.Final, 10.0.0.Beta3
> Reporter: Galder Zamarreño
> Assignee: Gustavo Fernandes
> Priority: Major
>
> A client that requests data in JSON format, does not always get data in JSON format.
> When using listener converters, such as "key-value-with-previous-converter-factory", the server must construct an instance of KeyValueWithPrevious in JSON format, but the resulting output looks like this:
> {code}
> { _type : 'org.infinispan.commons.util.KeyValueWithPrevious', key : '{"k":"jlisten-modify"}', value : '{"v":"jv1"}', prev : '{"v":"jv0"}' }
> {code}
> The problem here is that key/value/prev are wrapped in '' which makes them String. This wrapping should not be done.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 10 months
[JBoss JIRA] (ISPN-9919) Partial updates in Hibernate 2L cache upon failure
by Galder Zamarreño (Jira)
[ https://issues.jboss.org/browse/ISPN-9919?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-9919:
-----------------------------------
Fix Version/s: 9.4.15.Final
> Partial updates in Hibernate 2L cache upon failure
> --------------------------------------------------
>
> Key: ISPN-9919
> URL: https://issues.jboss.org/browse/ISPN-9919
> Project: Infinispan
> Issue Type: Bug
> Components: Hibernate Cache
> Affects Versions: 10.0.0.Alpha3, 9.4.6.Final
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Priority: Major
> Fix For: 10.0.0.Final, 9.4.15.Final
>
>
> This issue only affects 5.3:
> For a repl read-write, entity cache, if the failure happens on the async FutureUpdate call, that's fine because the Tombstone has already been sent and the cache won't return anything.
> If the failure happens when the Tombstone is sent, we seem to have a problem because it results in stale data in the node that failed to apply the Tombstone. The FutureUpdate that comes after the Tombstone cannot apply because it doesn't find the Tombstone.
> In 5.3, Sync logs any errors but does not propagate it, so it ends up with inconsistent state.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 10 months