[jira] [Assigned] (PROTON-140) [Proton-j] Add contib, examples directories
[ https://issues.apache.org/jira/browse/PROTON-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned PROTON-140: -- Assignee: Keith Wall [Proton-j] Add contib, examples directories --- Key: PROTON-140 URL: https://issues.apache.org/jira/browse/PROTON-140 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Rob Godfrey Assignee: Keith Wall Per IRC chat (and prior agreement at the F2F), we should create a contrib directory under proton-j and move the current structure under a proton directory (15:42:44) chirino: I think what needs to get done is: mkdir proton-j/proton; mv proton-j/* proton-j/proton; mkdir proton-j/contrib (15:45:18) robjgodfrey: rschloming: any issues with the above? (15:46:32) rschloming: robjgodfrey: not at all, makes sense to me (15:46:57) rschloming: robjgodfrey: I should be able to update the release script to accomodate that. (15:47:09) chirino: rschloming: you probably won't need to. (15:47:20) chirino: I'll be putting a pom.xml in the proton-j dir again. (15:47:36) rschloming: chirino: even better (15:48:17) rschloming: robjgodfrey: chirino: would you expect a java examples directory to be parallel to those? (15:48:33) rschloming: robjgodfrey: chirino: e.g. proton-j/examples? (15:48:35) chirino: yeah that would make sense. -- 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] [Assigned] (PROTON-138) [proton-j] BufferOverflowException
[ https://issues.apache.org/jira/browse/PROTON-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned PROTON-138: -- Assignee: Philip Harvey [proton-j] BufferOverflowException -- Key: PROTON-138 URL: https://issues.apache.org/jira/browse/PROTON-138 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Hiram Chirino Assignee: Philip Harvey java.nio.BufferOverflowException at java.nio.Buffer.nextPutIndex(Buffer.java:493) at java.nio.HeapByteBuffer.put(HeapByteBuffer.java:145) at org.apache.qpid.proton.codec.WritableBuffer$ByteBufferWrapper.put(WritableBuffer.java:63) at org.apache.qpid.proton.codec.CompositeWritableBuffer.putInt(CompositeWritableBuffer.java:105) at org.apache.qpid.proton.engine.impl.TransportImpl.writeFrame(TransportImpl.java:900) at org.apache.qpid.proton.engine.impl.TransportImpl.processClose(TransportImpl.java:847) at org.apache.qpid.proton.engine.impl.TransportImpl.transportOutput(TransportImpl.java:204) at org.apache.qpid.proton.engine.impl.TransportImpl.access$000(TransportImpl.java:42) at org.apache.qpid.proton.engine.impl.TransportImpl$1.output(TransportImpl.java:106) at org.apache.qpid.proton.engine.impl.SaslImpl$1.output(SaslImpl.java:507) at org.apache.qpid.proton.engine.impl.TransportImpl.output(TransportImpl.java:165) -- 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] [Created] (PROTON-141) [proton-j] 256K Messages do not get transfered properly
Hiram Chirino created PROTON-141: Summary: [proton-j] 256K Messages do not get transfered properly Key: PROTON-141 URL: https://issues.apache.org/jira/browse/PROTON-141 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Hiram Chirino -- 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-141) [proton-j] 256K Messages do not get transfered properly
[ https://issues.apache.org/jira/browse/PROTON-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-141: - Attachment: PROTON-141.patch Attaching junit test case to demonstrate the issue. [proton-j] 256K Messages do not get transfered properly --- Key: PROTON-141 URL: https://issues.apache.org/jira/browse/PROTON-141 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Hiram Chirino Attachments: PROTON-141.patch -- 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] [Commented] (PROTON-137) pn_messenger_incoming_subscription returning null
[ https://issues.apache.org/jira/browse/PROTON-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13498922#comment-13498922 ] William Henry commented on PROTON-137: -- Looks like this is working now after latest messenger.c fix. I'm doing some more testing. pn_messenger_incoming_subscription returning null - Key: PROTON-137 URL: https://issues.apache.org/jira/browse/PROTON-137 Project: Qpid Proton Issue Type: Bug Affects Versions: 0.2 Reporter: William Henry Priority: Blocker Calling pn_messenger_incoming_subscription after successfully calling pn_messenger_get is unexpectedly returning NULL. -- 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-141) [proton-j] 256K Messages do not get transfered properly
[ https://issues.apache.org/jira/browse/PROTON-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-141: - Attachment: PROTON-141-fix-written-result.patch Attaching patch that fixes the result of the output() call. If the connection start overflowing, the new write call would return an invalid write size. [proton-j] 256K Messages do not get transfered properly --- Key: PROTON-141 URL: https://issues.apache.org/jira/browse/PROTON-141 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Hiram Chirino Attachments: PROTON-141-fix-written-result.patch, PROTON-141.patch -- 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] [Commented] (PROTON-141) [proton-j] 256K Messages do not get transfered properly
[ https://issues.apache.org/jira/browse/PROTON-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13498935#comment-13498935 ] Hiram Chirino commented on PROTON-141: -- With the patch applied, the test case is now failing with the same BufferOverflowException as reported in PROTON-138 [proton-j] 256K Messages do not get transfered properly --- Key: PROTON-141 URL: https://issues.apache.org/jira/browse/PROTON-141 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Hiram Chirino Attachments: PROTON-141-fix-written-result.patch, PROTON-141.patch -- 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] [Commented] (PROTON-138) [proton-j] BufferOverflowException
[ https://issues.apache.org/jira/browse/PROTON-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13498936#comment-13498936 ] Hiram Chirino commented on PROTON-138: -- PROTON-141 contains a patch /w a test case that reproduces this issue. [proton-j] BufferOverflowException -- Key: PROTON-138 URL: https://issues.apache.org/jira/browse/PROTON-138 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Hiram Chirino Assignee: Philip Harvey java.nio.BufferOverflowException at java.nio.Buffer.nextPutIndex(Buffer.java:493) at java.nio.HeapByteBuffer.put(HeapByteBuffer.java:145) at org.apache.qpid.proton.codec.WritableBuffer$ByteBufferWrapper.put(WritableBuffer.java:63) at org.apache.qpid.proton.codec.CompositeWritableBuffer.putInt(CompositeWritableBuffer.java:105) at org.apache.qpid.proton.engine.impl.TransportImpl.writeFrame(TransportImpl.java:900) at org.apache.qpid.proton.engine.impl.TransportImpl.processClose(TransportImpl.java:847) at org.apache.qpid.proton.engine.impl.TransportImpl.transportOutput(TransportImpl.java:204) at org.apache.qpid.proton.engine.impl.TransportImpl.access$000(TransportImpl.java:42) at org.apache.qpid.proton.engine.impl.TransportImpl$1.output(TransportImpl.java:106) at org.apache.qpid.proton.engine.impl.SaslImpl$1.output(SaslImpl.java:507) at org.apache.qpid.proton.engine.impl.TransportImpl.output(TransportImpl.java:165) -- 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-141) [proton-j] 256K Messages do not get transfered properly
[ https://issues.apache.org/jira/browse/PROTON-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-141: - Attachment: (was: PROTON-141-fix-written-result.patch) [proton-j] 256K Messages do not get transfered properly --- Key: PROTON-141 URL: https://issues.apache.org/jira/browse/PROTON-141 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Hiram Chirino Attachments: PROTON-141-and-PROTON-138.patch, PROTON-141.patch -- 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-141) [proton-j] 256K Messages do not get transfered properly
[ https://issues.apache.org/jira/browse/PROTON-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-141: - Attachment: PROTON-141-and-PROTON-138.patch Attaching patch that fixes the test case. [proton-j] 256K Messages do not get transfered properly --- Key: PROTON-141 URL: https://issues.apache.org/jira/browse/PROTON-141 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Hiram Chirino Attachments: PROTON-141-and-PROTON-138.patch, PROTON-141.patch -- 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] [Commented] (PROTON-141) [proton-j] 256K Messages do not get transfered properly
[ https://issues.apache.org/jira/browse/PROTON-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13498949#comment-13498949 ] Hiram Chirino commented on PROTON-141: -- Patch also fixes PROTON-138 [proton-j] 256K Messages do not get transfered properly --- Key: PROTON-141 URL: https://issues.apache.org/jira/browse/PROTON-141 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Hiram Chirino Attachments: PROTON-141-and-PROTON-138.patch, PROTON-141.patch -- 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-138) [proton-j] BufferOverflowException
[ https://issues.apache.org/jira/browse/PROTON-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino resolved PROTON-138. -- Resolution: Duplicate Closing as a dup of 141. [proton-j] BufferOverflowException -- Key: PROTON-138 URL: https://issues.apache.org/jira/browse/PROTON-138 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Hiram Chirino Assignee: Philip Harvey java.nio.BufferOverflowException at java.nio.Buffer.nextPutIndex(Buffer.java:493) at java.nio.HeapByteBuffer.put(HeapByteBuffer.java:145) at org.apache.qpid.proton.codec.WritableBuffer$ByteBufferWrapper.put(WritableBuffer.java:63) at org.apache.qpid.proton.codec.CompositeWritableBuffer.putInt(CompositeWritableBuffer.java:105) at org.apache.qpid.proton.engine.impl.TransportImpl.writeFrame(TransportImpl.java:900) at org.apache.qpid.proton.engine.impl.TransportImpl.processClose(TransportImpl.java:847) at org.apache.qpid.proton.engine.impl.TransportImpl.transportOutput(TransportImpl.java:204) at org.apache.qpid.proton.engine.impl.TransportImpl.access$000(TransportImpl.java:42) at org.apache.qpid.proton.engine.impl.TransportImpl$1.output(TransportImpl.java:106) at org.apache.qpid.proton.engine.impl.SaslImpl$1.output(SaslImpl.java:507) at org.apache.qpid.proton.engine.impl.TransportImpl.output(TransportImpl.java:165) -- 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-141) [proton-j] 256K Messages do not get transfered properly
[ https://issues.apache.org/jira/browse/PROTON-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-141: - Attachment: PROTON-141-final.patch Attaching an all-in-one patch that includes the fix and the test case. Also adds in a new python based test case for large messages. [proton-j] 256K Messages do not get transfered properly --- Key: PROTON-141 URL: https://issues.apache.org/jira/browse/PROTON-141 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Hiram Chirino Attachments: PROTON-141-final.patch -- 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] [Commented] (PROTON-143) Trace the frame after the onPayloadTooLarge runnable is executed.
[ https://issues.apache.org/jira/browse/PROTON-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13499053#comment-13499053 ] Hiram Chirino commented on PROTON-143: -- Attached fix. Trace the frame after the onPayloadTooLarge runnable is executed. - Key: PROTON-143 URL: https://issues.apache.org/jira/browse/PROTON-143 Project: Qpid Proton Issue Type: Bug Reporter: Hiram Chirino Attachments: PROTON-143.patch -- 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] [Created] (PROTON-143) Trace the frame after the onPayloadTooLarge runnable is executed.
Hiram Chirino created PROTON-143: Summary: Trace the frame after the onPayloadTooLarge runnable is executed. Key: PROTON-143 URL: https://issues.apache.org/jira/browse/PROTON-143 Project: Qpid Proton Issue Type: Bug Reporter: Hiram Chirino Attachments: PROTON-143.patch -- 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-143) Trace the frame after the onPayloadTooLarge runnable is executed.
[ https://issues.apache.org/jira/browse/PROTON-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-143: - Attachment: PROTON-143.patch Trace the frame after the onPayloadTooLarge runnable is executed. - Key: PROTON-143 URL: https://issues.apache.org/jira/browse/PROTON-143 Project: Qpid Proton Issue Type: Bug Reporter: Hiram Chirino Attachments: PROTON-143.patch -- 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-143) Trace the frame after the onPayloadTooLarge runnable is executed.
[ https://issues.apache.org/jira/browse/PROTON-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-143: - Component/s: proton-j Trace the frame after the onPayloadTooLarge runnable is executed. - Key: PROTON-143 URL: https://issues.apache.org/jira/browse/PROTON-143 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Hiram Chirino Attachments: PROTON-143.patch -- 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
