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

ASF GitHub Bot commented on TS-4497:
------------------------------------

GitHub user shukitchan opened a pull request:

    https://github.com/apache/trafficserver/pull/685

    TS-4497: fix fetch api to release async item sooner

    @sudheerv this is what we have been discussing for a while. With TS-3777, 
the ts.fetch() of ts_lua is no longer working fine. I finally figure out that 
the original plugin code committed is not performing cleanup correctly.
    
    Thanks. please take a look.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/shukitchan/trafficserver swrsie

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafficserver/pull/685.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 #685
    
----
commit 76446b6289208ba666a2641164a0473d3d7dc80a
Author: Kit Chan <[email protected]>
Date:   2016-06-01T06:22:14Z

    fix fetch api to release async item sooner

----


> ts.fetch() stops working in ts_lua plugin
> -----------------------------------------
>
>                 Key: TS-4497
>                 URL: https://issues.apache.org/jira/browse/TS-4497
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Lua, Plugins
>            Reporter: Kit Chan
>            Assignee: Kit Chan
>             Fix For: 7.0.0
>
>
> The fetch functionality of the ts_lua plugin stops working. More specifically 
> the example here 
> -(https://github.com/apache/trafficserver/blob/master/plugins/experimental/ts_lua/example/test_fetch.lua)
>  stops working and results in the request being hanged without finishing.
> The traffic.out/ squid.log shows that the fetch is finished successfully but 
> main transaction somehow is not getting reenabled. 
> Furthermore, this works fine before the fix of TS-3777. The introduction of 
> the code to disable keep-alive for internal transaction is causing this. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to