ok, thanks. I've renamed the subject to shift threads. Anyone any options for my problem?
2011/12/6 SuoNayi <suonayi2...@163.com>: > No,it seems that you use the embedded memory broker to be a pending send > buffer for client. > > At 2011-12-06 20:09:34,"Joe Carter" <joe.car...@gmail.com> wrote: >>Is this the same/similar scenario to this? >> >>Configuration >>- embedded memory persisted broker >>- network connected to a standalone broker with kahadb persistence >>- remote consumer >> >>Use case normal behaviour >>- message sent to embedded broker. >>- this is relayed to the standalone broker >>- consumed by the remote process >> >>Problem >>- remote consumer is down >>- message remains in embedded broker and not relayed to standalone >>- this message can be lost if the process is restarted and also consumes >>memory >> >>Apologies if I'm hijacking an unrelated problem. >> >>Cheers >>Joe >> >>On 6 December 2011 11:44, Torsten Mielke <tors...@fusesource.com> wrote: >>> Hi, >>> >>> Is it the replayWhenNoConsumers feature that you're looking for? >>> >>> <conditionalNetworkBridgeFilterFactory replayWhenNoConsumers="true" /> >>> >>> See http://activemq.apache.org/networks-of-brokers.html, part "Stuck >>> messages". >>> >>> >>> Torsten Mielke >>> tors...@fusesource.com >>> tmie...@blogspot.com >>> >>> >>> >>> On Dec 6, 2011, at 6:54 AM, SuoNayi wrote: >>> >>>> Hi all and professionals at fusesource, is there a simple way to solve the >>>> issuse of stuck messages when network? >>>> Could I modify some source code ,for example the matchesForwardingFilter >>>> method in the class NetworkBridgeFilter ? >>>> I want to annotate the line code which checks a message passes through the >>>> target broker or not, >>>> but this maybe cause other potential and unknown problem. >>>> So could anyone give me a advice or some tips?Thanks a lot! >>> >>> >>>
