The message is put into the local or target storage before delivered to target queue. If message delivery fails, OTMQ will retry on behalf of the sender.

OTMQ sending operation does not need to wait until message actually delivered, and receiving operation does not need to block to wait for new message.

OTMQ sender can specify a location in the message delivery path, and ACK message will be sent back to sender when message arrives the specified place.

OTMQ can provide a mechanism to ensure guaranteed delivery, writes recoverable messages to nonvolatile storage on the sender or receiver system.

OTMQ supports publish-subscribe in topic.

OTMQ receiver can select message with various rules.

OTMQ applications can dynamically name a queue with an alias.

OTMQ sender can specify a way to process message when delivery fails.

OTMQ applications can store messages in either shared memory or permanent disk storage, to benefit from either higher performance or higher availability.

OTMQ can exchange messages with Oracle MessageQ.