[SECURITY] CVE-2017-15699: Apache Qpid Dispatch Router Denial of Service Vulnerability when specially crafted frame is sent to the Router

CVE-2017-15699: Apache Qpid Dispatch Router Denial of Service Vulnerability when specially crafted frame is sent to the Router Severity: Important Vendor: The Apache Software Foundation Versions Affected: Versions 0.7.0 and 0.8.0 Description: A Denial of Service vulnerability was found in

[ANNOUNCE] Apache Qpid Dispatch 0.8.1 released

The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid Dispatch 0.8.1. Qpid Dispatch is a router for the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org). It provides a flexible and scalable

Re: C++ imperative client API

On Tue, Feb 13, 2018 at 8:30 AM, Rabih M wrote: > Hello, > > As Olivier said at Murex we wrote a small C++ client with an imperative API > that wraps proton. At that time we did not know that the community had > plans to develop one. > > The API we wrote was inspired

Re: Stopping JMS Connection with unprocessed prefetched messages results in message moved to DLQ

I think I found why this behavior was occurring but I think I might have uncovered a bug with JMQ queue browsing... I tested with another source queue and there were no messages were being moved to the DLQ for that queue - the stayed on the source queue after the connection was closed and that is

Re: Stopping JMS Connection with unprocessed prefetched messages results in message moved to DLQ

I just ran another test where I set the url to have a maxprefetch of 0: String brokerUrl = "amqp:///spgqpiddev?maxprefetch='0'='tcp://spgappdevmutil:5672'"; And it still ended up moving 2 messages to the DLQ after the connection was stopped. I'm really confused about this behavior. -- Sent

Stopping JMS Connection with unprocessed prefetched messages results in message moved to DLQ

I'm using qpid-broker-j-7.0.1, qpid-jms-amqp-0-x-6.3.0 and JDK 1.8. We have a Java app that using using a JMS MessageListener to consume message from a Queue. Occasionally we want to stop message consumption on the Listener and then restart it. To stop message consumption I simply call the

Re: Error installing python-qpid-proton 0.20.0

Hi Yanislav The python binding attempts to build the C module using the development environment available on the system where the binding is installed. The setup.py script does its best to figure out which C libraries are available so it can avoid building optional features when libraries are

Re: [jira] [Closed] (PROTON-1755) How do create sessions and links dynamically once the connection is open ?

Yes, there is only one onConnectionBound event, when the connection object is initially bound to the transport object. You can create a session later by doing it in essentially any callback, the main concern is purely that the work is performed on the thread running the reactor, as all your

Re: C++ imperative client API

Hello, As Olivier said at Murex we wrote a small C++ client with an imperative API that wraps proton. At that time we did not know that the community had plans to develop one. The API we wrote was inspired from JMS (connection, session, messaging producer, messaging consumer...). So the whole

Re: Can't connect to ActiveMQ's AMQP transport connector using Qpid JMS

Were you able to get things going? The client is regularly tested against ActiveMQ and other servers, though your issue would seem to be independent of the server in use since its occuring prior to any connection. In particular, its failing to configure some internals of the client in a way I

Re: qpid-broker-j-7.0.1 Simple LDAP and Group Providers

Hello Bryan On 12 February 2018 at 21:01, bryand wrote: > I'm trying to get Simple LDAP setup with qpid-broker-j-7.0.1. I noticed in > the documentation that you can configure group info with LDAP. Yes, that's right. The SimpleLDAP authentication provider allows you to