[ 
https://issues.apache.org/jira/browse/TS-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13730530#comment-13730530
 ] 

ASF subversion and git services commented on TS-1501:
-----------------------------------------------------

Commit e413f12ce13ccfd2742d069501a102673e8975f7 in branch refs/heads/3.3.x from 
[~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=e413f12 ]

Merge branch 'master' into 3.3.x

* master:
  TS-2100 Initialize the SSL/NPN registration mutex
  add TS-1987, TS-2097 to CHANGES
  TS-2097: remove ink_strtok_r() wrapper
  TS-2097 Remove ink_string_find_dotted_extension()
  TS-2097 replace ink_string_copy() w/ ink_strlcpy()
  TS-2097: remove unsued string functions
  TS-1987: replace ink_string_fast functions
  TS-1987: rip out ink_string_fast_ functions
  TS-1501: fix the bug that mistaken the read as write of netvc.          
thanks zwoop for pointing it out.
  TS-2091: Fix spacing in separate commit
  TS-2091: Return an error from RecGetRecordOrderAndId if the stat isn't 
registered

                
> make the inactive event work
> ----------------------------
>
>                 Key: TS-1501
>                 URL: https://issues.apache.org/jira/browse/TS-1501
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Network
>    Affects Versions: 3.3.0, 3.2.0
>         Environment: all
>            Reporter: weijin
>            Assignee: weijin
>            Priority: Minor
>             Fix For: 3.5.0
>
>         Attachments: net_vc_inacitivity.diff
>
>
> we may define the INACTIVITY_TIMEOUT(not use the InactivityCop but schedule a 
> inactivity_timeout event in event system) after the event system becomes more 
> efficient. The current codes of inactivity event (enable INACTIVITY_TIMEOUT) 
> have a race condition, which may lead the net_vc received the 
> inacitivity_timeout after it was closed.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to