If you can live with possible message loss, which seems to be the case if the client does not want to wait then use the ActiveMQ connection factory property useAsyncSend. For persistence messages this defaults to false, such that the client waits till the message is stored, but when true, even persistence messages will be sent async and the client will not have to wait. This can be set on the broker connection Url also: use the query parameter: failover:(tcp://localhost:61616)?jms.useAsyncSend=true
On 28 October 2010 19:18, kseelam <krishna_see...@hotmail.com> wrote: > > Hi All > > We have a situation where we want to Persist the messages in the permanent > DB but first temporarily store in the memory(or similar) and 'some time > later' persist the messages in the DB. So that client don't wait till the > messages are written in the DB. > > We understand the Journal concept. But we want to achieve this in > Master/Slave approach by using one Mysql DB for HA. Other threads suggest > Journal does not work well for Master/Slave approach. So its limitation. > > We really struck of choosing the best approach. > > Just wondering any other workarounds or suggestions. > > Thank you all. > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Persistence-delay-in-JDBC-Master-Slave-approach-tp3017852p3017852.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- http://blog.garytully.com http://fusesource.com
