See the WebSphere eXtreme Scale Wiki for links to eXtreme Scale Version 7.0 documentation.
If you log in with your developerWorks ID, you can leave comments and feedback for the development team.

WebSphere Extended Deployment Data Grid 6.1.0.1, which includes ObjectGrid 6.1.0.1, includes bug fixes, as well as several new features and function enhancements. ObjectGrid 6.1 Fix Pack 1 (6.1.0.1) supersedes ObjectGrid 6.1 cumulative fix 3.

Download Information

Download the fix from the IBM support site. See WebSphere Extended Deployment V6.1.0 Fix Pack 1 for more information.

Features and enhancements

• Transaction isolation support
  ObjectGrid now supports three transaction isolation levels: repeatable read, read committed, and read uncommitted using the Session.setTransactionIsolation method.  As a user of the ObjectMap API and EntityManager API, you can further increase concurrency and performance of applications when using the pessimistic lock strategy with transaction isolation. See Map entry locking with transaction isolation for more information.

• Upgradeable lock support for indexes and query
  Index and query can now use upgradeable (U) locks to avoid deadlocks and lock timeouts. Previously, this feature was available only using the ObjectMap.getForUpdate method. The ObjectMap.getIndex method and the ObjectQuery and Query interfaces now provide a "FOR UPDATE" setting which locks each entry with an upgradeable (U) lock instead of an S lock. See Map entry locks with query and indexes for more information.

• Security improvements
  The following security enhancements are now available:
  • Transport security support for dynamic configuration environment
    Transport security support (TLS/SSL) is supported for the dynamic deployment environment. Previously, transport security is supported only for the static deployment environment. Using this feature, data communication among ObjectGrid clients, container servers, and catalog servers can be encrypted. See Client server SSL support for more information.
  • JMX security
    JMX security is supported for the dynamic deployment environment. Previously, secure MBean operations are supported only for the static deployment environment. Using this feature, catalog server MBeans and container server MBeans can be invoked within a secure environment. See JMX security support in a dynamic deployment topology for more information.

Bug fixes

• ObjectQuery and HashIndex ignore attributes on super classes — A HashIndex will fail to initialize, or a query will fail to run if any fields or attributes are referenced on a super class.
• ORB transport security is not supported in the dynamic environment — Object Request Broker (ORB) transport security is not supported in the dynamic environment.
• Security is not supported for MBean operations — Security is not supported for Managed Bean (MBean) operations.

Wiki Disclaimer and License

© Copyright IBM Corporation 2007,2009. All Rights Reserved.