l
>
> Thanks,
> Anuj
>
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/ActiveMQ-JDBC-with-journaling-enabled-tp4725234p4725239.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/ActiveMQ-JDBC-with-journaling-enabled-tp4725234p4725239.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
/Clustering_Guide/files/Failover-MasterSlave-JDBC.html
Thanks,
Anuj
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-JDBC-with-journaling-enabled-tp4725234p4725239.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
end DB, but
> > since backend DB doesn't have the message. So is it lost ? "
> >
>
> I'm not 100% following the scenario here. But in short, if you are using
> persistent messages (or an appropriate quality of service). You'll never
> get in a situation
, if you are using
persistent messages (or an appropriate quality of service). You'll never
get in a situation where you have messages lost. This is one of the
fundamental requirements of the broker.
>
> Thanks,
> Anuj
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/ActiveMQ-JDBC-with-journaling-enabled-tp4725234.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
nd DB, but
since backend DB doesn't have the message. So is it lost ? "
Thanks,
Anuj
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-JDBC-with-journaling-enabled-tp4725234.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
