Jenkins build is back to normal : clang-analyzer #670

See

[jira] [Updated] (TS-3509) Access permissions for storage entries in cache.config changed

[ https://issues.apache.org/jira/browse/TS-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-3509: Backport to Version: (was: 5.3.0) > Access permissions for storage entries in cache.config changed >

[jira] [Updated] (TS-3520) Core dump in logging unmapped url path, when the request url maps to catch-all (default) remap rule

[ https://issues.apache.org/jira/browse/TS-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-3520: Backport to Version: (was: 5.3.0) > Core dump in logging unmapped url path, when the request url maps to > c

Build failed in Jenkins: tsqa-master #308

See Changes: [Bryan Call] TS-3519: HTTP/2 seeing a lot of GOAWAY frames being sent -- [...truncated 13210 lines...] 10 655 3280.200 48252217/4825221 2119 2119 2119 79359662

[jira] [Assigned] (TS-3511) Perl API seems to have a permission issue

[ https://issues.apache.org/jira/browse/TS-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber reassigned TS-3511: --- Assignee: Mark Torluemke Mark, do you think you could take a look at this? It's a blocker for 5.3.0 rel

[jira] [Closed] (TS-3509) Access permissions for storage entries in cache.config changed

[ https://issues.apache.org/jira/browse/TS-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber closed TS-3509. --- Resolution: Invalid Fix Version/s: (was: 6.0.0) Invalid, per [~dcarlin]. > Access permissions for sto

[jira] [Commented] (TS-3509) Access permissions for storage entries in cache.config changed

[ https://issues.apache.org/jira/browse/TS-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499224#comment-14499224 ] David Carlin commented on TS-3509: -- Please close as invalid. Appears to be an intermittent

[jira] [Updated] (TS-3520) Core dump in logging unmapped url path, when the request url maps to catch-all (default) remap rule

[ https://issues.apache.org/jira/browse/TS-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-3520: Fix Version/s: 5.3.0 > Core dump in logging unmapped url path, when the request url maps to > catch-all (defau

[jira] [Comment Edited] (TS-3511) Perl API seems to have a permission issue

[ https://issues.apache.org/jira/browse/TS-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499230#comment-14499230 ] Phil Sorber edited comment on TS-3511 at 4/17/15 4:37 AM: -- [~mtorlue

[jira] [Commented] (TS-3520) Core dump in logging unmapped url path, when the request url maps to catch-all (default) remap rule

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

[jira] [Commented] (TS-3375) Potential memory leak bug

[ https://issues.apache.org/jira/browse/TS-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499563#comment-14499563 ] Sudheer Vinukonda commented on TS-3375: --- It seems that the change in commit 8152dbfc2af

[jira] [Resolved] (TS-3519) HTTP/2 seeing a lot of GOAWAY frames being sent

[ https://issues.apache.org/jira/browse/TS-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber resolved TS-3519. - Resolution: Fixed Assignee: Bryan Call Resolving per [~bcall] > HTTP/2 seeing a lot of GOAWAY frames b

[jira] [Updated] (TS-3522) Seg Fault due to inactivity_cop after lost continutation from write_signal_and_update

[ https://issues.apache.org/jira/browse/TS-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-3522: Backport to Version: 5.3.0 > Seg Fault due to inactivity_cop after lost continutation from > write_signal_and_

[jira] [Updated] (TS-3519) HTTP/2 seeing a lot of GOAWAY frames being sent

[ https://issues.apache.org/jira/browse/TS-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-3519: Fix Version/s: 5.3.0 > HTTP/2 seeing a lot of GOAWAY frames being sent > --

[jira] [Updated] (TS-3519) HTTP/2 seeing a lot of GOAWAY frames being sent

[ https://issues.apache.org/jira/browse/TS-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-3519: Backport to Version: (was: 5.3.0) > HTTP/2 seeing a lot of GOAWAY frames being sent > ---

[jira] [Created] (TS-3529) Add a config option to allow ATS to start even if some certificates are bad

Susan Hinrichs created TS-3529: -- Summary: Add a config option to allow ATS to start even if some certificates are bad Key: TS-3529 URL: https://issues.apache.org/jira/browse/TS-3529 Project: Traffic Serv

[jira] [Commented] (TS-3529) Add a config option to allow ATS to start even if some certificates are bad

[ https://issues.apache.org/jira/browse/TS-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499859#comment-14499859 ] Susan Hinrichs commented on TS-3529: Issue was identified by [~reveller] > Add a config

[jira] [Updated] (TS-3530) HTTP/2 memory leak with headers

[ https://issues.apache.org/jira/browse/TS-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-3530: --- Affects Version/s: 5.3.0 > HTTP/2 memory leak with headers > --- > >

[jira] [Updated] (TS-3530) HTTP/2 memory leak with headers

[ https://issues.apache.org/jira/browse/TS-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-3530: --- Fix Version/s: 6.0.0 > HTTP/2 memory leak with headers > --- > > Key:

[jira] [Created] (TS-3530) HTTP/2 memory leak with headers

Bryan Call created TS-3530: -- Summary: HTTP/2 memory leak with headers Key: TS-3530 URL: https://issues.apache.org/jira/browse/TS-3530 Project: Traffic Server Issue Type: Bug Components: HT

[jira] [Updated] (TS-3530) HTTP/2 memory leak with headers

[ https://issues.apache.org/jira/browse/TS-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-3530: --- Backport to Version: 5.3.0 > HTTP/2 memory leak with headers > --- > >

[jira] [Commented] (TS-3522) Seg Fault due to inactivity_cop after lost continutation from write_signal_and_update

[ https://issues.apache.org/jira/browse/TS-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500065#comment-14500065 ] Alan M. Carroll commented on TS-3522: - Looking at a core dump from this on 5.3.0. The pr

[jira] [Commented] (TS-3530) HTTP/2 memory leak with headers

[ https://issues.apache.org/jira/browse/TS-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500100#comment-14500100 ] Bryan Call commented on TS-3530: Looks like it is leaking here: {code} ->13.99% (12,295,778B)

[jira] [Created] (TS-3531) cacheurl plugin not working in 5.3.0->5.3.x

Faysal Banna created TS-3531: Summary: cacheurl plugin not working in 5.3.0->5.3.x Key: TS-3531 URL: https://issues.apache.org/jira/browse/TS-3531 Project: Traffic Server Issue Type: Bug

[jira] [Updated] (TS-81) Have one single place to store and lookup remap rules irrespective of type

[ https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-81: Assignee: Sudheer Vinukonda > Have one single place to store and lookup remap rules irrespective of type > --

[jira] [Updated] (TS-81) Have one single place to store and lookup remap rules irrespective of type

[ https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-81: Fix Version/s: (was: sometime) 6.0.0 > Have one single place to store and lookup remap rul

[jira] [Updated] (TS-81) Have one single place to store and lookup remap rules irrespective of type

[ https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-81: Labels: incompatible (was: ) > Have one single place to store and lookup remap rules irrespective of type >

[jira] [Created] (TS-3532) Expose IOBuffers to C API

Brian Geffon created TS-3532: Summary: Expose IOBuffers to C API Key: TS-3532 URL: https://issues.apache.org/jira/browse/TS-3532 Project: Traffic Server Issue Type: Improvement Componen

[jira] [Updated] (TS-3529) Add a config option to allow ATS to start even if some certificates are bad

[ https://issues.apache.org/jira/browse/TS-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-3529: Fix Version/s: 6.0.0 > Add a config option to allow ATS to start even if some certificates are bad > --

[jira] [Updated] (TS-3529) Add a config option to allow ATS to start even if some certificates are bad

[ https://issues.apache.org/jira/browse/TS-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-3529: Backport to Version: 5.3.0 > Add a config option to allow ATS to start even if some certificates are bad >

[jira] [Updated] (TS-3531) cacheurl plugin not working in 5.3.0->5.3.x

[ https://issues.apache.org/jira/browse/TS-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-3531: Fix Version/s: 6.0.0 > cacheurl plugin not working in 5.3.0->5.3.x > --

[jira] [Assigned] (TS-2581) Add / modify APIs to allow easy freelist allocation of iobuffer's from C/C++ plugins

[ https://issues.apache.org/jira/browse/TS-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber reassigned TS-2581: --- Assignee: Brian Geffon (was: Phil Sorber) > Add / modify APIs to allow easy freelist allocation of iobu

[jira] [Closed] (TS-3532) Expose IOBuffers to C API

[ https://issues.apache.org/jira/browse/TS-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber closed TS-3532. --- Resolution: Duplicate Closing as Duplicate. > Expose IOBuffers to C API > - > >

[jira] [Assigned] (TS-3530) HTTP/2 memory leak with headers and more...

[ https://issues.apache.org/jira/browse/TS-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call reassigned TS-3530: -- Assignee: Bryan Call > HTTP/2 memory leak with headers and more... > -

[jira] [Updated] (TS-3530) HTTP/2 memory leak with headers and more...

[ https://issues.apache.org/jira/browse/TS-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-3530: --- Summary: HTTP/2 memory leak with headers and more... (was: HTTP/2 memory leak with headers) > HTTP/2 memory lea

[jira] [Commented] (TS-3530) HTTP/2 memory leak with headers and more...

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

[jira] [Commented] (TS-3531) cacheurl plugin not working in 5.3.0->5.3.x

[ https://issues.apache.org/jira/browse/TS-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500511#comment-14500511 ] Leif Hedstrom commented on TS-3531: --- [~psudaemon] Hmmm, if this is the case, it sounds like

[jira] [Commented] (TS-3530) HTTP/2 memory leak with headers and more...

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

[jira] [Resolved] (TS-3530) HTTP/2 memory leak with headers and more...

[ https://issues.apache.org/jira/browse/TS-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call resolved TS-3530. Resolution: Fixed > HTTP/2 memory leak with headers and more... > --- >

[jira] [Commented] (TS-3531) cacheurl plugin not working in 5.3.0->5.3.x

[ https://issues.apache.org/jira/browse/TS-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500521#comment-14500521 ] Sudheer Vinukonda commented on TS-3531: --- fwiw, i've also heard that background_fetch is

[jira] [Updated] (TS-3530) HTTP/2 memory leak with headers and more...

[ https://issues.apache.org/jira/browse/TS-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-3530: Fix Version/s: 5.3.0 > HTTP/2 memory leak with headers and more... > --

[jira] [Updated] (TS-3530) HTTP/2 memory leak with headers and more...

[ https://issues.apache.org/jira/browse/TS-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-3530: Backport to Version: (was: 5.3.0) > HTTP/2 memory leak with headers and more... > ---

Build failed in Jenkins: tsqa-master #309

See Changes: [Bryan Call] TS-3530: HTTP/2 memory leak with headers and more... [Bryan Call] TS-3530: Updated CHANGES -- [...truncated 13198 lines...] 10 119 594.600 10122023/

[jira] [Updated] (TS-3533) Coring when a plugin is enabled with 5.3.0

[ https://issues.apache.org/jira/browse/TS-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-3533: --- Fix Version/s: 6.0.0 > Coring when a plugin is enabled with 5.3.0 > -- >

[jira] [Created] (TS-3533) Coring when a plugin is enabled with 5.3.0

Bryan Call created TS-3533: -- Summary: Coring when a plugin is enabled with 5.3.0 Key: TS-3533 URL: https://issues.apache.org/jira/browse/TS-3533 Project: Traffic Server Issue Type: Bug Com

[jira] [Updated] (TS-3533) Coring when a plugin is enabled with 5.3.0

[ https://issues.apache.org/jira/browse/TS-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-3533: --- Affects Version/s: 5.3.0 > Coring when a plugin is enabled with 5.3.0 > -

[jira] [Updated] (TS-3522) Seg Fault due to inactivity_cop after lost continutation from write_signal_and_update

[ https://issues.apache.org/jira/browse/TS-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Susan Hinrichs updated TS-3522: --- Attachment: inactivity_crash.diff After looking at a few more cores, we have a theory on the scenario and

[jira] [Comment Edited] (TS-3522) Seg Fault due to inactivity_cop after lost continutation from write_signal_and_update

[ https://issues.apache.org/jira/browse/TS-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14501072#comment-14501072 ] Susan Hinrichs edited comment on TS-3522 at 4/18/15 3:49 AM: - Aft