[
https://issues.apache.org/jira/browse/TS-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299188#comment-15299188
]
ASF GitHub Bot commented on TS-4481:
------------------------------------
GitHub user SolidWallOfCode opened a pull request:
https://github.com/apache/trafficserver/pull/663
TS-4481: CPP API - clear handles and reload on demand.
The changes are
* The handles are cleared, not re-initialized, per hook.
* Handles are loaded from the transaction object on demand.
* The current event is stored in the `state_` rather than being passed
around because only one method, as far as I can tell, actually needs it.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SolidWallOfCode/trafficserver ts-4481
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/663.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #663
----
commit 5ca66171890ae1bbcdb875885a2a461660c33ba3
Author: Alan M. Carroll <[email protected]>
Date: 2016-05-24T23:54:49Z
TS-4481: CPP API - clear handles and reload on demand.
----
> CPP API should not initialize all handles on every event.
> ---------------------------------------------------------
>
> Key: TS-4481
> URL: https://issues.apache.org/jira/browse/TS-4481
> Project: Traffic Server
> Issue Type: Bug
> Components: CPP API
> Reporter: Alan M. Carroll
> Assignee: Brian Geffon
>
> To avoid problems with stale handles to transaction headers the CPP API was
> changed to initialize all such handles for a set of events. However this
> causes the error log to be flooded because not all headers are available for
> all of the events and each one that is not generates an error message. This
> generates a lot of errors even in normal use without problems. Simply
> disabling the messages seems a poor choice as the cases where the particular
> header is accessed and not found should be noted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
