Hi,

version. 8.4.1
I have configured an AMQP trigger. The connection seems ok with the"Queue->Name" being populated ok with the queues from the RabbitMQ server.
I choose the relevant queue, and I set the trigger as "Active" - but immediately after "Ok", the Active toogle is cleared and the jobs trigger status is set as "No trigger Active".

What should I look out for ?

Best
Lars

Adding.
The AMQP protocol used is 0.9.1.
Is the Triggers inability to activate due to Visualcron only support protocol amqp 1.0 ?

If you get that deactivation immidiately there is something wrong with the settings. You might see in the server log (log_serverDATE.txt) why it was deactivated.

---

For anyone looking.
Seems its the difference in the protocol versions. The trigger expect AMQP 1.0, but gets AMQP 0.9.1.

logoutput
Info Job updated: rabbitmqtest
Err Trigger error: The protocol requested by peer '0 0 9 1' does not match expected '3 1 0 0'. Make sure both sides agree on protocol id and version.
Info JobAPI->Save->Saving Jobs (665) - in shut down: False
Debug Trigger was expired and inactivated
Info JobAPI->Save->Saving Jobs (665) - in shut down: False

For anyone looking.
Seems its the difference in the protocol versions. The trigger expect AMQP 1.0, but gets AMQP 0.9.1.

logoutput
Info Job updated: rabbitmqtest
Err Trigger error: The protocol requested by peer '0 0 9 1' does not match expected '3 1 0 0'. Make sure both sides agree on protocol id and version.
Info JobAPI->Save->Saving Jobs (665) - in shut down: False
Debug Trigger was expired and inactivated
Info JobAPI->Save->Saving Jobs (665) - in shut down: False

Is this something you can upgrade?

---

Maybe I will push for the AMQP 1.0 plugin to be installed in test environment.
But it does not seem AMQP 1.0 lives a first class citizen life within Rabbitmq world. (Unlike Azure)

Its not essential to trigger thru a queue, for now at least. But is is a nice addition to VC.

Best
Lars