[
https://issues.apache.org/jira/browse/TS-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14220243#comment-14220243
]
Leif Hedstrom commented on TS-2918:
-----------------------------------
This sounds similar to a problem we've had with an internal plugin. In that
case, the issue is something like this:
1) The plugin loads configurations at startup, via remap.config
2) The plugin creates continuations to be added to hooks like end of transaction
3) You modify remap.config, and do traffic_line -x
4) Upon reading the new config, the old config (which holds the continuation)
is put up for deletion at a later time.
5) When the deletion happens, the continuation and data is deleted, but the
continuation might still be scheduled.
I'm not saying this is the issue here, but the stack trace looks very very
similar. I have not looked at your plugin code.
> collapsed_connection Plugin Errors
> -----------------------------------
>
> Key: TS-2918
> URL: https://issues.apache.org/jira/browse/TS-2918
> Project: Traffic Server
> Issue Type: Bug
> Components: Performance, Plugins
> Reporter: Faysal Banna
> Assignee: Alan M. Carroll
> Labels: crash
> Fix For: 5.3.0
>
>
> Hi Guys.
> I been using trafficserver for over a year with all the good stuff it holds
> still there are bugs that are yet not fixed
> one of the common bug in a plugin experimental called collapsed_connection
> and here's the output
> FATAL: InkAPI.cc:989: failed assert `!"Plugin tries to use a continuation
> which is deleted"`
> /usr/local/bin/traffic_server - STACK TRACE:
> /usr/local/lib/libtsutil.so.5(+0x1e897)[0x2b587580c897]
> /usr/local/lib/libtsutil.so.5(+0x1d84f)[0x2b587580b84f]
> /usr/local/bin/traffic_server[0x4b73b3]
> /usr/local/bin/traffic_server(HttpSM::state_api_callout(int,
> void*)+0x102)[0x5ae762]
> /usr/local/bin/traffic_server(HttpSM::state_cache_open_read(int,
> void*)+0x170)[0x5af510]
> /usr/local/bin/traffic_server(HttpSM::main_handler(int, void*)+0xbd)[0x5b319d]
> /usr/local/bin/traffic_server(HttpCacheSM::state_cache_open_read(int,
> void*)+0x156)[0x5910c6]
> /usr/local/bin/traffic_server(Cache::open_read(Continuation*, INK_MD5*,
> HTTPHdr*, CacheLookupHttpConfig*, CacheFragType, char*, int)+0x642)[0x6dfd12]
> /usr/local/bin/traffic_server(CacheProcessor::open_read(Continuation*, URL*,
> bool, HTTPHdr*, CacheLookupHttpConfig*, long, CacheFragType)+0x9b)[0x6beecb]
> /usr/local/bin/traffic_server(HttpCacheSM::open_read(URL*, HTTPHdr*,
> CacheLookupHttpConfig*, long)+0x81)[0x591381]
> /usr/local/bin/traffic_server(HttpSM::do_cache_lookup_and_read()+0xfb)[0x5a163b]
> /usr/local/bin/traffic_server(HttpSM::set_next_state()+0x7aa)[0x5b3c2a]
> /usr/local/bin/traffic_server(HttpSM::state_api_callout(int,
> void*)+0x2c0)[0x5ae920]
> /usr/local/bin/traffic_server(HttpSM::state_api_callback(int,
> void*)+0x82)[0x5b3382]
> /usr/local/bin/traffic_server(TSHttpTxnReenable+0x244)[0x4c9c34]
> /usr/local/libexec/trafficserver/collapsed_connection.so(+0x2edf)[0x2b587b651edf]
> /usr/local/libexec/trafficserver/collapsed_connection.so(+0x4714)[0x2b587b653714]
> /usr/local/libexec/trafficserver/collapsed_connection.so(+0x4b90)[0x2b587b653b90]
> /usr/local/bin/traffic_server(EThread::process_event(Event*,
> int)+0x170)[0x73e030]
> /usr/local/bin/traffic_server(EThread::execute()+0x7e1)[0x73ec51]
> /usr/local/bin/traffic_server[0x73d94a]
> each time this happens the server is being restarted
> much regards
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
