JIRA: https://issues.apache.org/jira/browse/AMQ-
I'm running now with a patched version without the "command.isMessage()"
condition and fail-over behaviour has substantially improved.
Can't really judge whether it is the correct fix, however.
- Martin
On 30.04.2017 18:50, Tim Bain wrote:
It does seem like there needs to be another path out of that code block,
though I wonder if the expectation was that nothing that wasn't a message
would ever make it to that block. Either way, it seems to not be working
the way it should, so please submit a bug in JIRA for the problem.
Tim
On Apr
I'm running into a situation with the Failover Transport not respecting the
timeout that's been set.
The symptom is endless messages of this kind:
2017-04-29 09:48:26,128 | TRACE | .engine.cfgengine.in]-11 | FailoverTransport
| sport.failover.FailoverTransport 615 | 81 -
org.apa
