Re: How to forcedly close a broker side connection

How about ConnectionContext.getConnection().stop()? -- View this message in context: http://activemq.2283324.n4.nabble.com/How-to-forcedly-close-a-broker-side-connection-tp4685817p4685952.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: ActiveMQ stops delivering messages to consumers when saturating a high-latency network link

Honestly, that doesn't sound reasonable to me. ActiveMQ has no solid way to know which messages *should* or *should not* reach their destination before the TTL expires. That would require some feedback from across the broker-to-broker connection so the sending broker could take that into account.

Re: ActiveMQ broker automatically move messages with same JMSXGroupID to DLQ

That feature does not exist. It would also be tricky to implement as ActiveMQ stores messages for serial access, not random access. -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-broker-automatically-move-messages-with-same-JMSXGroupID-to-DLQ-tp4685943p4685950.