Hi Igor,
Each node in the group monitors the state of its counterparts by sending
ping commands using "com.sleepycat.je.rep.util.DbPing".
The older versions of BDB JE environment did not react promptly on majority
loss. As result, the monitoring functionality was added to detect when
other nodes i
Broker-J 7.1.1
I have a following HA node setup:
Datacenter 1: node 1 (master)
Datacenter 2: node 2 (replica), node 3 (replica)
All nodes are set to sync because data preservation and consistency is
critical for this use-case (latency not high priority).
Ping between the two datacenters (which are
Thanks! I was able to unbrick the broker via Management Mode. It works
really well.
Concerning 417 error, browser restart didn't fix it (and the issue was only
happening with just 1 of the 3 nodes). I restarted the broker and it works
OK for now, I'll just monitor it a bit.
On Wed, Apr 10, 2019 at
On 11/04/2019 10:07 am, Toralf Lund wrote:
On 11/04/2019 09:39, Toralf Lund wrote:
On 10/04/2019 18:18, Gordon Sim wrote:
On 10/04/2019 10:10 am, Toralf Lund wrote:
Hi,
In one of my C++ "messaging" programs I sometimes use
qpid::Messaging::Session::checkError() as a way to "rethrow" (in as
On 11/04/2019 09:39, Toralf Lund wrote:
On 10/04/2019 18:18, Gordon Sim wrote:
On 10/04/2019 10:10 am, Toralf Lund wrote:
Hi,
In one of my C++ "messaging" programs I sometimes use
qpid::Messaging::Session::checkError() as a way to "rethrow" (in as
somewhat loose sense) sender or receiver exc
On 10/04/2019 18:18, Gordon Sim wrote:
On 10/04/2019 10:10 am, Toralf Lund wrote:
Hi,
In one of my C++ "messaging" programs I sometimes use
qpid::Messaging::Session::checkError() as a way to "rethrow" (in as
somewhat loose sense) sender or receiver exceptions that were already
caught elsewhe
