On Thu, 2014-10-23 at 15:57 +, Steve Huston wrote:
> I'm in favor of this.
> -Steve
>
Thanks, I'm going ahead. The code changes are checked in, I just need to
put together some documentation and release notes.
> > -Original Message-
> > From: Alan Conway [mailto:acon...@redhat.com]
>
I'm in favor of this.
-Steve
> -Original Message-
> From: Alan Conway [mailto:acon...@redhat.com]
> Sent: Monday, October 20, 2014 1:37 PM
> To: users@qpid.apache.org
> Cc: Ted Ross
> Subject: [dispatch] management compatibilitiy for next release.
>
> I'd like to make some incompatible ch
On 10/23/2014 03:58 PM, Chris Richardson wrote:
Hi,
I've just found a problem configuring a 0.30 broker with TLS but without
SASL - the broker rejects connections as unencrypted while a packet trace
shows that the connection is, in fact, decidedly encrypted (as with a
working system, certificate
Hi,
I've just found a problem configuring a 0.30 broker with TLS but without
SASL - the broker rejects connections as unencrypted while a packet trace
shows that the connection is, in fact, decidedly encrypted (as with a
working system, certificate transfer can be seen in packet 6 after inital
TCP
On Thu, 2014-10-23 at 16:19 +0200, Andreas Welchlin wrote:
> Hi List,
>
> I saw the following message when I wanted to create a transactional session:
>
> "Transactions not yet supported"
>
>
> I am currently using qpid 0.28 with AMQP 1.0.
>
> In former times when I used AMQP 0.10 the tra
Hi List,
I saw the following message when I wanted to create a transactional session:
"Transactions not yet supported"
I am currently using qpid 0.28 with AMQP 1.0.
In former times when I used AMQP 0.10 the transaction support was there.
What can I do to get transaction support with AMQP
