[jira] [Created] (PROTON-153) [proton-j] Sender should throw an exception if send is called after the endpoint is locally closed.
Hiram Chirino created PROTON-153: Summary: [proton-j] Sender should throw an exception if send is called after the endpoint is locally closed. Key: PROTON-153 URL: https://issues.apache.org/jira/browse/PROTON-153 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-153) [proton-j] Sender should throw an exception if send is called after the endpoint is locally closed.
[ https://issues.apache.org/jira/browse/PROTON-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-153: - Attachment: PROTON-153.patch attaching possible fix. > [proton-j] Sender should throw an exception if send is called after the > endpoint is locally closed. > --- > > Key: PROTON-153 > URL: https://issues.apache.org/jira/browse/PROTON-153 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Reporter: Hiram Chirino > Attachments: PROTON-153.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-153) [proton-j] Sender should throw an exception if send is called after the endpoint is locally closed.
[ https://issues.apache.org/jira/browse/PROTON-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-153. Resolution: Fixed Fix Version/s: 0.3 > [proton-j] Sender should throw an exception if send is called after the > endpoint is locally closed. > --- > > Key: PROTON-153 > URL: https://issues.apache.org/jira/browse/PROTON-153 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Reporter: Hiram Chirino >Assignee: Rob Godfrey > Fix For: 0.3 > > Attachments: PROTON-153.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] [Assigned] (PROTON-153) [proton-j] Sender should throw an exception if send is called after the endpoint is locally closed.
[ https://issues.apache.org/jira/browse/PROTON-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned PROTON-153: -- Assignee: Rob Godfrey > [proton-j] Sender should throw an exception if send is called after the > endpoint is locally closed. > --- > > Key: PROTON-153 > URL: https://issues.apache.org/jira/browse/PROTON-153 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Reporter: Hiram Chirino >Assignee: Rob Godfrey > Fix For: 0.3 > > Attachments: PROTON-153.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-154) link attach, detach, attach sequence on single session does not result in a new link for the 2nd attach
Hiram Chirino created PROTON-154: Summary: 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 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-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 ] Hiram Chirino updated PROTON-154: - Component/s: 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-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-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
]
Hiram Chirino updated PROTON-154:
-
Description:
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);
> 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-j
>Reporter: Hiram Chirino
>
> 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, initialDe
[jira] [Created] (PROTON-155) [proton-j] Detach toString() does not include the handle field.
Hiram Chirino created PROTON-155: Summary: [proton-j] Detach toString() does not include the handle field. Key: PROTON-155 URL: https://issues.apache.org/jira/browse/PROTON-155 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Hiram Chirino Attachments: PROTON-155.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-155) [proton-j] Detach toString() does not include the handle field.
[ https://issues.apache.org/jira/browse/PROTON-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-155: - Attachment: PROTON-155.patch attaching fix. > [proton-j] Detach toString() does not include the handle field. > --- > > Key: PROTON-155 > URL: https://issues.apache.org/jira/browse/PROTON-155 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Reporter: Hiram Chirino > Attachments: PROTON-155.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-156) [proton-j] Detach close field is not being set to true.
Hiram Chirino created PROTON-156: Summary: [proton-j] Detach close field is not being set to true. Key: PROTON-156 URL: https://issues.apache.org/jira/browse/PROTON-156 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] [Resolved] (PROTON-155) [proton-j] Detach toString() does not include the handle field.
[ https://issues.apache.org/jira/browse/PROTON-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-155. Resolution: Fixed Fix Version/s: 0.3 > [proton-j] Detach toString() does not include the handle field. > --- > > Key: PROTON-155 > URL: https://issues.apache.org/jira/browse/PROTON-155 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Reporter: Hiram Chirino >Assignee: Rob Godfrey > Fix For: 0.3 > > Attachments: PROTON-155.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] [Assigned] (PROTON-155) [proton-j] Detach toString() does not include the handle field.
[ https://issues.apache.org/jira/browse/PROTON-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned PROTON-155: -- Assignee: Rob Godfrey > [proton-j] Detach toString() does not include the handle field. > --- > > Key: PROTON-155 > URL: https://issues.apache.org/jira/browse/PROTON-155 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Reporter: Hiram Chirino >Assignee: Rob Godfrey > Fix For: 0.3 > > Attachments: PROTON-155.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-136) Add support for SSL session resumption
[ https://issues.apache.org/jira/browse/PROTON-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502557#comment-13502557 ] Affan Dar commented on PROTON-136: -- The client side user model looks good to me and furthermore I think if/when support for RFC 5077 is added then the same user model will continue to work which is great. Is this going to be available for messenger API consumers as well? > 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 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
