Chapter 5. Known Issues
5.1. Known Issues
- JDG-96 - Cache events are incompatible with CDI 1.1 in JDG 7
When using CDI annotations with the CDI 1.1 API, such as the version found within JBoss EAP 7, a
java.lang.RuntimeException
is thrown; this exception is thrown as the cache events used by JBoss Data Grid 7.1.1 include content that has been removed by CDI 1.1.This is a known issue in JBoss Data Grid 7.1.1. This issue is resolved in the CDI 1.2 API; to workaround this issue attach the listeners manually, as outlined in the following steps:
-
Remove CDI annotations from the listener bean, including removing all
@Observes
annotations from methods. -
Add Listener annotations on desired methods; for example,
@CacheStarted
. -
Manually register listeners using
AdvancedCache#addListener
.
-
Remove CDI annotations from the listener bean, including removing all
- JDG-436 - JMX operation ClusterCacheStats.resetStatistics() not working
When executing the JMX operation
ClusterCacheStats.resetStatistics()
none of the cluster statistics are reset.This is a known issue in JBoss Data Grid 7.1.1, and to workaround this issue execute
Statistics.resetStatistics()
on each server individually.- JDG-474 - CLI - container and cache commands don’t work in domain mode
When executing
container
orcache
based commands through the CLI in domain mode the following message is displayed:Container does not exists
This is a known issue in JBoss Data Grid 7.1.1, and no workaround exists at this time.
- JDG-244 - Spark connector fails with CCE when compatibility mode is enabled
When attempting to insert values into a cache using the Spark connector while compatibility mode is enabled the request will fail with a
ClassCastException
.This is a known issue in JBoss Data Grid 7.1.1, and to workaround this issue disable compatibility mode.
- JDG-826 - Deadlock during stopping CacheManager
When a new cache is started during server shutdown it can result in a deadlock.
This is a known issue in JBoss Data Grid 7.1.1, and to workaround this issue do not start any caches while the server is shutting down.
- JDG-841 - Rolling Upgrades from JDG 6.6.0 or earlier ignore cache store
The rolling upgrade procedure from JBoss Data Grid 6.6.0 and before records all the keys in the source cluster and transfers these keys to the target cluster. This operation does not persist the entry in the cache store.
This is a known issue in JBoss Data Grid 7.1.1, and no workaround exists at this time.
- JDG-840 - Rolling Upgrades from JDG 6.6.0 or ealier migrates all data to a single node
When performing a rolling upgrade from JBoss Data Grid 6.6.0 or before all of the data is migrated to a single node instead of being distributed across the cache.
This is a known issue in JBoss Data Grid 7.1.1, and no workaround exists at this time.
- JDG-831 - Rolling Upgrade from 6.1 to 7 not working
When attempting to synchronize data during a rolling upgrade the following error is thrown:
[standalone@localhost:10990 /] /subsystem=datagrid-infinispan/cache-container=clustered/replicated-cache=sample-cache:synchronize-data(migrator-name=hotrod) { "outcome" => "failed", "failure-description" => "DGISPN0118: Failed to invoke operation: java.lang.ClassNotFoundException: org.infinispan.util.ByteArrayKey from [Module \"org.infinispan.persistence.remote:main\" from local module loader @42f30e0a (finder: local module finder @24273305 (roots: /opt/jboss-datagrid-7.0.0-server/modules,/opt/jboss-datagrid-7.0.0-server/modules/system/layers/base))]", "rolled-back" => true }
This is a known issue in JBoss Data Grid 7.1.1, and no workaround exists at this time.
- JDG-869 - Deploying a task requires server reload
After deploying a task to the server any attempts to call this task result in an
Unknown task 'localScript_throwingException'
error.After restarting or reloading the server the task executes without issue.
This is a known issue in JBoss Data Grid 7.1.1, and no workaround exists at this time.
- JDG-823 - JPA cache store in weblogic and Postgresql 9.3 produces error
Any attempts to use the JPA cache store with weblogic and Postgresql 9.3 results in a
NoSuchMethodError
:java.lang.NoSuchMethodError: javax.persistence.Table.indexes()[Ljavax/persistence/Index; [java] at org.hibernate.cfg.annotations.EntityBinder.processComplementaryTableDefinitions(EntityBinder.java:1100) [java] at org.hibernate.cfg.AnnotationBinder.bindClass(AnnotationBinder.java:772) [java] at org.hibernate.boot.model.source.internal.annotations.AnnotationMetadataSourceProcessorImpl.processEntityHierarchies(AnnotationMetadataSourceProcessorImpl.java:245) [java] at org.hibernate.boot.model.process.spi.MetadataBuildingProcess$1.processEntityHierarchies(MetadataBuildingProcess.java:222) [java] at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:265) [java] at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:847) [java] at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:874) [java] at org.hibernate.jpa.HibernatePersistenceProvider.createContainerEntityManagerFactory(HibernatePersistenceProvider.java:135) [java] at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:50) [java] at weblogic.persistence.BasePersistenceUnitInfo.initializeEntityManagerFactory(BasePersistenceUnitInfo.java:461) [java] at weblogic.persistence.BasePersistenceUnitInfo.initializeEntityManagerFactory(BasePersistenceUnitInfo.java:454) [...]
This is a known issue in JBoss Data Grid 7.1.1, and no workaround exists at this time.