Hi Guys,
‘SslEngineFacadeFactory’ uses reflection on some bouncy-castle classes to load
certificates and keys from the configured PEM files.
Currently the code expects to find ‘org.bouncycastle.openssl.PEMReader’ but
this has been removed and as far as I can tell
On 26 April 2016 at 17:37, Robbie Gemmell wrote:
> As per the subject, I'd like to suggest removing
> 'proton/contrib/proton-hawtdispatch' module.
>
> hawtdispatch itself doesn't appear to be seeing any development these
> days, with only a handful of commits in the last
On 26 April 2016 at 15:41, Robbie Gemmell wrote:
> As per the subject, I'd like to suggest removing
> 'proton/contrib/proton-jms' module.
>
> It was written as part of adding AMQP 1.0 support to the ActiveMQ 5.x
> broker and then contributed to Proton, and used across
Another update. CI is now in decent, if not perfect, shape. I've added
lots of suppressions for apparently real memory leaks. I'll send a
separate email regarding those.
Now that the vote on the migration to git has passed, I've raised two INFRA
jiras to start the migration process:
If someone wants to point me at the doc for the C++ broker extensions to
the selector syntax, I'll try to find some time to add support. Obviously
we are still waiting on the official JMS over AMQP spec to define a
complete filter syntax (hint: Robbie).
-- Rob
On 3 May 2016 9:17 a.m., "Vavricka"
Gordon Sim wrote
> For the timestamp query, why are you dividing by 1000? The JMSTimestamp is
> in milliseconds. Is 'tomorrow' a Date object?
Thanks for pointing this out, I used same code for testing qpid c++ broker.
Qpid c++ broker expects timestamp in seconds.
When I removed division by