[JBoss JIRA] (ISPN-11140) RemoteCache w/near cache throws InstanceAlreadyExistsException following restart
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-11140?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-11140:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 10.1.1.Final
Resolution: Done
> RemoteCache w/near cache throws InstanceAlreadyExistsException following restart
> --------------------------------------------------------------------------------
>
> Key: ISPN-11140
> URL: https://issues.redhat.com/browse/ISPN-11140
> Project: Infinispan
> Issue Type: Bug
> Components: Hot Rod
> Affects Versions: 10.1.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Critical
> Fix For: 10.1.1.Final
>
>
> A RemoteCache using a near cache throws javax.management.InstanceAlreadyExistsException on restart. RemoteCache w/out a near cache restarts without issue.
> This is because InvalidatedNearRemoteCache.stop() does not call the super implementation, which unregisters its mbeans.
> This issue technically affects older versions, but the allowDuplicateDomains logic circumvents the InstanceAlreadyExistsException problem.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months
[JBoss JIRA] (ISPN-11132) Data not indexed during state transfer in server mode
by Nistor Adrian (Jira)
[ https://issues.redhat.com/browse/ISPN-11132?page=com.atlassian.jira.plugi... ]
Nistor Adrian updated ISPN-11132:
---------------------------------
Fix Version/s: 9.4.18.Final
> Data not indexed during state transfer in server mode
> -----------------------------------------------------
>
> Key: ISPN-11132
> URL: https://issues.redhat.com/browse/ISPN-11132
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Querying
> Affects Versions: 9.4.17.Final, 10.1.0.Final
> Reporter: Gustavo Fernandes
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.1.1.Final, 9.4.18.Final
>
>
> A REPL cache with index auto-config, during State transfer is skipping index of data.
> The order of events observed is:
> CACHE_STARTING LIFECYCLE -> ST HAPPENS -> DATA WRITTEN -> CACHE STARTED LIFECYCLE
> During data writes, the {{ProtobufValueWrapperIndexingInterceptor}} is activated by Hibernate Search and skips the indexing altogether since the {{ProtobufValueWrapperSearchWorkCreator}} is not used, and thus it cannot extract the descriptor from the entities. That search creator is only installed at cacheStarted phase.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 11 months