5.2. Resolved Issues
- BZ-1213749 - Camel throwing java.lang.LinkageError for Remote Query when running in EAP
- When the Remote Query feature is used through the
camel-jbossdatagridcomponent in EAP, and JDG modules for EAP are installed, the application throws ajava.lang.LinkageErrorand the Remote Query feature does not work properly.This issue is resolved as of Red Hat JBoss Data Grid 6.5.0. - BZ-1206590 - Nearcache broken after SocketTimeoutException
- When a near cache has not received remote events for some time, for instance if the cluster is inactive or the client does not load new data, the connection to remote JDG servers fails with
java.net.SocketTimeoutException.This issue is resolved as of Red Hat JBoss Data Grid 6.5.0. - BZ-1198267 - Transaction is recommitted by joining node during merge
- When a node which was not part of previous view (e.g. due to network partition) joins a cluster, it may request retransmission of previous messages (JGroup's NAKACK). If some of those messages are prepare commands of transactions which have already finished on other nodes, then transactions can be prepared and committed on the joining node once again. This behavior may lead to inconsistent values across the cluster if the affected entries have been modified on nodes from the original view.This issue is resolved as of Red Hat JBoss Data Grid 6.5.0.
- BZ-1217480 - Camel-jbossdatagrid has a dependency on infinispan-core when only remote cache is in use
- The
camel-jbossdatagridcomponent requires embedded cache dependencies when a remote cache is used. The required dependency isinfinispan-embedded.jaras well as the expectedinfinispan-remote.jar. The same issue exists when using only an embedded cache, as theinfinispan-remote.jardependency is required in this case together with theinfinispan-embedded.jar.This issue is resolved as of Red Hat JBoss Data Grid 6.5.0. - BZ-1198971 - JSR-107 Make sure HotRod implementation passes all TCK tests
- Passing TCK test suite is an ultimate criterion of complying with the JCache specification. Some of the tests are still not passing with HotRod implementation (i.e. functionality is not provided yet).These relate to JMX statistics, expiration and listeners, where correct functioning currently cannot be guaranteed.This issue is resolved as of Red Hat JBoss Data Grid 6.5.0.
- BZ-1210313 - JDG Maven dependencies require EAP maven repo
- A new Maven repository,
jboss-datagrid-$RELEASE-maven-repository-full.ziphas been provided as a zip file; however, this repository is missing required dependencies.This issue is resolved as of Red Hat JBoss Data Grid 6.5.0. - BZ-1217380 - Deadlock on GlobalComponentRegistry when starting a cluster
- When starting a cluster with multiple nodes concurrently, a deadlock on GlobalComponentRegistry sporadically occurs which will prevent the nodes from starting completely.This issue is resolved as of Red Hat JBoss Data Grid 6.5.0.
- BZ-1224770 - Error being logged even if Backup Failure policy is set to IGNORE
- When datacenter replication is configured and the backup node is down messages similar to the following are seen in the log:
11:50:37,455 ERROR [org.jgroups.protocols.relay.RELAY2] (OOB-15,shared=udp) node-1/PRIMARY: no route to DR: dropping message
However, these error messages are logged even with failure-policy set toIGNORE.These messages indicate that the cluster can not communicate with the backup node, and do not represent immediate issues with the cluster itself.The Backup Failure policy is now honored as of Red Hat JBoss Data Grid 6.5.0; to resolve this issue ensure that the remote backup is online and there are no communication errors.
