5.2

Release Notes

XAP/EDG Documentation

General Resources

Summary: New features in GigaSpaces 5.2.

GigaSpaces 5.2 New Features

For links to the new features documentation, see below.

This release includes a large number of bug fixes. For more details, see the full list of fixed bugs and known issues.

SBA components – the SBA IWorker, ISpaceFilter, and IReplicationFilter components declarations support the new tags: <shutdown-space-on-init-failure>, <active-when-backup> (click each component for more details).

The Space Local View - Data streaming – The space local view proxy maintains a subset of the master space's data, allowing the client to read distributed data without any remote operations.
Data is streamed into the client view in an implicit manner – as opposed to local cache data, that is loaded into the client on-demand, and later updated or evicted.
The local view is defined via a filter – regular template or SQLQuery – as opposed to the local cache that caches data at the client side only after the data has been read (see the Space Local View section for more details).

Slow Consumer – The space includes a special mechanism that detects clients that cannot consume the notifications sent fast enough – i.e. slow consumers.
Slow consumers can cause problems, since they force the space to keep the notification in memory till all consumers consumed the event. Once the space process memory is full, the space is forced to slow down the response to clients, causing fast consumers to be slowed down. In extreme cases, this behavior might eventually cause the space process to exit abnormally with an out of memory error.

Active Election and Avoiding Split-Brain Scenarios – the active election mechanism is based by default on the Jini Lookup Service, which serves as the distributed naming service to coordinate a three-phase join flow electing the active service. The current implementation is based on a generic naming service abstraction, that can be replaced with any other distributed directory service, such as LDAP (see Active Election and Avoiding Split-Brain Scenarios for more details).

Distributed Unicast Based Lookup Service Support – in environments that do not support multicast, you can use the new locators space URL property to instruct the started space or a client to locate the Jini Lookup Service on a specific host name and port. The locators are used in a similar way to the groups URL property (see the Space URL section for more details).

Exclusive Read Lock – a new lock mode has been added to the GigaSpaces locking model – the exclusive read lock (ERL). The ERL is similar to select for update SQL for RDBMS, or update lock with ODBMS.
In the JavaSpaces specification, a read under a transaction does not allow other users to modify the Entry, but it does allow two readers or more to read the same Entry under different transactions. To allow a user to block other users from reading an object, a read using exclusive read lock mode with a transaction should be performed.

.Net enhancements – performance improvements, multiple assembly load order, reduced threads usage when using notifications, JVM Environment settings, inner classes support, support for all .NET data types (PODS), complex Objects support using the [serializeable()] attribute, and more (see the .NET PONO API Framework section for more details).

POJO Decorations enhancements and changes – the @SpaceVersion, @SpacePersist, @SpaceRouting (technology preview only), and @SpaceExclude annotations have been added, alongside several enhancemements (see the POJO Class and Field Level Annotations section for more details). Furthermore, POJO performance has been enhanced.

Space SQL Query enhancements – new JavaSpaces methods supported (see the SQLQuery in JavaSpaces section for more details).

GSIterator Extended Matching support, FIFO by-template support, and improved concurrency handling.

UPDATE_OR_WRITE semantics enhanced – new single update semantics, batch update semantics, and Map API semantics (see the About Space Operations section for more details).

Space Filter enhancements – new com.j_spaces.core.filters.FilterOperationCodes events provide notification statistics infrastructure, durable notifications infrastructure, notification recovery infrastructure, and four new notify trigger operations (BEFORE_NOTIFY_TRIGGER, AFTER_NOTIFY_TRIGGER, BEFORE_ALL_NOTIFY_TRIGGER, and AFTER_ALL_NOTIFY_TRIGGER) (see the Space Filter section for more details).

Space Browser enhancements
- Object Inspector – the Object Inspector allows you to view a specific object's information. using the selected object's UID, the Object Inspector takes the object itself from the space and displays its class fields, allowing you to drill down into any non-primitive types.
- Transactions View – the Transactions View allows you to view all of the transactions that are currently taking place in the selected space. This option can give helpful information when a transaction is stuck.
- Network view count column – shows the number of objects in each space (see the Spaces Network View section for more details).
- Viewing sent and acknowledged notifications statistics – new Notify sent and Notify ack. check boxes display the number of notifications sent, and the number of acknowledgements sent to the client after successful notifications (see the Statistics View section for more details).
- Selecting different object types in the Benchmark View – select Entry, POJO, Externalizable, Serializable, FIFO, or UID from the drop-down menu (see the Benchmark View section for more details).

Service Grid Management Framework – the Service Grid Management Framework centralizes the management of Service Grid components distributed across the network. It consists of a standalone process called the Focal Server.

Big Blob Support – large BLOBs (Binary Large OBjects) allow you to persist large Entry binary fields (smaller than 4G). BLOBs are defined as binary=BLOB in the type.properties configuration file.
Service Grid Enhancements – the Service Grid Deployment Descriptor Association element supports the following new options:
- Colocated – An association which requires that A be collocated with B in the same JVM. If B does not exist, or cannot be located, A shall not be created without B
- Opposed – An association which requires that A exist in a different JVM then B.

Add Labels
Enter labels to add to this page: Looking for a label? Just start typing.