[jira] [Assigned] (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:all-tabpanel ] Dominic Evans reassigned PROTON-154: Assignee: Dominic Evans > 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 >Assignee: Dominic Evans > Attachments: PROTON-154-test.patch, PROTON-154.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}, 2target=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 was sent by Atlassian JIRA (v6.3.4#6332)
[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-tabpanel&focusedCommentId=14314292#comment-14314292 ] ASF GitHub Bot commented on PROTON-154: --- GitHub user dnwe opened a pull request: https://github.com/apache/qpid-proton/pull/7 PROTON-154: proton-j attach same link on a session Link attach, detach, attach sequence on single session did not result in a new link being established for the 2nd attach, it was just quietly ignored. You can merge this pull request into a Git repository by running: $ git pull https://github.com/dnwe/qpid-proton fix-proton-154 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-proton/pull/7.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #7 commit e6d36bab841262335e34a55f19933499f668a53d Author: Dominic Evans Date: 2015-02-10T11:36:17Z PROTON-154: proton-j attach same link on a session Link attach, detach, attach sequence on single session did not result in a new link being established for the 2nd attach, it was just quietly ignored. > 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 >Assignee: Dominic Evans > Attachments: PROTON-154-test.patch, PROTON-154.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}, 2target=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 was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-154) proton-j: 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:all-tabpanel ] Dominic Evans updated PROTON-154: - Summary: proton-j: link attach, detach, attach sequence on single session does not result in a new link for the 2nd attach (was: link attach, detach, attach sequence on single session does not result in a new link for the 2nd attach) > proton-j: 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 >Assignee: Dominic Evans > Attachments: PROTON-154-test.patch, PROTON-154.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}, 2target=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 was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-154) proton-j: 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-tabpanel&focusedCommentId=14314293#comment-14314293 ] Dominic Evans commented on PROTON-154: -- hit this issue on proton-j in HEAD, no longer appears to be an issue on proton-c or any of the bindings thereof > proton-j: 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 >Assignee: Dominic Evans > Attachments: PROTON-154-test.patch, PROTON-154.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}, 2target=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 was sent by Atlassian JIRA (v6.3.4#6332)
Re: Non-reactive engine examples?
On Tue, 2015-02-03 at 16:26 -0500, Darryl L. Pierce wrote: > On Mon, Feb 02, 2015 at 09:12:22AM -0500, Darryl L. Pierce wrote: > > Are there any example apps for Python that don't use the reactive APIs? > > If no examples, perhaps a primer of how the logical components of the > enger interact to help guide providing an example? > Not sure about Rafi's new C reactor but Gordon's util.py contains a BlockingConnection which allows you to do simple blocking command-style messaging built on top of the reactive framework. There's a utils.SyncRequestResponse class I added that implements the request-response pattern using BlockingConnection. You can use these quite similarly to an API like qpid::messaging. IMO this is the way to go - the simpler patterns are built over the reactor framework so that they are easy to use without worrying about reactive programming *but* the power of the reactive framework is lurking just below the surface when you need it.