You could achieve it from your application logic. You could have your
producer or consumers break the JMSXGroupID stickiness by sending
JMSXGroupSeq=-1
message after producing or receiving N messages from the same groupID.
After stickiness break up, new consumers would get a chance to acquire the
g
On 11/13/2015 02:33 AM, terry wrote:
> hi all:
> need your help.
> ActiveMq version is 5.12.1, using mqtt protocol:
> I want keep alive adjust to 6 minutes, so I define, but what I setting,
> the keep alive remain 30 seconds:
>
> uri="mqtt://0.0.0.0:2883?transport.keepAlive
A single connection is a single TCP socket, which goes to a single remote
machine. There is no way to load balance a single connection across
multiple brokers. Either accept all clients being on the same broker or
create multiple connections.
Tim
On Nov 15, 2015 11:55 PM, "Emily Johnson" wrote:
Right, it's https://issues.apache.org/jira/browse/AMQ-6042
> On 14 Nov 2015, at 18:29, Tim Bain wrote:
>
> Martin,
>
> Gary's suggestion that you create a unit test to confirm the incorrect
> behavior is a good one. Also submit a bug in JIRA for this.
>
> Tim
> On Nov 12, 2015 11:51 AM, "Mart
