[
https://issues.apache.org/jira/browse/TS-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809181#comment-13809181
]
Alan M. Carroll commented on TS-2264:
-------------------------------------
Very critical. Changing that will make things even worse.
If terminate_sm is set, then HttmSM::kill_this() will be called, you don't need
to call it at the bind fail point. The problem is that there is a pending
action outstanding in netProcessor.connect_re that gets called after
HttpSM::kill_this which crashes because the SM no longer exists. I think that's
stored in HttpSM::pending_action but is not cleared because of API call out
state. That is what I am looking in to now.
Note that HttpSM::kill_this is precisely what we want to call, it does the
cache_sm.end_both() call and all the other things that need to be cleaned up.
> The current cache connection counter is not reliably decremented with
> use_client_source_port
> --------------------------------------------------------------------------------------------
>
> Key: TS-2264
> URL: https://issues.apache.org/jira/browse/TS-2264
> Project: Traffic Server
> Issue Type: Bug
> Components: TProxy
> Reporter: Alan M. Carroll
> Assignee: Alan M. Carroll
> Priority: Minor
> Fix For: 4.2.0
>
>
> If use_client_target_addr and use_client_source_port are enabled with
> transparent proxy, in some cases the current cache connection counter is not
> decremented. This happens when a client connection is terminated due to an
> EADDRNOTAVAIL failure.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
