Thanks Tim for youe feedback!
I'm using JDBC persistence adapter, storing the messages in PostgreSQL.
I'm using GroupID for ordering the messages withing the group. So, adding
more consumers does not help if message burst is from couple of groups.
I'm using memoryUsage setting to limit the memor
What was the delay between stopping and restarting the broker? Longer than
the 3-second inactivity check?
The inability to tell that a TCP connection has been severed until a
timeout has elapsed may be contributing to this problem, and may explain
the behavior is different when you shut them down
I've never seen any code that responds to slow consumers like that. There
are a few plugins that allow you to abort (i.e. disconnect) slow consumers,
but you have to enable them explicitly and you'd see logging about how the
broker was aborting them.
Are you using a persistence store, or just sto
