 | Summary: Fixed issues in GigaSpaces 6.0.1 (build 1903).
|
Overview
Below is a list of fixed issues since GigaSpaces 6.0 G.A (build 1855).
See the list of new features and known issues in GigaSpaces 6.0.1.
Core
- GS-2721 – Fixed: JDBCStorageAdapter connections were not closed when an exceptions occurred.
- GS-2596 – Fixed: When using the Session based messaging API with ComType.MULTIPLEX or MultiplexNotifyDelegator, externalizable notifications weren't supported.
- GS-2580 – Fixed: When performing batch operations under a transaction on a class in FIFO mode, not all notifications were sent (usually, notifications were sent only for the first operation).
- GS-2548 – Fixed: When the space was initialized and data recovery was being performed, the output replication filter was not started.
- GS-2436 – Fixed: Transient Entries in a persistent space with LRU didn't return leases.
- GS-2819 – Fixed: When running a replicated space with MySQL, the prepared statements inserted to the redo-log was missing one parameter, which caused the statement to fail.
- GS-2904 – Fixed: Write with the UPDATE_OR_WRITE modifier and externalizable did not increase the version of the provided Entry (e.g. when using optimistic locking).
- GS-2938 – Fixed: UpdateMultiple in a partitioned space threw a NullPointerException.
- GS-2302 – Fixed: Custom EventRegistration took too long (up to 1 minute) per registeation.
- GS-2055 – Redundant container and TCP server/client ports have been removed, since this is now set through a single value in the GenericExporter, see Setting Communication Protocol.
- GS-115 – Fixed: Externalizable Entries didn't support the following IJSpace attributes: setFifo, setOptimisticLock, setNoWriteLease.
- GS-2692 – Fixed: GSIterator blocking next did not unblock when the iterator was canceled/expired.
- GS-2683 – Fixed: A GetExternalEntry call inside a space filter caused a class structure to change in the space.
OpenSpaces
- GS-2861 – Fixed: Using OpenSpaces to deploy a Processing Unit used AWT (and didn't work in headless mode).
- GS-2552 – Fixed: A NullPointerException was thrown when configuring both giga-space-context and giga-space-late-context.
- GS-2448 – Fixed: SpaceSecurityException was thrown when attempting to deploy a secured space with a Processing Unit or Service Grid deployment.
Configuration, Jini Services and Tools
- GS-2901 – Fixed: <GigaSpaces Root>\bin\gs-ui.bat/sh and <GigaSpaces Root>\bin\gs.bat/sh scripts didn't include -Xbootclasspath/p:%XML_JARS% as part of their classpath.
- GS-2681 – Fixed: Different space proxies were created with the same URL in embedded spaces. This caused several duplicated spaces to be displayed in the GigaSpaces Management Center.
- GS-2501 – RMI garbage collection is now performed every hour (instead of 10 minutes in previous versions).
- GS-2216 – Fixed: In a non-multicast environment, a client might not have "re-acquired" a Lookup Service after all Lookup Services were killed.
- GS-2812 – Fixed: When using the SpaceFinder with the Space URL, there was no automatic Java security handling (setting a policy file was required).
Service Grid
- GS-2985 – Fixed: When using beans as Service Beans with the Service Grid, the Jeri exporter was used instead of LRMI.
- GS-2767 – Fixed: The <GigaSpaces Root>\lib\ext didn't load all classes/JARs into the Service Grid common classloader.
- GS-2595 – Fixed: Webster stopped working when failure occurred, and tried to send 500 HTTP responses. If failure occurred when trying to send 500 errors, Webster stopped accepting new connections.
.NET
- GS-2711 – Fixed: In an existing configuration file that did not contain Codemesh configuration, default Codemesh values were not set.
- GS-2277 – Fixed: Guid arrays were not mapped to UUID arrays due to Codemesh problems. Instead, they were treated as user-defined objects.
- GS-2984 – Fixed: Local View resources were not released when the proxy was disposed – in scenarios which use a lot of local views the system could have been exhausted.
- GS-2822 – Fixed: EntryAlreadyInSpaceException was thrown when writing a PONO with the UpdateOnly update modifiers.
- GS-2784 – Fixed: Problem working with secured spaces due to missing ANONYMOUS user.
- GS-2818 – Fixed: VersionID field was not incremented with PONO update (OptimisticLocking was true).
- GS-2910 – Fixed: SqlQuery read on a string field failed in partitioned spaces.
- GS-2644 – Fixed: Write failed in the .NET proxy when NoWriteLease=True.