[
https://issues.apache.org/jira/browse/TS-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson resolved TS-5039.
Resolution: Cannot Reproduce
> Crash when connecting to downed parent.
>
[
https://issues.apache.org/jira/browse/TS-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15676954#comment-15676954
]
Thomas Jackson commented on TS-5039:
Hmm, well I guess we close as can't repro then :/
> Crash when
[
https://issues.apache.org/jira/browse/TS-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670962#comment-15670962
]
Thomas Jackson commented on TS-5039:
[~jpe...@apache.org] spent a few minutes, but I can't seem to
[
https://issues.apache.org/jira/browse/TS-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15667666#comment-15667666
]
Thomas Jackson commented on TS-5039:
I should be able to take a look at this this week, doesn't sound
[
https://issues.apache.org/jira/browse/TS-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson closed TS-5052.
--
Resolution: Cannot Reproduce
Turns out this is only applicable to some backport builds I've made-- not
[
https://issues.apache.org/jira/browse/TS-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson reassigned TS-5052:
--
Assignee: Thomas Jackson
> Segfault in HostDB sync if something fails while not holding the
Thomas Jackson created TS-5052:
--
Summary: Segfault in HostDB sync if something fails while not
holding the parent continuation mutex
Key: TS-5052
URL: https://issues.apache.org/jira/browse/TS-5052
[
https://issues.apache.org/jira/browse/TS-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson closed TS-3067.
--
Resolution: Cannot Reproduce
>From the details in this ticket I'm unable to reproduce this issue. Sadly
[
https://issues.apache.org/jira/browse/TS-4968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson resolved TS-4968.
Resolution: Fixed
> Log a warning if connect_attempts_rr_retries is >=
> connect_attempts_max_retries
[
https://issues.apache.org/jira/browse/TS-4796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4796:
---
Backport to Version: 6.1.2
> ATS not closing origin connections on first RST from client
>
[
https://issues.apache.org/jira/browse/TS-4796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson resolved TS-4796.
Resolution: Fixed
> ATS not closing origin connections on first RST from client
>
[
https://issues.apache.org/jira/browse/TS-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4970:
---
Backport to Version: 5.3.2, 6.2.1
> Crash in INKVConnInternal when handle_event is called after
[
https://issues.apache.org/jira/browse/TS-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15596682#comment-15596682
]
Thomas Jackson commented on TS-4970:
This patch is now out running on our infra, and the issues have
[
https://issues.apache.org/jira/browse/TS-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15585605#comment-15585605
]
Thomas Jackson commented on TS-4970:
Not duplicate as they are PRs against different branches, although I
[
https://issues.apache.org/jira/browse/TS-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15583311#comment-15583311
]
Thomas Jackson commented on TS-4970:
after spending some time looking at it-- [~shinrich] is correct, I
[
https://issues.apache.org/jira/browse/TS-4969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson closed TS-4969.
--
Resolution: Duplicate
> Add log field for number of retries against origin
>
[
https://issues.apache.org/jira/browse/TS-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4970:
---
Summary: Crash in INKVConnInternal when handle_event is called after
destroy() (was: Crash in
[
https://issues.apache.org/jira/browse/TS-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson reassigned TS-4970:
--
Assignee: Thomas Jackson
> Crash in INKVConnInternal if handle_event is called after destroy()
>
Thomas Jackson created TS-4970:
--
Summary: Crash in INKVConnInternal if handle_event is called after
destroy()
Key: TS-4970
URL: https://issues.apache.org/jira/browse/TS-4970
Project: Traffic Server
Thomas Jackson created TS-4969:
--
Summary: Add log field for number of retries against origin
Key: TS-4969
URL: https://issues.apache.org/jira/browse/TS-4969
Project: Traffic Server
Issue Type:
Thomas Jackson created TS-4968:
--
Summary: Log a warning if connect_attempts_rr_retries is >=
connect_attempts_max_retries
Key: TS-4968
URL: https://issues.apache.org/jira/browse/TS-4968
Project: Traffic
[
https://issues.apache.org/jira/browse/TS-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15569429#comment-15569429
]
Thomas Jackson commented on TS-4960:
There is a fairly long chain of bugs around this-- so I'll attempt
[
https://issues.apache.org/jira/browse/TS-4509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson resolved TS-4509.
Resolution: Fixed
> Dropped keep-alive connections not being re-established (TS-3959 continued)
>
[
https://issues.apache.org/jira/browse/TS-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4921:
---
Description:
In {{HttpTransact::is_request_retryable}}, nothing seems to be retryable if you
have sent
[
https://issues.apache.org/jira/browse/TS-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4921:
---
Description:
In {{HttpTransact::is_request_retryable}}, nothing seems to be retryable if you
have sent
[
https://issues.apache.org/jira/browse/TS-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4921:
---
Description:
In {{HttpTransact::is_request_retryable}}, nothing seems to be retryable if you
have sent
[
https://issues.apache.org/jira/browse/TS-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4921:
---
Description:
In {{HttpTransact::is_request_retryable}}, nothing seems to be retryable if you
have sent
[
https://issues.apache.org/jira/browse/TS-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson reassigned TS-4921:
--
Assignee: Thomas Jackson
> Safe HTTP methods should be retryable.
>
[
https://issues.apache.org/jira/browse/TS-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4921:
---
Description:
In {{HttpTransact::is_request_retryable}}, nothing seems to be retryable if you
have sent
[
https://issues.apache.org/jira/browse/TS-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4915:
---
Description:
Saw this while testing fix for TS-4813 with debug enabled.
{code}
(gdb) bt full
#0
[
https://issues.apache.org/jira/browse/TS-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson resolved TS-4867.
Resolution: Fixed
> Race condition in RefCountCacheSerializer Initialization
>
[
https://issues.apache.org/jira/browse/TS-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4867:
---
Summary: Race condition in RefCountCacheSerializer (was: Potential race
condition in
[
https://issues.apache.org/jira/browse/TS-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4866:
---
Fix Version/s: 7.1.0
> Remove traffic_cop health checking.
> ---
>
>
[
https://issues.apache.org/jira/browse/TS-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4866:
---
Fix Version/s: (was: 7.1.0)
7.0.0
> Remove traffic_cop health checking.
>
[
https://issues.apache.org/jira/browse/TS-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4866:
---
Affects Version/s: 7.0.0
> Remove traffic_cop health checking.
> ---
>
>
[
https://issues.apache.org/jira/browse/TS-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4866:
---
Backport to Version: 7.0.0
> Remove traffic_cop health checking.
> ---
>
[
https://issues.apache.org/jira/browse/TS-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4867:
---
Summary: Race condition in RefCountCacheSerializer Initialization (was:
Race condition in
[
https://issues.apache.org/jira/browse/TS-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson reassigned TS-4867:
--
Assignee: Thomas Jackson
> Race condition in RefCountCacheSerializer Initialization
>
Thomas Jackson created TS-4867:
--
Summary: Potential race condition in RefCountCacheSerializer
Key: TS-4867
URL: https://issues.apache.org/jira/browse/TS-4867
Project: Traffic Server
Issue Type:
[
https://issues.apache.org/jira/browse/TS-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson resolved TS-4276.
Resolution: Fixed
> Segmentation fault when hostdb runs out of space
>
[
https://issues.apache.org/jira/browse/TS-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475729#comment-15475729
]
Thomas Jackson commented on TS-4276:
This is actually no longer an issue since the hostdb rewrite I did,
[
https://issues.apache.org/jira/browse/TS-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456173#comment-15456173
]
Thomas Jackson commented on TS-4684:
That is correct, and thanks :)
> Leaked references to HostDBInfos
[
https://issues.apache.org/jira/browse/TS-4796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson reassigned TS-4796:
--
Assignee: Thomas Jackson
> ATS not closing origin connections on first RST from client
>
[
https://issues.apache.org/jira/browse/TS-4796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4796:
---
Description:
*TLDR; similar to TS-4720 -- slower to close than it should, instead of never
closing*
As
Thomas Jackson created TS-4796:
--
Summary: ATS not closing origin connections on first RST from
client
Key: TS-4796
URL: https://issues.apache.org/jira/browse/TS-4796
Project: Traffic Server
[
https://issues.apache.org/jira/browse/TS-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4720:
---
Summary: ATS not properly closing origin connections in client abort
situations (was: ATS not properly
[
https://issues.apache.org/jira/browse/TS-4342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426814#comment-15426814
]
Thomas Jackson commented on TS-4342:
And replace it with what? Or are we planning on just dropping when
[
https://issues.apache.org/jira/browse/TS-4342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson reopened TS-4342:
> Connections queued when hitting `proxy.config.http.origin_max_connections`
> don't honor order
>
[
https://issues.apache.org/jira/browse/TS-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4343:
---
Fix Version/s: sometime
> When ATS hits `proxy.config.http.origin_max_connections`, the requests queued
[
https://issues.apache.org/jira/browse/TS-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4346:
---
Fix Version/s: sometime
> Requests that hit conneciton limits (max_origin_connections, etc.) incur a
>
[
https://issues.apache.org/jira/browse/TS-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson reopened TS-4343:
> When ATS hits `proxy.config.http.origin_max_connections`, the requests queued
> will not abort even if
[
https://issues.apache.org/jira/browse/TS-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426809#comment-15426809
]
Thomas Jackson commented on TS-4346:
Why would we close this won't fix? We simply need to queue the
[
https://issues.apache.org/jira/browse/TS-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson reopened TS-4346:
> Requests that hit conneciton limits (max_origin_connections, etc.) incur a
> hard coded latency hit
>
[
https://issues.apache.org/jira/browse/TS-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424816#comment-15424816
]
Thomas Jackson commented on TS-4027:
>From the looks of the report it sounds like the reported problem is
[
https://issues.apache.org/jira/browse/TS-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15422932#comment-15422932
]
Thomas Jackson commented on TS-2358:
I'm not sure if this is still an issue-- haven't run into that
[
https://issues.apache.org/jira/browse/TS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421988#comment-15421988
]
Thomas Jackson commented on TS-2134:
This should be fixed in 7.x (not sure exactly which patch, but I
[
https://issues.apache.org/jira/browse/TS-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson resolved TS-4720.
Resolution: Fixed
> ATS not properly closing origin connections in client abort situationsounce
>
[
https://issues.apache.org/jira/browse/TS-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4720:
---
Backport to Version: 6.2.1
Summary: ATS not properly closing origin connections in client
[
https://issues.apache.org/jira/browse/TS-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4710:
---
Fix Version/s: 7.0.0
> Make `proxy.config.srv_enabled` transaction overrideable
>
[
https://issues.apache.org/jira/browse/TS-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson resolved TS-4710.
Resolution: Fixed
> Make `proxy.config.srv_enabled` transaction overrideable
>
[
https://issues.apache.org/jira/browse/TS-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4720:
---
Comment: was deleted
(was: https://github.com/apache/trafficserver/pull/841)
> ATS not properly closing
[
https://issues.apache.org/jira/browse/TS-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408718#comment-15408718
]
Thomas Jackson commented on TS-4720:
https://github.com/apache/trafficserver/pull/841
> ATS not properly
[
https://issues.apache.org/jira/browse/TS-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4720:
---
Fix Version/s: 7.0.0
> ATS not properly closing origin connections in client abort situations
>
Thomas Jackson created TS-4720:
--
Summary: ATS not properly closing origin connections in client
abort situations
Key: TS-4720
URL: https://issues.apache.org/jira/browse/TS-4720
Project: Traffic Server
[
https://issues.apache.org/jira/browse/TS-4509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407042#comment-15407042
]
Thomas Jackson commented on TS-4509:
[~amc] we had discussed adding a "sent byte count" before, the issue
[
https://issues.apache.org/jira/browse/TS-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15403203#comment-15403203
]
Thomas Jackson commented on TS-4710:
https://github.com/apache/trafficserver/pull/836
> Make
[
https://issues.apache.org/jira/browse/TS-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson reassigned TS-4710:
--
Assignee: Thomas Jackson
> Make `proxy.config.srv_enabled` transaction overrideable
>
Thomas Jackson created TS-4710:
--
Summary: Make `proxy.config.srv_enabled` transaction overrideable
Key: TS-4710
URL: https://issues.apache.org/jira/browse/TS-4710
Project: Traffic Server
Issue
[
https://issues.apache.org/jira/browse/TS-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4693:
---
Fix Version/s: (was: sometime)
7.0.0
> SRV priorities don't work
>
[
https://issues.apache.org/jira/browse/TS-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson closed TS-4692.
--
Resolution: Duplicate
> SRV weights don't work
> --
>
> Key: TS-4692
>
[
https://issues.apache.org/jira/browse/TS-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395095#comment-15395095
]
Thomas Jackson commented on TS-4693:
PR with fix (and re-enabling tests:
[
https://issues.apache.org/jira/browse/TS-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4692:
---
Issue Type: Bug (was: Improvement)
> SRV weights don't work
> --
>
>
[
https://issues.apache.org/jira/browse/TS-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4693:
---
Issue Type: Bug (was: Improvement)
> SRV priorities don't work
> -
>
>
[
https://issues.apache.org/jira/browse/TS-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4692:
---
Description: Although weights are stored in hostdb (and code exists that
attempts to do weighting)--
[
https://issues.apache.org/jira/browse/TS-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4693:
---
Description:
Although priorities are stored in hostdb (and code exists that attempts to do
[
https://issues.apache.org/jira/browse/TS-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson reassigned TS-4692:
--
Assignee: Thomas Jackson
> SRV weights don't work
> --
>
>
[
https://issues.apache.org/jira/browse/TS-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson reassigned TS-4693:
--
Assignee: Thomas Jackson
> SRV priorities don't work
> -
>
>
Thomas Jackson created TS-4693:
--
Summary: SRV priorities don't work
Key: TS-4693
URL: https://issues.apache.org/jira/browse/TS-4693
Project: Traffic Server
Issue Type: Bug
Components:
Thomas Jackson created TS-4692:
--
Summary: SRV weights don't work
Key: TS-4692
URL: https://issues.apache.org/jira/browse/TS-4692
Project: Traffic Server
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/TS-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson resolved TS-4615.
Resolution: Fixed
> Dynamic SRV lookups
> ---
>
> Key: TS-4615
>
[
https://issues.apache.org/jira/browse/TS-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on TS-4615 started by Thomas Jackson.
--
> Dynamic SRV lookups
> ---
>
> Key: TS-4615
>
[
https://issues.apache.org/jira/browse/TS-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson reassigned TS-4615:
--
Assignee: Thomas Jackson
> Dynamic SRV lookups
> ---
>
> Key:
[
https://issues.apache.org/jira/browse/TS-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4615:
---
Component/s: HostDB
> Dynamic SRV lookups
> ---
>
> Key: TS-4615
>
[
https://issues.apache.org/jira/browse/TS-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson resolved TS-4622.
Resolution: Fixed
> Ports from SRV lookups aren't used
> --
>
>
[
https://issues.apache.org/jira/browse/TS-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson resolved TS-4688.
Resolution: Fixed
> DNS resolver doesn't handle DNS compression labels for SRV responses
>
[
https://issues.apache.org/jira/browse/TS-4674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson reassigned TS-4674:
--
Assignee: Thomas Jackson
> Cleanup incorrect assert after TS-4403
>
[
https://issues.apache.org/jira/browse/TS-4674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4674:
---
Fix Version/s: 7.0.0
> Cleanup incorrect assert after TS-4403
> --
>
[
https://issues.apache.org/jira/browse/TS-4674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson resolved TS-4674.
Resolution: Fixed
> Cleanup incorrect assert after TS-4403
> --
>
[
https://issues.apache.org/jira/browse/TS-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384385#comment-15384385
]
Thomas Jackson commented on TS-4688:
I ran into this problem while creating tsqa tests for SRV
[
https://issues.apache.org/jira/browse/TS-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson reassigned TS-4688:
--
Assignee: Thomas Jackson
> DNS resolver doesn't handle DNS compression labels for SRV responses
>
Thomas Jackson created TS-4688:
--
Summary: DNS resolver doesn't handle DNS compression labels for
SRV responses
Key: TS-4688
URL: https://issues.apache.org/jira/browse/TS-4688
Project: Traffic Server
[
https://issues.apache.org/jira/browse/TS-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4688:
---
Fix Version/s: 7.0.0
> DNS resolver doesn't handle DNS compression labels for SRV responses
>
[
https://issues.apache.org/jira/browse/TS-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson resolved TS-4684.
Resolution: Fixed
Fix Version/s: 7.0.0
> Leaked references to HostDBInfos from HttpTransact
>
Thomas Jackson created TS-4685:
--
Summary: Strict round robin isn't followed for KA connections
Key: TS-4685
URL: https://issues.apache.org/jira/browse/TS-4685
Project: Traffic Server
Issue
[
https://issues.apache.org/jira/browse/TS-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson reassigned TS-4685:
--
Assignee: Thomas Jackson
> Strict round robin isn't followed for KA connections
>
[
https://issues.apache.org/jira/browse/TS-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4684:
---
Affects Version/s: 7.0.0
> Leaked references to HostDBInfos from HttpTransact
>
[
https://issues.apache.org/jira/browse/TS-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson reassigned TS-4684:
--
Assignee: Thomas Jackson
> Leaked references to HostDBInfos from HttpTransact
>
Thomas Jackson created TS-4684:
--
Summary: Leaked references to HostDBInfos from HttpTransact
Key: TS-4684
URL: https://issues.apache.org/jira/browse/TS-4684
Project: Traffic Server
Issue Type:
[
https://issues.apache.org/jira/browse/TS-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4682:
---
Component/s: HostDB
> HostDB caching of SOA responses doesn't honor TTL
>
[
https://issues.apache.org/jira/browse/TS-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson reassigned TS-4682:
--
Assignee: Thomas Jackson
> HostDB caching of SOA responses doesn't honor TTL
>
1 - 100 of 400 matches
Mail list logo
