$ 117.92
In-App Purchases| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 2725 |
| Technical Name |
rabbitmq_ultimate |
| License | OPL-1 |
| Website | http://nguyentuann1004@gmail.com |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 2725 |
| Technical Name |
rabbitmq_ultimate |
| License | OPL-1 |
| Website | http://nguyentuann1004@gmail.com |
| Versions | 17.0 18.0 19.0 |
RabbitMQ Ultimate
The most complete RabbitMQ integration for Odoo 19. Publish messages from any Odoo event, consume queues with background threads, track every message with a full audit log, and manage it all from a beautiful real-time dashboard — zero code required.
Key Features
Everything you need to connect Odoo to the RabbitMQ ecosystem, out of the box.
|
🔌
Multi-Connection ManagerCreate and manage unlimited Producer and Consumer connections. Each has its own host, credentials, exchange, queue, SSL/TLS settings, and status tracking. |
⬆️
Message Publisher (Producer)Publish JSON messages to any Exchange with routing key. Supports direct, topic, fanout and header exchange types. Durable queue and persistent delivery options. |
⬇️
Background Consumer (Listener)A thread-safe daemon thread continuously listens to a RabbitMQ queue. Automatically routes incoming messages to any Odoo model method you configure. |
|
📋
Full Message History & RetryEvery message is logged with payload, headers, routing info, processing time, status (Success / Failed / Dead Letter) and error details. Retry failed messages in one click. |
📊
Real-Time DashboardA beautiful OWL dashboard shows active connections, messages sent/received/failed, and per-connection status cards with last activity time — all updated live. |
🔁
Auto-Reconnect & Health CheckA scheduled health-check cron automatically detects dropped consumer threads and reconnects them. Configure the interval (in minutes) from Odoo Settings. |
|
📝
Jinja2 Message TemplatesDesign dynamic message payloads using Jinja2 syntax. Inject Odoo record fields directly into JSON output. Includes a live Preview tab with sample context validation. |
💀
Dead Letter Queue (DLQ)Configure a Dead Letter Exchange and routing key per connection. Failed messages are automatically routed for further inspection, preventing silent data loss. |
⚙️
Flexible ConfigurationSet default host, port, virtual host and credentials in Odoo Settings. Each connection can override individually or load from environment variables for Docker/CI deployments. |
See It In Action
Real screenshots from a live Odoo 19 instance.
Connection Form View
Create a Producer or Consumer connection. Choose type, set credentials, exchange, queue and routing key. Quick-access Sent / Received / Failed stat buttons in the top corner give instant visibility.
Exchange & Queue Configuration
Configure Exchange name, type (Direct / Topic / Fanout / Headers), durability, and routing key. Queue settings include Durable, Auto-Delete, and Exclusive options — mirroring RabbitMQ's native controls.
One-Click Connect & Disconnect
Hit Connect — the statusbar instantly jumps to Connected without a page reload. Last Activity timestamp updates in real time. Disconnect, Restart, Test Connection, Send Test Message, and Purge Queue buttons always visible in the header.
Connections List View
All connections at a glance: Name, Type, Host, Port, Exchange, Queue, Status badge, Sent count, Received count and Last Activity — sortable and searchable.
Message Log List
Full audit trail of all messages. Each row shows Time, Direction (Incoming / Outgoing), Connection, Exchange, Routing Key, Size in bytes, Status badge, and Processing Time.
Message Detail View
Drill into any message to see full payload Body, Headers, routing details (Exchange, Routing Key, Queue), processing time in milliseconds, and retry count. The JSON payload is displayed in readable format.
Verified on RabbitMQ Management UI
Messages published from Odoo appear immediately in RabbitMQ's native Management UI.
The sales_order_queue shows ready messages, delivery rates, and acknowledgement state — confirming real end-to-end delivery.
Full Payload Delivery
Messages sent from Odoo carry the full JSON payload, routing key, exchange name, content type (application/json), and properties.
Every field arrives intact on the RabbitMQ side.
Consumer Connection
Set up a Consumer connection by selecting type Consumer. The form adds an extra Consumer tab where you configure the Call Model, Call Method, Auto Acknowledge, and Prefetch Count.
Consumer Queue Binding
Bind the consumer to any queue. The Exchange & Queue tab provides the same rich settings as the producer: exchange type, durable/exclusive queue, and routing key.
Consumer Processing Settings
Specify which Odoo model and method should handle incoming messages.
The built-in Method Signature hint shows exactly how to write the handler:
def process_rabbitmq_message(self, body: str, headers: dict).
Supports RPC Mode and OCA Queue Job integration.
End-to-End Consumer Test
Publish a JSON message from RabbitMQ Management UI directly into the queue. Odoo's background consumer thread picks it up immediately and logs it in the Message Log.
Incoming Message Logged Successfully
Odoo captures the message, logs it as Incoming from Inventory Consumer, and marks it Success. All three rows (Incoming + 2x Outgoing) are visible in the audit log together.
Incoming Message Detail
The full JSON payload received from RabbitMQ is stored and displayed in Odoo with routing key, direction, status, timestamp, and processing latency.
Real-Time Dashboard
The dashboard shows 4 KPI cards (Active Connections, Messages Sent, Messages Received, Failed Messages) and a connection grid with per-connection status badge (Connected / Error), host, exchange, queue, sent/received counters, and last activity timestamp.
Jinja2 Message Templates
Design message payloads with Jinja2 template syntax. Use {{ object.field }} to inject live Odoo data.
The form has separate Template and Preview tabs for easy composition and validation.
Odoo Settings Integration
Configure default connection parameters (Host, Port, Virtual Host, Username) directly from Odoo Settings. Quick links to Test Connection and Open Connections are right there in the settings panel.
Message Logging & Retention
Enable or disable message logging per environment. Set log retention in days (0 = keep forever). A Clean Up Now button immediately purges old logs on demand — keeping your database lean.
Auto-Reconnect Health Check
Enable automatic reconnection and configure how frequently the health check cron runs (in minutes). Dropped consumer threads are detected and restarted automatically — no manual intervention needed.
Settings Dashboard Overview
A built-in Dashboard block inside Settings shows live KPI stats (Connections, Messages Sent/Received, Failed/Dead Letter), pika library status, and a direct link to the main dashboard — all without leaving Settings.
RabbitMQ Ultimate vs Basic Modules
| Feature | RabbitMQ Ultimate | Basic Modules |
|---|---|---|
| Producer & Consumer in one module | ✓ | ✗ |
| Background Consumer Thread (no cron needed) | ✓ | ✗ |
| Full Message Audit Log | ✓ | ✗ |
| Retry Engine & Dead Letter Queue | ✓ | ✗ |
| Real-Time OWL Dashboard | ✓ | ✗ |
| Auto-Reconnect & Health Check Cron | ✓ | ✗ |
| Jinja2 Message Templates | ✓ | ✗ |
Quick Setup
Install the module, install pika, and you're live in minutes:
# 1. Install Python dependency pip install pika # 2. Install the module in Odoo # Apps > Search "RabbitMQ Ultimate" > Install # 3. Go to RabbitMQ > Connections > New # Set Type = Producer or Consumer # Fill Host, Port, Credentials # Click Connect ✓
Compatible with RabbitMQ 3.x+ — Tested on RabbitMQ 3.13.3 / Erlang 26.2.5
Frequently Asked Questions
| Does the Consumer work without a cron? Yes. Each Consumer connection spawns a dedicated daemon thread that listens continuously in the background. No polling cron is needed. The auto-reconnect cron only monitors thread health and restarts them if they crash. |
| Can I have multiple connections to different RabbitMQ servers? Absolutely. Each connection record is fully independent with its own host, credentials, exchange and queue. You can have dozens of producers and consumers running simultaneously on different servers. |
What Odoo method signature does the consumer call?
The method receives body: str (the raw message payload) and headers: dict (AMQP headers).
Example: def process_rabbitmq_message(self, body: str, headers: dict).
The signature hint is shown directly in the Consumer tab.
|
| What happens if the RabbitMQ server goes down? The consumer thread marks itself as Error and stops. When the health check cron runs next (every N minutes you configure), it detects the dropped thread and automatically reconnects. No manual intervention needed. |
Need Help?
Full support included. Bug reports, feature requests, or custom integration questions — just reach out!
nguyentuann1004@gmail.comVersion: 19.0.1.0.0 | License: OPL-1 | Author: Tuan Nguyen Van
Compatible with Odoo 19 Community, Enterprise, and Odoo.sh
© 2026 Tuan Nguyen Van. All rights reserved.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module