Re: Dead letter queue not being created

Jira created. https://issues.apache.org/activemq/browse/AMQ-2756 https://issues.apache.org/activemq/browse/AMQ-2756 KRISHNAS wrote: > > Gary > > 5.4-SNAPSHOT has the same issue. Looks like addMessage method of > JDBCMessageStore class has changed in 5.3.1. The followin

Re: Dead letter queue not being created

Gary 5.4-SNAPSHOT has the same issue. Looks like addMessage method of JDBCMessageStore class has changed in 5.3.1. The following code is added to it, seems it is stopping to persist in the DB. public void addMessage(ConnectionContext context, Message message) throws IOException {

Re: Dead letter queue not being created

Gary We have this issue with persistent messages. We are using ActiveMQ 5.3.2. We defined persistence adaptor as below: Our persistent messages are storing FINE in the 'activemq_msgs' table in the DB (verified by select statement). We also see the messages

Re: How to use the File System for locking purpose and use the DB for Message Persistency only?

Thanks Gary That clears all our confusions. ok. I understand the confusion now. I have fixed the incorrect configuration example in https://cwiki.apache.org/confluence/display/ACTIVEMQ/Shared+File+System+Master+Slave -- View this message in context: http://old.nabble.com/How-to-use-the-F

Re: How to use the File System for locking purpose and use the DB for Message Persistency only?

also ActiveMQ says; The following example shows how to configure the broker for Shared File System Master Slave where /sharedFileSystem is some directory on a shared file system So the "Shared file system master slave" approach uses the common Journal + common DB (Here derby d

Re: How to use the File System for locking purpose and use the DB for Message Persistency only?

you still say this is NOT appropriate for Failover. THANK YOU. Gary Tully wrote: > > Shared file system master slave is fine. > The problem is with "journal + jdbc" as the journal part of that is local > to > a broker instance. > > > On 29 April 2010 17:02,

Re: How to use the File System for locking purpose and use the DB for Message Persistency only?

te. Do you see any cons of it? Thank you for replies. Gary Tully wrote: > > For fail over, the batching nature of the journal is not appropriate, you > need to send messages directly to the store, either jdbc or file based. > > On 29 April 2010 02:51, KRISHNAS wrote: > >&g

Re: How to use the File System for locking purpose and use the DB for Message Persistency only?

Thanks lot for your reply Gary, We have also looked at the 'jdbc statemetns', unfortunately as per DB2, any statement on the lock table - could cause error, so jdbc statements may not help (Still we are investigating though) So we have to use either specific data source for the locking or we m

Is there any way to contol the checkpointInterval in High performance journal ?

Hi, We are new to ActiveMq and looking at the Journal. Our config is as below. this works fine. But a coupls of questions. Is there any way to control the checkpointInterval in Journal ? Also If we understand correctly, by setting journalLogFileSize="1024", once the journal

How to use the File System for locking purpose and use the DB for Message Persistency only?

We are planning to use "Clustering - JDBC Master Slave" approach for Failover and using the Shared DB by multiple brokers When the Master Broker is started, it puts a lock on the lock table. When the Slave Broker started it keeps check the lock (whether the lock was released by Master or not