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 mandatory ObjectGrid 6.1 cumulative intermediate fix 2, which supersedes ObjectGrid 6.1 cumulative fix 1.

Download Information

The fix is available from the IBM support site: PK50998

Fix contents

• A NotSerializableException occurs when serializing field-access entities — Managed, field-access entities with multi-valued relationships cannot be serialized.
• Agent exceptions are not visible on an AgentManager client — Exceptions that result from a MapGridAgent or ReduceGridAgent are not available on the client.
• Auto-commit EntityManager and Query exceptions are not thrown — The EntityManager API and Query API auto-commit methods do not throw commit or rollback exceptions.
• ClassNotFoundException using AgentManager in WebSphere Application Server — A ClassNotFoundException exception might result when you are submitting a MapGridAgent or ReduceGridAgent to an AgentManager in a WebSphere Application Server environment.
• Container process MBeans cannot be disabled — ObjectGrid Managed Beans (MBeans) in a container process cannot be disabled.
• Duplicate query results with indexed attributes using OR — EntityManager Query and ObjectQuery may produce duplicate results if two indexed attributes in the query's WHERE clause are selected with an OR logical operator.
• DuplicateKeyException, KeyNotFoundException or vote to rollback occur after ObjectGrid server start — After starting multiple ObjectGrid servers, the application might receive DuplicateKeyExceptions, KeyNotFoundExceptions or replicas voting to rollback exceptions during a session commit.
• EntityManager operations in a partitioned environment might fail — EntityManager operations against a partitioned local ObjectGrid server instance incorrectly result in a PersistenceException exception with the following message:
• Host and port are not configurable on ObjectGrid container — The host and port settings are not configurable for an ObjectGrid container.
• IllegalArgumentException from EntityManager find with TTL evictor enabled — The exception: "java.lang.IllegalArgumentException: Invalid entity class: OrderBy failed" incorrectly results from an EntityManager.find operation if the relationship between the specified entity and a referenced entity is broken.
• Invalid or missing CGLIB library is not tolerated by the EntityManager API — Unexpected exceptions might occur when you are accessing property-access entities without the CGLIB library or an incompatible CGLIB library is in the classpath.
• LockTimeoutException using HTTP session manager — A LockTimeoutException may occur when retrieving data from a HTTP session.
• MetadataException CWPRJ1100E results for short entity version types — If an entity has a version field of type short or java.lang.Short, a MetadataException exception with message CWPRJ1100E results.
• Null string query results fail — If a query result includes a string type and the value is null, a NullPointerException might result, or the null value might be suppressed.
• NullPointerException in EntityMetadataFactoryImpl.getSchemaRootPathForTuple — If an association in an Entity graph has a circular relationship, a java.lang.NullPointerException exception might result.
• NullPointerException is thrown from AgentManager if null is returned from MapGridAgent — If a MapGridAgent instance returns a null value instead of a Serializable Map instance, the client receives a java.lang.NullPointerException exception.
• Queries are never routed to replicas — EntityManager Query API and ObjectQuery API execution requests are incorrectly routed only to primaries even when replica-read is enabled.
• Query over pessimistic maps locks unused keys — A query might retain too many locks than are realized in a query result.
• Read only transactions not replicated when an Evictor is used — Entries can be evicted prematurely when a primary fails.
• Subset Entity has problems with inserts and updates — Various problems exist when entities are persisted or updated with the EntityManager API.
• Transaction exceptions result from query when using an external TransactionCallback plug-in — A NoActiveTransactionException or TransactionAlreadyAlreadyActiveException exception might incorrectly result from the EntityManager Query API or ObjectQuery API when you are using a TransactionCallback plug-in with external transaction integration enabled.
• Zero lock timeout is not allowed — The ObjectMap.setLockTimeout method does not allow a value of 0 seconds.

Wiki Disclaimer and License

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