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.

This page includes details about ObjectGrid 6.1 cumulative intermediate fix 3, which supersedes ObjectGrid 6.1 cumulative fix 2.

Cumulative intermediate fix 3 (FIX3) includes bug fixes as well as several new features and function enhancements.

Download Information

Download the fix from the IBM support site: PK52322

Features and enhancements

• Enhanced shard placement using zones
  As an administrator, use placement zones to control where primary and replica shards are placed, which allows for the set up of advanced high performance and highly available topologies. You can define a zone to any logical grouping of ObjectGrid processes. These zones can correspond to physical workstation locations such as a data center, a floor of a data center, or a blade chassis. You can stripe data across zones, which provides increased availability, or you can split the primaries and replicas into separate zones when a hot standby is required. Read more...

• Administration for dynamic deployment topology ObjectGrids
  ObjectGrid now provides several systems management features when running with a dynamic deployment topology:
  • JMX MBeans
    The catalog service and containers provide MBeans to allow introspection and operational control of the ObjectGrid (Read more... ):
    • Retrieve Java process details, such as memory usage, number of processors, zone name, and host name.
    • Retrieve current shard placement topology.
    • Quiesce and shut down containers.
    • Retrieve performance statistics.
  • Embedded server support
    You can start ObjectGrid catalog services and containers within any arbitrary Java process. Prior to this feature, ObjectGrid catalog services and containers could be started using only the startOgServer.sh and startOgServer.bat command line scripts or in a WebSphere Application Server deployment. Read more...

• Highly available catalog service support in WebSphere Application Server
  You can make ObjectGrid catalog services highly available with WebSphere Application Server. You can run a catalog service with any WebSphere Application Server process, such as the deployment manager, node agent, or application server. Prior to this feature, the catalog service was started in the deployment manager process only. [Read more... ]

• Query queue support for entities
  Query queues allow any entity query to share its result set. This function provides greatly improved performance in client or server environments that need to use queues with selection criteria. This feature provides similar function to the ObjectMap.getNextKey method, but with the power of the entity query API. Read more...

• Entity listener support
  You can register entity listener classes with ObjectGrid, which then sends notification when entities are created, loaded, removed, and updated. As a result, non-persistent entity fields are populated with transient data, entity fields are validated for accuracy, and logging and auditing are included in the entity lifecycle. Read more...

• Security improvements
  Several security enhancements are now available:
  • Access by creator authorization support
    You can limit the access of caching entries to the user who initially creates the entry. This feature overrides or complements the existing ObjectGrid authorization security settings, which allows flexible patterns for protecting your data. Read more...
  • Dynamic deployment topology security
    You can enforce ObjectGrid security for the ObjectGrid dynamic deployment topology. An additional security descriptor XML file is now available that provides details on how you can authenticate and authorize access to ObjectGrid resources. Read more...

• WebSphere transaction integration
  ObjectGrid provides a TransactionCallback plug-in, which allows an ObjectGrid transaction to participate in a container-managed transaction of WebSphere Application Server. This feature simplifies Java 2 Platform, Enterprise Edition business logic by allowing the enterprise container to manage the ObjectGrid transaction. Read more...

• Spring framework support
  ObjectGrid now provides enhanced support for the Spring framework (Read more... ):
  • ObjectGrid transaction support
    You can manage ObjectGrid transactions with Spring, which provides automatic transaction demarcation for Spring managed beans.
  • Spring beans as ObjectGrid plugins
    ObjectGrid uses Spring beans as ObjectGrid plug-ins. In the descriptor XML file for ObjectGrid, you can set the spring bean name, prefixed by {spring}, instead of the plug-in class name. As a result, Spring manages the lifecycle of the plug-in.

• HTTP session filter support dynamic deployment topology ObjectGrids
  The ObjectGrid HTTP session filter is now available when running with a dynamic deployment topology and adds the following features (Read more... ):
  • High speed, local access to ObjectGrid
    The session filter hosts session state in the local process which promotes low latency read operations and low latency write operations when running asynchronous replication.
  • Automatic distributed state retrieval
    State is automatically retrieved from remote servers if the data does not exist locally. This can happen when servers fail.

Bug fixes

• AgentManager memory leak — Submitting agents to the AgentManager slows down as usage increases.
• ArrayIndexOutOfBoundsException in catalog server with IBM SDK 1.6 — The ObjectGridManager.getObjectGrid method might generate an "ObjectGridRuntimeException: ObjectGrid <objectGridName> not found." exception in Java SE 6 provided in the IBM Software Development Kit in a dynamic deployment topology environment.
• Cannot start more than one ObjectGrid application in the same WebSphere process — ObjectGrid shards are not placed on WebSphere Application Server processes that host more than one enterprise application.
• DataGrid agents do not report server information on failure — The ReduceGridAgent and MapGridAgent do not provide the partition, server name, or complete exception information when some exceptions are encountered.
• Entity optimistic lock fails to detect version changes — Optimistic locking might fail to detect a collision or might incorrectly display an OptimisticCollisionException exception.
• Exceptions occur when using asynchronous replication — Asynchronous replication might result in the following exceptions: LockTimeoutException, NullPointerException, or DuplicateKeyException.
• Exceptions occur while stopping an ObjectGrid server — Unexpected exceptions might occur when you are stopping an ObjectGrid server in the dynamic deployment topology in a WebSphere Application Server environment.
• LogElement.beforeImage() method returns the wrong value — The getBeforeImage method of the LogElement interface returns a wrong value, resulting in a ClassCastException exception.
• NotSerializableException thrown when finding entity key classes — Exception java.io.NotSerializableException may be thrown from the EntityManager.find method when the key class contains an entity association.
• Pessmistic locking problems — Several locking issues were discovered for the pessimistic locking strategy.
• Replica does not start or does not enter peer mode — Message CWOBJ1527 is logged or message CWOBJ1526 is missing from log.
• Server side exception is not shown in the client-side exception stack — The original server-side exception is propagated to the client-side exception stack.
• startOgServer hangs in WebSphere — The startOgServer.bat/sh command hangs when starting an ObjectGrid server process in a WebSphere environment.
• UnknownRequestException occurs when starting clustered catalog services — A com.ibm.ws.objectgrid.UnknownRequestException exception occurs when a clustered catalog service is started.

Wiki Disclaimer and License

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