We have two Neuron Application servers, call them A and B. Both are configured to use a single database, called NeuronAudit. Each have their own RabbitMQ. Frequently, about once a week, messages appear in the RabbitMQ of, for instance Server B that originated on Server A, or vice versa. These messages are destined for workflow endpoints. Since the endpoints on Server A are not the same as on B, this "message crosstalk" causes issues when they appear on the wrong server.
What's the best way to remedy the situation? We want messages that originate on Server A to be processed on Server A, and the same for Server B without exception. My simpleminded solution would be to define a new database, and have each server connected to its own database, but I am not sure.
Tags: queueing
check the availability group deployment settings. if you do not want the workflow endpoint to run on the other server, make sure the other server is marked as a failover and not a primary for the workflow endpoint
Ah yes, I see. This is the config of the Avail group on Server A:Interestingly, on Server B, only itself is listed. In any case, if ...
so....are these running different solutions? if they were using the same config, both servers would be listed in a deployment group. but from the picture....it looks like you named your deployment group after maybe a server name? usually deployment groups are named dev, qa, test, prod, etc. the deployment group should list ALL the servers that will be running the solution. when you do that...all the servers for a deployment group would show up here. basically it looks like the entire deployment configuration is misconfigured....or it was seperated out ...copied for each server, rather than both servers using the same config
feel free and reach out to Steve tomorrow and have him review what your solution looks like. if I have time...I can jump on as well. Steve can setup a web ex for you.
WIll do
Neuron ESB Product Support Forums and Communities
© 2024 Created by Neuron Admin. Powered by