Hi,
Sorry about the DST, I didn't verify that part of the problem myself when I
got this thing to solve and included it as a (bad) example so it probably
doesn't cause any erratic behaviour in J-Broker.
My problem more specifically manifests itself in a server pair where time
(among other things)
I verified that system.currentTimeMillis returns walltime instead of
monotonic time so it cannot be used to calculate timeouts.
The problem here concerns every situation where walltime has shifted somehow
and adjusted back, for example when system clock is somehow drifted enough
and NTP is used to
Hello,
I've setup J-Broker version 6.1.4 on Windows 10 platform using OpenJDK version
9.0.0.1-ojdkbuildea and using RabbitMQ-client version 4.1.3 from .Net. The
problem is very similar to this bug description in the C++-broker:
https://bugzilla.redhat.com/show_bug.cgi?id=1080165 The broker drop
