We are experiencing similar problems.
We are informed by the mbean queueSize property that around 5000 messages
are still in the queue.
This is the configuration of our broker:

        <amq:broker brokerName="mdms-broker" start="true"
dataDirectory="${importer.jms.directory}" >
                <amq:destinationPolicy>
                        <amq:policyMap>
                                <amq:policyEntries>
                                        <amq:policyEntry queue="*" 
producerFlowControl="false">
                                                <amq:dispatchPolicy>
                                                        
<amq:strictOrderDispatchPolicy/>                                                
        
                                                </amq:dispatchPolicy>
                                                <amq:subscriptionRecoveryPolicy>
                                                        
<amq:lastImageSubscriptionRecoveryPolicy/>
                                                
</amq:subscriptionRecoveryPolicy>
                                        </amq:policyEntry>
                                </amq:policyEntries>
                        </amq:policyMap>
                </amq:destinationPolicy>
                <amq:transportConnectors>
                        <amq:transportConnector
uri="${importer.jms.transportConnector.uri}"></amq:transportConnector>
                </amq:transportConnectors>
        </amq:broker>

Is there any workaround for timeout issue?

Thanks for any tip
-- 
View this message in context: 
http://old.nabble.com/Q-Consumers-stop-receiving-messages-tp21438163p26792856.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to