[JBoss JIRA] (ISPN-9977) java.lang.NoClassDefFoundError: org/infinispan/commons/util/FastCopyHashMap$Values (wrong name: org/infinispan/commons/dataconversion/BinaryEncoder) when starting in repackaged Spring Boot jar with Java 11
by Katia Aresti (Jira)
[ https://issues.jboss.org/browse/ISPN-9977?page=com.atlassian.jira.plugin.... ]
Katia Aresti commented on ISPN-9977:
------------------------------------
I tested adding commons 9.4.3.Final and indeed, it worked. But testing with 9.4.2.Final and 9.4.1.Final (commons) fails too. There aren't any suspect changes between infinispan 9.4.3 and 9.4.4. I will keep you posted on the fix. Thanks for the report and for using infinispan sb starter!
> java.lang.NoClassDefFoundError: org/infinispan/commons/util/FastCopyHashMap$Values (wrong name: org/infinispan/commons/dataconversion/BinaryEncoder) when starting in repackaged Spring Boot jar with Java 11
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-9977
> URL: https://issues.jboss.org/browse/ISPN-9977
> Project: Infinispan
> Issue Type: Bug
> Components: Spring Integration
> Affects Versions: 10.0.0.Alpha3, 9.4.6.Final
> Environment: * ubuntu 16.04
> * openjdk 11.0.1
> * maven 3.6.0
> * spring boot 2.1.2.RELEASE
> * infinispan-spring-boot-starter 2.1.3.Final (and 2.1.4-SNAPSHOT)
> Reporter: Benjamin Schröder
> Assignee: Katia Aresti
> Priority: Major
>
> The infinispan-spring-boot-starter will fail with
> {code:java}
> java.lang.NoClassDefFoundError: org/infinispan/commons/util/FastCopyHashMap$Values (wrong name: org/infinispan/commons/dataconversion/BinaryEncoder)
> {code}
> when ran in an repackaged Spring Boot jar if built and ran with Java 11. It works if built and ran with Java 8. It works with Java 11 too but only if ran with mvn spring-boot:run
> It can be reproduced with the infinispan-spring-boot-samples. (see steps to reproduce). Otherwise there is a demo project linked here: https://stackoverflow.com/questions/54635814
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-9980) Upgrade Spring Version
by Katia Aresti (Jira)
Katia Aresti created ISPN-9980:
----------------------------------
Summary: Upgrade Spring Version
Key: ISPN-9980
URL: https://issues.jboss.org/browse/ISPN-9980
Project: Infinispan
Issue Type: Component Upgrade
Components: Spring Integration
Reporter: Katia Aresti
Spring 5.1.5.RELEASE
Boot version 2.1.3.RELEASE
Security 5.1.4.RELEASE
Session 2.1.4.RELEASE
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-9979) AbstractComponentRegistry.stop() can hang if called concurrently
by Philippe Julien (Jira)
Philippe Julien created ISPN-9979:
-------------------------------------
Summary: AbstractComponentRegistry.stop() can hang if called concurrently
Key: ISPN-9979
URL: https://issues.jboss.org/browse/ISPN-9979
Project: Infinispan
Issue Type: Bug
Affects Versions: 9.4.3.Final
Reporter: Philippe Julien
I believe that there is a bug in org.infinispan.factories.AbstractComponentRegistry.stop()
Our Wildfly 15 nodes often hang on shutdown on the following:
{noformat}
"MSC service thread 1-2" #37 prio=5 os_prio=0 tid=0x0000000003807000 nid=0xf32d in Object.wait() [0x00007f0012c6f000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000005cc795fa8> (a org.infinispan.factories.ComponentRegistry)
at java.lang.Object.wait(Object.java:502)
at org.infinispan.factories.AbstractComponentRegistry.stop(AbstractComponentRegistry.java:359)
- locked <0x00000005cc795fa8> (a org.infinispan.factories.ComponentRegistry)
at org.infinispan.cache.impl.CacheImpl.performImmediateShutdown(CacheImpl.java:1159)
at org.infinispan.cache.impl.CacheImpl.stop(CacheImpl.java:1124)
at org.infinispan.cache.impl.AbstractDelegatingCache.stop(AbstractDelegatingCache.java:520)
at org.infinispan.manager.DefaultCacheManager.terminate(DefaultCacheManager.java:734)
at org.infinispan.manager.DefaultCacheManager.stopCaches(DefaultCacheManager.java:786)
at org.infinispan.manager.DefaultCacheManager.stop(DefaultCacheManager.java:762)
at org.jboss.as.clustering.infinispan.subsystem.CacheContainerServiceConfigurator.accept(CacheContainerServiceConfigurator.java:114)
at org.jboss.as.clustering.infinispan.subsystem.CacheContainerServiceConfigurator.accept(CacheContainerServiceConfigurator.java:70)
at org.wildfly.clustering.service.FunctionalService.stop(FunctionalService.java:77)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1794)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.execute(ServiceControllerImpl.java:1763)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1364)
at java.lang.Thread.run(Thread.java:748)
{noformat}
There are no other threads that are working with 0x00000005cc795fa8 in the thread dump.
I checked in a heap dump and the 0x00000005cc795fa8 org.infinispan.factories.ComponentRegistry object state is TERMINATED.
I think that the finally block of AbstractComponentRegistry.stop() is missing a notifyAll().
Shouldn't this:
{code}
...
} finally {
synchronized (this) {
state = ComponentStatus.TERMINATED;
}
}
{code}
Be:
{code}
...
} finally {
synchronized (this) {
state = ComponentStatus.TERMINATED;
notifyAll();
}
}
{code}
This way, if two thread try to stop the same cache, the one that wins will notify the one that is waiting letting its stop complete.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-3835) Index Update command is processed before the registry listener is triggered
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-3835?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-3835:
----------------------------------
Fix Version/s: 9.4.8.Final
(was: 9.4.7.Final)
> Index Update command is processed before the registry listener is triggered
> ---------------------------------------------------------------------------
>
> Key: ISPN-3835
> URL: https://issues.jboss.org/browse/ISPN-3835
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 6.0.0.Final
> Reporter: Sanne Grinovero
> Priority: Critical
> Labels: 64QueryBlockers
> Fix For: 9.4.8.Final
>
>
> When using the InfinispanIndexManager backend the master node might receive an index update command about an index which it hasn't defined yet.
> Index definitions are triggered by the type registry, which in turn is driven by the ClusterRegistry and an event listener on the ClusterRegistry. It looks like slaves are sending update requests before the master has processed the configuration event.
> This leads to index update commands to be lost (with a stacktrace logged)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-4817) Cluster Listener replication of listener to remote dist nodes needs privilege action
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-4817?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-4817:
----------------------------------
Fix Version/s: 9.4.8.Final
(was: 9.4.7.Final)
> Cluster Listener replication of listener to remote dist nodes needs privilege action
> ------------------------------------------------------------------------------------
>
> Key: ISPN-4817
> URL: https://issues.jboss.org/browse/ISPN-4817
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 7.0.0.CR1
> Reporter: William Burns
> Priority: Critical
> Fix For: 9.4.8.Final
>
>
> The ClusterListenerReplicateCallable needs to add the listener in a privileged block so that it can work properly.
> I was also thinking if we need to change all of our messages to send along the current Subject so it can be properly applied to remote invocations as well. In this case we wouldn't need to wrap the listener invocation.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-4624) Allow custom partition handling strategy
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-4624?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-4624:
----------------------------------
Fix Version/s: 9.4.8.Final
(was: 9.4.7.Final)
> Allow custom partition handling strategy
> ----------------------------------------
>
> Key: ISPN-4624
> URL: https://issues.jboss.org/browse/ISPN-4624
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 7.0.0.Beta1
> Reporter: Dan Berindei
> Priority: Major
> Labels: partition_handling
> Fix For: 9.4.8.Final
>
>
> Users should be able to configure a custom PartitionHandlingStrategy. It should be able to specify a behaviour on merge as well.
> We might want to merge this with the RebalancePolicy, which was also supposed to be configurable.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month