[
https://issues.apache.org/jira/browse/TS-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-798:
-----------------------------
Attachment: TS-798.diff
I need someone to review these changes. Basically, I've done three things:
1) Delay the "addition" to the mapping containers until a map rules is
succesfully initialized.
2) Fixed the Warning state to update the parsing token.
3) Made the error case less draconian, and allow subsequent lines to succeed.
Of these, I'm least sure about 3), should we simply stop parsing the file as
the original code as doing in an "error" case? It's hard to judge the
differences between a warning case and error case.
> traffic_server crash if add non-existent plugin in remap rule
> -------------------------------------------------------------
>
> Key: TS-798
> URL: https://issues.apache.org/jira/browse/TS-798
> Project: Traffic Server
> Issue Type: Bug
> Components: Remap API
> Affects Versions: 2.1.8, 2.1.7
> Environment: Mac OS X 10.6.7, Centos 5.4
> Reporter: Conan Wang
> Assignee: Leif Hedstrom
> Priority: Minor
> Fix For: 3.0.0
>
> Attachments: TS-798.diff
>
>
> remap.config: map http://www.example.com/ http://server1.example.com/
> @plugin=xxx.so
> start traffic_server at port 8080, then "curl -x 127.0.0.1:8080
> http://www.example.com/";
> opps.
> log:
> (http_seq) [HttpSM::do_remap_request] Remapping request
> NOTE: Traffic Server received User Sig 11 from pid: 0 uid: 0
> gdb:
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000017
> [Switching to process 7596 thread 0x1703]
> RemapPlugins::run_single_remap (this=0x1010fbd80) at RemapPlugins.cc:157
> 157 toPath = map_to->path_get(&toPathLen);
> for some reason the plugin is not install correctly, so maybe it's better not
> to crash. :)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
