[jira] [Created] (TS-797) Wrong delete used in StatProcessor
Wrong delete used in StatProcessor Key: TS-797 URL: https://issues.apache.org/jira/browse/TS-797 Project: Traffic Server Issue Type: Bug Components: Stats Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 2.1.9 There's a delete being done in this code, which really should be a delete[]. It's surprising the compiler doesn't complain, but valgrind does. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-745) Support ssd
[ https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mohan_zl updated TS-745: Attachment: ssd_cache2.patch I'm sorry John, maybe we could not use http://codereview.appspot.com/ for detailed reviews, because i am living in a magical country like Korea, i couldn't open that website... Current changes follow your advices: (1) Now the new patch delete 146 lines, and add 842 lines. I'm trying to avoid code duplicate (2) Now the patch support multi SSD, the config file is storage_ssd.config file, and the syntax to add file is the same as storage.config (3)(4)(5) I now use xmalloc to store and xfree to delete the docs. I don't understand how to use various allocators to malloc and free the docs. Besides, now i also use another CacheVC to write the docs to ssd, because i have no idea to write after calling back the user, so (4) and (5) is not done also. Support ssd --- Key: TS-745 URL: https://issues.apache.org/jira/browse/TS-745 Project: Traffic Server Issue Type: New Feature Components: Cache Reporter: mohan_zl Assignee: mohan_zl Fix For: 3.1 Attachments: ssd_cache.patch, ssd_cache2.patch A patch for supporting, not work well for a long time with --enable-debug -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-745) Support ssd
[ https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13038371#comment-13038371 ] mohan_zl commented on TS-745: - In my thoughts, if we use the same CacheVC to write after calling back the user, we can do it before free_CacheVC, but when i did this, i could not pass the function test. Support ssd --- Key: TS-745 URL: https://issues.apache.org/jira/browse/TS-745 Project: Traffic Server Issue Type: New Feature Components: Cache Reporter: mohan_zl Assignee: mohan_zl Fix For: 3.1 Attachments: ssd_cache.patch, ssd_cache2.patch A patch for supporting, not work well for a long time with --enable-debug -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-745) Support ssd
[ https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13038374#comment-13038374 ] mohan_zl commented on TS-745: - My boss have give me another passport to visit http://codereview.appspot.com/. John, i did not search the traffic server results in this site. Support ssd --- Key: TS-745 URL: https://issues.apache.org/jira/browse/TS-745 Project: Traffic Server Issue Type: New Feature Components: Cache Reporter: mohan_zl Assignee: mohan_zl Fix For: 3.1 Attachments: ssd_cache.patch, ssd_cache2.patch A patch for supporting, not work well for a long time with --enable-debug -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-798) traffic_server crash if add non-existent plugin in remap rule
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.7, 2.1.8 Environment: Mac OS X 10.6.7, Centos 5.4 Reporter: Conan Wang Priority: Minor 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: 0x0017 [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
