-
This happens only on QPid Dispatch which uses AMQP protocol. The code is using QPid JMS 0.27.
> javax.jms.JMSException: Delivery failed: released by receiver
> at org.apache.qpid.jms.prov…
-
When testing messaging components capable of very large throughputs (such as the Qpid Dispatch Router with ```anycast``` addresses), the volume of data generated by Maestro can be problematic both in …
-
Having deployed Prometheus in EnMasse, the `metrics` container in the `qdrouterd` pod seems to stop working after it has done 4 router requests.
`Metrics` component log (with some added output and …
-
**Problem**
It is often hard to follow specific problems from end-to-end. This is true in particular with many different devices talking to Hono with different adapters on one side and also many di…
-
The Qpid Dispatch Router used by enMasse is able to delegate authentication of clients to another component (very similar to the way that Hono services delegate to Hono Auth for that purpose).
The …
-
I am using the Qpid broker, but this should be reproducible with RabbitMQ.
1) Start a single celeryd worker with a single worker process, and configure that worker to use `CELERY_WORKER_DIRECT = True…
-
Testing with 1000 devices sending telemetry messages with a target throughput over all devices of 200 messages per second, we have noticed that the dispatch router crashed multiple times with the foll…
-
This ticket shall track the update of the "qdrouterd-base" docker image to include Qpid Dispatch 1.0.1.
Eclipse Hono uses the "qdrouterd-base" as well and it would be good to have the latest fixes co…
-
const client = require('rhea')
client.connect({'host': 'localhost', 'port': 5671, 'username': 'admin', 'password': 'admin'})
client.on('connection_open', function (context) {
c…
-
JMS subscriber raises Timed Out Waiting for close response: AmqpConsumer when receives messages from topic in standard address space. this situation is not 100% reproducible but it happens very often.…