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.

IBM WebSphere eXtreme Scale Version 6.1 Fix Pack 5 (6.1.0.5), including the ObjectGrid component, provides several new features and bug fixes. Version 6.1.0.5 supersedes ObjectGrid Version 6.1.0.4.

Download Information

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

Features and enhancements

• WebSphere Application Server Version 7.0 support
  WebSphere eXtreme Scale can now be installed on WebSphere Application Server versions 6.0.2, 6.1 and 7.0. Read more...

• Query and HashIndex performance enhancements
  HashIndex has been enhanced to allow indexing of entity relationships. Both single- and multi-valued associations may now have the @Index annotation or a HashIndex plug-in defined. Adding an index on a relationship can speed up queries that use cyclical references or use the IS EMPTY, SIZE and MEMBER OF query filters. Read more...
  
  ObjectGrid query and HashIndex have also been generally improved to process index results more effectively when using PESSIMISTIC locking. Most queries will see a performance improvement without making any changes.

• Query, HashIndex, and AgentManager statistics
  Additional statistics, Performance Monitoring Infrastructure (PMI) modules and MBeans have been added for queries, HashIndex, and agents. These statistic modules allow administrators and developers to more easily troubleshoot performance problems without instrumenting the code, enabling trace, or using profiling tools.

• Object Request Broker (ORB) is now included
  WebSphere eXtreme Scale now includes the IBM ORB. Customers using a non-IBM Java virtual machine in a standalone environment no longer need to extract the ORB from an IBM Java virtual machine install image. To use the provided ORB, simply edit the setupCmdLine.sh or setupCmdLine.bat script files and uncomment the line that sets the OBJECTGRID_ENDORSED_DIRS variable.

• Improved performance for finding entities with eager relationships
  Entities that have eager relationships are now fetched with fewer network requests. By default, all entities with FetchType.EAGER will be retrieved in a single request instead of multiple requests. The fetch depth can be overridden by altering the FetchPlan for the EntityManager. The FetchPlan will affect all entities that are loading using EntityManager.find() or Query.

• Multiple entity schema root support
  A single ObjectGrid can now have multiple schema roots. Each entity relationship hierarchy defined in an ObjectGrid can have an independent schema root defined, allowing greater flexibility when deploying complex object models. Read more...

• Entity projector utility
  The Projector utility allows simple conversion of entities to key and value Tuple objects. This utility can improve performance and reduce complexity of applications that interact directly with entity maps such as custom Loaders plug-ins.

• java.util.Calendar support
  Query, HashIndex, and EntityManager now support attributes of type java.util.Calendar. Calendar types are treated similarly to java.util.Date types and no longer have dependencies on implementation-specific behaviors. This feature adds consistency with other object relational mapping products and specifications such as the Java Persistence API.

• SSL-Required support
  Secure Sockets Layer (SSL) can now be enforced using the SSL-Required option. Prior to this release, transport security could only be configured using SSL-Supported.

• BackingMap numberOfBuckets improvement
  ObjectGrid backing maps no longer require the use of the numberOfBuckets attribute. When not specified, an improved hash table implementation is used that does not rely on hash buckets. When the total number of cache entries is known, setting the numberOfBuckets to a prime number larger than the total number of expected cache entries will perform best. However, if the number of entries is not known, leaving the numberOfBuckets attribute unset will normally provide sufficient performance without sacrificing memory utilization.

• WebSphere Application Server Version 7.0.0.1 Session Initiation Protocol support
  A new, more flexible Session Initiation Protocol (SIP) solution is now available with this release. WebSphere Application Server version 7.0.0.1 and APARs PK72195 and PK76241 are required for SIP to function correctly on the version 7 platform.

• xsAdmin Sample Utility Enhancements
  The xsAdmin sample utility has several enhancements:
  • Added WebSphere Application Server 7.0 support.
  • The -mbeanservers command-line option provides a list of available MBeanServer URLs.
  • The -jmxUrl command-line option to connect to an alternative MBeanServer endpoint rather than the default endpoint.
  • Read more...

Bug fixes

• ClassCastException in JPAEntityLoader — ClassCastException is thrown for the JPAEntityLoader when using property-access entities.
• CountStatistic does not increment properly — The CountStatistic's active count attribute does not reflect the correct value.
• DuplicateKeyException during failover — With two or more sync replicas, a DuplicateKeyException occurs during failover
• Exceptions during server shutdown — Exceptions during server shutdown including ObjectTransformer instance not found, ClassCastException, or an IllegalStateException
• java.util.Calendar attributes for entities not interoperable — Entity attributes of type java.util.Calendar will not interoperate with previous versions of ObjectGrid.
• LockTimeoutExceptions using Async Replication — Running with async replication, LockTimeoutExceptions occur on the servers running the primary shards.
• No messages for partition movement — No helpful messages for replica promotion and stopping primary and replica shards.
• NullPointerException on POAImpl — NullPointerException POAImpl.deactivate_object during shard movement
• PartitionManager calculation changed for entities — Improve the algorithm used to choose the partition of an entity.
• PartitionManager.getPartition returns 1 — PartitionManager returns a partition number of 1 for all entities if the schema root is not defined.
• PlacementServiceMBean does not return well-formatted XML — The PlacementServiceMBean does not return well-formed XML.
• Replica fails but is not replaced — Replica fails entering peer mode or exceeds maximum attempts to reregister, but not replaced.
• SSL-Required ORB transport security is not supported in the dynamic deployment topology — Object Request Broker (ORB) transport security only supports the "SSL-Supported" transport type.
• The xsAdmin -mapsizes option fails when a container is co-located with a catalog service — The xsAdmin sample utility will fail to display any information when the container is co-located with a catalog server.
• WebSphere Application Server transaction incorrectly flows to ObjectGrid servers — JTA transactions incorrectly flow from ObjectGrid clients in WebSphere Application Server applications to ObjectGrid servers.

Wiki Disclaimer and License

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