[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=13124562#comment-13124562 ] jirapos...@reviews.apache.org commented on QPID-3417: - ---

Review Request: QPID-3417: add timestamp to message delivery properties on arrival at broker.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/2335/ --- Review request for qpid, Gordon Sim and Ted Ross. Summary --- A slight devi

[jira] [Assigned] (QPID-3533) qpid-config does not properly set some options if value evaluates to False

[ https://issues.apache.org/jira/browse/QPID-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned QPID-3533: -- Assignee: Nuno Santos > qpid-config does not properly set some options if value evaluates to False >

[jira] [Created] (QPID-3540) Typecasting and alignment requirements for various platforms - "increases required alignment of target type"

Typecasting and alignment requirements for various platforms - "increases required alignment of target type" Key: QPID-3540 URL: https://issues.apache.org

[jira] [Commented] (QPID-3522) SASL EXTERNAL mechanism no longer works

[ https://issues.apache.org/jira/browse/QPID-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124174#comment-13124174 ] jirapos...@reviews.apache.org commented on QPID-3522: - ---

[jira] [Commented] (QPID-3522) SASL EXTERNAL mechanism no longer works

[ https://issues.apache.org/jira/browse/QPID-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124153#comment-13124153 ] jirapos...@reviews.apache.org commented on QPID-3522: - bq. On 2011-1

[jira] [Commented] (QPID-3522) SASL EXTERNAL mechanism no longer works

[ https://issues.apache.org/jira/browse/QPID-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124151#comment-13124151 ] jirapos...@reviews.apache.org commented on QPID-3522: - ---

[jira] [Assigned] (QPID-3536) Topic Session Rollback/Recover does not work when using ADDR address destinations

[ https://issues.apache.org/jira/browse/QPID-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reassigned QPID-3536: Assignee: Keith Wall (was: Andrew MacBean) Could you please review and commit if happy?

[jira] [Commented] (QPID-3536) Topic Session Rollback/Recover does not work when using ADDR address destinations

[ https://issues.apache.org/jira/browse/QPID-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124146#comment-13124146 ] Andrew MacBean commented on QPID-3536: -- Removed the logic to override the accept mode

[jira] [Updated] (QPID-3536) Topic Session Rollback/Recover does not work when using ADDR address destinations

[ https://issues.apache.org/jira/browse/QPID-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-3536: - Attachment: 0001-QPID-3536-0-10-overrides-JMS-AcceptMode-with-a-defau.patch > Topic Session Ro

[jira] [Created] (QPID-3539) The setting of NoLocal when creating a durable subscription does not have the desired affect of preventing delivery of message on same connection.

The setting of NoLocal when creating a durable subscription does not have the desired affect of preventing delivery of message on same connection. --

[jira] [Created] (QPID-3537) Rename the :block option to :sync in Sender.send so that it matches the C++ APIs.

Rename the :block option to :sync in Sender.send so that it matches the C++ APIs. - Key: QPID-3537 URL: https://issues.apache.org/jira/browse/QPID-3537 Project: Qpid

[jira] [Created] (QPID-3538) ADDR address format not supported for topic. and queue. entries in JNDI properties

ADDR address format not supported for topic. and queue. entries in JNDI properties -- Key: QPID-3538 URL: https://issues.apache.org/jira/browse/QPID-3538 Project: Qpid

[jira] [Updated] (QPID-3537) Rename the :block option to :sync in Sender.send so that it matches the C++ APIs.

[ https://issues.apache.org/jira/browse/QPID-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce updated QPID-3537: --- Attachment: 0001-RUBY-Change-the-block-arg-to-be-sync-in-the-Sender-c.patch > Rename the :

[jira] [Created] (QPID-3536) Topic Session Rollback/Recover does not work when using ADDR address destinations

Topic Session Rollback/Recover does not work when using ADDR address destinations - Key: QPID-3536 URL: https://issues.apache.org/jira/browse/QPID-3536 Project: Qpid

[jira] [Updated] (QPID-3536) Topic Session Rollback/Recover does not work when using ADDR address destinations

[ https://issues.apache.org/jira/browse/QPID-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-3536: - Description: User should be able to consume a message on topic session and then rollback/recover

[jira] [Created] (QPID-3535) On protocol negotiation 0-9-1 client sends ConnectionClose command when broker protocol version is not supported by a client.

On protocol negotiation 0-9-1 client sends ConnectionClose command when broker protocol version is not supported by a client. - Key: QPID-3535

[jira] [Created] (QPID-3534) 0-9-1 client attempts to reuse the connection after sending ConnectionCloseOk

0-9-1 client attempts to reuse the connection after sending ConnectionCloseOk - Key: QPID-3534 URL: https://issues.apache.org/jira/browse/QPID-3534 Project: Qpid Iss

[jira] [Commented] (QPID-1834) Misconfiguration of config path for Debian libsasl2-2 (SASL support)

[ https://issues.apache.org/jira/browse/QPID-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123929#comment-13123929 ] Gordon Sim commented on QPID-1834: -- See QPID-3528 > Misconfiguration of c