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

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

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

                
> Persistent stats not working
> ----------------------------
>
>                 Key: TS-2091
>                 URL: https://issues.apache.org/jira/browse/TS-2091
>             Project: Traffic Server
>          Issue Type: Bug
>    Affects Versions: 3.3.4
>            Reporter: Phil Sorber
>            Assignee: Phil Sorber
>              Labels: C
>             Fix For: 3.3.6
>
>
> When creating TS_STAT_PERSISTENT stats in plugins in 3.3dev I don't see them 
> as reloading properly. I can create them fine, and they get stored. Upon 
> restarting TS I can see them in stats, but when doing TSStatFindName() I 
> always get 0 back with a TS_SUCCESS. So it sees that they are there but does 
> not have the correct ID for them to return.

--
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