hello
My issue lies in the environment-specific configuration of RabbitMQ in my Camunda workflow application. In our setup, each environment—whether it’s development, staging, or production—has its own dedicated RabbitMQ settings defined in the application.yml file and activated via Spring profiles. However, when executing processes that use the RabbitMQ Producer Connector, the connector sometimes fails to load the correct configuration for the active profile. This misconfiguration results in connection failures or incorrect message routing, meaning that messages might be sent to the wrong RabbitMQ server or exchange. Ultimately, this undermines the reliability and consistency of our asynchronous communication between microservices, complicating the orchestration of our business processes and making troubleshooting significantly more difficult.
Hi @Rabeb_Abid - I’m a bit confused on how you’re using the application.yaml file. The connector is configured within your process when modeling and doesn’t use local environment settings, unless you’re using secrets or have forked the connector and are running a custom implementation.
What application is the application.yaml file configuring? What values is it configuring?
@Rabeb_Abid What kind of configuration is expected to be picked up by the RabbitMQ Connector. You usually have to configure the Connector in the BPMN model