All Apps and Add-ons

AMQP Messaging Modular Input: Getting "channel error; protocol method...no previously declared queue"

maximus_reborn
Path Finder

I am getting the below error when I am pushing json data to the exchange.

05-21-2016 14:01:56.567 +0530 ERROR ExecProcessor - message from "python /usr/local/splunk/etc/apps/amqp_ta/bin/amqp.py" Caused by: com.rabbitmq.client.ShutdownSignalException: channel error; protocol method: #method(reply-code=404, reply-text=NOT_FOUND - no previously declared queue, class-id=50, method-id=20)

Using rabbitmq_server-3.6.1 and the latest version of AMQP Messaging Modular Input

0 Karma
1 Solution

maximus_reborn
Path Finder

Resolved

There is a mismatch between the queue name in Splunk and that I gave in Producer code of RabbitMQ.

View solution in original post

0 Karma

maximus_reborn
Path Finder

Resolved

There is a mismatch between the queue name in Splunk and that I gave in Producer code of RabbitMQ.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...