[JBoss JIRA] (ISPN-9402) Upgrade to JGroups 4.0.13.Final
by Katia Aresti (JIRA)
[ https://issues.jboss.org/browse/ISPN-9402?page=com.atlassian.jira.plugin.... ]
Katia Aresti updated ISPN-9402:
-------------------------------
Fix Version/s: 9.4.0.Final
(was: 9.4.0.CR1)
> Upgrade to JGroups 4.0.13.Final
> -------------------------------
>
> Key: ISPN-9402
> URL: https://issues.jboss.org/browse/ISPN-9402
> Project: Infinispan
> Issue Type: Component Upgrade
> Components: Core
> Affects Versions: 9.4.0.Alpha1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 9.4.0.Final
>
>
> Interesting changes in JGroups 4.0.13.Final:
> {quote}
> - Changed the way a coord leaves gracefully (JGRP-2277): instead of creating the last view itself, the leaving coord asks the next-in-line to create and install it. This has the advantage that the new coord can retransmit the view (if lost) as it's stil alive and simplifies code, because the path for graceful leave and crash is now the same.
> - Reactive style of merging (JGRP-2281): when using MERGE3 and TCP, a merge could be only partial and multiple merge rounds would be needed, increasing the total time for a complete merge.
> This was changed by providing a new event which implements a reactive style of discovery by invoking a callback every time a discovery response is received.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 9 months
[JBoss JIRA] (ISPN-9397) Check TX support for remote caches
by Katia Aresti (JIRA)
[ https://issues.jboss.org/browse/ISPN-9397?page=com.atlassian.jira.plugin.... ]
Katia Aresti updated ISPN-9397:
-------------------------------
Fix Version/s: 9.4.0.Final
(was: 9.4.0.CR1)
> Check TX support for remote caches
> ----------------------------------
>
> Key: ISPN-9397
> URL: https://issues.jboss.org/browse/ISPN-9397
> Project: Infinispan
> Issue Type: Bug
> Components: Hot Rod, Remote Protocols, Transactions
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Fix For: 9.4.0.Final
>
>
> The {{RemoteCacheManager.getCache()}} methods would fail to return a transactional cache if the cache in server isn't transactional. It would throw an exception! {{NotTransactionalException}}?
> The user can fallback to the non transaction case, example
> {code:java}
> try {
> cache = remoteCacheManager.getCache("some-cache", TransactionMode.NON_XA);
> } catch(NotTransactionalException e) {
> cache = remoteCacheManager.getCache("some-cache", TransactionMode.NONE);
> }
> {code}
> In addition, some helper method can be added to the {{RemoteCacheManager}} to avoid dealing with exceptions:
> {code:java}
> boolean supportsTransactions(String cacheName);
> {code}
> simple example:
> {code:java}
> boolean txCache = remoteCacheManager.supportsTransactions("some-cache");
> remoteCacheManager.getCache("some-cache", txCache ? TransactionMode.NON_XA : TransactionMode.NONE);
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 9 months
[JBoss JIRA] (ISPN-9369) Non transactional query cache only cache results if transaction is committed
by Katia Aresti (JIRA)
[ https://issues.jboss.org/browse/ISPN-9369?page=com.atlassian.jira.plugin.... ]
Katia Aresti updated ISPN-9369:
-------------------------------
Fix Version/s: (was: 9.4.0.CR1)
> Non transactional query cache only cache results if transaction is committed
> ----------------------------------------------------------------------------
>
> Key: ISPN-9369
> URL: https://issues.jboss.org/browse/ISPN-9369
> Project: Infinispan
> Issue Type: Bug
> Components: Hibernate Cache
> Affects Versions: 9.3.0.Final
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 9.4.0.Final
>
>
> {quote}Local query caches are not populated if the transaction is not committed.
> The same test case works on hibernate 4.3.11
> Our scenario: Read-only services that only execute queries and never commit the transaction. It should still be possible to use/configure hibernate/infinispan to cache the results, regardless the transaction state.{quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 9 months
[JBoss JIRA] (ISPN-9459) Remove compat mode from the Memcached server
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-9459?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-9459:
------------------------------------
Description:
The memcached server makes it hard to enable interoperability with other endpoints, as it stores keys as java.lang.String and treats byte[] as opaque values.
It should respect the cache storage configuration and provide a way to specify what is the data type of the value that clients sends and receive, in order to convert it to/from the storage format.
was:
The memcached server makes it hard to enable interoperability with other endpoints, as it stores keys as java.lang.String and treats byte[] as opaque values.
It should respect the cache storage configuration and provide a way to specify what is the data type of the value that clients sends and receive, in order to convert it to/from the storage format.
> Remove compat mode from the Memcached server
> --------------------------------------------
>
> Key: ISPN-9459
> URL: https://issues.jboss.org/browse/ISPN-9459
> Project: Infinispan
> Issue Type: Sub-task
> Components: Memcached
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> The memcached server makes it hard to enable interoperability with other endpoints, as it stores keys as java.lang.String and treats byte[] as opaque values.
> It should respect the cache storage configuration and provide a way to specify what is the data type of the value that clients sends and receive, in order to convert it to/from the storage format.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 9 months
[JBoss JIRA] (ISPN-9459) Remove compat mode from the Memcached server
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-9459?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-9459:
------------------------------------
Description:
The memcached server makes it hard to enable interoperability with other endpoints, as it stores keys as java.lang.String and treats byte[] as opaque values.
It should respect the cache storage configuration and provide a way to specify what is the data type of the value that clients sends and receive, in order to convert it to/from the storage format.
was:
The memcached server makes it hard to enable interoperability with other endpoints, as it stores keys as java.lang.String and treats byte[] as opaque values.
It should respect the cache configuration storage configuration and provide a way to specify what is the data type of the value that clients sends and receive, in order to convert it to/from the storage format.
> Remove compat mode from the Memcached server
> --------------------------------------------
>
> Key: ISPN-9459
> URL: https://issues.jboss.org/browse/ISPN-9459
> Project: Infinispan
> Issue Type: Sub-task
> Components: Memcached
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> The memcached server makes it hard to enable interoperability with other endpoints, as it stores keys as java.lang.String and treats byte[] as opaque values.
> It should respect the cache storage configuration and provide a way to specify what is the data type of the value that clients sends and receive, in order to convert it to/from the storage format.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 9 months