[jira] [Created] (TS-3878) icp.config is not reloadable

Gota Adachi created TS-3878: --- Summary: icp.config is not reloadable Key: TS-3878 URL: https://issues.apache.org/jira/browse/TS-3878 Project: Traffic Server Issue Type: Bug Components:

[jira] [Commented] (TS-3872) Enhance open_write_fail_action feature to support returning error on revalidation.

[ https://issues.apache.org/jira/browse/TS-3872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14724593#comment-14724593 ] William Bardwell commented on TS-3872: -- Do any of those options go ahead and do a conditional revalidate

[jira] [Updated] (TS-3878) icp.config is not reloadable

[ https://issues.apache.org/jira/browse/TS-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gota Adachi updated TS-3878: Affects Version/s: 4.2.3 5.3.1 > icp.config is not reloadable >

[jira] [Commented] (TS-3874) Header-rewrite doesn't support multiple header values in conditionals

[ https://issues.apache.org/jira/browse/TS-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14723558#comment-14723558 ] Thomas Jackson commented on TS-3874: I'm fine with a backport, although I haven't done one before-- whats

[jira] [Updated] (TS-3874) Header-rewrite doesn't support multiple header values in conditionals

[ https://issues.apache.org/jira/browse/TS-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudheer Vinukonda updated TS-3874: -- Backport to Version: 6.0.0 > Header-rewrite doesn't support multiple header values in conditionals

[jira] [Commented] (TS-3874) Header-rewrite doesn't support multiple header values in conditionals

[ https://issues.apache.org/jira/browse/TS-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14723561#comment-14723561 ] Sudheer Vinukonda commented on TS-3874: --- You just need to mark the jira with "Back port to Version" to

Jenkins build is still unstable: tsqa-lint #514

See

Jenkins build is still unstable: tsqa-lint #515

See

Build failed in Jenkins: tsqa-master #828

See Changes: [nkew] stream_editor: #define WHITESPACE rather than spell it out every time -- [...truncated 491 lines...] INFO 2015-08-31 17:42:32,093 - Client disconnected INFO 2015-08-31

[jira] [Created] (TS-3875) Have SPDY allocate the MIOBuffers directly so we can track memory usage better

Bryan Call created TS-3875: -- Summary: Have SPDY allocate the MIOBuffers directly so we can track memory usage better Key: TS-3875 URL: https://issues.apache.org/jira/browse/TS-3875 Project: Traffic Server

[jira] [Commented] (TS-3875) Have SPDY allocate the MIOBuffers directly so we can track memory usage better

[ https://issues.apache.org/jira/browse/TS-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14723915#comment-14723915 ] Bryan Call commented on TS-3875: Instead of using TSIOBufferCreate, we can use

[jira] [Updated] (TS-3875) Have SPDY allocate the MIOBuffers directly so we can track memory usage better

[ https://issues.apache.org/jira/browse/TS-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-3875: --- Affects Version/s: 5.3.0 > Have SPDY allocate the MIOBuffers directly so we can track memory usage better >

[jira] [Assigned] (TS-3875) Have SPDY allocate the MIOBuffers directly so we can track memory usage better

[ https://issues.apache.org/jira/browse/TS-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call reassigned TS-3875: -- Assignee: Bryan Call > Have SPDY allocate the MIOBuffers directly so we can track memory usage better >

[jira] [Commented] (TS-3875) Have SPDY allocate the MIOBuffers directly so we can track memory usage better

[ https://issues.apache.org/jira/browse/TS-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14723919#comment-14723919 ] ASF subversion and git services commented on TS-3875: - Commit

Jenkins build is still unstable: tsqa-lint #516

See

[jira] [Updated] (TS-3875) Have SPDY allocate the MIOBuffers directly so we can track memory usage better

[ https://issues.apache.org/jira/browse/TS-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Carlin updated TS-3875: - Labels: yahoo (was: ) > Have SPDY allocate the MIOBuffers directly so we can track memory usage better >

[jira] [Assigned] (TS-3876) add unit test framework for scripts for lua plugin

[ https://issues.apache.org/jira/browse/TS-3876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kit Chan reassigned TS-3876: Assignee: Kit Chan > add unit test framework for scripts for lua plugin >

[jira] [Created] (TS-3877) Add a tracking ClassAllocator to keep track of where the allocation happened

Bryan Call created TS-3877: -- Summary: Add a tracking ClassAllocator to keep track of where the allocation happened Key: TS-3877 URL: https://issues.apache.org/jira/browse/TS-3877 Project: Traffic Server

[jira] [Commented] (TS-3877) Add a tracking ClassAllocator to keep track of where the allocation happened

[ https://issues.apache.org/jira/browse/TS-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14724539#comment-14724539 ] ASF subversion and git services commented on TS-3877: - Commit

[jira] [Commented] (TS-3877) Add a tracking ClassAllocator to keep track of where the allocation happened

[ https://issues.apache.org/jira/browse/TS-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14724541#comment-14724541 ] Bryan Call commented on TS-3877: To use the TrackerClassAllocator you will need to replace the ClassAllocator

Jenkins build is still unstable: tsqa-lint #517

See

Jenkins build is still unstable: tsqa-lint #518

See

[jira] [Comment Edited] (TS-3877) Add a tracking ClassAllocator to keep track of where the allocation happened

[ https://issues.apache.org/jira/browse/TS-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14724541#comment-14724541 ] Bryan Call edited comment on TS-3877 at 9/1/15 1:34 AM: To use the

[jira] [Updated] (TS-3877) Add a tracking ClassAllocator to keep track of where the allocation happened

[ https://issues.apache.org/jira/browse/TS-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-3877: --- Component/s: Core > Add a tracking ClassAllocator to keep track of where the allocation happened >

[jira] [Updated] (TS-3877) Add a tracking ClassAllocator to keep track of where the allocation happened

[ https://issues.apache.org/jira/browse/TS-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-3877: --- Fix Version/s: 6.1.0 > Add a tracking ClassAllocator to keep track of where the allocation happened >

[jira] [Resolved] (TS-3877) Add a tracking ClassAllocator to keep track of where the allocation happened

[ https://issues.apache.org/jira/browse/TS-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call resolved TS-3877. Resolution: Fixed > Add a tracking ClassAllocator to keep track of where the allocation happened >

Build failed in Jenkins: tsqa-master #830

See Changes: [Bryan Call] TS-3877: Add a tracking ClassAllocator to keep track of where the allocation happened -- [...truncated 491 lines...] INFO 2015-09-01 01:43:38,841 - Client

[jira] [Updated] (TS-3878) icp.config is not reloadable

[ https://issues.apache.org/jira/browse/TS-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gota Adachi updated TS-3878: Attachment: ts-3878_5.3.x.patch ts-3878_master.patch > icp.config is not reloadable >

[jira] [Commented] (TS-3585) Redirection does not do DNS if cache is disabled

[ https://issues.apache.org/jira/browse/TS-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14723470#comment-14723470 ] Alan M. Carroll commented on TS-3585: - Fixed in commit 60ffbfda03997c018dac1d02118170c1eb1ecc1e. >