Hi, We are trying to understand how persistence works in ServiceMix. We have read all the documentation that we have found about it:
1- http://servicemix.apache.org/6-configuring-servicemix.html: persistent boolean If set to true, all exchanges sent to the JBI broker will have a persistence flag set to true by default. This is used to determine the QoS used, hence the flow to choose. Defaults to false 2- http://servicemix.apache.org/2-introduction.html: As an agile ESB, ServiceMix allows plug-in services which can combine to create a service oriented architecture. ServiceMix allows services to operate in an event driven way as well. In other words, the services are decoupled and listen on the bus for service requests. The bus is responsible for quality of service (QoS) features such as message persistence, guaranteed delivery, failure handling, and transaction support. 3- http://servicemix.apache.org/lightweight-components.html: JMS via the Java Messaging Service plus all of the great, reliable and scalable transports in ActiveMQ which includes persistence, recovery and transaction support. 4- http://servicemix.apache.org/component-matrix.html : JMS LW BC JMS via the Java Messaging Service plus all of the great, reliable, and scalable transports in ActiveMQ which includes persistence, recovery, and transaction support. 5- http://servicemix.apache.org/specifications.html: start if component is running, do nothing if component is shutdown, call init on its lifecycle call start persist state if not system restart if system restart, initialize all SUs (they become stopped) restore previous state (started, stopped or shutdown) We have seen, as the documentation said, that some information is stored in the data/amq directory, but we want to know what happens when ServiceMix goes down and how the persisted messages are recovered when Servicemix is restarted. Can somebody help us please? Thank in advance for any suggestion. Javier
