Show Table of Contents
6.3.2 Release Notes
Red Hat JBoss Data Grid 6.3
Resolved issues for Red Hat JBoss Data Grid 6.3.2
The Red Hat JBoss Data Grid 6.3.2 Release Notes list and provide descriptions for a series of bugzilla bugs. The bugs highlights issues that are resolved issues for this release.
Chapter 1. Introduction to Red Hat JBoss Data Grid
Welcome to the Red Hat JBoss Data Grid 6.3.2. As you become familiar with the newest version of JBoss Data Grid, these Release Notes provide information about resolved issues. Use this document in conjunction with the entire JBoss Data Grid 6.3.x documentation suite, available at the Red Hat Customer Service Portal's JBoss Data Grid documentation page.
1.1. About Red Hat JBoss Data Grid
Red Hat's JBoss Data Grid is an open source, distributed, in-memory key/value data store built from the Infinispan open source software project. Whether deployed in client/server mode or embedded in a Java Virtual Machine, it is built to be elastic, high performance, highly available and to scale linearly.
JBoss Data Grid is accessible for both Java and Non-Java clients. Using JBoss Data Grid, data is distributed and replicated across a manageable cluster of nodes, optionally written to disk and easily accessible using the REST, Memcached and Hot Rod protocols, or directly in process through a traditional Java Map API.
This document contains information about the new features and known issues of Red Hat JBoss Data Grid version 6.3.2. Customers are requested to read this documentation prior to installing this version.
Chapter 2. Supported and Component Information
2.1. Supported Configurations
For supported hardware and software configurations, see the Red Hat JBoss Data Grid Supported Configurations reference on the Customer Portal at https://access.redhat.com/site/articles/115883.
Chapter 3. Resolved Issues
- BZ-1168235 - TransactionTable.start() initialize the TxCleanupService thread pool even when the cache is NON_TRANSACTIONAL
- Previously in Red Hat JBoss Data Grid, TransactionTable.start() initialized the TxCleanupService thread pool when dealing with a non-transactional cache.This is fixed in JBoss Data Grid 6.3.2 so that the TxCleanupService is disabled for non-transactional caches as expected.
- BZ-1168241 - Statetransfer thread pool deadlock
- Previously in Red Hat JBoss Data Grid, the OOB and/or thread pool became deadlocked during large state transfer operations (for example, 300 nodes with 3000 caches).This is now fixed in JBoss Data Grid 6.3.2 and the state transfer thread no longer becomes deadlocked during large state transfer operations.
- BZ-1168233 - Rebalancing "Finished cluster wide rebalance" message is not logged in INFO
- Previously in Red Hat JBoss Data Grid, the rebalancing "Finished cluster wide rebalance" message was not logged in INFO as expected. Users could access the log (started/enabled/suspended) messages, but could not view the expected "finished cluster wide rebalance" message in INFO.This is now fixed in JBoss Data Grid 6.3.2 and the message is logged in INFO as expected.
- BZ-1159559 - Bulk HotRod operations fail when using authorization
- Previously in Red Hat JBoss Data Grid, the Hot Rod Bulk operations used MapReduce which implied the EXEC permission even though conceptually they should be BULK_READ operations.This is now fixed in JBoss Data Grid 6.3.2.
- BZ-1168245 - HR size command broken in cluster mode
- Previously in Red Hat JBoss Data Grid, Hot Rod authentication succeeded with a clustered cache, but executing the RemoteCache.size() command threw a an unexpected SecurityException.This is now fixed in JBoss Data Grid 6.3.2 and Hot Rod authentication works as expected.
- BZ-1168237 - HR authentication broken in cluster mode
- Previously in Red Hat JBoss Data Grid, when the server cache was clustered, the Hot Rod client was unable to authenticate itself despite using the correct credentials and displayed the following error:
09:44:00,343 INFO [org.infinispan.AUDIT] (HotRodServerWorker-1) [DENY] null ADMIN cache[securedcache]The transport layer in JBoss Data Grid was breaking the authentication process. However, authentication worked as expected when a local cache was used instead of a clustered cache.This is now fixed in JBoss Data Grid 6.3.2 and Hot Rod authentication for a clustered server works as expected.
- BZ-1159162 - Possible false positive suspect of FD_HOST when the number of hosts is large
- Previously in Red Hat JBoss Data Grid, when using the FD_HOST protocol in JGroups for node failure detection (whether the node was alive was checked using ICMP pings), a node was suspected to be dead even if it was responsive. This issue was more likely to occur in larger clusters.This issue is now fixed in JBoss Data Grid 6.3.2.
Appendix A. Revision History
|Revision 6.3.2-1||Fri Dec 05 2014|
|Revision 6.3.2-0||Thu Dec 04 2014|
Copyright © 2014 Red Hat, Inc.
This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.