[
https://issues.apache.org/jira/browse/PROTON-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262566#comment-15262566
]
Sreeram Garlapati commented on PROTON-1185:
-------------------------------------------
To help the understand the symptoms of the issue better - both are very similar
issues. In 1171 'transport read stack' experienced the stuck issue - where as
in 1185 - 'transport write stack' has this issue.
> [proton-j] writing to the transport stack doesn't flush all bytes to the
> Network
> --------------------------------------------------------------------------------
>
> Key: PROTON-1185
> URL: https://issues.apache.org/jira/browse/PROTON-1185
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Affects Versions: 0.12.2
> Environment: All
> Reporter: Sreeram Garlapati
> Labels: proton-j, send-stuck
> Fix For: 0.13.0
>
>
> We are experiencing this issue intermittently - writing to Proton-j transport
> stack doesn't flush bytes to the Network. The application remains in "stuck
> state" - until more bytes are written to that Transport.
> We are experiencing this in both these APIs - SenderImpl.send(...) and
> ReceiverImpl.flow(...) - which under-the-covers writes bytes to Transport. We
> can see our Traces where we are invoking these APIs - but at this point - the
> Proton frames (set PN_TRACE_FRM=1) stops.
> We use SSL transport and our Amqp layer is here:
> https://github.com/Azure/azure-event-hubs/tree/master/java/azure-eventhubs/src/main/java/com/microsoft/azure/servicebus/amqp
> Please let me know what exact information will be useful to diagnose this
> issue.
> This issue currently consistently repro's after Sending on 1 Link (on 1
> Session - 1 AmqpConnection) **for a long time**. While I am trying hard to
> break this down to a simplest possible reproducer code - I filed the issue to
> communicate ahead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
