Unrelated to your symptom, there is a misconfiguration in your setup.
You have two inter-router connections between your routers, one
established in each direction (i.e. each router has an inter-router
listener _and_ connector). You only need one inter-router connection.
-Ted
On Mon, Jul 23,
On Mon, Jul 23, 2018 at 10:58 AM, Ted Ross wrote:
> -- Forwarded message --
> From: VERMEULEN Olivier
> Date: Mon, Jul 23, 2018 at 10:18 AM
> Subject: Inter-connected dispatch-routers
> To: "users@qpid.apache.org"
>
>
> Hello,
>
> I started 2 Dispatch-Routers (version 0.7.0)
There were 5 binding +1 votes, and no other votes received. The vote has passed.
I will add the files to the dist release repo and release the maven
staging repo shortly. The website will be updated once the artifacts
have had time to sync to the mirrors and maven central.
Robbie
Hello,
I started 2 Dispatch-Routers (version 0.7.0) and 1 Broker-J (version 7.0.3)
My first Dispatch-Router has an out autolink on a topic:
router {
id: router.10104
mode: interior
worker-threads: 4
}
listener {
host : 0.0.0.0
port: 10104
role: normal
+1
My testing included the following:
* verified signatures and checksums
* built and ran tests from source bundle
* ran Broker-J integration tests using 0.35.0 staging artefacts
On 20 July 2018 at 11:10, Robbie Gemmell wrote:
> I have put together a spin for a 0.35.0 Qpid JMS client release,
