Hi, I’m using brokers in bridge mode(store & forward), where brokers B1 and B2 are running in separate machines, The problem I’m seeing is when ever B1 MQ consumers are up, the zero sized MQ files(as shown below)are created at B2. Since we may expect to have several ten thousands of consumers at B1, we don’t want to see huge number of empty files at B2. Environment: Linux, CMS and NMS clients, where clients may on at both windows/linux
/apache-activemq-5.2.0/data/kr-store/data -rw-r--r-- 1 root root 2498 Sep 29 06:52 data-container-roots-1 -rw-r--r-- 1 root root 0 Sep 29 06:52 hash-index-queue-data_queue#3a#2f#2fCA.DA.444.CMD.MQ -rw-r--r-- 1 root root 0 Sep 29 06:52 hash-index-queue-data_queue#3a#2f#2fCA.DA.444.DOC.MQ -rw-r--r-- 1 root root 0 Sep 29 06:52 hash-index-queue-data_queue#3a#2f#2fCA.DV.111.CMD.MQ -rw-r--r-- 1 root root 0 Sep 29 06:52 hash-index-queue-data_queue#3a#2f#2fCA.DV.111.DOC.MQ -rw-r--r-- 1 root root 0 Sep 29 06:52 hash-index-queue-data_queue#3a#2f#2fCA.RV.333.CMD.MQ -rw-r--r-- 1 root root 0 Sep 29 06:52 hash-index-queue-data_queue#3a#2f#2fCA.RV.333.DOC.MQ -rw-r--r-- 1 root root 0 Sep 29 06:52 hash-index-queue-data_queue#3a#2f#2fMA.555.CMD.MQ -rw-r--r-- 1 root root 0 Sep 29 06:52 hash-index-queue-data_queue#3a#2f#2fMA.555.DOC.MQ-rw-r--r-- 1 root root 561 Sep 29 06:52 index-container-roots -rw-r--r-- 1 root root 459 Sep 29 06:52 index-queue-data Let me know is there any way to preventing to create these files at B2 broker? Thanks Raju -- View this message in context: http://www.nabble.com/Empty-MQ-files-at-broker-2-in-in-the-store---forward-bridge-mode-tp25661282p25661282.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
