[JBoss JIRA] (ISPN-11926) Remote JCacheManager creates two RemoteCacheManager instances
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-11926?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-11926:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/8384
> Remote JCacheManager creates two RemoteCacheManager instances
> -------------------------------------------------------------
>
> Key: ISPN-11926
> URL: https://issues.redhat.com/browse/ISPN-11926
> Project: Infinispan
> Issue Type: Bug
> Components: Hot Rod, JCache
> Affects Versions: 11.0.0.CR1, 10.1.8.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> {{org.infinispan.jcache.remote.JCacheManager}} creates two {{RemoteCacheManager}} instances, one with {{forceReturnValues(false)}} and one with {{forceReturnValues(true)}}. This is wasteful, because each {{RemoteCacheManager}} will create its own server connections and threads.
> It also breaks {{JCache}} listeners when the user explicitly sets the marshaller to {{org.infinispan.commons.marshall.ProtoStreamMarshaller}}, because {{JCacheManager}} registers the {{KeyValueWithPrevious}} marshaller (from {{GlobalContextInitializer}}) in only one of the managers.
> The test suites work by accident:
> * The {{jcache/remote}} test suite doesn't configure a marshaller, instead {{ConfigurationBuilder.build()}} creates a {{ProtostreamMarshaller}} instance (because {{jboss-marshalling}} is not on the classpath) and the next {{Configuration.build()}} call uses **the same {{ProtostreamMarshaller}} instance**, so the {{RemoteCacheManager}}s share the serialization context.
> * The {{jcache/tck-runner-remote}} test suite has {{jboss-marshalling}} on the classpath from the {{server/runtime}} dependency, so it uses {{GenericJBossMarshaller}}.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months
[JBoss JIRA] (ISPN-11932) JCache remote events do not work with ProtostreamMarshaller
by Dan Berindei (Jira)
Dan Berindei created ISPN-11932:
-----------------------------------
Summary: JCache remote events do not work with ProtostreamMarshaller
Key: ISPN-11932
URL: https://issues.redhat.com/browse/ISPN-11932
Project: Infinispan
Issue Type: Bug
Components: Hot Rod, JCache, Marshalling
Affects Versions: 10.1.8.Final, 11.0.0.CR1
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 11.0.0.Final
JCache remote events use {{key-value-with-previous-converter-factory}}, which creates a {{KeyValueWithPrevious}} instance with the key, new value, and old value.
The {{KeyValueWithPrevious}} protostream serialization is broken: the new and old values are both replaced by the key.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months
[JBoss JIRA] (ISPN-11932) JCache remote events do not work with ProtostreamMarshaller
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-11932?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-11932:
--------------------------------
Status: Open (was: New)
> JCache remote events do not work with ProtostreamMarshaller
> -----------------------------------------------------------
>
> Key: ISPN-11932
> URL: https://issues.redhat.com/browse/ISPN-11932
> Project: Infinispan
> Issue Type: Bug
> Components: Hot Rod, JCache, Marshalling
> Affects Versions: 11.0.0.CR1, 10.1.8.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> JCache remote events use {{key-value-with-previous-converter-factory}}, which creates a {{KeyValueWithPrevious}} instance with the key, new value, and old value.
> The {{KeyValueWithPrevious}} protostream serialization is broken: the new and old values are both replaced by the key.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months