I spoke a bit too soon in my first reply. The tracking windows are
*supposed* to be measured from the point where the tracker is first
assigned, so from when you call put or get. This means that it shouldn't
matter how many times you call recv or how much credit recv gives out, the
only thing that
[
https://issues.apache.org/jira/browse/PROTON-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming reassigned PROTON-295:
--
Assignee: Rafael H. Schloming
recv(-1) + incoming_window == bad
[
https://issues.apache.org/jira/browse/PROTON-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross reassigned PROTON-294:
---
Assignee: Ted Ross
Driver - Enable TCP_NODELAY on connections by default.
[
https://issues.apache.org/jira/browse/PROTON-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jin updated PROTON-297:
---
Attachment: proton_poll_busy_fix_arm.patch
Patch that fixes this issue.
100% CPU usage on ARM in
[
https://issues.apache.org/jira/browse/PROTON-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jin updated PROTON-297:
---
Description:
Deep down pn_messenger_recv() issues a poll() with a specific timeout. On ARM9
the poll timeout is
Cliff Jansen created PROTON-298:
---
Summary: proton-c on Android
Key: PROTON-298
URL: https://issues.apache.org/jira/browse/PROTON-298
Project: Qpid Proton
Issue Type: Wish
Components:
[
https://issues.apache.org/jira/browse/PROTON-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated PROTON-294:
Summary: Driver - Enable TCP_NODELAY on connections by default (posix)
(was: Driver - Enable TCP_NODELAY
[
https://issues.apache.org/jira/browse/PROTON-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross resolved PROTON-294.
-
Resolution: Fixed
Driver - Enable TCP_NODELAY on connections by default (posix)