[jira] [Updated] (PROTON-157) invalid delivery-id sent(?)
[ https://issues.apache.org/jira/browse/PROTON-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated PROTON-157: -- Attachment: PROTON-157-improved+test.patch More efficient fix + test to show issue. invalid delivery-id sent(?) --- Key: PROTON-157 URL: https://issues.apache.org/jira/browse/PROTON-157 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.2 Reporter: Gordon Sim Attachments: PROTON-157-improved+test.patch E.g. the following trace is from the client side (the peer was qpidd) and appears to show a delivery-id being skipped: [0xb2a800:1] - TRANSFER @20 [1, 1520, b\xf0\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbd\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd1\xc5\xdf\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1521, b\xf1\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbe\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd1\xe8c\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1522, b\xf2\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbf\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\x8b\x95\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1523, b\xf3\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xc0\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\xa8\xa5\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1525, b\xf4\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xc1\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\xc01\x00Su\xa0d [0xb2a800:0] - CLOSE @24 [@29 [:amqp:session:invalid-field]] ERROR amqp:session:invalid-field sequencing error, expected delivery-id 1524, got 1525 It is of course possible that I am doing something wrong in the broker code, but I can't think what would cause something like this (since I can't influence the delivery ids directly). It only seems to happen when there is a prefetch greater than 900. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-157) invalid delivery-id sent(?)
[ https://issues.apache.org/jira/browse/PROTON-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated PROTON-157: -- Attachment: PROTON-157-improved+test-2.patch Improved test case that hits the exact symptom reported by this bug (previous test hits the same underlying structural issue but it manifests itself as a delivery ordering issue, with the delivery ids assigned correctly but the content/tag received out of order). invalid delivery-id sent(?) --- Key: PROTON-157 URL: https://issues.apache.org/jira/browse/PROTON-157 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.2 Reporter: Gordon Sim Fix For: 0.3 Attachments: PROTON-157-improved+test-2.patch E.g. the following trace is from the client side (the peer was qpidd) and appears to show a delivery-id being skipped: [0xb2a800:1] - TRANSFER @20 [1, 1520, b\xf0\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbd\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd1\xc5\xdf\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1521, b\xf1\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbe\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd1\xe8c\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1522, b\xf2\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbf\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\x8b\x95\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1523, b\xf3\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xc0\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\xa8\xa5\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1525, b\xf4\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xc1\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\xc01\x00Su\xa0d [0xb2a800:0] - CLOSE @24 [@29 [:amqp:session:invalid-field]] ERROR amqp:session:invalid-field sequencing error, expected delivery-id 1524, got 1525 It is of course possible that I am doing something wrong in the broker code, but I can't think what would cause something like this (since I can't influence the delivery ids directly). It only seems to happen when there is a prefetch greater than 900. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-157) invalid delivery-id sent or out of order delivery
[ https://issues.apache.org/jira/browse/PROTON-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated PROTON-157: -- Priority: Critical (was: Major) Fix Version/s: 0.3 Assignee: Gordon Sim Summary: invalid delivery-id sent or out of order delivery (was: invalid delivery-id sent(?)) invalid delivery-id sent or out of order delivery - Key: PROTON-157 URL: https://issues.apache.org/jira/browse/PROTON-157 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.2 Reporter: Gordon Sim Assignee: Gordon Sim Priority: Critical Fix For: 0.3 Attachments: PROTON-157-improved+test-2.patch E.g. the following trace is from the client side (the peer was qpidd) and appears to show a delivery-id being skipped: [0xb2a800:1] - TRANSFER @20 [1, 1520, b\xf0\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbd\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd1\xc5\xdf\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1521, b\xf1\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbe\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd1\xe8c\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1522, b\xf2\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbf\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\x8b\x95\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1523, b\xf3\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xc0\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\xa8\xa5\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1525, b\xf4\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xc1\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\xc01\x00Su\xa0d [0xb2a800:0] - CLOSE @24 [@29 [:amqp:session:invalid-field]] ERROR amqp:session:invalid-field sequencing error, expected delivery-id 1524, got 1525 It is of course possible that I am doing something wrong in the broker code, but I can't think what would cause something like this (since I can't influence the delivery ids directly). It only seems to happen when there is a prefetch greater than 900. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-157) invalid delivery-id sent or out of order delivery
[ https://issues.apache.org/jira/browse/PROTON-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated PROTON-157: -- Attachment: (was: PROTON-157-improved+test.patch) invalid delivery-id sent or out of order delivery - Key: PROTON-157 URL: https://issues.apache.org/jira/browse/PROTON-157 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.2 Reporter: Gordon Sim Assignee: Gordon Sim Priority: Critical Fix For: 0.3 Attachments: PROTON-157-improved+test-2.patch E.g. the following trace is from the client side (the peer was qpidd) and appears to show a delivery-id being skipped: [0xb2a800:1] - TRANSFER @20 [1, 1520, b\xf0\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbd\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd1\xc5\xdf\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1521, b\xf1\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbe\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd1\xe8c\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1522, b\xf2\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbf\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\x8b\x95\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1523, b\xf3\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xc0\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\xa8\xa5\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1525, b\xf4\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xc1\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\xc01\x00Su\xa0d [0xb2a800:0] - CLOSE @24 [@29 [:amqp:session:invalid-field]] ERROR amqp:session:invalid-field sequencing error, expected delivery-id 1524, got 1525 It is of course possible that I am doing something wrong in the broker code, but I can't think what would cause something like this (since I can't influence the delivery ids directly). It only seems to happen when there is a prefetch greater than 900. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-172) Implement SSL within proton-j
[ https://issues.apache.org/jira/browse/PROTON-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Harvey updated PROTON-172: - Attachment: 0001-PROTON-172-refactored-Java-SSL-implementation-to-mak.patch refactored Java SSL implementation to make it more readable Implement SSL within proton-j - Key: PROTON-172 URL: https://issues.apache.org/jira/browse/PROTON-172 Project: Qpid Proton Issue Type: New Feature Components: proton-j Reporter: Philip Harvey Assignee: Keith Wall Attachments: 0001-PROTON-172-Java-SSL-implementation-enable-system-tes.patch, 0001-PROTON-172-refactored-Java-SSL-implementation-to-mak.patch, 0002-PROTON-172-Extra-tests-and-enhanced-pump-method.patch Implement SSL within proton-j -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-157) invalid delivery-id sent or out of order delivery
[ https://issues.apache.org/jira/browse/PROTON-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated PROTON-157: -- Attachment: PROTON-157-improved+test-3.patch Cleaned up test changes: no need to disable asserts, simply allow buffer size to be passed in so we can use something large than existing default. invalid delivery-id sent or out of order delivery - Key: PROTON-157 URL: https://issues.apache.org/jira/browse/PROTON-157 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.2 Reporter: Gordon Sim Assignee: Gordon Sim Priority: Critical Fix For: 0.3 Attachments: PROTON-157-improved+test-3.patch E.g. the following trace is from the client side (the peer was qpidd) and appears to show a delivery-id being skipped: [0xb2a800:1] - TRANSFER @20 [1, 1520, b\xf0\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbd\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd1\xc5\xdf\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1521, b\xf1\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbe\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd1\xe8c\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1522, b\xf2\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbf\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\x8b\x95\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1523, b\xf3\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xc0\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\xa8\xa5\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1525, b\xf4\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xc1\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\xc01\x00Su\xa0d [0xb2a800:0] - CLOSE @24 [@29 [:amqp:session:invalid-field]] ERROR amqp:session:invalid-field sequencing error, expected delivery-id 1524, got 1525 It is of course possible that I am doing something wrong in the broker code, but I can't think what would cause something like this (since I can't influence the delivery ids directly). It only seems to happen when there is a prefetch greater than 900. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-157) invalid delivery-id sent or out of order delivery
[ https://issues.apache.org/jira/browse/PROTON-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated PROTON-157: -- Attachment: (was: PROTON-157-improved+test-2.patch) invalid delivery-id sent or out of order delivery - Key: PROTON-157 URL: https://issues.apache.org/jira/browse/PROTON-157 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.2 Reporter: Gordon Sim Assignee: Gordon Sim Priority: Critical Fix For: 0.3 Attachments: PROTON-157-improved+test-3.patch E.g. the following trace is from the client side (the peer was qpidd) and appears to show a delivery-id being skipped: [0xb2a800:1] - TRANSFER @20 [1, 1520, b\xf0\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbd\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd1\xc5\xdf\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1521, b\xf1\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbe\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd1\xe8c\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1522, b\xf2\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbf\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\x8b\x95\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1523, b\xf3\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xc0\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\xa8\xa5\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1525, b\xf4\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xc1\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\xc01\x00Su\xa0d [0xb2a800:0] - CLOSE @24 [@29 [:amqp:session:invalid-field]] ERROR amqp:session:invalid-field sequencing error, expected delivery-id 1524, got 1525 It is of course possible that I am doing something wrong in the broker code, but I can't think what would cause something like this (since I can't influence the delivery ids directly). It only seems to happen when there is a prefetch greater than 900. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (PROTON-157) invalid delivery-id sent or out of order delivery when credit is close to or greater than session window
[ https://issues.apache.org/jira/browse/PROTON-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved PROTON-157. --- Resolution: Fixed Fixed by r1416944. invalid delivery-id sent or out of order delivery when credit is close to or greater than session window Key: PROTON-157 URL: https://issues.apache.org/jira/browse/PROTON-157 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.2 Reporter: Gordon Sim Assignee: Gordon Sim Priority: Critical Fix For: 0.3 Attachments: PROTON-157-improved+test-3.patch E.g. the following trace is from the client side (the peer was qpidd) and appears to show a delivery-id being skipped: [0xb2a800:1] - TRANSFER @20 [1, 1520, b\xf0\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbd\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd1\xc5\xdf\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1521, b\xf1\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbe\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd1\xe8c\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1522, b\xf2\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xbf\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\x8b\x95\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1523, b\xf3\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xc0\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\xa8\xa5\x00Su\xa0d [0xb2a800:1] - TRANSFER @20 [1, 1525, b\xf4\x05\x00\x00\x00\x00\x00\x00, 0, false, false] (177) \x00Sp\xc0\x08\x05BP\x00@@R\x01\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x0d@\x00St\xd1\x00\x00\x00\x1a\x00\x00\x00\x04\xa1\x02snp\x00\x00\x16\xc1\xa1\x02ts\x80\x12\xc8\xfb\xe4\xdb\xd2\xc01\x00Su\xa0d [0xb2a800:0] - CLOSE @24 [@29 [:amqp:session:invalid-field]] ERROR amqp:session:invalid-field sequencing error, expected delivery-id 1524, got 1525 It is of course possible that I am doing something wrong in the broker code, but I can't think what would cause something like this (since I can't influence the delivery ids directly). It only seems to happen when there is a prefetch greater than 900. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Proton Port for Windows
Thanks! protonWinSnap works fine for me, at least from what I have seen so far. If I understood correctly, protonWinSnap will be kept up to date until the merge to the main codebase is done, and that protonWin is meant only for patch reviews? Regards, Ljupco On 30 November 2012 14:27, Mary Hinton m.hin...@nc.rr.com wrote: Sure, it may take a while to get the proton group's approval for a merge. In the meantime, I have a snapshot of the Windows port at github. protonWinSnap is a snapshot of the code and protonWin will be the one used to add patches for the proton community to check out. To see the Windows port running, use this branch https://github.com/MaryDHinton/qpid-proton/tree/protonWinSnap To compile and run this code, all you should need to do is: Select the zip button on the page above and extract the code. Select the proton.sln file in the proton-c folder and open it in Visual Studio 2010. Compile the qpid-proton and proton projects. Go to the Debug folder and run proton (the debug version is the only mode set up, the release will have to be set up). You should be able to see messages passed between a proton client and server. The patches will be added to this branch as they become available: https://github.com/MaryDHinton/qpid-proton/commits/protonWin Let me know how it works for you. Mary Hinton -Original Message- From: Ljupco Taseski [mailto:t...@digiverse.si] Sent: Friday, November 30, 2012 5:45 AM To: proton@qpid.apache.org Cc: m.hin...@nc.rr.com Subject: Re: Proton Port for Windows Is it possible to have a look at the Windows port? I wouldn't mind even if it is a simple tgz/zip snapshot. Thanks, Ljupco
RE: Proton Port for Windows
I'm glad protonWinSnap worked for you. You're right about protonWin. It is just for patch reviews and will not compile in Windows without all the patches added to the code. I won't be able to keep protonWinSnap as up to date as I would like, but if it gets too far out of date, let me know and I will try to rebase the code with the current proton codebase. Right now, I'm trying to get the amqpd.dll broker plug-in (a project created within QPID) to load. To get the new AMQP 1.0 (includes proton) to compile, I had to change some code and don't have everything resolved yet. Mary Hinton From: Ljupco Taseski [mailto:t...@digiverse.si] Sent: Tuesday, December 04, 2012 11:35 AM To: Mary Hinton Cc: proton@qpid.apache.org Subject: Re: Proton Port for Windows Thanks! protonWinSnap works fine for me, at least from what I have seen so far. If I understood correctly, protonWinSnap will be kept up to date until the merge to the main codebase is done, and that protonWin is meant only for patch reviews? Regards, Ljupco On 30 November 2012 14:27, Mary Hinton m.hin...@nc.rr.com wrote: Sure, it may take a while to get the proton group's approval for a merge. In the meantime, I have a snapshot of the Windows port at github. protonWinSnap is a snapshot of the code and protonWin will be the one used to add patches for the proton community to check out. To see the Windows port running, use this branch https://github.com/MaryDHinton/qpid-proton/tree/protonWinSnap To compile and run this code, all you should need to do is: Select the zip button on the page above and extract the code. Select the proton.sln file in the proton-c folder and open it in Visual Studio 2010. Compile the qpid-proton and proton projects. Go to the Debug folder and run proton (the debug version is the only mode set up, the release will have to be set up). You should be able to see messages passed between a proton client and server. The patches will be added to this branch as they become available: https://github.com/MaryDHinton/qpid-proton/commits/protonWin Let me know how it works for you. Mary Hinton -Original Message- From: Ljupco Taseski [mailto:t...@digiverse.si] Sent: Friday, November 30, 2012 5:45 AM To: proton@qpid.apache.org Cc: m.hin...@nc.rr.com Subject: Re: Proton Port for Windows Is it possible to have a look at the Windows port? I wouldn't mind even if it is a simple tgz/zip snapshot. Thanks, Ljupco
[jira] [Commented] (PROTON-136) Add support for SSL session resumption
[ https://issues.apache.org/jira/browse/PROTON-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13509870#comment-13509870 ] Philip Harvey commented on PROTON-136: -- Hi Ken, I'm keen to explore what corresponding Java changes will need to be made. To allow me to do this, is it possible you could commit your work so far to a branch? That would give us a chance to get the tests passing against both proton-c and proton-j before merging to trunk. How does that sound to you? Add support for SSL session resumption -- Key: PROTON-136 URL: https://issues.apache.org/jira/browse/PROTON-136 Project: Qpid Proton Issue Type: New Feature Components: proton-c Affects Versions: 0.3 Reporter: Affan Dar Assignee: Ken Giusti Labels: ssl, sslContext, sslresume Open SSL supports resumption of SSL sessions which by-pass the heavy SSL handshake process. This is critical for scenarios involving low powered devices especially on cellular data networks where bandwidth is precious. It would be great if Proton exposes this ssl resume feature to users. . From: rhs [mailto:rschlom...@gmail.com] Sent: Tuesday, November 13, 2012 11:34 AM To: Affan Dar Cc: David Ingham Subject: Re: SSL session resumption On Tue, Nov 13, 2012 at 8:05 PM, Affan Dar affan...@microsoft.com wrote: Serializing/restoring the whole session state for the messenger will work for the scenario I think. Ok, let's start with this step then. I'm open to providing something finer grained if there is a need, but my preference is to keep it simple for the moment. One more thing, RFC 5077 has another flavor of session resumption which openssl supports (original implemented as RFC 4057 back in 2007 I think). This allows us to resume sessions without carrying state on the server side which as you can imagine is a big deal for service vendors. Probably there is no API level impact if messenger handles the session state itself but just wanted to put this on your radar. Ok, good to know. Could one of you file a JIRA for this upstream? I'm trying to get things a little more organized on the process front and keep everything centralized in JIRA. ;-) --Rafael -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Problems building and running proton-c on Linux RHEL 5
Thanks for the reply Ted. In an attempt to avoid the uuid module problem I've managed to upgrade to a later version of Python (2.6), and am now hitting a different error -- now at build time. When I run make all I get the following error: $ cd build $ cmake -DCMAKE_INSTALL_PREFIX=/usr .. $ make all ... ... Scanning dependencies of target _cproton [ 86%] Swig source /home/phil/dev/proton/proton- c/include/proton/engine.h:67: Warning(451): Setting a const char * variable may leak memory. [ 91%] Building C object bindings/python /CMakeFiles/_cproton.dir/pythonPYTHON_wrap.c.o /home/phil/dev/proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c: In function ‘SWIG_Python_ConvertFunctionPtr’: /home/phil/dev/proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2035: warning: initialization discards qualifiers from pointer target type /home/phil/dev/proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c: In function ‘SWIG_AsCharPtrAndSize’: /home/phil/dev/proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2548: warning: passing argument 3 of ‘PyString_AsStringAndSize’ from incompatible pointer type /home/phil/dev/proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c: In function ‘SWIG_Python_FixMethods’: /home/phil/dev/proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:19222: warning: initialization discards qualifiers from pointer target type Linking C shared module _cproton.so /usr/bin/ld: /usr/local/lib/python2.6/config/libpython2.6.a(abstract.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/local/lib/python2.6/config/libpython2.6.a: could not read symbols: Bad value collect2: ld returned 1 exit status make[2]: *** [bindings/python/_cproton.so] Error 1 make[1]: *** [bindings/python/CMakeFiles/_cproton.dir/all] Error 2 make: *** [all] Error 2 This looks like it could be an environmental problem rather than an issue with Proton itself, but any suggestions about how to work around it would be gratefully received. I don't build a lot of C code so am not the best at diagnosing this kind of error. Thanks, Phil On 29 November 2012 19:44, Ted Ross tr...@redhat.com wrote: Phil, With regard to the python uuid issue, this was handled in qpid (see qpid/python/build/lib/qpid/**datatypes.py). Perhaps proton needs to use a similar approach. -Ted On 11/29/2012 11:13 AM, Phil Harvey wrote: I'm having problems building and running proton-c on my machine. I'm hitting two problems so far: - I get an Unable to find 'php.swg' error. A web search suggests that this relates to the version of swig I have installed (it's v1.3.29). My current workaround is to comment out the php Swig stuff in the make file. - When I try to run the Python tests, Python errors with the message No module named uuid. Again, I believe this is a versioning problem. I'm running Python 2.4, and I believe the uuid module was included in later versions of Python. Unfortunately my rights to upgrade the packages on my machine are quite limited. I'm interested to know if others have seen this problem and whether they believe any changes need to be made to the make files, or is my environment simply too old to be supported by Proton? Also, although dependencies such as Python and Swig are mentioned in proton-c/README, the required *versions* of them are not. Is this stuff written down anywhere? If not, does anyone know what the required versions of the dependencies actually are? Thanks Phil
Re: Problems building and running proton-c on Linux RHEL 5
On Tue, 2012-12-04 at 17:46 +, Phil Harvey wrote: ... Linking C shared module _cproton.so /usr/bin/ld: /usr/local/lib/python2.6/config/libpython2.6.a(abstract.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/local/lib/python2.6/config/libpython2.6.a: could not read symbols: Bad value collect2: ld returned 1 exit status make[2]: *** [bindings/python/_cproton.so] Error 1 make[1]: *** [bindings/python/CMakeFiles/_cproton.dir/all] Error 2 make: *** [all] Error 2 It looks to me like you need to build the local version of python2.6 with a shared library rather than a static one. The basic complaint above is the linker saying: You told me to build position independent code, but the library you gave me to resolve this symbol isn't compiled position independently. The library name libpython2.6.a is the give-away that it's trying to link against a static library instead of a dynamic shared lib. This looks like it could be an environmental problem rather than an issue with Proton itself, but any suggestions about how to work around it would be gratefully received. I don't build a lot of C code so am not the best at diagnosing this kind of error. You can't work around it as far as I know, you'll have to build python 2.6 correctly. Andrew
Re: Perl language bindings are now pushed...
On Thu, 2012-11-29 at 17:16 -0500, Darryl L. Pierce wrote: I've pushed the Perl language bindings as well as the send/recv examples for using the qpid::proton::Messenger and qpid::proton::Message classes. These changes break make install for a developer build installing in a non system location: ... -- Installing: /home/andrew/Work/proton/install/lib64/python2.7/site-packages/proton.pyo -- Installing: /home/andrew/Work/proton/install/lib64/python2.7/site-packages/_cproton.so -- Removed runtime path from /home/andrew/Work/proton/install/lib64/python2.7/site-packages/_cproton.so -- Installing: /home/andrew/Work/proton/install/lib64/ruby/cproton.so -- Removed runtime path from /home/andrew/Work/proton/install/lib64/ruby/cproton.so -- Installing: /usr/lib64/perl5/libcproton_perl.so CMake Error at bindings/perl/cmake_install.cmake:44 (FILE): file INSTALL cannot copy file /home/andrew/Work/proton/bld/bindings/perl/libcproton_perl.so to /usr/lib64/perl5/libcproton_perl.so. Call Stack (most recent call first): bindings/cmake_install.cmake:39 (INCLUDE) cmake_install.cmake:137 (INCLUDE) It seems like this new stuff just ignores CMAKE_INSTALL_PREFIX. Andrew
