[jira] [Updated] (PROTON-81) Expose send/receive settle modes
[ https://issues.apache.org/jira/browse/PROTON-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated PROTON-81: -- Component/s: (was: proton-j) Expose send/receive settle modes Key: PROTON-81 URL: https://issues.apache.org/jira/browse/PROTON-81 Project: Qpid Proton Issue Type: Bug Components: proton-c Reporter: Hiram Chirino Priority: Critical -- 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-81) Expose send/receive settle modes
[ https://issues.apache.org/jira/browse/PROTON-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13507224#comment-13507224 ] Rob Godfrey commented on PROTON-81: --- This was resolved in commits 1399329,1399330 for proton-j, and was part of the 0.2 release. Expose send/receive settle modes Key: PROTON-81 URL: https://issues.apache.org/jira/browse/PROTON-81 Project: Qpid Proton Issue Type: Bug Components: proton-c Reporter: Hiram Chirino Priority: Critical -- 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-145) 256K Messages do not get transfered properly with a 64k pump size
[ https://issues.apache.org/jira/browse/PROTON-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-145. Resolution: Fixed Fix Version/s: 0.3 256K Messages do not get transfered properly with a 64k pump size - Key: PROTON-145 URL: https://issues.apache.org/jira/browse/PROTON-145 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Hiram Chirino Fix For: 0.3 Attachments: PROTON-145-Fix.patch, PROTON-145-Simplified.patch, PROTON-145-Test.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
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 On 14 November 2012 15:19, Mary Hinton m.hin...@nc.rr.com wrote: Hi everyone, I'd like to share the status of the Windows port of the proton code. The last rebase of the proton dll codebase was this Saturday, Nov. 10th. I haven't updated to the latest python tests yet, but currently, the port is running and passing most of the python tests. Totals: 119 tests, 105 passed, 6 skipped, 0 ignored, 8 failed I can run proton in both client and server mode and pass the messages between the client/server proton executables. It will be a while for all the Jiras for the port to be discussed and implemented to merge the two ports. I tried to maintain the code to keep the two versions working, but haven't actually tested my version on Linux yet. There are #ifdef's around areas that are specific to each port. A lot of these #ifdef's can be merged when the proton group decides on the best way to handle the specific areas. In the meantime, I would like to have a public place to put the port so that others can join in with the Windows version. What is the best way to do this using git so that I don't interfere with the current codebase? Thanks, Mary Hinton
RE: Proton Port for Windows
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 On 14 November 2012 15:19, Mary Hinton m.hin...@nc.rr.com wrote: Hi everyone, I'd like to share the status of the Windows port of the proton code. The last rebase of the proton dll codebase was this Saturday, Nov. 10th. I haven't updated to the latest python tests yet, but currently, the port is running and passing most of the python tests. Totals: 119 tests, 105 passed, 6 skipped, 0 ignored, 8 failed I can run proton in both client and server mode and pass the messages between the client/server proton executables. It will be a while for all the Jiras for the port to be discussed and implemented to merge the two ports. I tried to maintain the code to keep the two versions working, but haven't actually tested my version on Linux yet. There are #ifdef's around areas that are specific to each port. A lot of these #ifdef's can be merged when the proton group decides on the best way to handle the specific areas. In the meantime, I would like to have a public place to put the port so that others can join in with the Windows version. What is the best way to do this using git so that I don't interfere with the current codebase? Thanks, Mary Hinton
[jira] [Updated] (PROTON-170) generated pkg config file is broken
[
https://issues.apache.org/jira/browse/PROTON-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated PROTON-170:
--
Description:
E.g. cmake -DCMAKE_INSTALL_PREFIX=/path/to/non-standard/install make install
will install a pkg config file that doesn't have the include and lib
directories set.
Also Cflags is set to -I${includedir} which breaks compilation even for a
standard install if the includedir is not set.
was:E.g. cmake -DCMAKE_INSTALL_PREFIX=/path/to/non-standard/install make
install will install a pkg config file that doesn't have the include and lib
directories set.
Summary: generated pkg config file is broken (was: generated pkg
config file doesn't actually include paths if a different install location is
used)
generated pkg config file is broken
---
Key: PROTON-170
URL: https://issues.apache.org/jira/browse/PROTON-170
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Affects Versions: 0.2
Reporter: Gordon Sim
Assignee: Andrew Stitcher
Attachments: PROTON-170.patch
E.g. cmake -DCMAKE_INSTALL_PREFIX=/path/to/non-standard/install make
install will install a pkg config file that doesn't have the include and lib
directories set.
Also Cflags is set to -I${includedir} which breaks compilation even for a
standard install if the includedir is not set.
--
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-173) Message annotations not properly encoded
Hiram Chirino created PROTON-173: Summary: Message annotations not properly encoded Key: PROTON-173 URL: https://issues.apache.org/jira/browse/PROTON-173 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Hiram Chirino Attachments: PROTON-173.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-173) Message annotations not properly encoded
[ https://issues.apache.org/jira/browse/PROTON-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-173: - Attachment: PROTON-173.patch Attaching patch with fix. Message annotations not properly encoded Key: PROTON-173 URL: https://issues.apache.org/jira/browse/PROTON-173 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Hiram Chirino Attachments: PROTON-173.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-173) Message annotations not properly encoded
[ https://issues.apache.org/jira/browse/PROTON-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-173. Resolution: Fixed Fix Version/s: 0.3 Assignee: Rob Godfrey Patch applied Message annotations not properly encoded Key: PROTON-173 URL: https://issues.apache.org/jira/browse/PROTON-173 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Hiram Chirino Assignee: Rob Godfrey Fix For: 0.3 Attachments: PROTON-173.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-154) link attach, detach, attach sequence on single session does not result in a new link for the 2nd attach
[
https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13507406#comment-13507406
]
Rob Godfrey commented on PROTON-154:
I've applied the patch for proton-j as a temporary measure since this is
causing Hiram issues right now... but this is not a real solution - it will
just manifest in different use cases being broken.
link attach, detach, attach sequence on single session does not result in a
new link for the 2nd attach
---
Key: PROTON-154
URL: https://issues.apache.org/jira/browse/PROTON-154
Project: Qpid Proton
Issue Type: Bug
Components: proton-c, proton-j
Reporter: Hiram Chirino
Attachments: PROTON-154.patch, PROTON-154-test.patch
Protocol trace:
tcp://127.0.0.1:58348 | RECV: Attach{name='topic', handle=1, role=RECEIVER,
sndSettleMode=0, rcvSettleMode=0,
source=Source{address='topic://testJoramTopic', durable=2,
expiryPolicy=never, timeout=0, dynamic=false, dynamicNodeProperties=null,
distributionMode=copy, filter=null, defaultOutcome=null, outcomes=null,
capabilities=null}, target=Target{address='null', durable=0,
expiryPolicy=session-end, timeout=0, dynamic=false,
dynamicNodeProperties=null, capabilities=null}, unsettled=null,
incompleteUnsettled=false, initialDeliveryCount=null, maxMessageSize=null,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
tcp://127.0.0.1:58348 | SENT: Attach{name='topic', handle=1, role=SENDER,
sndSettleMode=2, rcvSettleMode=0,
source=Source{address='topic://testJoramTopic', durable=2,
expiryPolicy=never, timeout=0, dynamic=false, dynamicNodeProperties=null,
distributionMode=copy, filter=null, defaultOutcome=null, outcomes=null,
capabilities=null}, target=Target{address='null', durable=0,
expiryPolicy=session-end, timeout=0, dynamic=false,
dynamicNodeProperties=null, capabilities=null}, unsettled=null,
incompleteUnsettled=false, initialDeliveryCount=0, maxMessageSize=null,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
tcp://127.0.0.1:58348 | RECV: Flow{nextIncomingId=1, incomingWindow=2048,
nextOutgoingId=0, outgoingWindow=2048, handle=1, deliveryCount=0,
linkCredit=100, available=null, drain=false, echo=false, properties=null}
tcp://127.0.0.1:58348 | RECV: Detach{handle=1, closed=true, error=null}
tcp://127.0.0.1:58348 | SENT: Detach{handle=1, closed=false, error=null}
tcp://127.0.0.1:58348 | RECV: Attach{name='topic', handle=1, role=RECEIVER,
sndSettleMode=0, rcvSettleMode=0, source=null,
target=Target{address='644cf32c-d6c7-45eb-a8b7-3018d4c9594e', durable=0,
expiryPolicy=session-end, timeout=0, dynamic=false,
dynamicNodeProperties=null, capabilities=null}, unsettled=null,
incompleteUnsettled=false, initialDeliveryCount=null, maxMessageSize=null,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
no link is produced on the second attach when you call:
protonConnection.linkHead(UNINITIALIZED_SET, INITIALIZED_SET);
--
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: Language example apps...
On Tue, Nov 20, 2012 at 2:34 PM, Darryl L. Pierce dpie...@redhat.comwrote: Last week Justin asked me to take a look at the examples for Proton across language bindings. What I found are the following: C Python Ruby Perl Mailbox (Raw API)[ ] [X] [X] [ ] Send/Receive (Messenger classes) [ ] [X] [X] [X] Send/Receive (Non-Messenger) [X] [ ] [ ] [ ] We also have a PHP binding and it has some examples also. What came out of the discussion was that there's a definite lack of depth with the examples. The Mailbox demo is a nice, specific example of stored messaging. The Send/Receive examples show very simple point-to-point messaging. But what else should be included in examples? The first thing that comes to mind is an example demonstrating subscriptions. Ideas? A couple of random thoughts off the top of my head... I think the focus for the dynamic language bindings should really be messenger based examples. I would say it's really not worth having non messenger examples for the dynamic languages, particularly as those kinds of examples are much more involved and maintaining duplicate examples involves some significant maintenance effort. I would rather see a very well maintained/structured C example for the non messenger stuff. In fact I'd go so far as to say we shouldn't bother exposing the non messenger APIs through the bindings at all, with the exception of python for testing purposes of course. To be clear I'm not opposed to exposing them, I just don't think there is any demand at this point and I think it just creates unnecessary work until there is. In terms of depth, I'm concerned that deep examples will be difficult/impossible to maintain well in 5 different languages (6 if we do something with C++). What I'd suggest we start with is a basic, well thought out, but simple messenger based example geared towards getting people started, and strive to keep that consistent and up to date across all the bindings. I'd keep deep scenarios to one language only (at least at first), choosing whichever seems most appropriate for that particular deep scenario. --Rafael
[jira] [Commented] (PROTON-170) generated pkg config file is broken
[
https://issues.apache.org/jira/browse/PROTON-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13507600#comment-13507600
]
Andrew Stitcher commented on PROTON-170:
No problem with the comment change! (although I did copy the initial file
directly from qpid so I expect the same problem exists there)
I'm not 100% sure about the fix you've got there since I don't think that
CMAKE_INSTALL_PREFIX has to be an absolute path (and I seem to remember
discussing with Rafi that in fact that is the way he uses CMAKE_INSTALL_PREFIX).
I think it'd be more flexible to add in definitions for LIBDIR and INCLUDEDIR
to CMakeLists.txt rather than change the .pc file (that is how we do it in
qpid) - it seems I just failed to copy it over correctly from qpid and didn't
notice
generated pkg config file is broken
---
Key: PROTON-170
URL: https://issues.apache.org/jira/browse/PROTON-170
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Affects Versions: 0.2
Reporter: Gordon Sim
Assignee: Andrew Stitcher
Attachments: PROTON-170.patch
E.g. cmake -DCMAKE_INSTALL_PREFIX=/path/to/non-standard/install make
install will install a pkg config file that doesn't have the include and lib
directories set.
Also Cflags is set to -I${includedir} which breaks compilation even for a
standard install if the includedir is not set.
--
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-170) generated pkg config file is broken
[
https://issues.apache.org/jira/browse/PROTON-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13507609#comment-13507609
]
Gordon Sim commented on PROTON-170:
---
The comment was added after you put the template into protons tree (I think as
part of some automated process in response to RAT), so in qpid it has no
comment (which I actually think is probably not a problem anyway).
generated pkg config file is broken
---
Key: PROTON-170
URL: https://issues.apache.org/jira/browse/PROTON-170
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Affects Versions: 0.2
Reporter: Gordon Sim
Assignee: Andrew Stitcher
Attachments: PROTON-170.patch
E.g. cmake -DCMAKE_INSTALL_PREFIX=/path/to/non-standard/install make
install will install a pkg config file that doesn't have the include and lib
directories set.
Also Cflags is set to -I${includedir} which breaks compilation even for a
standard install if the includedir is not set.
--
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: Language example apps...
On Fri, Nov 30, 2012 at 12:36:34PM -0500, Rafael Schloming wrote: On Tue, Nov 20, 2012 at 2:34 PM, Darryl L. Pierce dpie...@redhat.comwrote: Last week Justin asked me to take a look at the examples for Proton across language bindings. What I found are the following: C Python Ruby Perl Mailbox (Raw API)[ ] [X] [X] [ ] Send/Receive (Messenger classes) [ ] [X] [X] [X] Send/Receive (Non-Messenger) [X] [ ] [ ] [ ] We also have a PHP binding and it has some examples also. Yeah, sorry to forget that. What came out of the discussion was that there's a definite lack of depth with the examples. The Mailbox demo is a nice, specific example of stored messaging. The Send/Receive examples show very simple point-to-point messaging. But what else should be included in examples? The first thing that comes to mind is an example demonstrating subscriptions. Ideas? A couple of random thoughts off the top of my head... I think the focus for the dynamic language bindings should really be messenger based examples. I would say it's really not worth having non messenger examples for the dynamic languages, particularly as those kinds of examples are much more involved and maintaining duplicate examples involves some significant maintenance effort. I would rather see a very well maintained/structured C example for the non messenger stuff. In fact I'd go so far as to say we shouldn't bother exposing the non messenger APIs through the bindings at all, with the exception of python for testing purposes of course. To be clear I'm not opposed to exposing them, I just don't think there is any demand at this point and I think it just creates unnecessary work until there is. In terms of depth, I'm concerned that deep examples will be difficult/impossible to maintain well in 5 different languages (6 if we do something with C++). What I'd suggest we start with is a basic, well thought out, but simple messenger based example geared towards getting people started, and strive to keep that consistent and up to date across all the bindings. I'd keep deep scenarios to one language only (at least at first), choosing whichever seems most appropriate for that particular deep scenario. If we keep the languages as consist as possible across the bindings, then one language doing a deep example and others doing more general examples should be workable. Assuming the one language is as easy to understand for someone not familiar with it to follow. -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/ pgpNjSPMiZ3Yn.pgp Description: PGP signature
[jira] [Created] (PROTON-174) [proton-j contrib] Ehance the JMS mapping logic to support carrying type info for the JMSDestination and JMSReplyTo, also support mapping the JMSX properties in AMQP Appl
Hiram Chirino created PROTON-174: Summary: [proton-j contrib] Ehance the JMS mapping logic to support carrying type info for the JMSDestination and JMSReplyTo, also support mapping the JMSX properties in AMQP Application properties Key: PROTON-174 URL: https://issues.apache.org/jira/browse/PROTON-174 Project: Qpid Proton Issue Type: Improvement 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-174) [proton-j contrib] Ehance the JMS mapping logic to support carrying type info for the JMSDestination and JMSReplyTo, also support mapping the JMSX properties in AMQP Appl
[ https://issues.apache.org/jira/browse/PROTON-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-174: - Attachment: PROTON-174.patch Attaching patch to fix the issue. [proton-j contrib] Ehance the JMS mapping logic to support carrying type info for the JMSDestination and JMSReplyTo, also support mapping the JMSX properties in AMQP Application properties Key: PROTON-174 URL: https://issues.apache.org/jira/browse/PROTON-174 Project: Qpid Proton Issue Type: Improvement Reporter: Hiram Chirino Attachments: PROTON-174.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
