Description:
For EMS 4.1.0 and earlier, when a user set maxbytes on a topic, the EMS server would honor that level regardless of whether the producer was using transactions or not.  So once the maxbytes is reached for any subscriber, the EMS server would not queue any further messages to that subscriber until the level is below maxbytes.

In EMS 4.2.0, the EMS server honors the maxbytes level on topics only for non-transactional messages.  For transactional messages, the EMS server will continue to put messages into the subscriber's queues without restriction.

Setting maxbytes on a queue works as expected in EMS 4.2.0, regardless of with the queues are being operated on in transactional or non-transactional mode.

Note: In all releases the EMS server does not return an exception when it does not queue a message for any given subscriber.  This is intended behavior.

Symptoms:

Cause:

EMS 4.2.0 does not honor the maxbytes level when using topics and transactional semantics.