> On Sep 9, 2016, at 2:22 PM, Alan Carroll
> wrote:
>
> 1.
So why the output array then?
>
>
>On Friday, September 9, 2016 1:19 PM, James Peach
> wrote:
>
>
>
>> On Sep 9, 2016, at 10:55 AM, Alan Carroll
>> wrote:
>>
>> No. I'm not completely sure what I meant when I wrote that
1.
On Friday, September 9, 2016 1:19 PM, James Peach wrote:
> On Sep 9, 2016, at 10:55 AM, Alan Carroll
> wrote:
>
> No. I'm not completely sure what I meant when I wrote that (maybe it was a
> typo). My view on review was that it should be an in/out parameter where the
> tag (poss
Based on this data the most likely explanation is a plugin that didn't call
TSHttpTxnReenable().
On Friday, September 9, 2016 2:04 PM, Shu Kit Chan
wrote:
Is there any plugins you are using?
On Fri, Sep 9, 2016 at 10:10 AM, Siddharth Agarwal
wrote:
> Hi,
>
> We are on the traffic se
Is there any plugins you are using?
On Fri, Sep 9, 2016 at 10:10 AM, Siddharth Agarwal
wrote:
> Hi,
>
> We are on the traffic server 6.2 release. We are experiencing performance
> issues with this release and have enabled slow request logging. Our health
> check end point sometimes is taking taki
> On Sep 9, 2016, at 10:55 AM, Alan Carroll
> wrote:
>
> No. I'm not completely sure what I meant when I wrote that (maybe it was a
> typo). My view on review was that it should be an in/out parameter where the
> tag (possibly just a prefix) is passed in and the actual tag found is passed
>
No. I'm not completely sure what I meant when I wrote that (maybe it was a
typo). My view on review was that it should be an in/out parameter where the
tag (possibly just a prefix) is passed in and the actual tag found is passed
back. Susan has convinced me it would be better to make split that
> On Sep 9, 2016, at 10:15 AM, Susan Hinrichs
> wrote:
>
>
>
> On 9/9/2016 12:01 PM, James Peach wrote:
>>> On Sep 9, 2016, at 9:39 AM, Susan Hinrichs
>>> wrote:
>>>
>>> I'd like to propose a slight tweak for TSHttpTxnClientProtocolStackContains
>>> and TSHttpSsnClientProtocolStackContain
On 9/9/2016 12:01 PM, James Peach wrote:
On Sep 9, 2016, at 9:39 AM, Susan Hinrichs
wrote:
I'd like to propose a slight tweak for TSHttpTxnClientProtocolStackContains and
TSHttpSsnClientProtocolStackContains
Replace the tag argument with two explicit input and output arguments, e.g.
int T
Hi,
We are on the traffic server 6.2 release. We are experiencing performance
issues with this release and have enabled slow request logging. Our health
check end point sometimes is taking taking more than 3 seconds to respond.
Our CPU is idle. We are seeing most of time spent in plugin_total whil
> On Sep 9, 2016, at 9:39 AM, Susan Hinrichs
> wrote:
>
> I'd like to propose a slight tweak for TSHttpTxnClientProtocolStackContains
> and TSHttpSsnClientProtocolStackContains
>
> Replace the tag argument with two explicit input and output arguments, e.g.
>
> int TSHttpTxnClientProtocolStac
I'd like to propose a slight tweak for
TSHttpTxnClientProtocolStackContains and
TSHttpSsnClientProtocolStackContains
Replace the tag argument with two explicit input and output arguments, e.g.
int TSHttpTxnClientProtocolStackContains(TSHttpTxn txnp, char const
*contains_tag, char const **spec
11 matches
Mail list logo