On Apr 10, 2016 15:27, "Leon Pollak" <le...@plris.com> wrote: > > After your answer I again looked through the both manuals and did not find > anything saying that connectionless messaging allows drops. Vice verse, the > programmer's manual explicitly states that "TIPC is designed to be a reliable > messaging mechanism, in which an application can send a message and assume > that the message will be delivered to the specified destination as long as > that destination is reachable." > > Now, is it a bug, corrected in Nov 6th 2013? Or a feature? > > i can't move to connection oriented methods, because I need to support one- > to-3 and 3-to-one. >
This sounds a lot like the problem when connectionless messages are received, acked on the tipc link layer and passed to the socket, but dropped there because the socket receive buffer is full. If the receiving application does not drain the queue faster than messages build up, there will be losses as there us no concept of flow control at this level. Try bumping the prio of the server, maybe run it as an rt thread? //E > Sorry. > -- > Leon ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/ gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 _______________________________________________ tipc-discussion mailing list tipc-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tipc-discussion
