[jira] [Assigned] (QPID-3333) Make Python SWIG bindings a drop-in replacement for pure Python qpid.messaging package

[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned QPID-: Assignee: Gordon Sim > Make Python SWIG bindings a drop-in replacement for pure Python > qpid.messa

[jira] [Commented] (QPID-3333) Make Python SWIG bindings a drop-in replacement for pure Python qpid.messaging package

[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061511#comment-13061511 ] Gordon Sim commented on QPID-: -- fyi: I'm going to commit this patch next week. If anyo

[jira] [Commented] (QPID-3333) Make Python SWIG bindings a drop-in replacement for pure Python qpid.messaging package

[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061516#comment-13061516 ] Gordon Sim commented on QPID-: -- Spooky! You commented at (almost) exactly the same tim

[jira] [Commented] (QPID-3333) Make Python SWIG bindings a drop-in replacement for pure Python qpid.messaging package

[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064044#comment-13064044 ] Gordon Sim commented on QPID-: -- Committed patches 0001-0008 as r1145698. I'll leave th

[jira] [Commented] (QPID-3333) Make Python SWIG bindings a drop-in replacement for pure Python qpid.messaging package

[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064046#comment-13064046 ] Gordon Sim commented on QPID-: -- Re auto_delete v. auto-delete, we probably want to sup

[jira] [Commented] (QPID-3355) Client aborts when replaying sender after connection recovery

[ https://issues.apache.org/jira/browse/QPID-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064459#comment-13064459 ] Gordon Sim commented on QPID-3355: -- I have committed this patch since it is logically cons

[jira] [Resolved] (QPID-3355) Client aborts when replaying sender after connection recovery

[ https://issues.apache.org/jira/browse/QPID-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3355. -- Resolution: Fixed Fix Version/s: 0.13 > Client aborts when replaying sender after connection reco

[jira] [Created] (QPID-3356) Dynamic Federation doesn't work as expected for headers exchange

Dynamic Federation doesn't work as expected for headers exchange Key: QPID-3356 URL: https://issues.apache.org/jira/browse/QPID-3356 Project: Qpid Issue Type: Bug Com

[jira] [Updated] (QPID-3356) Dynamic Federation doesn't work as expected for headers exchange

[ https://issues.apache.org/jira/browse/QPID-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated QPID-3356: - Description: start two brokers, link amq.match using a dynamic route in one direction, start two subscrib

[jira] [Commented] (QPID-3356) Dynamic Federation doesn't work as expected for headers exchange

[ https://issues.apache.org/jira/browse/QPID-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065213#comment-13065213 ] Gordon Sim commented on QPID-3356: -- The AMQP spec requires the exchange+queue+bindingkey t

[jira] [Created] (QPID-3363) broker allows unbind on default exchange

broker allows unbind on default exchange Key: QPID-3363 URL: https://issues.apache.org/jira/browse/QPID-3363 Project: Qpid Issue Type: Bug Affects Versions: 0.10, 0.12 Reporter: Gordon

[jira] [Created] (QPID-3372) Asserting on arguments does not work for exchanges; incorrectly throws exception

Asserting on arguments does not work for exchanges; incorrectly throws exception Key: QPID-3372 URL: https://issues.apache.org/jira/browse/QPID-3372 Project: Qpid

[jira] [Resolved] (QPID-3372) Asserting on arguments does not work for exchanges; incorrectly throws exception

[ https://issues.apache.org/jira/browse/QPID-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3372. -- Resolution: Fixed > Asserting on arguments does not work for exchanges; incorrectly throws > exception

[jira] [Assigned] (QPID-3375) qpid-route does not resolve hostname and this causes problems with localhost among others

[ https://issues.apache.org/jira/browse/QPID-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned QPID-3375: Assignee: Gordon Sim > qpid-route does not resolve hostname and this causes problems with localhost

[jira] [Commented] (QPID-3375) qpid-route does not resolve hostname and this causes problems with localhost among others

[ https://issues.apache.org/jira/browse/QPID-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072900#comment-13072900 ] Gordon Sim commented on QPID-3375: -- Yes, its really the latter. In general we connect to t

[jira] [Created] (QPID-3382) Incorrect exceptions thrown from qpid::messaging::Connection::open()

Incorrect exceptions thrown from qpid::messaging::Connection::open() Key: QPID-3382 URL: https://issues.apache.org/jira/browse/QPID-3382 Project: Qpid Issue Type: Bug A

[jira] [Created] (QPID-3383) qpid-perftest sometimes hangs when using --iterations greater than 1 and a large number of publishers

qpid-perftest sometimes hangs when using --iterations greater than 1 and a large number of publishers -- Key: QPID-3383 URL: https://issues.apache.org/jira/browse

[jira] [Resolved] (QPID-3383) qpid-perftest sometimes hangs when using --iterations greater than 1 and a large number of publishers

[ https://issues.apache.org/jira/browse/QPID-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3383. -- Resolution: Fixed > qpid-perftest sometimes hangs when using --iterations greater than 1 and a > large

[jira] [Resolved] (QPID-3382) Incorrect exceptions thrown from qpid::messaging::Connection::open()

[ https://issues.apache.org/jira/browse/QPID-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3382. -- Resolution: Fixed Now at least connectivity related errors are correctly signalled and distinguishable

[jira] [Commented] (QPID-3263) Java (org.apache.qpid.client) XAResourceImpl always returns false for isSameRM

[ https://issues.apache.org/jira/browse/QPID-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073646#comment-13073646 ] Gordon Sim commented on QPID-3263: -- Looks fine to me. (I might have been tempted to call t

[jira] [Created] (QPID-3393) CRAM-MD5 does not work

CRAM-MD5 does not work -- Key: QPID-3393 URL: https://issues.apache.org/jira/browse/QPID-3393 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.10, 0.12 Reporter: Gordon Si

[jira] [Commented] (QPID-3333) Make Python SWIG bindings a drop-in replacement for pure Python qpid.messaging package

[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079376#comment-13079376 ] Gordon Sim commented on QPID-: -- Possibly, I'll see if I can get a RHEL5.3 to debug. On

[jira] [Resolved] (QPID-3393) CRAM-MD5 does not work

[ https://issues.apache.org/jira/browse/QPID-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3393. -- Resolution: Fixed > CRAM-MD5 does not work > -- > > Key: QPID-3393 >

[jira] [Commented] (QPID-3333) Make Python SWIG bindings a drop-in replacement for pure Python qpid.messaging package

[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079383#comment-13079383 ] Gordon Sim commented on QPID-: -- Doh, just forgot to install python-devel. With that do

[jira] [Commented] (QPID-3333) Make Python SWIG bindings a drop-in replacement for pure Python qpid.messaging package

[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079418#comment-13079418 ] Gordon Sim commented on QPID-: -- Fixed in r1153906. > Make Python SWIG bindings a dro

[jira] [Created] (QPID-3400) Released (and redundant) delivery records not removed

Released (and redundant) delivery records not removed - Key: QPID-3400 URL: https://issues.apache.org/jira/browse/QPID-3400 Project: Qpid Issue Type: Bug Components: C++ Broker

[jira] [Updated] (QPID-3375) qpid-route does not resolve hostname and this causes problems with localhost among others

[ https://issues.apache.org/jira/browse/QPID-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated QPID-3375: - Attachment: QPID-3375.patch Suggested alternative fix. I think this is a little simpler and more direct.

[jira] [Resolved] (QPID-3400) Released (and redundant) delivery records not removed

[ https://issues.apache.org/jira/browse/QPID-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3400. -- Resolution: Fixed > Released (and redundant) delivery records not removed >

[jira] [Commented] (QPID-3375) qpid-route does not resolve hostname and this causes problems with localhost among others

[ https://issues.apache.org/jira/browse/QPID-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081717#comment-13081717 ] Gordon Sim commented on QPID-3375: -- I'm neutral on the warning v. error question. The key

[jira] [Resolved] (QPID-3363) broker allows unbind on default exchange

[ https://issues.apache.org/jira/browse/QPID-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3363. -- Resolution: Fixed > broker allows unbind on default exchange >

[jira] [Commented] (QPID-3375) qpid-route does not resolve hostname and this causes problems with localhost among others

[ https://issues.apache.org/jira/browse/QPID-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081914#comment-13081914 ] Gordon Sim commented on QPID-3375: -- I think we are simply trying to reduce a common error.

[jira] [Assigned] (QPID-3403) Empty bindings are not internally pruned from the direct exchange

[ https://issues.apache.org/jira/browse/QPID-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned QPID-3403: Assignee: Gordon Sim > Empty bindings are not internally pruned from the direct exchange > -

[jira] [Updated] (QPID-3403) Empty bindings are not internally pruned from the direct exchange

[ https://issues.apache.org/jira/browse/QPID-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated QPID-3403: - Attachment: QPID-3403.patch I think you have attached the wrong patch here? Suggested patch attached. Goo

[jira] [Resolved] (QPID-3403) Empty bindings are not internally pruned from the direct exchange

[ https://issues.apache.org/jira/browse/QPID-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3403. -- Resolution: Fixed > Empty bindings are not internally pruned from the direct exchange >

[jira] [Commented] (QPID-3333) Make Python SWIG bindings a drop-in replacement for pure Python qpid.messaging package

[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082550#comment-13082550 ] Gordon Sim commented on QPID-: -- One question on the 0009 patch: How are you triggering

[jira] [Created] (QPID-3411) Can't turn off x-reconnect-on-limit-exceeded

Can't turn off x-reconnect-on-limit-exceeded Key: QPID-3411 URL: https://issues.apache.org/jira/browse/QPID-3411 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions

[jira] [Resolved] (QPID-3411) Can't turn off x-reconnect-on-limit-exceeded

[ https://issues.apache.org/jira/browse/QPID-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3411. -- Resolution: Fixed > Can't turn off x-reconnect-on-limit-exceeded > -

[jira] [Commented] (QPID-3403) Empty bindings are not internally pruned from the direct exchange

[ https://issues.apache.org/jira/browse/QPID-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083044#comment-13083044 ] Gordon Sim commented on QPID-3403: -- That's a good suggestion; I've added that test in. >

[jira] [Commented] (QPID-3412) Python and C++ clients translate address differently

[ https://issues.apache.org/jira/browse/QPID-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083056#comment-13083056 ] Gordon Sim commented on QPID-3412: -- "response/response.hey_Joe" is *not* translated to "re

[jira] [Assigned] (QPID-3412) Python and C++ clients translate address differently

[ https://issues.apache.org/jira/browse/QPID-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned QPID-3412: Assignee: Gordon Sim > Python and C++ clients translate address differently > --

[jira] [Commented] (QPID-3412) Python and C++ clients translate address differently

[ https://issues.apache.org/jira/browse/QPID-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083082#comment-13083082 ] Gordon Sim commented on QPID-3412: -- To illustrate the point in previous comment, consider

[jira] [Updated] (QPID-3412) Python and C++ clients use link name option differently

[ https://issues.apache.org/jira/browse/QPID-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated QPID-3412: - Summary: Python and C++ clients use link name option differently (was: Python and C++ clients translate a

[jira] [Resolved] (QPID-3412) Python and C++ clients use link name option differently

[ https://issues.apache.org/jira/browse/QPID-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3412. -- Resolution: Fixed Fix Version/s: 0.13 > Python and C++ clients use link name option differently >

[jira] [Commented] (QPID-3417) Support for timestamping messages on arrival at the broker.

[ https://issues.apache.org/jira/browse/QPID-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084183#comment-13084183 ] Gordon Sim commented on QPID-3417: -- Are you saying you could set the message timestamp its

[jira] [Commented] (QPID-3417) Support for timestamping messages on arrival at the broker.

[ https://issues.apache.org/jira/browse/QPID-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084194#comment-13084194 ] Gordon Sim commented on QPID-3417: -- That's what I thought, those names are indeed better.

[jira] [Created] (QPID-3425) Using create mode (e.g. for x-bindings) with standard exchanges does not work

Using create mode (e.g. for x-bindings) with standard exchanges does not work - Key: QPID-3425 URL: https://issues.apache.org/jira/browse/QPID-3425 Project: Qpid Iss

[jira] [Resolved] (QPID-3425) Using create mode (e.g. for x-bindings) with standard exchanges does not work

[ https://issues.apache.org/jira/browse/QPID-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3425. -- Resolution: Fixed > Using create mode (e.g. for x-bindings) with standard exchanges does not work >

[jira] [Commented] (QPID-3333) Make Python SWIG bindings a drop-in replacement for pure Python qpid.messaging package

[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086431#comment-13086431 ] Gordon Sim commented on QPID-: -- Thanks! Regarding the NotAttachedException, I don't be

[jira] [Commented] (QPID-3333) Make Python SWIG bindings a drop-in replacement for pure Python qpid.messaging package

[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086434#comment-13086434 ] Gordon Sim commented on QPID-: -- and obviously if it maps to RuntimeException then ther

[jira] [Created] (QPID-3435) Reconnect during Session::close can cause an infinite loop

Reconnect during Session::close can cause an infinite loop -- Key: QPID-3435 URL: https://issues.apache.org/jira/browse/QPID-3435 Project: Qpid Issue Type: Bug Affects Versions: 0.1

[jira] [Resolved] (QPID-3435) Reconnect during Session::close can cause an infinite loop

[ https://issues.apache.org/jira/browse/QPID-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3435. -- Resolution: Fixed > Reconnect during Session::close can cause an infinite loop > ---

[jira] [Assigned] (QPID-3445) Assertion, and unexpected exception in qpid::messaging::decode

[ https://issues.apache.org/jira/browse/QPID-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned QPID-3445: Assignee: Gordon Sim > Assertion, and unexpected exception in qpid::messaging::decode >

[jira] [Commented] (QPID-3445) Assertion, and unexpected exception in qpid::messaging::decode

[ https://issues.apache.org/jira/browse/QPID-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088647#comment-13088647 ] Gordon Sim commented on QPID-3445: -- Looks good to me. Can you attach that patch as a file

[jira] [Assigned] (QPID-3443) the C++ broker uses the wrong exception type when clients try to modify the default exchange

[ https://issues.apache.org/jira/browse/QPID-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned QPID-3443: Assignee: Gordon Sim > the C++ broker uses the wrong exception type when clients try to modify the

[jira] [Resolved] (QPID-3443) the C++ broker uses the wrong exception type when clients try to modify the default exchange

[ https://issues.apache.org/jira/browse/QPID-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3443. -- Resolution: Fixed Fix Version/s: (was: Future) 0.13 Fixed (note the except

[jira] [Commented] (QPID-3443) the C++ broker uses the wrong exception type when clients try to modify the default exchange

[ https://issues.apache.org/jira/browse/QPID-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089411#comment-13089411 ] Gordon Sim commented on QPID-3443: -- There is an illegal argument code as well(!), just not

[jira] [Resolved] (QPID-3445) Assertion, and unexpected exception in qpid::messaging::decode

[ https://issues.apache.org/jira/browse/QPID-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3445. -- Resolution: Fixed Fix Version/s: 0.13 > Assertion, and unexpected exception in qpid::messaging::d

[jira] [Updated] (QPID-3451) c++ version of drain only drains one message by default...

[ https://issues.apache.org/jira/browse/QPID-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated QPID-3451: - Component/s: Qpid Examples C++ Client > c++ version of drain only drains one message by d

[jira] [Created] (QPID-3451) c++ version of drain only drains one message by default...

c++ version of drain only drains one message by default... -- Key: QPID-3451 URL: https://issues.apache.org/jira/browse/QPID-3451 Project: Qpid Issue Type: Improvement Repor

[jira] [Resolved] (QPID-3451) c++ version of drain only drains one message by default...

[ https://issues.apache.org/jira/browse/QPID-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3451. -- Resolution: Fixed > c++ version of drain only drains one message by default... > ---

[jira] [Created] (QPID-3455) Large message sent over sasl_wrapper encryption layer causes infinite loop in broker

Large message sent over sasl_wrapper encryption layer causes infinite loop in broker Key: QPID-3455 URL: https://issues.apache.org/jira/browse/QPID-3455 Project: Qpi

[jira] [Resolved] (QPID-3455) Large message sent over sasl_wrapper encryption layer causes infinite loop in broker

[ https://issues.apache.org/jira/browse/QPID-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3455. -- Resolution: Fixed > Large message sent over sasl_wrapper encryption layer causes infinite loop in > bro

[jira] [Assigned] (QPID-3456) Python and C++ clients behave differently

[ https://issues.apache.org/jira/browse/QPID-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned QPID-3456: Assignee: Gordon Sim > Python and C++ clients behave differently > -

[jira] [Commented] (QPID-3333) Make Python SWIG bindings a drop-in replacement for pure Python qpid.messaging package

[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094393#comment-13094393 ] Gordon Sim commented on QPID-: -- Thanks Anthony! I've committed patches 0009 through 00

[jira] [Created] (QPID-3460) Better support for non-blocking usage in messaging API

Better support for non-blocking usage in messaging API -- Key: QPID-3460 URL: https://issues.apache.org/jira/browse/QPID-3460 Project: Qpid Issue Type: Improvement Components: C++

[jira] [Created] (QPID-3476) Timer warnings are too verbose

Timer warnings are too verbose -- Key: QPID-3476 URL: https://issues.apache.org/jira/browse/QPID-3476 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.12 Reporter:

[jira] [Commented] (QPID-3464) Fix QPID Build on Debian Squeeze

[ https://issues.apache.org/jira/browse/QPID-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099279#comment-13099279 ] Gordon Sim commented on QPID-3464: -- Patches apply to trunk fine for me and build and test

[jira] [Resolved] (QPID-3476) Timer warnings are too verbose

[ https://issues.apache.org/jira/browse/QPID-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3476. -- Resolution: Fixed > Timer warnings are too verbose > -- > >

[jira] [Commented] (QPID-3481) Acquired messages are not sent to alternate exchange when queue is deleted and receiver's session closed

[ https://issues.apache.org/jira/browse/QPID-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103565#comment-13103565 ] Gordon Sim commented on QPID-3481: -- Deleting a queue before you have released or accepted

[jira] [Commented] (QPID-3481) Acquired messages are not sent to alternate exchange when queue is deleted and receiver's session closed

[ https://issues.apache.org/jira/browse/QPID-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103674#comment-13103674 ] Gordon Sim commented on QPID-3481: -- Why do you want to delete the queue on closing the rec

[jira] [Resolved] (QPID-3487) Client should send completions when closing a receiver

[ https://issues.apache.org/jira/browse/QPID-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3487. -- Resolution: Fixed Fix Version/s: 0.13 Assignee: Gordon Sim > Client should send completi

[jira] [Commented] (QPID-3487) Client should send completions when closing a receiver

[ https://issues.apache.org/jira/browse/QPID-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105297#comment-13105297 ] Gordon Sim commented on QPID-3487: -- I believe the correct fix here is to ensure the broker

[jira] [Assigned] (QPID-3488) Setting receiver capacity to zero does not always stop the message flow

[ https://issues.apache.org/jira/browse/QPID-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned QPID-3488: Assignee: Gordon Sim > Setting receiver capacity to zero does not always stop the message flow > ---

[jira] [Resolved] (QPID-3488) Setting receiver capacity to zero does not always stop the message flow

[ https://issues.apache.org/jira/browse/QPID-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3488. -- Resolution: Fixed Fix Version/s: 0.13 > Setting receiver capacity to zero does not always stop th

[jira] [Created] (QPID-3492) String values in address are parsed as binary (and sent as vbin16/32 rather than str16)

String values in address are parsed as binary (and sent as vbin16/32 rather than str16) --- Key: QPID-3492 URL: https://issues.apache.org/jira/browse/QPID-3492 Projec

[jira] [Resolved] (QPID-3492) String values in address are parsed as binary (and sent as vbin16/32 rather than str16)

[ https://issues.apache.org/jira/browse/QPID-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3492. -- Resolution: Fixed > String values in address are parsed as binary (and sent as vbin16/32 rather > than

[jira] [Created] (QPID-3502) Durable messages not acked on queue-based federation route

Durable messages not acked on queue-based federation route -- Key: QPID-3502 URL: https://issues.apache.org/jira/browse/QPID-3502 Project: Qpid Issue Type: Bug Components: C++

[jira] [Commented] (QPID-3502) Durable messages not acked on queue-based federation route

[ https://issues.apache.org/jira/browse/QPID-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113363#comment-13113363 ] Gordon Sim commented on QPID-3502: -- I believe this can be fixed by the following change (a

[jira] [Commented] (QPID-3502) Durable messages not acked on queue-based federation route

[ https://issues.apache.org/jira/browse/QPID-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113444#comment-13113444 ] Gordon Sim commented on QPID-3502: -- On consultation with Ken, the following is preferred:

[jira] [Updated] (QPID-3502) Durable messages not acked on queue-based federation route

[ https://issues.apache.org/jira/browse/QPID-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated QPID-3502: - Affects Version/s: 0.10 Assignee: Gordon Sim > Durable messages not acked on queue-based fede

[jira] [Resolved] (QPID-3502) Durable messages not acked on queue-based federation route

[ https://issues.apache.org/jira/browse/QPID-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3502. -- Resolution: Fixed Fix Version/s: 0.13 > Durable messages not acked on queue-based federation rout

[jira] [Created] (QPID-3969) arguments for QMFv2 methods may have undefined values if not specified

Gordon Sim created QPID-3969: Summary: arguments for QMFv2 methods may have undefined values if not specified Key: QPID-3969 URL: https://issues.apache.org/jira/browse/QPID-3969 Project: Qpid Is

[jira] [Created] (QPID-3970) If reroute specifies that alt exchane should be used, and no such exchange was defined, then messages are silently dropped

Gordon Sim created QPID-3970: Summary: If reroute specifies that alt exchane should be used, and no such exchange was defined, then messages are silently dropped Key: QPID-3970 URL: https://issues.apache.org/jira/brow

[jira] [Updated] (QPID-3970) If reroute specifies that alt exchange should be used, and no such exchange was defined, then messages are silently dropped

[ https://issues.apache.org/jira/browse/QPID-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated QPID-3970: - Summary: If reroute specifies that alt exchange should be used, and no such exchange was defined, then mes

[jira] [Resolved] (QPID-3970) If reroute specifies that alt exchange should be used, and no such exchange was defined, then messages are silently dropped

[ https://issues.apache.org/jira/browse/QPID-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3970. -- Resolution: Fixed > If reroute specifies that alt exchange should be used, and no such exchange > w

[jira] [Resolved] (QPID-3974) replication exchange msgDrop and byteDrop to increase when duplicate messages detected

[ https://issues.apache.org/jira/browse/QPID-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3974. -- Resolution: Fixed Fix Version/s: 0.17 Assignee: Gordon Sim Thanks Pavel!

[jira] Commented: (QPID-1766) Implemention of selector using Xquery

[ https://issues.apache.org/jira/browse/QPID-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688266#action_12688266 ] Gordon Sim commented on QPID-1766: -- Couple of comments on the broker side patch: (1) we re

[jira] Commented: (QPID-1766) Implemention of selector using Xquery

[ https://issues.apache.org/jira/browse/QPID-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688311#action_12688311 ] Gordon Sim commented on QPID-1766: -- Commented out lines should be removed before committing

[jira] Created: (QPID-1771) clustered qpidd segfaults when java client connects

clustered qpidd segfaults when java client connects --- Key: QPID-1771 URL: https://issues.apache.org/jira/browse/QPID-1771 Project: Qpid Issue Type: Bug Components: C++ Broker, Java

[jira] Commented: (QPID-1771) clustered qpidd segfaults when java client connects

[ https://issues.apache.org/jira/browse/QPID-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688638#action_12688638 ] Gordon Sim commented on QPID-1771: -- Looks like its caused by changes introduced in r751557.

[jira] Resolved: (QPID-1771) clustered qpidd segfaults when java client connects

[ https://issues.apache.org/jira/browse/QPID-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-1771. -- Resolution: Fixed Fixed by 757808 on trunk and r757808 on the 0.5 branch. > clustered qpidd segfaults w

[jira] Created: (QPID-1785) Race condition in closing session due to exception

Race condition in closing session due to exception -- Key: QPID-1785 URL: https://issues.apache.org/jira/browse/QPID-1785 Project: Qpid Issue Type: Bug Components: C++ Client Affe

[jira] Created: (QPID-1788) Allow channels to be reused on a connection

Allow channels to be reused on a connection --- Key: QPID-1788 URL: https://issues.apache.org/jira/browse/QPID-1788 Project: Qpid Issue Type: Improvement Components: C++ Client Affects Ve

[jira] Created: (QPID-1789) out of scope sessions incorrectly treated as detached

out of scope sessions incorrectly treated as detached - Key: QPID-1789 URL: https://issues.apache.org/jira/browse/QPID-1789 Project: Qpid Issue Type: Bug Components: C++ Client

[jira] Assigned: (QPID-1645) Kerberos auth support for the java client

[ https://issues.apache.org/jira/browse/QPID-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned QPID-1645: Assignee: Rajith Attapattu (was: Jan Sarenik) > Kerberos auth support for the java client > ---

[jira] Resolved: (QPID-1785) Race condition in closing session due to exception

[ https://issues.apache.org/jira/browse/QPID-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-1785. -- Resolution: Fixed Fixed as r762312 on 0.5 branch and as r763163 on trunk. QPID-1789 tracks the logicall

[jira] Assigned: (QPID-1645) Kerberos auth support for the java client

[ https://issues.apache.org/jira/browse/QPID-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned QPID-1645: Assignee: Jan Sarenik (was: Rajith Attapattu) > Kerberos auth support for the java client > ---

[jira] Resolved: (QPID-1808) setup.py does not include mllib

[ https://issues.apache.org/jira/browse/QPID-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-1808. -- Resolution: Fixed Resolved by r765092 on trunk and r765091 on the 0.5 branch. > setup.py does not inclu

[jira] Created: (QPID-1808) setup.py does not include mllib

setup.py does not include mllib --- Key: QPID-1808 URL: https://issues.apache.org/jira/browse/QPID-1808 Project: Qpid Issue Type: Bug Components: Python Client Affects Versions: M4 Report

[jira] Created: (QPID-1819) Large messages cause hangs and crashes when using digest-md5 and security layer (ssf 128)

Large messages cause hangs and crashes when using digest-md5 and security layer (ssf 128) - Key: QPID-1819 URL: https://issues.apache.org/jira/browse/QPID-1819 Pr

  1   2   3   4   5   6   7   8   9   10   >