This release adds copying accessors for embedded entities to ADM generated messages and entities of the form getXXXTo(Entity target), and also creates copy() and copyInto(Entity target) methods on generated entities.

In Xbuf and Protobuf generated code the copy() operations preserve pass-through field value for received entities that have not been modified (a pass-through field is a field not defined in the generated code, but encoded on the wire by a sender). Additionally, in Xbuf generated code the copy is zero garbage.

Prior to this change applications could:

• use the clone() method to copy an embedded entity in a zero garbage fashion, but does not preserve pass-through fields.
  or
• use EmbeddedEntity.deserializeFrom(other.serializeToByteBuffer()); which preserves pass-through fields, but is not zero garbage.

The new copy() methods provide a way to do a pass-through field preserving copy that is also zero garbage.

See Embedded Entities

To take advantage of this functionality code regeneration is required.

This release provides the ability to globally configure the initial backing buffers size for embedded xbuf entities by setting the property:

For example:

-Dnv.xbuf.com.myapp.messages.Address.initialbackingbuffersize=32

or in DDL

<env>
    <nv>
      <xbuf>
        <com.myapp.messages>
          <Address.initialbackingbuffersize>32</Address.initialbackingbuffersize>
          <Recipient.initialbackingbuffersize>32</Recipient.initialbackingbuffersize>
        </com.myapp.state>
      </xbuf>
  </nv>
</env>

To take advantage of this functionality code regeneration is required. When not configured, the default backing buffer size of 256 bytes will continue to be used.

Usage of both adaptive transaction commit and parallel cluster replication is not supported. This release enforces this by disabling parallel cluster replication if an adaptive commit batch size is specified for the engine.

This fix resolves an issue in which the scheduling events into an Aep Engine's input multiplexer queue can result in adaptively batched transactions not being closed if no new message events are received.

This release fixes an issue in which Xbuf embedded entities were not being disposed when initializing a backup member from a primary member's transaction log.

Failing to dispose the entities during initialization can cause a lot of allocations to occur which can lead to significant garbage collection pauses.