[JBoss JIRA] (ISPN-12202) Invalidation Cache with a shared store doesn't work properly after new SPI changes
by Pedro Ruivo (Jira)
Pedro Ruivo created ISPN-12202:
----------------------------------
Summary: Invalidation Cache with a shared store doesn't work properly after new SPI changes
Key: ISPN-12202
URL: https://issues.redhat.com/browse/ISPN-12202
Project: Infinispan
Issue Type: Bug
Components: Core, Loaders and Stores
Affects Versions: 11.0.1.Final
Reporter: Paul Ferraro
Assignee: Will Burns
Fix For: 12.0.0.Final, 11.0.3.Final
There seems to be something amiss with the new NonBlockingStore changes. When a transactional invalidation cache is used with a shared cache store, I've observed the entries published to the removePublisher of the NonBlockStore.batch(...) which should have targeted the writePublisher. This seems to happen when a batch only contains writes, but no removes.
See the attached test to reproduce the issue, which executes two simple cache operations against a transactional vs non-transactional cache using a shared write-through store. The transactional version fails due to unexpected removals triggered by the batch(...) method (which, in the case of the JDBC store delegates to the deleteBatch(...) and bulkUpdate(...) methods. TRACE logging indicates that entries are unexpectedly published to the removePublisher of batch(...) when transactions are enabled causing entries to be removed unexpectedly from the store (as the result of a Cache.put(...)). When tx are disabled, the batch(...) method is, of course, not in play, and everything works correctly via the individual write/delete methods.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months
[JBoss JIRA] (ISPN-12201) Cache creation wizard
by Katia Aresti (Jira)
Katia Aresti created ISPN-12201:
-----------------------------------
Summary: Cache creation wizard
Key: ISPN-12201
URL: https://issues.redhat.com/browse/ISPN-12201
Project: Infinispan
Issue Type: Enhancement
Components: Console
Affects Versions: 12.0.0.Dev01
Reporter: Katia Aresti
Assignee: Katia Aresti
Create a wizard that creates a cache.
Chose:
* name
* marshaller
* transaction
* indexation
* xsite
* memory
* ...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months
[JBoss JIRA] (ISPN-11851) FD_SOCK should use the same bind address as TCP
by Pedro Ruivo (Jira)
[ https://issues.redhat.com/browse/ISPN-11851?page=com.atlassian.jira.plugi... ]
Pedro Ruivo updated ISPN-11851:
-------------------------------
Fix Version/s: 11.0.3.Final
(was: 11.0.2.Final)
> FD_SOCK should use the same bind address as TCP
> -----------------------------------------------
>
> Key: ISPN-11851
> URL: https://issues.redhat.com/browse/ISPN-11851
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration, Core
> Affects Versions: 11.0.0.Dev05, 10.1.8.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.3.Final
>
>
> In the JGroups configuration files we ship, we use a different default for {{TCP.bind_addr}} and {{UDP.bind_addr}} than JGroups does.
> {code:xml}
> <TCP bind_addr="${jgroups.bind.address,jgroups.tcp.address:SITE_LOCAL}"/>
> <UDP bind_addr="${jgroups.bind.address,jgroups.udp.address:SITE_LOCAL}"/>
> {code}
> However, we didn't change the default for {{FD_SOCK}}, so it uses the JGroups default:
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months