public static interface MatsOutgoingMessage.MatsSentOutgoingMessage extends MatsOutgoingMessage
MatsOutgoingMessage.DispatchType, MatsOutgoingMessage.MatsEditableOutgoingMessage, MatsOutgoingMessage.MatsSentOutgoingMessage, MatsOutgoingMessage.MessageType
Modifier and Type | Method and Description |
---|---|
int |
getDataSerializedSize() |
long |
getEnvelopeCompressionNanos() |
long |
getEnvelopeProduceNanos() |
long |
getEnvelopeSerializationNanos() |
int |
getEnvelopeSerializedSize() |
int |
getEnvelopeWireSize() |
long |
getMessageSystemProduceAndSendNanos() |
default int |
getMessageSystemTotalWireSize() |
java.lang.String |
getSystemMessageId() |
getBytes, getBytesKeys, getData, getDispatchType, getFlowId, getFrom, getInitialTargetState, getInitiatingAppName, getInitiatingAppVersion, getInitiatorId, getMatsMessageId, getMessageType, getReplyTo, getSameStackHeightState, getString, getStringKeys, getTimeToLive, getTo, getTraceId, getTraceProperty, getTracePropertyKeys, isInteractive, isNoAudit, isNonPersistent, isReplyToSubscription, isToSubscription
java.lang.String getSystemMessageId()
long getEnvelopeProduceNanos()
getUserLambdaNanos()
for both init and
stage), as it is done at the time of e.g. invoking processContext.request()
inside the user lambda.long getEnvelopeSerializationNanos()
int getEnvelopeSerializedSize()
getEnvelopeWireSize()
too, as the same applies here: This size only refers to the Mats
envelope, not the messaging system's final message size.long getEnvelopeCompressionNanos()
0
if no compression was
applied, while it will return > 0 if compression was applied.int getEnvelopeWireSize()
getEnvelopeSerializedSize()
. Note that the returned size is only the (compressed) Mats
envelope, and does not include the size of the messaging system's message/envelope and any meta-data
that Mats adds to this. This means that the message size on the wire will be larger.long getMessageSystemProduceAndSendNanos()
default int getMessageSystemTotalWireSize()
int getDataSerializedSize()