[jira] [Created] (TS-1215) Ram Cache: we should check system free memory before we setup the ram_cache_size
Zhao Yongming created TS-1215: - Summary: Ram Cache: we should check system free memory before we setup the ram_cache_size Key: TS-1215 URL: https://issues.apache.org/jira/browse/TS-1215 Project: Traffic Server Issue Type: Improvement Components: Core Affects Versions: 3.1.3 Reporter: Zhao Yongming Priority: Minor Fix For: 3.3.0 when your system run out of memory, it is a very bad situation. we should prevent from ram cache use more memories than system free: first, during cache init and ram_cache init, be sure to check free. second, can we make the ram_cache a dynamic system? I think that is my long term wish for ram_cache -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1179) libraries and plugins are installed with .la files
[
https://issues.apache.org/jira/browse/TS-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-1179:
--
Fix Version/s: sometime
Moving to "sometime", unless someone really is bothered about this :).
> libraries and plugins are installed with .la files
> --
>
> Key: TS-1179
> URL: https://issues.apache.org/jira/browse/TS-1179
> Project: Traffic Server
> Issue Type: Bug
> Components: Build
>Reporter: Igor Galić
> Fix For: sometime
>
>
> Who needs or uses {{.la}} files?
> We have {{tsxs}} which compiles stuff without {{libtool}}, and the plugins
> definitely don't need {{.la}} files for loading.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1180) gzip plugin needs to be configurable for certain file/mime types
[ https://issues.apache.org/jira/browse/TS-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-1180: -- Fix Version/s: 3.3.0 Moving to 3.3.0, but this can be fixed any time. > gzip plugin needs to be configurable for certain file/mime types > > > Key: TS-1180 > URL: https://issues.apache.org/jira/browse/TS-1180 > Project: Traffic Server > Issue Type: New Feature > Components: Plugins >Reporter: Igor Galić >Assignee: Otto van der Schaaf > Fix For: 3.3.0 > > > Most browsers don't take it very well when JavaScript is compressed - or > rather, when AJAX requests are. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1181) TSHttpTxnConfigInt* don't look right with MgmtByte fields in OverridableHttpConfigParams
[ https://issues.apache.org/jira/browse/TS-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-1181: -- Fix Version/s: 3.1.4 Hmmm, this seems pretty serious. William, are you going to work on this in the next week or so? If not, I'll take a look at it. > TSHttpTxnConfigInt* don't look right with MgmtByte fields in > OverridableHttpConfigParams > > > Key: TS-1181 > URL: https://issues.apache.org/jira/browse/TS-1181 > Project: Traffic Server > Issue Type: Bug > Components: TS API >Affects Versions: 3.0.4 >Reporter: William Bardwell >Priority: Minor > Fix For: 3.1.4 > > > TSHttpTxnConfigIntSet and Get use _conf_to_memberp to get a pointer to > various fields, and then access it as a 32bit int. But many of the fields > are now bytes. A fix would be to make _conf_to_memberp return the type > properly, and make TSHttpTxnConfigInt* access the field as the proper size. > I saw valgrind complaining about uninitialized data from the code (which is > probably because of padding in the structure, since it is cleared a field at > a time), but there are probably much worse effects around reading and writing > unrelated fields. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1206) stats snap file may crash during server crash
[ https://issues.apache.org/jira/browse/TS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-1206: -- Fix Version/s: 3.1.4 > stats snap file may crash during server crash > - > > Key: TS-1206 > URL: https://issues.apache.org/jira/browse/TS-1206 > Project: Traffic Server > Issue Type: Bug >Reporter: Zhao Yongming > Fix For: 3.1.4 > > > when sometimes traffic_server crashed, some or all of the stats counter are > not updating anymore. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1183) issue with videos on yahoo website
[ https://issues.apache.org/jira/browse/TS-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258729#comment-13258729 ] Leif Hedstrom commented on TS-1183: --- Can you provide some links to reproduce this with ? I'm going to mark this for v3.3.0 (after our next stable release), but if someone wants to work on it now, please move it back to 3.1.4. > issue with videos on yahoo website > -- > > Key: TS-1183 > URL: https://issues.apache.org/jira/browse/TS-1183 > Project: Traffic Server > Issue Type: Bug > Components: HTTP >Affects Versions: 3.0.4 >Reporter: Luca > Fix For: 3.3.0 > > > Can't view yahoo videos (tested in forwarding mode). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1183) issue with videos on yahoo website
[ https://issues.apache.org/jira/browse/TS-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-1183: -- Fix Version/s: 3.3.0 > issue with videos on yahoo website > -- > > Key: TS-1183 > URL: https://issues.apache.org/jira/browse/TS-1183 > Project: Traffic Server > Issue Type: Bug > Components: HTTP >Affects Versions: 3.0.4 >Reporter: Luca > Fix For: 3.3.0 > > > Can't view yahoo videos (tested in forwarding mode). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1209) background_fill values don't seem to be working
[ https://issues.apache.org/jira/browse/TS-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258727#comment-13258727 ] Leif Hedstrom commented on TS-1209: --- Did you try if allowing for HT_TRANSFORM works? :) If so, seems like an easy fix. Also, why do you still need the transformation plugin? Not saying we shouldn't fix this, but curious as to why you still need it. > background_fill values don't seem to be working > --- > > Key: TS-1209 > URL: https://issues.apache.org/jira/browse/TS-1209 > Project: Traffic Server > Issue Type: Bug > Components: Cache >Affects Versions: 3.0.4 >Reporter: Robert Logue >Priority: Minor > Fix For: 3.1.4 > > > If I request a 57 MB file TS caches the fill no problem and on subsequent > requests the file gets served from cache. If I cut the request early, about > 40MB downloaded and I have > proxy.config.http.background_fill_completed_threshold = 0.5 and > proxy.config.http.background_fill_active_timeout is suitably high, the file > is not cached. I am of the understanding that the background fill values > should keep the OS connection open and allow the full item to be cached > though this is not happening. > I have tried various values for > proxy.config.http.background_fill_completed_threshold ranging from 0.0 -> > 0.5, none seem to work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1212) can not limit ram cache
[
https://issues.apache.org/jira/browse/TS-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-1212:
--
Affects Version/s: (was: 2.1.3)
3.0.3
Fix Version/s: 3.1.4
> can not limit ram cache
> ---
>
> Key: TS-1212
> URL: https://issues.apache.org/jira/browse/TS-1212
> Project: Traffic Server
> Issue Type: Bug
> Components: Cache
>Affects Versions: 3.0.3
> Environment: we are on v3.0.x but maybe affected v3.1 and later too.
>Reporter: Zhao Yongming
> Fix For: 3.1.4
>
>
> ram cache limit is not activate at sometime:
> {code}
> [yonghao@cache177 ~]$ links -dump http://localhost:8080/stat/ | grep ram
> proxy.config.cache.ram_cache.size=10737418240
> proxy.config.cache.ram_cache_cutoff=131072
> proxy.config.cache.ram_cache.algorithm=1
> proxy.config.cache.ram_cache.compress=0
> proxy.config.cache.ram_cache.ssd_percent=25
> proxy.config.cache.ram_cache.compress_percent=90
> proxy.process.cache.ram_cache.total_bytes=12884901886
> proxy.process.cache.volume_0.ram_cache.total_bytes=-7301066
> proxy.process.cache.ram_cache.bytes_used=11840122880
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1209) background_fill values don't seem to be working
[ https://issues.apache.org/jira/browse/TS-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-1209: -- Fix Version/s: 3.1.4 > background_fill values don't seem to be working > --- > > Key: TS-1209 > URL: https://issues.apache.org/jira/browse/TS-1209 > Project: Traffic Server > Issue Type: Bug > Components: Cache >Affects Versions: 3.0.4 >Reporter: Robert Logue >Priority: Minor > Fix For: 3.1.4 > > > If I request a 57 MB file TS caches the fill no problem and on subsequent > requests the file gets served from cache. If I cut the request early, about > 40MB downloaded and I have > proxy.config.http.background_fill_completed_threshold = 0.5 and > proxy.config.http.background_fill_active_timeout is suitably high, the file > is not cached. I am of the understanding that the background fill values > should keep the OS connection open and allow the full item to be cached > though this is not happening. > I have tried various values for > proxy.config.http.background_fill_completed_threshold ranging from 0.0 -> > 0.5, none seem to work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1213) Crash report: update will crash at HttpTransact::process_quick_http_filter
[
https://issues.apache.org/jira/browse/TS-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-1213:
--
Fix Version/s: 3.1.4
> Crash report: update will crash at HttpTransact::process_quick_http_filter
> --
>
> Key: TS-1213
> URL: https://issues.apache.org/jira/browse/TS-1213
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
>Affects Versions: 3.1.3
> Environment: git master with update enabled.
>Reporter: Zhao Yongming
> Fix For: 3.1.4
>
>
> the new ip_allow & quick filter may affect the scheduled update functions:
> {code}
> NOTE: Traffic Server received Sig 11: Segmentation fault
> /opt/ats/bin/traffic_server - STACK TRACE:
> /lib64/libpthread.so.0(+0x10bc0)[0x2ab9e4318bc0]
> /opt/ats/bin/traffic_server(HttpTransact::process_quick_http_filter(HttpTransact::State*,
> int)+0x3b)[0x5501db]
> /opt/ats/bin/traffic_server(HttpTransact::EndRemapRequest(HttpTransact::State*)+0x3a1)[0x55ed91]
> /opt/ats/bin/traffic_server(HttpSM::call_transact_and_set_next_state(void
> (*)(HttpTransact::State*))+0x62)[0x530202]
> /opt/ats/bin/traffic_server(HttpSM::set_next_state()+0x54a)[0x54031a]
> /opt/ats/bin/traffic_server(HttpSM::set_next_state()+0x41c)[0x5401ec]
> /opt/ats/bin/traffic_server(HttpSM::set_next_state()+0x41c)[0x5401ec]
> /opt/ats/bin/traffic_server(HttpSM::state_add_to_list(int,
> void*)+0x18f)[0x53b2df]
> /opt/ats/bin/traffic_server(HttpSM::main_handler(int, void*)+0xe8)[0x53c288]
> /opt/ats/bin/traffic_server(HttpUpdateSM::start_scheduled_update(Continuation*,
> HTTPHdr*)+0x1c7)[0x576d97]
> /opt/ats/bin/traffic_server(UpdateSM::http_scheme(UpdateSM*)+0x197)[0x4fbd77]
> /opt/ats/bin/traffic_server(UpdateSM::HandleSMEvent(int,
> Event*)+0x378)[0x4f7198]
> /opt/ats/bin/traffic_server(EThread::process_event(Event*,
> int)+0x90)[0x6b0250]
> /opt/ats/bin/traffic_server(EThread::execute()+0x5eb)[0x6b0e0b]
> /opt/ats/bin/traffic_server[0x6af042]
> /lib64/libpthread.so.0(+0x8e2c)[0x2ab9e4310e2c]
> /lib64/libc.so.6(clone+0x6d)[0x2ab9e6beb35d]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1195) IPv6 address URLs are not parsed.
[ https://issues.apache.org/jira/browse/TS-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-1195: -- Fix Version/s: (was: 3.2.0) 3.3.0 Moving these out to 3.3.0. > IPv6 address URLs are not parsed. > - > > Key: TS-1195 > URL: https://issues.apache.org/jira/browse/TS-1195 > Project: Traffic Server > Issue Type: Bug > Components: HTTP >Affects Versions: 3.1.3 >Reporter: Alan M. Carroll >Assignee: Alan M. Carroll >Priority: Minor > Labels: ipv6, parsing, url > Fix For: 3.3.0 > > > A URL with a raw IPv6 address is not parsed. It should be parsed with or > without braces (per RFC). > http://fe80:2710::1:1/some/path > http://[fe80:2810::1:1]/some/path -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1130) ink_time_t is 64bit on x86_64
[ https://issues.apache.org/jira/browse/TS-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258724#comment-13258724 ] Leif Hedstrom commented on TS-1130: --- Looks good, commit it. > ink_time_t is 64bit on x86_64 > - > > Key: TS-1130 > URL: https://issues.apache.org/jira/browse/TS-1130 > Project: Traffic Server > Issue Type: Sub-task > Components: Core >Reporter: Zhao Yongming >Assignee: weijin > Fix For: 3.1.4 > > Attachments: TS-1130.diff, TS-1130.try2.diff, TS-1130.try3.diff > > > Weijin: paste your patch here, :D -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1062) TSFetchUrl doesn't handle chunked encoding
[ https://issues.apache.org/jira/browse/TS-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-1062: -- Fix Version/s: (was: 3.2.0) 3.3.0 Moving these out to 3.3.0. > TSFetchUrl doesn't handle chunked encoding > -- > > Key: TS-1062 > URL: https://issues.apache.org/jira/browse/TS-1062 > Project: Traffic Server > Issue Type: Bug > Components: TS API >Reporter: James Peach >Assignee: James Peach > Fix For: 3.3.0 > > > If you use TSFetchUrl() to fetch a resource and the response comes back with > chunked encoding, you are basically hosed. The caller never gets the SUCCESS > event because FetchSM does not know how to decode the body. There's no > content-length header and the origin server doesn't drop the TCP connection, > so we just sit there waiting for the response to finish forever (well until > the origin server drops the connection 10s later). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1202) install traffic_shell man/doc pages in a more appropriate location
[ https://issues.apache.org/jira/browse/TS-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258710#comment-13258710 ] Igor Galić commented on TS-1202: 0c985fd61d5246582162602fcb3f749de25d20c7 > install traffic_shell man/doc pages in a more appropriate location > -- > > Key: TS-1202 > URL: https://issues.apache.org/jira/browse/TS-1202 > Project: Traffic Server > Issue Type: Improvement >Affects Versions: 3.1.4 >Reporter: Igor Brezac >Assignee: Igor Galić >Priority: Minor > Fix For: 3.1.4 > > Attachments: doc.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1127) Wrong returned value of incoming port address
[ https://issues.apache.org/jira/browse/TS-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258703#comment-13258703 ] Leif Hedstrom commented on TS-1127: --- Fwiw, this is a deprecated API (which is why the regressions missed it). > Wrong returned value of incoming port address > - > > Key: TS-1127 > URL: https://issues.apache.org/jira/browse/TS-1127 > Project: Traffic Server > Issue Type: Bug > Components: HTTP >Affects Versions: 3.1.2 >Reporter: Yakov Kopel >Assignee: Leif Hedstrom > Fix For: 3.1.4 > > Attachments: fix.patch > > Original Estimate: 1m > Remaining Estimate: 1m > > The API TSHttpTxnClientIncomingPortGet has been changed in Wed Oct 5 19:14:07 > 2011 (TS-926) and it returns another value. > in the old version it returned the incoming port of the TS(the port which the > client connected to the TS). > in the new version the returned value is the sending port of the user. > The different is in the line: > - return sm->t_state.client_info.port; > + return ink_inet_get_port(&sm->t_state.client_info.addr); > The assignment of those two members (port, addr) are in the HttpSM.cc file > ink_inet_copy(&t_state.client_info.addr, netvc->get_remote_addr()); > t_state.client_info.port = netvc->get_local_port(); > > The old code gave the right answer from the port member, and the new one > gives us wrong answer from the remote address. > I attached a patch to fix this returned value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1214) a race condition in CacheVol init
[ https://issues.apache.org/jira/browse/TS-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] weijin updated TS-1214: --- Attachment: TS-1214.diff > a race condition in CacheVol init > - > > Key: TS-1214 > URL: https://issues.apache.org/jira/browse/TS-1214 > Project: Traffic Server > Issue Type: Bug > Components: Cache >Affects Versions: 3.1.1, 3.0.4 > Environment: all >Reporter: weijin >Assignee: weijin >Priority: Minor > Fix For: 3.3.0 > > Attachments: TS-1214.diff > > > A race condition in CacheVol init, If config muti CacheVol, maybe not work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-1214) a race condition in CacheVol init
weijin created TS-1214: -- Summary: a race condition in CacheVol init Key: TS-1214 URL: https://issues.apache.org/jira/browse/TS-1214 Project: Traffic Server Issue Type: Bug Components: Cache Affects Versions: 3.0.4, 3.1.1 Environment: all Reporter: weijin Assignee: weijin Priority: Minor Fix For: 3.3.0 Attachments: TS-1214.diff A race condition in CacheVol init, If config muti CacheVol, maybe not work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1130) ink_time_t is 64bit on x86_64
[ https://issues.apache.org/jira/browse/TS-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258694#comment-13258694 ] weijin commented on TS-1130: try2 have a compile error, blame me. > ink_time_t is 64bit on x86_64 > - > > Key: TS-1130 > URL: https://issues.apache.org/jira/browse/TS-1130 > Project: Traffic Server > Issue Type: Sub-task > Components: Core >Reporter: Zhao Yongming >Assignee: weijin > Fix For: 3.1.4 > > Attachments: TS-1130.diff, TS-1130.try2.diff, TS-1130.try3.diff > > > Weijin: paste your patch here, :D -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1130) ink_time_t is 64bit on x86_64
[ https://issues.apache.org/jira/browse/TS-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] weijin updated TS-1130: --- Attachment: TS-1130.try3.diff > ink_time_t is 64bit on x86_64 > - > > Key: TS-1130 > URL: https://issues.apache.org/jira/browse/TS-1130 > Project: Traffic Server > Issue Type: Sub-task > Components: Core >Reporter: Zhao Yongming >Assignee: weijin > Fix For: 3.1.4 > > Attachments: TS-1130.diff, TS-1130.try2.diff, TS-1130.try3.diff > > > Weijin: paste your patch here, :D -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1127) Wrong returned value of incoming port address
[ https://issues.apache.org/jira/browse/TS-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258689#comment-13258689 ] Leif Hedstrom commented on TS-1127: --- Taking this, reading the docs, and looking at the code, I'm 99% certain the proposed patch is correct. > Wrong returned value of incoming port address > - > > Key: TS-1127 > URL: https://issues.apache.org/jira/browse/TS-1127 > Project: Traffic Server > Issue Type: Bug > Components: HTTP >Affects Versions: 3.1.2 >Reporter: Yakov Kopel >Assignee: Leif Hedstrom > Fix For: 3.1.4 > > Attachments: fix.patch > > Original Estimate: 1m > Remaining Estimate: 1m > > The API TSHttpTxnClientIncomingPortGet has been changed in Wed Oct 5 19:14:07 > 2011 (TS-926) and it returns another value. > in the old version it returned the incoming port of the TS(the port which the > client connected to the TS). > in the new version the returned value is the sending port of the user. > The different is in the line: > - return sm->t_state.client_info.port; > + return ink_inet_get_port(&sm->t_state.client_info.addr); > The assignment of those two members (port, addr) are in the HttpSM.cc file > ink_inet_copy(&t_state.client_info.addr, netvc->get_remote_addr()); > t_state.client_info.port = netvc->get_local_port(); > > The old code gave the right answer from the port member, and the new one > gives us wrong answer from the remote address. > I attached a patch to fix this returned value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TS-1127) Wrong returned value of incoming port address
[ https://issues.apache.org/jira/browse/TS-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-1127: - Assignee: Leif Hedstrom (was: Alan M. Carroll) > Wrong returned value of incoming port address > - > > Key: TS-1127 > URL: https://issues.apache.org/jira/browse/TS-1127 > Project: Traffic Server > Issue Type: Bug > Components: HTTP >Affects Versions: 3.1.2 >Reporter: Yakov Kopel >Assignee: Leif Hedstrom > Fix For: 3.1.4 > > Attachments: fix.patch > > Original Estimate: 1m > Remaining Estimate: 1m > > The API TSHttpTxnClientIncomingPortGet has been changed in Wed Oct 5 19:14:07 > 2011 (TS-926) and it returns another value. > in the old version it returned the incoming port of the TS(the port which the > client connected to the TS). > in the new version the returned value is the sending port of the user. > The different is in the line: > - return sm->t_state.client_info.port; > + return ink_inet_get_port(&sm->t_state.client_info.addr); > The assignment of those two members (port, addr) are in the HttpSM.cc file > ink_inet_copy(&t_state.client_info.addr, netvc->get_remote_addr()); > t_state.client_info.port = netvc->get_local_port(); > > The old code gave the right answer from the port member, and the new one > gives us wrong answer from the remote address. > I attached a patch to fix this returned value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TS-1211) listen queue doesn't get modified for traffic_manager when setting configuration option in records.config
[ https://issues.apache.org/jira/browse/TS-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-1211: - Assignee: Bryan Call > listen queue doesn't get modified for traffic_manager when setting > configuration option in records.config > - > > Key: TS-1211 > URL: https://issues.apache.org/jira/browse/TS-1211 > Project: Traffic Server > Issue Type: Bug >Affects Versions: 3.1.3 >Reporter: Bryan Call >Assignee: Bryan Call > Fix For: 3.1.4 > > > listen queue only gets modified if you are running the traffic_server binary > and not if you use traffic_cop or the startup scripts > traffic_manager is hardcoded to have a listen backlog of 1024. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TS-1211) listen queue doesn't get modified for traffic_manager when setting configuration option in records.config
[ https://issues.apache.org/jira/browse/TS-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-1211. --- Resolution: Fixed > listen queue doesn't get modified for traffic_manager when setting > configuration option in records.config > - > > Key: TS-1211 > URL: https://issues.apache.org/jira/browse/TS-1211 > Project: Traffic Server > Issue Type: Bug >Affects Versions: 3.1.3 >Reporter: Bryan Call >Assignee: Bryan Call > Fix For: 3.1.4 > > > listen queue only gets modified if you are running the traffic_server binary > and not if you use traffic_cop or the startup scripts > traffic_manager is hardcoded to have a listen backlog of 1024. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1130) ink_time_t is 64bit on x86_64
[ https://issues.apache.org/jira/browse/TS-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] weijin updated TS-1130: --- Attachment: TS-1130.try2.diff > ink_time_t is 64bit on x86_64 > - > > Key: TS-1130 > URL: https://issues.apache.org/jira/browse/TS-1130 > Project: Traffic Server > Issue Type: Sub-task > Components: Core >Reporter: Zhao Yongming >Assignee: weijin > Fix For: 3.1.4 > > Attachments: TS-1130.diff, TS-1130.try2.diff > > > Weijin: paste your patch here, :D -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1130) ink_time_t is 64bit on x86_64
[ https://issues.apache.org/jira/browse/TS-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258130#comment-13258130 ] weijin commented on TS-1130: According Leif`s advice, by checking the sizeof() on ink_time_t before the atomic CAS. > ink_time_t is 64bit on x86_64 > - > > Key: TS-1130 > URL: https://issues.apache.org/jira/browse/TS-1130 > Project: Traffic Server > Issue Type: Sub-task > Components: Core >Reporter: Zhao Yongming >Assignee: weijin > Fix For: 3.1.4 > > Attachments: TS-1130.diff > > > Weijin: paste your patch here, :D -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
