The Service Bus for the Connected Business
I have experienced a problem when a subscriber has more than one Endpoint adapter attached.
My setup:
Publisher, gets messages from a file adapter.
Subscriber, File adapter, FTP adapter
There is no logic at the subscriber, is just sends the message to the adapters. No transformation of the message.
If I dump 1880 files to my publisher, not all messages are delivered by the adapters. And no errors are logged.
If I disable one of the adapters at the subscriber site, then all messages is delivered with no trouble.
I have tried to change the transport method on the topic. Only if I chose “Peer” all messages are delivered by all adapters. Choosing other methods gives a huge packed lost.
Any special settings I have to be aware of, when having adapters of different types on a subscriber?
Tags: Adapter, Lost, Message, Transport
Views: 187
if you use MSMQ or Rabbit MQ based topics and you use more than one "instance" of a subscriber....i.e. you associate the subscriber with more than one endpoint, then only one endpoint at a time will receive a message...in a round robin delivery behavior. For example, you publish 1000 messages, and you have 2 subscribing endpoints each associated with the same party id, each one will get approx 500 messages for a total of 1000. However, if you use TCP/PEER/Named Pipes based topics, each one will receive a copy of the message.
in any case, you will not see message loss
But also with TCP and named pipes I have a huge message lost.
The result with MSMQ does not fit what you describe.
This is my actually results
Named pipes:
In(Publisher): 1888
Subscriber1
File Adapter:1850
FTP Adapter:1731
Failed:3
MSMQ:
In(Publisher): 1887
Subscriber1
File Adapter: 1673
FTP Adapter: 1740
Failed: 15
Peer:
In: 1888
Subscriber1
File Adapter: 1888
FTP Adapter: 1888
Failed: 0
Neuron ESB Product Support Forums and Communities
© 2024 Created by Neuron Admin.
Powered by
