[jira] [Commented] (PROTON-1479) C++ scheduled_send examples send in an unsafe context

[ https://issues.apache.org/jira/browse/PROTON-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16008838#comment-16008838 ] ASF subversion and git services commented on PROTON-1479: - Commit

[jira] [Created] (PROTON-1479) C++ scheduled_send examples send in an unsafe context

Andrew Stitcher created PROTON-1479: --- Summary: C++ scheduled_send examples send in an unsafe context Key: PROTON-1479 URL: https://issues.apache.org/jira/browse/PROTON-1479 Project: Qpid Proton

[jira] [Commented] (PROTON-1478) [c proactor] self test failures

[ https://issues.apache.org/jira/browse/PROTON-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16008571#comment-16008571 ] Chuck Rolke commented on PROTON-1478: - The last test in the original issue failed on lines 308 309

[jira] [Updated] (PROTON-1478) [c proactor] self test failures

[ https://issues.apache.org/jira/browse/PROTON-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke updated PROTON-1478: Attachment: PROTON-1478_timeout_100percent_cpu.svg While the test is hanging there for the 25

[jira] [Commented] (DISPATCH-390) New pn_proactor-based IO driver

[ https://issues.apache.org/jira/browse/DISPATCH-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16008554#comment-16008554 ] ASF subversion and git services commented on DISPATCH-390: -- Commit

[jira] [Commented] (PROTON-1476) C tests strict aliasing error on gcc 4.4.7

[ https://issues.apache.org/jira/browse/PROTON-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16008368#comment-16008368 ] ASF subversion and git services commented on PROTON-1476: - Commit

[jira] [Created] (PROTON-1478) [c proactor] self test failures

Chuck Rolke created PROTON-1478: --- Summary: [c proactor] self test failures Key: PROTON-1478 URL: https://issues.apache.org/jira/browse/PROTON-1478 Project: Qpid Proton Issue Type: Bug

[jira] [Closed] (QPID-7780) [Java Broker] Message conversion layers should be able to convert unsigned numbers into their corresponding unsigned equivalents on the target protocol

[ https://issues.apache.org/jira/browse/QPID-7780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy closed QPID-7780. Resolution: Won't Fix > [Java Broker] Message conversion layers should be able to convert unsigned >

[jira] [Commented] (DISPATCH-769) Links popup on topology page only shows a single link

[ https://issues.apache.org/jira/browse/DISPATCH-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16008318#comment-16008318 ] ASF subversion and git services commented on DISPATCH-769: -- Commit

[jira] [Resolved] (DISPATCH-769) Links popup on topology page only shows a single link

[ https://issues.apache.org/jira/browse/DISPATCH-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-769. --- Resolution: Fixed Fix Version/s: 1.0.0 > Links popup on topology page only shows a

[jira] [Resolved] (DISPATCH-768) On topology page, show connections that go to more than one router

[ https://issues.apache.org/jira/browse/DISPATCH-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-768. --- Resolution: Fixed Fix Version/s: 1.0.0 > On topology page, show connections that go

[jira] [Resolved] (QPID-7774) [Qpid JMS Client 0-x] [0-8..0-91] MessageConsumer#receiveNoWait() always returns null after a successful failover

[ https://issues.apache.org/jira/browse/QPID-7774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-7774. -- Resolution: Fixed > [Qpid JMS Client 0-x] [0-8..0-91] MessageConsumer#receiveNoWait() always > returns

[jira] [Resolved] (QPID-7769) [AMQP 0-8..0-91] Support decoding of type codes u (unsigned short) and B (unsigned byte) to maximise compatibility with other AMQP implementations

[ https://issues.apache.org/jira/browse/QPID-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-7769. -- Resolution: Fixed > [AMQP 0-8..0-91] Support decoding of type codes u (unsigned short) and B >

[jira] [Created] (QPID-7782) [Java Broker] [AMQP1.0] NPE on connection when no default virtualhost exists

Lorenz Quack created QPID-7782: -- Summary: [Java Broker] [AMQP1.0] NPE on connection when no default virtualhost exists Key: QPID-7782 URL: https://issues.apache.org/jira/browse/QPID-7782 Project: Qpid

[jira] [Commented] (QPID-7781) [Java Broker] 500 error whilst deleting a virtualhost with attached links.

[ https://issues.apache.org/jira/browse/QPID-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16008227#comment-16008227 ] Lorenz Quack commented on QPID-7781: This also happens with out any connected clients. > [Java Broker]

[jira] [Comment Edited] (QPID-7781) [Java Broker] 500 error whilst deleting a virtualhost with attached links.

[ https://issues.apache.org/jira/browse/QPID-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16008227#comment-16008227 ] Lorenz Quack edited comment on QPID-7781 at 5/12/17 2:40 PM: - This also happens

[jira] [Created] (QPID-7781) [Java Broker] 500 error whilst deleting a virtualhost with attached links.

Lorenz Quack created QPID-7781: -- Summary: [Java Broker] 500 error whilst deleting a virtualhost with attached links. Key: QPID-7781 URL: https://issues.apache.org/jira/browse/QPID-7781 Project: Qpid

[jira] [Commented] (QPID-7769) [AMQP 0-8..0-91] Support decoding of type codes u (unsigned short) and B (unsigned byte) to maximise compatibility with other AMQP implementations

[ https://issues.apache.org/jira/browse/QPID-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16008206#comment-16008206 ] Alex Rudyy commented on QPID-7769: -- The implemented changes look reasonable to me. I raised JIRA QPID-7780

[jira] [Created] (QPID-7780) [Java Broker] Message conversion layers should be able to convert unsigned numbers into their corresponding unsigned equivalents on the target protocol

Alex Rudyy created QPID-7780: Summary: [Java Broker] Message conversion layers should be able to convert unsigned numbers into their corresponding unsigned equivalents on the target protocol Key: QPID-7780 URL:

[jira] [Commented] (QPID-7774) [Qpid JMS Client 0-x] [0-8..0-91] MessageConsumer#receiveNoWait() always returns null after a successful failover

[ https://issues.apache.org/jira/browse/QPID-7774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16008054#comment-16008054 ] ASF subversion and git services commented on QPID-7774: --- Commit

[jira] [Commented] (QPID-7774) [Qpid JMS Client 0-x] [0-8..0-91] MessageConsumer#receiveNoWait() always returns null after a successful failover

[ https://issues.apache.org/jira/browse/QPID-7774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16008053#comment-16008053 ] ASF subversion and git services commented on QPID-7774: --- Commit

[jira] [Commented] (QPID-7777) [AMQP 1.0] NPE during consumer target delivery path

[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007940#comment-16007940 ] ASF subversion and git services commented on QPID-: --- Commit

[jira] [Commented] (QPID-7777) [AMQP 1.0] NPE during consumer target delivery path

[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007941#comment-16007941 ] ASF subversion and git services commented on QPID-: --- Commit

[jira] [Commented] (QPID-7774) [Qpid JMS Client 0-x] [0-8..0-91] MessageConsumer#receiveNoWait() always returns null after a successful failover

[ https://issues.apache.org/jira/browse/QPID-7774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007937#comment-16007937 ] ASF subversion and git services commented on QPID-7774: --- Commit

[jira] [Commented] (QPID-7779) [Qpid JMS Client 0-x] [0-8..0-91] sasl_mechs and other SASL connection options not supported

[ https://issues.apache.org/jira/browse/QPID-7779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007938#comment-16007938 ] ASF subversion and git services commented on QPID-7779: --- Commit

[jira] [Updated] (QPID-7779) [Qpid JMS Client 0-x] [0-8..0-91] sasl_mechs and other SASL connection options not supported

[ https://issues.apache.org/jira/browse/QPID-7779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-7779: -- Summary: [Qpid JMS Client 0-x] [0-8..0-91] sasl_mechs and other SASL connection options not supported

[jira] [Created] (QPID-7779) [Qpid JMS Client 0-x] [0-8..0-91] sasl_mechs and other SASL connection options not suported

Rob Godfrey created QPID-7779: - Summary: [Qpid JMS Client 0-x] [0-8..0-91] sasl_mechs and other SASL connection options not suported Key: QPID-7779 URL: https://issues.apache.org/jira/browse/QPID-7779

[jira] [Created] (QPID-7778) [Java Broker, Documentation] The Message encryption pages should mention that they require the Unlimited Strength JCE

Lorenz Quack created QPID-7778: -- Summary: [Java Broker, Documentation] The Message encryption pages should mention that they require the Unlimited Strength JCE Key: QPID-7778 URL:

[jira] [Closed] (DISPATCH-434) Remember all entities expanded on overview and entities pages

[ https://issues.apache.org/jira/browse/DISPATCH-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek closed DISPATCH-434. --- Works for me. > Remember all entities expanded on overview and entities pages >

[jira] [Closed] (DISPATCH-440) Use the placeholder HTML attribute to communicate default values in the Connect form

[ https://issues.apache.org/jira/browse/DISPATCH-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek closed DISPATCH-440. --- Works for me. > Use the placeholder HTML attribute to communicate default values in the > Connect

[jira] [Comment Edited] (DISPATCH-521) Switch to verify qdrouterd installation

[ https://issues.apache.org/jira/browse/DISPATCH-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007772#comment-16007772 ] Jiri Danek edited comment on DISPATCH-521 at 5/12/17 8:01 AM: -- The current

[jira] [Closed] (DISPATCH-521) Switch to verify qdrouterd installation

[ https://issues.apache.org/jira/browse/DISPATCH-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek closed DISPATCH-521. --- The current state is good enough for me. the -v/--version switch was added and it fulfills points 2.

[jira] [Closed] (DISPATCH-746) Standalone console does not connect if port is left as default

[ https://issues.apache.org/jira/browse/DISPATCH-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek closed DISPATCH-746. --- Works for me now, closing. > Standalone console does not connect if port is left as default >

[jira] [Closed] (DISPATCH-751) Clicking entities/connector in stand-alone console prints "Error: [ngModel:numfmt] Expected `1` to be a number"

[ https://issues.apache.org/jira/browse/DISPATCH-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek closed DISPATCH-751. --- Works for me, thank you for fixing. > Clicking entities/connector in stand-alone console prints

[jira] [Closed] (DISPATCH-763) Router crashes when config file defines listener { addr: } instead of { host: }

[ https://issues.apache.org/jira/browse/DISPATCH-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek closed DISPATCH-763. --- Works for me, thank you for the fix. > Router crashes when config file defines listener { addr: }

[jira] [Updated] (DISPATCH-390) New pn_proactor-based IO driver

[ https://issues.apache.org/jira/browse/DISPATCH-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-390: Attachment: exp_count.core.zip > New pn_proactor-based IO driver >

[jira] [Commented] (DISPATCH-390) New pn_proactor-based IO driver

[ https://issues.apache.org/jira/browse/DISPATCH-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007671#comment-16007671 ] Jiri Danek commented on DISPATCH-390: - Here is backtrace for one of the other errors, since I've