Persistence will only allow to recover non delivered exchanges. If you want full receovery, you'd have to use transaction on top of that. I would consider using a <jms:consumer /> endpoint configured with xa transactions: the default behavior is synchronous, so everything should work as expected.
On Tue, Feb 26, 2008 at 6:10 PM, Jérémy SEVELLEC <[EMAIL PROTECTED]> wrote: > Hi all, > > I'vo got 2 service assembly : > - one with a jms consumer su. > - one with a jms provider su. > > The consumer is listening a jms queue on a broker and the provider is > writing jms message from the consumer in another queue on another broker. > > If i stop the target jms broker, serviceMix stop sending jms message and > keep messages while the target jms broker is not started. If I stop > serviceMix, It loses all messages inside!!! > > My config : > - serviceMix in persistent mode : > > <!-- the JBI container --> > <sm:container id="jbi" > rootDir="./data/smx" > MBeanServer="#jmxServer" > installationDirPath="./hotdeploy" > monitorDeploymentDirectory="false" > monitorInterval="1" > transactionManager="#transactionManager" > createJmxConnector="false" > depends-on="jndi" > persistent="true"> > > - internal activeMQ persistent mode with kaha persistence: > > <amq:broker id="broker" depends-on="jmxServer" useShutdownHook="false" > persistent="true"> > > So how to configure ServiceMix to persist his internal message if there is a > crash on its server to allow a restoration of messages when i restart > ServiceMix? > > cordialement... > > -- > Jérémy > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
