[
https://issues.apache.org/jira/browse/PROTON-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593726#comment-13593726
]
Rafael H. Schloming commented on PROTON-259:
--------------------------------------------
I wouldn't say it's a bug to create deliveries and/or receivers irrespective of
endpoint state. The endpoint state captures the state of the remote/local setup
handshake, but it's really kind of orthogonal to the data structures that
capture the state of messages in transit. Certainly for recovery you need to
create deliveries on links prior to opening them and you need to be able to
fully access and examine the link data structure after the endpoint is closed.
Put another way, the CLOSED state is really about controlling what you want to
communicate to the remote endpoint rather than controlling how you want to use
the endpoint data structures locally.
> proton-j engine operations do not check if the endpoint is already closed
> -------------------------------------------------------------------------
>
> Key: PROTON-259
> URL: https://issues.apache.org/jira/browse/PROTON-259
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Affects Versions: 0.3
> Reporter: Philip Harvey
>
> Operations such as SessionImpl#receiver(receiverName) and LinkImpl#delivery
> do not check the state of the endpoint. I believe they should throw an
> exception.
> Moreover, I notice that the following sequence of calls cause the transport
> to produce no output:
> ---------------
> sender.close;
> // deliberately use a closed sender.
> // The presence of this line causes the subsequent transport.output to
> produce zero bytes.
> sender.delivery(deliveryTag);
> transport.output(....);
> ---------------
--
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
