The OpenWire Wire Format
OpenWire is the default Wire Format that ActiveMQ uses. It provides a highly efficent binary format for high speed messaging. OpenWire options can be configured on a JMS client's connection URI string or on a Brokers transport bind URI.
Should the stack trace of exception that occur on the broker be sent to the client?
Does not affect the wire format, but provides a hint to the peer that TCP nodelay should be enabled on the communications Socket.
Should commonly repeated values be cached so that less marshalling occurs?
Should wire size be optimized over CPU usage ?
Should the size of the packet be prefixed before each packet is marshalled?
The maximum inactivity duration (before which the socket is considered dead) in milliseconds. On some platforms it can take a long time for a socket to appear to die, so we allow the broker to kill connections if they are inactive for a period of time. Use by some transports to enable a keep alive heart beat feature. Set to a value <= 0 to disable inactivity monitoring.
The initial delay in starting the maximum inactivity checks (and, yes, the word 'Inital' is supposed to be misspelled like that)
If cacheEnabled is true, then this specifies the maximum number of values to cached. This property was added in ActiveMQ 4.1
Maximum frame size that can be sent. Can help help prevent OOM DOS attacks
All options for wire formats must be prepended with
wireFormat. in order to take effect. Without this proper formatting, the option will have zero effect.