The problems is not on the publisher send, but on the subscriber side. The WS-Notification component uses JMS underneath and the default persistent option is not changed, which means that the messages are persistent. But subscribers on the JMS topics are not durable, which means that if the WS-Component restarts, all subscriptions are lost, which leads to all messages to be discarded afaik. There is another thread on this list where we are discussing several enhancements servicemix-wsn2005, including having durable subscribers which should fix your problem.
On Tue, Sep 16, 2008 at 1:56 PM, antjohns <[EMAIL PROTECTED]> wrote: > > Hi , > > I am using Wsn2005 Component which is http-binded. So I'm able to publish > and subscribe using > SOAP request to the running service. > > The problem starts here, > > The messages sent/published by the publisher is not persistent, i.e > I'm losing all the sent messages when Servicemix is restarted. > > When it is restarted, I'm not able to get message on the topic > which was present using the old reference id. > > I intially thought, wsn2005 component would store the sent messages > in a file so that it can restore it back even though it gets crashed and > restarted. > > Can anyone tell me how to tune the Servicemix to achieve what > i said? Is there any special component I need to use to make > all the messages persistent? > > Thanks in advance, > Antony Johnson. > -- > View this message in context: > http://www.nabble.com/Plz-Help-me-on-Servicemix-Wsn2005-Component.-tp19510254p19510254.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
