The Service Bus for the Connected Business
I have encountered a trouble sending RabbitMQ message on Neuron.
I just run the sample code under Client API-> Patterns -> Pub/Sub. I can monitor the whole messaging process on RabbitMQ Management. And the message was successfully received by subscriber. But for Neuron Explorer, nothing happens when I monitor the EndPoint Health and Deployment->RabbitMQ. Even when I disable the subscriber on Neuron Explorer, it hasn't influence the communication.
I wonder whether Neuron directly direct the message to RabbitMQ Management. Can anyone help with this problem
Views: 267
if you are seeing the message get published and sent to the underlying queue for the subscriber, then the message is there. do you have a subscriber connected to Neuron to receive the message?
I can see the message from RabbitMQ Management, but in Neuron Explorer, the queue has no message at all and the message rate for Publisher is just 0 even when I successfully send a message. I means, the whole process can be monitored on RabbitMQ Management HTTP API, sending, receiving, queuing, all work well. However, Neuron Explorer has no reaction to this process. I can't see message rate change on Endpoint Health, and can't see any changes in Deployment -> RabbitMQ, all fields are blank. It seems Neuron Explorer hasn't show anything about the process.
I have a subscriber connected to Neuron to receive the message and it receives message successfully.
so..your saying it works now, good.
within Neuron explorer..there is no facility to view the messages or underlying message count of the queues that we use for the Neuron parties. RabbitMQ doesn't expose an API that would allow us to manage those. That's why we usually recommend that customers use our MSMQ transport for the topics. Neuron explorer does allow you to view and manage those.
oh I see, thank you very much. And another question, can I use adapter in this situation?
what situation?
adapters can be used to bridge the bus to another technology....use case could be where one system...needs to act as a publisher or subscriber. In that example, salesforce could be a publisher...using our adapter. our adapter would receive the message from salesforce over its native api, and publish it to a topic. Then another adapter could be a subscriber...that could be a database adapter, queue adapter or application adapter. that adapter would receive the message and know how to talk to the endpoint system
Neuron ESB Product Support Forums and Communities
© 2024 Created by Neuron Admin.
Powered by
