Hi all,
I don't know if this is a bug or there is a specific reason to be
implemented in that way. So:
Goal:
Start 2 embedded MQTT brokers for integration tests purposes. Both brokers
have different SSLContexts with different keystores with different
certificates.
Expected Result:
Both brokers
Looks like I made a bit of a git foobar when cherry-picking the commits
from master on the 1.x branch. I will rectify this. Thanks for pointing
this out.
On Fri, Feb 10, 2017 at 2:06 PM, Francesco PADOVANI <
francesco.padov...@bticino.it> wrote:
> Sorry Martyn,
>
> about the clientID lenght:
Sorry Martyn,
about the clientID lenght: it was a problem of my mqtt Client which had the
compatibility with mqtt 3.1.1 disabled (stupid me).
Instead, I confirm to you the lack of fixing for weird chars on messages
recovered from journal.
Francesco
From:
Hi Martyn,
we're testing your 1.6.0 snapshot.
The issues related to retained messages ACK and durable queues seem ok now.
Great!
I noticed that this snapshot doesn't include the fix for weird chars when
messages are recovered from journal: do you think it will be included in 1.5.3
release?
Hello aphor,
I managed to get it working by doing the following 2 things:
1. In the JNDI provider on the Weblogic server in the provider URL I used
the property *jms.prefetchPolicy.all=0* i.e.
tcp://:61616?jms.prefetchPolicy.all=0
2. In the OSB proxy flow if you have a "Service Callout" or a
