[
https://issues.apache.org/jira/browse/TS-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Peach updated TS-4922:
----------------------------
Description:
When proxying from a plugin, you call {{TSVConnWrite}} passing in a
{{TSIOBufferReader}} that is specific for the write side of the VC. The
implication is that the core will use this reader to read out of the buffer as
the plugin writes into it.
However, if you subsequently call {{TSIOBufferReaderAvail}} on the buffer
reader that you created, you will find that this count of available bytes never
goes down. It seems possible (likely?) that the consumer side of the write
never calls {{consume()}} on the reader.
This can be demonstrated using the {{example/passthru/passthru.cc}}.
was:
When proxying from a plugin, you call {{TSVConnWrite}} passing in a
{TSIOBufferReader}} that is specific for the write side of the VC. The
implication is that the core will use this reader to read out of the buffer as
the plugin writes into it.
However, if you subsequently call {{TSIOBufferReaderAvail}} on the buffer
reader that you created, you will find that this count of available bytes never
goes down. It seems possible (likely?) that the consumer side of the write
never calls {{consume()}} on the reader.
This can be demonstrated using the {{example/passthru/passthru.cc}}.
> TSIOBufferReaderAvail not updates by the VConn write side
> ---------------------------------------------------------
>
> Key: TS-4922
> URL: https://issues.apache.org/jira/browse/TS-4922
> Project: Traffic Server
> Issue Type: Bug
> Components: TS API
> Reporter: James Peach
>
> When proxying from a plugin, you call {{TSVConnWrite}} passing in a
> {{TSIOBufferReader}} that is specific for the write side of the VC. The
> implication is that the core will use this reader to read out of the buffer
> as the plugin writes into it.
> However, if you subsequently call {{TSIOBufferReaderAvail}} on the buffer
> reader that you created, you will find that this count of available bytes
> never goes down. It seems possible (likely?) that the consumer side of the
> write never calls {{consume()}} on the reader.
> This can be demonstrated using the {{example/passthru/passthru.cc}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
