[jira] [Created] (TS-1212) can not limit ram cache

[Zhao Yongming (Created) (JIRA)]

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: 2.1.3
 Environment: we are on v3.0.x but maybe affected v3.1 and later too.
Reporter: Zhao Yongming


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] [Created] (TS-1213) Crash report: update will crash at HttpTransact::process_quick_http_filter

[Zhao Yongming (Created) (JIRA)]

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
 Environment: git master with update enabled.
Reporter: Zhao Yongming


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] [Created] (TS-1208) check_memory() in traffic_cop never active on linux

[Zhao Yongming (Created) (JIRA)]

check_memory() in traffic_cop never active on linux
---

 Key: TS-1208
 URL: https://issues.apache.org/jira/browse/TS-1208
 Project: Traffic Server
  Issue Type: Bug
  Components: Management
Reporter: Zhao Yongming
Assignee: Zhao Yongming


check_memory() will check system memory usage to prevent OOM. and it is still 
on linux v2.2 codes.



--
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-1209) background_fill values don't seem to be working

[Robert Logue (Created) (JIRA)]

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


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] [Created] (TS-1211) listen queue doesn't get modified for traffic_manager when setting configuration option in records.config

[Bryan Call (Created) (JIRA)]

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


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] [Created] (TS-1207) request for plugin cacheurl move into master tree

[Zhao Yongming (Created) (JIRA)]

request for plugin cacheurl move into master tree
-

 Key: TS-1207
 URL: https://issues.apache.org/jira/browse/TS-1207
 Project: Traffic Server
  Issue Type: New Feature
  Components: Plugins
Affects Versions: 3.1.3
Reporter: Zhao Yongming


from my testing, the cacheurl plugin is stable and usable in any version of 2.x 
 3.x, should we move into the meanline?

--
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-1204) Crash report: HttpSM::main_handler HttpSM.cc:2412: failed assert `magic == HTTP_SM_MAGIC_ALIVE`

[Zhao Yongming (Created) (JIRA)]

Crash report: HttpSM::main_handler HttpSM.cc:2412: failed assert `magic == 
HTTP_SM_MAGIC_ALIVE`
---

 Key: TS-1204
 URL: https://issues.apache.org/jira/browse/TS-1204
 Project: Traffic Server
  Issue Type: Bug
  Components: HTTP
Affects Versions: 3.1.3
 Environment: git master Sat Apr  7 03:29:50 2012. forwarding proxy on 
centos 6.2 x86_64, with cacheurl plugin
Reporter: Zhao Yongming


{code}
FATAL: HttpSM.cc:2412: failed assert `magic == HTTP_SM_MAGIC_ALIVE`
/usr/bin/traffic_server - STACK TRACE:
/usr/lib64/trafficserver/libtsutil.so.3(ink_fatal+0x88)[0x3ddba14368]
/usr/lib64/trafficserver/libtsutil.so.3(_ink_assert+0x1f)[0x3ddba12c6f]
/usr/bin/traffic_server(HttpSM::main_handler(int, void*)+0x2e)[0x5163fe]
/usr/bin/traffic_server[0x628b4b]
/usr/bin/traffic_server(write_to_net_io(NetHandler*, UnixNetVConnection*, 
EThread*)+0x353)[0x62c7a3]
/usr/bin/traffic_server(NetHandler::mainNetEvent(int, Event*)+0x2fe)[0x624cce]
/usr/bin/traffic_server(EThread::process_event(Event*, int)+0xb4)[0x6494f4]
/usr/bin/traffic_server(EThread::execute()+0x4c3)[0x649e83]
/usr/bin/traffic_server[0x648832]
/lib64/libpthread.so.0[0x380dc077f1]
/lib64/libc.so.6(clone+0x6d)[0x380d0e592d]
{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] [Created] (TS-1205) Crash report: double free when RecDataSet in cluster mode

[Zhao Yongming (Created) (JIRA)]

Crash report: double free when RecDataSet in cluster mode
-

 Key: TS-1205
 URL: https://issues.apache.org/jira/browse/TS-1205
 Project: Traffic Server
  Issue Type: Bug
  Components: Clustering, Configuration
Affects Versions: 3.1.3
 Environment: v3.0.x, with cluster mode 2
Reporter: Zhao Yongming
 Fix For: 3.3.0


we have seen some config system syncing config files in cluster mode.

{code}
*** glibc detected *** /usr/bin/traffic_server: double free or corruption 
(fasttop): 0x2b639c0009a0 ***
=== Backtrace: =
/lib64/libc.so.6[0x3f8f0750c6]
/usr/bin/traffic_server(RecDataSet(RecDataT, RecData*, RecData*)+0xb8)[0x65dd58]
/usr/bin/traffic_server(RecForceInsert(RecRecord*)+0x74)[0x6584b4]
/usr/bin/traffic_server[0x65cd62]
/usr/bin/traffic_server(RecMessageRecvThis(void*, char*, int)+0x16)[0x65ed46]
/usr/bin/traffic_server(BaseManager::executeMgmtCallback(int, char*, 
int)+0x3d)[0x5b562d]
/usr/bin/traffic_server(ProcessManager::processEventQueue()+0x29)[0x5b5d49]
/usr/bin/traffic_server(startProcessManager(void*)+0x8d)[0x5b633d]
/lib64/libpthread.so.0[0x3f8f4077f1]
/lib64/libc.so.6(clone+0x6d)[0x3f8f0e570d]
=== Memory map: 
{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] [Created] (TS-1206) stats snap file may crash during server crash

[Zhao Yongming (Created) (JIRA)]

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


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] [Created] (TS-1201) Crash report: hostdb multicache, double free

[Zhao Yongming (Created) (JIRA)]

Crash report: hostdb multicache, double free


 Key: TS-1201
 URL: https://issues.apache.org/jira/browse/TS-1201
 Project: Traffic Server
  Issue Type: Bug
Reporter: Zhao Yongming
Assignee: weijin



{code}
*** glibc detected *** /usr/bin/traffic_server: corrupted double-linked list: 
0x1fe10ef0 ***
=== Backtrace: =
/lib64/libc.so.6[0x3db2072555]   
/lib64/libc.so.6(cfree+0x4b)[0x3db20728bb]
/usr/bin/traffic_server(_ZN14MultiCacheSync7mcEventEiP5Event+0xa4)[0x5dae04]
/usr/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x22f)[0x691c8f]
/usr/bin/traffic_server(_ZN7EThread7executeEv+0x6a1)[0x692681]
/usr/bin/traffic_server[0x69115e]
/lib64/libpthread.so.0[0x3db280673d]
/lib64/libc.so.6(clone+0x6d)[0x3db20d44bd]
=== Memory map: 
{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] [Created] (TS-1200) DOAP file reference incorrect

[Sebb (Created) (JIRA)]

DOAP file reference incorrect
-

 Key: TS-1200
 URL: https://issues.apache.org/jira/browse/TS-1200
 Project: Traffic Server
  Issue Type: Bug
Reporter: Sebb
Priority: Critical


The DOAP file for the project needs to be available for the projects.a.o 
website to function correctly.

Currently the build is looking for

http://svn.apache.org/repos/asf/trafficserver/traffic/trunk/doc/doap.rdf

However this does not exist, so the build is reporting an error.

Please update the file

https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml

with the new location ASAP.

--
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-1196) the via metrix in PURGE response should be documented

[Zhao Yongming (Created) (JIRA)]

the via metrix in PURGE response should be documented
-

 Key: TS-1196
 URL: https://issues.apache.org/jira/browse/TS-1196
 Project: Traffic Server
  Issue Type: Task
  Components: Documentation
Affects Versions: 3.1.3
Reporter: Zhao Yongming
Assignee: Zhao Yongming
Priority: Minor


{code}
[yonghao@cache161.cn50 trafficserver]$ echo -ne PURGE 
http://img01.taobaocdn.com/bao/uploaded/i1/000/160/T1RoNcXn5Qj0JX.jpg_60x60.jpg
 HTTP/1.0\r\n\r\n | nc -i 1 cache162.cn50 81
HTTP/1.0 200 Ok
Date: Tue, 10 Apr 2012 07:10:30 GMT
Via: http/1.1 cn50 (ApacheTrafficServer/3.0.2 [cRs f ])
Content-Length: 0
{code}

what does the cR mean? we should document it down!

--
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-1197) Build fails when building outside the source tree

[Yossi Gottlieb (Created) (JIRA)]

Build fails when building outside the source tree
-

 Key: TS-1197
 URL: https://issues.apache.org/jira/browse/TS-1197
 Project: Traffic Server
  Issue Type: Bug
  Components: Build
Affects Versions: 3.1.3
Reporter: Yossi Gottlieb
Priority: Minor
 Fix For: 3.1.4


Currently some Makefiles assume $(builddir) == $(srcdir), which is an incorrect 
assumption.

--
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-1199) Out of memory: Kill process 1490 ([ET_NET 0]) score 963 or sacrifice child Killed process 1490, UID 99, ([ET_NET 0]) total-vm:10837656kB, anon-rss:7834172kB, file-rss:180kB

[bettydramit (Created) (JIRA)]

Out of memory: Kill process 1490 ([ET_NET 0]) score 963 or sacrifice child 
Killed process 1490, UID 99, ([ET_NET 0]) total-vm:10837656kB, 
anon-rss:7834172kB, file-rss:180kB 
-

 Key: TS-1199
 URL: https://issues.apache.org/jira/browse/TS-1199
 Project: Traffic Server
  Issue Type: Bug
  Components: Core
Affects Versions: 3.0.3
 Environment: centos 6 x86_64
Reporter: bettydramit


Out of memory: Kill process 1490 ([ET_NET 0]) score 963 or sacrifice child
Killed process 1490, UID 99, ([ET_NET 0]) total-vm:10837656kB, 
anon-rss:7834172kB, file-rss:180kB


--
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-1195) IPv6 address URLs are not parsed.

[Alan M. Carroll (Created) (JIRA)]

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
 Fix For: 3.2.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] [Created] (TS-1192) Remove gethostbyname usage in test code

[Brian Geffon (Created) (JIRA)]

Remove gethostbyname usage in test code
---

 Key: TS-1192
 URL: https://issues.apache.org/jira/browse/TS-1192
 Project: Traffic Server
  Issue Type: Improvement
Affects Versions: 3.1.3
Reporter: Brian Geffon


NetTest-simple-proxy.cc and test_I_simple_proxy.cc directly use 
gethostbyname(). These will be changed to use getaddrinfo().

We're removing gethostbyname() and gethostbyaddr() in an effort to get traffic 
server building on more platforms.

--
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-1193) Traffic Server building on OpenBSD

[Brian Geffon (Created) (JIRA)]

Traffic Server building on OpenBSD
--

 Key: TS-1193
 URL: https://issues.apache.org/jira/browse/TS-1193
 Project: Traffic Server
  Issue Type: Improvement
Reporter: Brian Geffon
Assignee: Brian Geffon


This is a parent issue for the task of getting traffic server building on 
OpenBSD.

--
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-1189) Build problem on CentOS5

[Leif Hedstrom (Created) (JIRA)]

Build problem on CentOS5


 Key: TS-1189
 URL: https://issues.apache.org/jira/browse/TS-1189
 Project: Traffic Server
  Issue Type: Bug
  Components: SSL
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
Priority: Critical
 Fix For: 3.1.4


{code}
diff --git a/iocore/net/SSLNetVConnection.cc b/iocore/net/SSLNetVConnection.cc
index 33ebe64..0a41a08 100644
--- a/iocore/net/SSLNetVConnection.cc
+++ b/iocore/net/SSLNetVConnection.cc
@@ -673,9 +673,9 @@ SSLNetVConnection::registerNextProtocolSet(const 
SSLNextProtocolSet * s)
 }
 
 int
-SSLNetVConnection::advertise_next_protocol(
-SSL *ssl, const unsigned char **out, unsigned int *outlen, void *arg)
+SSLNetVConnection::advertise_next_protocol(SSL *ssl, const unsigned char 
**out, unsigned int *outlen, void *arg)
 {
+#if TS_USE_TLS_NPN
   SSLNetVConnection * netvc = (SSLNetVConnection *)SSL_get_app_data(ssl);
 
   ink_release_assert(netvc != NULL);
@@ -686,4 +686,7 @@ SSLNetVConnection::advertise_next_protocol(
   }
 
   return SSL_TLSEXT_ERR_NOACK;
+#else
+  return 0;
+#endif
 }
{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] [Created] (TS-1190) Change default for proxy.config.http.share_server_sessions

[Leif Hedstrom (Created) (JIRA)]

Change default for proxy.config.http.share_server_sessions
--

 Key: TS-1190
 URL: https://issues.apache.org/jira/browse/TS-1190
 Project: Traffic Server
  Issue Type: Improvement
  Components: HTTP
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
 Fix For: 3.1.4


We should enable session sharing with dedicated session pools per net-thread as 
the default. It has the best performance for a majority of our use cases.

CONFIG proxy.config.http.share_server_sessions INT 2


--
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-1191) change the default for search domains for dns to 0

[Bryan Call (Created) (JIRA)]

change the default for search domains for dns to 0
--

 Key: TS-1191
 URL: https://issues.apache.org/jira/browse/TS-1191
 Project: Traffic Server
  Issue Type: Improvement
Reporter: Bryan Call
Assignee: Bryan Call
Priority: Minor
 Fix For: 3.1.4


As part of TS-703.  Making this change a separate bug that is easy to change.

--
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-1186) Problem with Perl stats API not parsing the stats as 64-bit int

[Bryan Call (Created) (JIRA)]

Problem with Perl stats API not parsing the stats as 64-bit int
---

 Key: TS-1186
 URL: https://issues.apache.org/jira/browse/TS-1186
 Project: Traffic Server
  Issue Type: Bug
Affects Versions: 3.1.3
 Environment: RHEL 6.2
Reporter: Bryan Call
Assignee: Bryan Call
Priority: Minor
 Fix For: 3.1.4


Stats will rollover because they are parsed as 32-bit int instead of 64-bit int 
in the Apache::TS::AdminClient module.

Change:
-@resp = unpack( slsl, $res );
+@resp = unpack( slsq, $res );


--
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-1187) TSMimeHdrFieldNameSet does not work for headers read from the client or origin server (but does work for headers added by traffic server)

[Alistair Stevenson (Created) (JIRA)]

TSMimeHdrFieldNameSet does not work for headers read from the client or origin 
server (but does work for headers added by traffic server)
-

 Key: TS-1187
 URL: https://issues.apache.org/jira/browse/TS-1187
 Project: Traffic Server
  Issue Type: Bug
  Components: MIME
Affects Versions: 3.0.2
 Environment: Redhat linux with plugin that wants to rename a header 
read from the client.
Reporter: Alistair Stevenson
 Fix For: 3.1.4


TSMimeHdrFieldNameSet does not work for headers read from the client or origin 
server (but does work for headers added by traffic server)

The name appears set (and the function returns SUCCESS) but when the data is 
sent to the origin Server it is corrupted at the point where the header is set. 
i.e the header name is sent but the header is corrupted after this.

I am having to create a new header and copy the values and then destroy the 
original header which is not as efficient.

--
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-1188) http://trafficserver.apache.org/docs/trunk/admin/ts_admin_chinese.pdf is 404

[James Peach (Created) (JIRA)]

http://trafficserver.apache.org/docs/trunk/admin/ts_admin_chinese.pdf is 404


 Key: TS-1188
 URL: https://issues.apache.org/jira/browse/TS-1188
 Project: Traffic Server
  Issue Type: Bug
  Components: Web site
Reporter: James Peach
Assignee: Igor Galić
Priority: Minor


The main docs page tries to point to the Chinese admin docs at 
http://trafficserver.apache.org/docs/trunk/admin/ts_admin_chinese.pdf, but 
there's nothing there.

--
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-1185) fails to build from source with gcc 4.7

[Arno Toell (Created) (JIRA)]

fails to build from source with gcc 4.7
---

 Key: TS-1185
 URL: https://issues.apache.org/jira/browse/TS-1185
 Project: Traffic Server
  Issue Type: Bug
Affects Versions: 3.0.4, 3.1.3
 Environment: Debian Unstable with gcc 4.7
Reporter: Arno Toell


Using gcc 4.7, ATS fails to build from source. See Debian bug 667396 
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667396) for further 
information. gcc 4.7 fails with

{code} 
g++ -DHAVE_CONFIG_H -I. -I../../lib/ts  -I../../iocore/eventsystem 
-I../../iocore/net -I../../iocore/aio -I../../iocore/hostdb 
-I../../iocore/cache -I../../iocore/cluster -I../../iocore/utils 
-I../../iocore/dns -I../../proxy -I../../lib/records -I../../mgmt 
-I../../mgmt/preparse -I../../mgmt/utils -I../../proxy/hdrs 
-I../../proxy/http/remap -I../../proxy/logging -D_FORTIFY_SOURCE=2 
-D_LARGEFILE64_SOURCE=1 -D_COMPILE64BIT_SOURCE=1 -D_GNU_SOURCE -D_REENTRANT 
-Dlinux -I/usr/include/tcl8.5  -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security 
-pipe -Wall -Werror -feliminate-unused-debug-symbols -fno-strict-aliasing 
-Wno-invalid-offsetof -MT HttpClientSession.o -MD -MP -MF 
.deps/HttpClientSession.Tpo -c -o HttpClientSession.o HttpClientSession.cc
In file included from ../../lib/ts/libts.h:96:0,
 from HttpClientSession.h:35,
 from HttpClientSession.cc:35:
../../lib/ts/Map.h: In instantiation of 'C MapK, C, A::get(K) [with K = 
unsigned int; C = int; A = DefaultAlloc]':
HttpConnectionCount.h:51:34:   required from here
../../lib/ts/Map.h:240:29: error: 'set_in' was not declared in this scope, and 
no declarations were found by argument-dependent lookup at the point of 
instantiation [-fpermissive]
../../lib/ts/Map.h:240:29: note: declarations in dependent base 
'VecMapElemunsigned int, int, DefaultAlloc, 2' are not found by unqualified 
lookup
../../lib/ts/Map.h:240:29: note: use 'this-set_in' instead
../../lib/ts/Map.h: In instantiation of 'MapElemK, C* MapK, C, A::put(K, C) 
[with K = unsigned int; C = int; A = DefaultAlloc]':
HttpConnectionCount.h:64:37:   required from here
../../lib/ts/Map.h:258:29: error: 'set_in' was not declared in this scope, and 
no declarations were found by argument-dependent lookup at the point of 
instantiation [-fpermissive]
../../lib/ts/Map.h:258:29: note: declarations in dependent base 
'VecMapElemunsigned int, int, DefaultAlloc, 2' are not found by unqualified 
lookup
../../lib/ts/Map.h:258:29: note: use 'this-set_in' instead
../../lib/ts/Map.h:263:21: error: 'set_add' was not declared in this scope, and 
no declarations were found by argument-dependent lookup at the point of 
instantiation [-fpermissive]
../../lib/ts/Map.h:263:21: note: declarations in dependent base 
'VecMapElemunsigned int, int, DefaultAlloc, 2' are not found by unqualified 
lookup
../../lib/ts/Map.h:263:21: note: use 'this-set_add' instead
make[4]: *** [HttpClientSession.o] Error 1
{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] [Created] (TS-1182) Add a flag to LogBuffer's for endian used

[Leif Hedstrom (Created) (JIRA)]

Add a flag to LogBuffer's for endian used
-

 Key: TS-1182
 URL: https://issues.apache.org/jira/browse/TS-1182
 Project: Traffic Server
  Issue Type: Improvement
  Components: Logging
Reporter: Leif Hedstrom
 Fix For: 3.3.0


After discussions with amc: To support reading logs (either via logcat or log 
collation) on a box with a different endian from where it was generated, we 
need to know which endian we generated the log in. Either that, or go back and 
do the htonl / ntohl  conversions always.  I favor the flag, since most sane 
platforms are little endian anyways (certainly all platforms we support are), 
so why take the cost of the conversions if they are rarely used.

This would let us check the endian flag in e.g. the log collation server, and 
in logcat like tools, and do the conversions only when necessary.

--
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-1181) TSHttpTxnConfigInt* don't look right with MgmtByte fields in OverridableHttpConfigParams

[William Bardwell (Created) (JIRA)]

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


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] [Created] (TS-1177) Download mirrors and cache hits

[Jack Bates (Created) (JIRA)]

Download mirrors and cache hits
---

 Key: TS-1177
 URL: https://issues.apache.org/jira/browse/TS-1177
 Project: Traffic Server
  Issue Type: Improvement
Reporter: Jack Bates


I just applied to GSoC with a proposal to use RFC 6249 (Metalink/HTTP: Mirrors 
and Hashes) to discover requests for the same files from different mirrors and 
redirect clients to mirrors that are already cached

I am filing this JIRA ticket describing my proposal to cause the Apache 
organization to process it [2]. Thanks for considering this proposal

[1] 
http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/nottheoilrig/4001
[2] 
http://mail-archives.apache.org/mod_mbox/trafficserver-dev/201203.mbox/%3CF28ED27B-8224-4362-B98C-945530CADC7C%40me.com%3E

--
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-1178) cop will kill manager server, even cop it self

[Zhao Yongming (Created) (JIRA)]

cop will kill manager  server, even cop it self


 Key: TS-1178
 URL: https://issues.apache.org/jira/browse/TS-1178
 Project: Traffic Server
  Issue Type: Bug
  Components: Management
Affects Versions: 3.1.4
 Environment: git master on RHEL6.1 x86_64
Reporter: Zhao Yongming
Assignee: Zhao Yongming
 Fix For: 3.1.4


{code}
[root@test58 trafficserver]# cat /tmp/traffic_cop.trace 
1333239680. [DEBUG]: Entering init()
1333239680. [DEBUG]: Entering init_signals()
1333239680. [DEBUG]: Entering set_alarm_death()
1333239680. [DEBUG]: Leaving set_alarm_death()
1333239680. [DEBUG]: Leaving init_signals()
1333239680. [DEBUG]: Entering init_config_dir()
1333239680. [DEBUG]: Leaving init_config_dir()
1333239680. [DEBUG]: Entering init_config_file()
1333239680. [DEBUG]: Leaving init_config_file()
1333239680. [DEBUG]: Entering init_lockfiles()
1333239680. [DEBUG]: Leaving init_lockfiles()
1333239680. [DEBUG]: Entering check_lockfile()
1333239680. [unknown]: --- Cop Starting [Version: Apache Traffic Server - 
traffic_cop - 3.1.4-unstable - (build # 310 on Apr  1 2012 at 00:34:30)] ---
1333239680. [DEBUG]: Leaving check_lockfile()
1333239680. [DEBUG]: Leaving init()
1333239680. [DEBUG]: Entering check()
1333239680. [DEBUG]: Entering check_no_run()
1333239680. [DEBUG]: Entering transient_error(2, 500)
1333239680. [DEBUG]: Leaving transient_error(2, 500) -- false
1333239680. [DEBUG]: Leaving check_no_run() -- 0
1333239680. [DEBUG]: Entering read_config()
1333239680. [DEBUG]: Entering build_config_table(33932704)
1333239680. [DEBUG]: Leaving build_config_table(33932704)
1333239680. [DEBUG]: Entering process_syslog_config()
1333239680. [DEBUG]: Leaving process_syslog_config()
1333239680. [DEBUG]: Leaving read_config()
1333239680. [DEBUG]: Entering check_programs()
1333239680. [DEBUG]: Entering heartbeat_manager()
1333239680. [WARNING]: (cli test) unable to retrieve manager_binary
1333239680. [WARNING]: manager heartbeat [variable] failed [1]
1333239680. [DEBUG]: Leaving heartbeat_manager() -- -1
1333239680. [DEBUG]: Entering check_memory()
1333239680. [DEBUG]: Leaving check_memory()
1333239680. [DEBUG]: Entering millisleep(1)
1333239680. [DEBUG]: Leaving millisleep(1)
1333239680. [DEBUG]: Entering check_no_run()
1333239680. [DEBUG]: Entering transient_error(2, 500)
1333239680. [DEBUG]: Leaving transient_error(2, 500) -- false
1333239680. [DEBUG]: Leaving check_no_run() -- 0
1333239680. [DEBUG]: Entering read_config()
1333239680. [DEBUG]: Entering check_programs()
1333239680. [DEBUG]: Entering heartbeat_manager()
1333239680. [DEBUG]: Entering milliseconds()
1333239680. [DEBUG]: Leaving milliseconds()
1333239680. [DEBUG]: Entering open_socket(8088, (null), (null))
1333239680. [DEBUG]: Entering transient_error(115, 500)
1333239680. [DEBUG]: Leaving transient_error(115, 500) -- false
1333239680. [DEBUG]: Leaving open_socket(8088, 127.0.0.1, (null)) -- 8
1333239680. [DEBUG]: Entering milliseconds()
1333239680. [DEBUG]: Leaving milliseconds()
1333239680. [DEBUG]: Entering milliseconds()
1333239680. [DEBUG]: Leaving milliseconds()
1333239680. [DEBUG]: Entering milliseconds()
1333239680. [DEBUG]: Leaving milliseconds()
1333239680. [WARNING]: (manager test) bad response value
1333239680. [WARNING]: manager heartbeat [variable] failed [2]
1333239680. [WARNING]: killing manager
1333239680. [DEBUG]: Entering 
safe_kill(/var/run/trafficserver/manager.lock, traffic_manager, 1)
1333239680. [DEBUG]: Entering set_alarm_warn()
1333239680. [DEBUG]: Leaving set_alarm_warn()
1333239680. [DEBUG]: Entering set_alarm_death()
1333239680. [DEBUG]: Leaving set_alarm_death()
1333239680. [DEBUG]: Leaving 
safe_kill(/var/run/trafficserver/manager.lock, traffic_manager, 1)
1333239680. [DEBUG]: Leaving heartbeat_manager() -- -1
1333239680. [DEBUG]: Entering check_memory()
1333239680. [DEBUG]: Leaving check_memory()
1333239680. [DEBUG]: Entering millisleep(1)
1333239680. [DEBUG]: Leaving millisleep(1)
1333239680. [DEBUG]: Entering check_no_run()
1333239680. [DEBUG]: Entering transient_error(2, 500)
1333239680. [DEBUG]: Leaving transient_error(2, 500) -- false
1333239680. [DEBUG]: Leaving check_no_run() -- 0
1333239680. [DEBUG]: Entering read_config()
1333239680. [DEBUG]: Entering check_programs()
1333239680. [WARNING]: traffic_manager not running, making sure 
traffic_server is dead
1333239680. [DEBUG]: Entering 
safe_kill(/var/run/trafficserver/server.lock, traffic_server, 0)
1333239680. [DEBUG]: Entering set_alarm_warn()
1333239680. [DEBUG]: Leaving set_alarm_warn()
1333239680. 

[jira] [Created] (TS-1179) libraries and plugins are installed with .la files

[Created]

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ć


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] [Created] (TS-1180) gzip plugin needs to be configurable for certain file/mime types

[Created]

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ć


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] [Created] (TS-1173) remap.config comments are wrong

[Alan M. Carroll (Created) (JIRA)]

remap.config comments are wrong
---

 Key: TS-1173
 URL: https://issues.apache.org/jira/browse/TS-1173
 Project: Traffic Server
  Issue Type: Bug
  Components: Configuration
Affects Versions: 3.1.3
Reporter: Alan M. Carroll
Assignee: Leif Hedstrom
Priority: Minor
 Fix For: 3.3.0


The comments in remap.config describe the configuration lines incorrectly.

--
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-1175) The LogBuffer object is allocated with new (and deallocated with delete)

[Leif Hedstrom (Created) (JIRA)]

The LogBuffer object is allocated with new (and deallocated with delete)


 Key: TS-1175
 URL: https://issues.apache.org/jira/browse/TS-1175
 Project: Traffic Server
  Issue Type: Improvement
  Components: Logging
Reporter: Leif Hedstrom
 Fix For: 3.3.0


We should at least use a class allocator for LogBuffer itself, and perhaps even 
its internal buffer.

--
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-1176) Eliminate the delayed delete of LogBuffer

[Leif Hedstrom (Created) (JIRA)]

Eliminate the delayed delete of LogBuffer
-

 Key: TS-1176
 URL: https://issues.apache.org/jira/browse/TS-1176
 Project: Traffic Server
  Issue Type: Improvement
  Components: Logging
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
 Fix For: 3.1.4


There's a race condition in another place in the code, and it's obvious to me 
that this deferred delete was done to avoid this race condition.

--
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-1172) Remove remap/StringHash.{cc,h}

[Leif Hedstrom (Created) (JIRA)]

Remove remap/StringHash.{cc,h}
--

 Key: TS-1172
 URL: https://issues.apache.org/jira/browse/TS-1172
 Project: Traffic Server
  Issue Type: Improvement
  Components: HTTP
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
 Fix For: 3.1.4


These files are not used, nuke.

--
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-1170) ats_ip_getbestaddrinfo should provide better options

[Alan M. Carroll (Created) (JIRA)]

ats_ip_getbestaddrinfo should provide better options


 Key: TS-1170
 URL: https://issues.apache.org/jira/browse/TS-1170
 Project: Traffic Server
  Issue Type: Improvement
  Components: Network
Affects Versions: 3.1.3
Reporter: Alan M. Carroll
Assignee: Alan M. Carroll
Priority: Minor
 Fix For: sometime


ats_ip_getaddrinfo should support better options about how it selects addresses.

* Pick just one address that can be either family.
* Force IPv4, IPv6 or be able to prefer if two are equivalent.

--
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-1171) Crash report: http_ui cache lookup, double free

[Zhao Yongming (Created) (JIRA)]

Crash report: http_ui cache lookup, double free
---

 Key: TS-1171
 URL: https://issues.apache.org/jira/browse/TS-1171
 Project: Traffic Server
  Issue Type: Bug
  Components: Core
Affects Versions: 3.1.4
Reporter: Zhao Yongming


{code}
*** glibc detected *** /opt/ats/bin/traffic_server: double free or corruption 
(!prev): 0x013e9a50 ***
=== Backtrace: =
/lib64/libc.so.6(+0x77856)[0x2b14ef973856]
/lib64/libc.so.6(cfree+0x6c)[0x2b14ef97774c]
/opt/ats/bin/traffic_server(ShowCache::~ShowCache()+0x20)[0x6428c0]
/opt/ats/bin/traffic_server(ShowCont::done(int, int, void*)+0x23)[0x5e1c63]
/opt/ats/bin/traffic_server(ShowCache::handleCacheEvent(int, 
Event*)+0x15d7)[0x641ee7]
/opt/ats/bin/traffic_server(Cache::open_read(Continuation*, INK_MD5*, 
CacheFragType, char*, int)+0x42c)[0x64e62c]
/opt/ats/bin/traffic_server(ShowCache::lookup_url(int, Event*)+0x1a5)[0x63f655]
/opt/ats/bin/traffic_server(EThread::process_event(Event*, int)+0x90)[0x6a6350]
/opt/ats/bin/traffic_server(EThread::execute()+0x31b)[0x6a6c3b]
/opt/ats/bin/traffic_server[0x6a5142]
/lib64/libpthread.so.0(+0x8e2c)[0x2b14ed0f5e2c]
/lib64/libc.so.6(clone+0x6d)[0x2b14ef9d63cd]
{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] [Created] (TS-1169) in enable-debug and pristine_host_hdr=0 mode, TS will crash when purge a cached object which is after TSCacheUrlSet

[Conan Wang (Created) (JIRA)]

in enable-debug and pristine_host_hdr=0 mode, TS will crash when purge a cached 
object which is after TSCacheUrlSet
---

 Key: TS-1169
 URL: https://issues.apache.org/jira/browse/TS-1169
 Project: Traffic Server
  Issue Type: Bug
Affects Versions: 3.0.4, 3.1.3
 Environment: configure --enable-debug
Reporter: Conan Wang


{code}
#6  0x000100d269af in _ink_assert (a=0x1003c6be0 md5a == md5b || 
t_state.txn_conf-maintain_pristine_host_hdr, f=0x1003c514e HttpSM.cc, 
l=3921) at ink_assert.cc:44
#7  0x000100123e59 in HttpSM::do_cache_delete_all_alts (this=0x109d41190, 
cont=0x0) at HttpSM.cc:3921
{code}

in HttpSM::do_cache_delete_all_alts debug code, if a object key is rewritten by 
TSCacheUrlSet, md5a will not equal md5b, and it will crash because 
maintain_pristine_host_hdr = 0 ( when disable pristine_host_hdr ).

Anyway, the cached object is purged successfully. Maybe it's just a wrong 
assert which didn't consider TSCacheUrlSet case.

{code}
#ifdef DEBUG
  INK_MD5 md5a;
  INK_MD5 md5b;
  t_state.hdr_info.client_request.url_get()-MD5_get(md5a);
  t_state.cache_info.lookup_url-MD5_get(md5b);
  ink_assert(md5a == md5b || t_state.txn_conf-maintain_pristine_host_hdr);
#endif

{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] [Created] (TS-1166) proxy/Stuffer.cc is not IPv6 compatible.

[Alan M. Carroll (Created) (JIRA)]

proxy/Stuffer.cc is not IPv6 compatible.


 Key: TS-1166
 URL: https://issues.apache.org/jira/browse/TS-1166
 Project: Traffic Server
  Issue Type: Bug
  Components: Clustering
Affects Versions: 3.1.3
Reporter: Alan M. Carroll
Priority: Minor
 Fix For: 3.1.4


Parent IP tracking in proxy/Stuff.cc is IPv4 only.

Also the use of ink_gethostbyname should be removed.

--
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-1167) proxy/ParentSelection.cc is not IPv6 compliant.

[Alan M. Carroll (Created) (JIRA)]

proxy/ParentSelection.cc is not IPv6 compliant.
---

 Key: TS-1167
 URL: https://issues.apache.org/jira/browse/TS-1167
 Project: Traffic Server
  Issue Type: Bug
  Components: Clustering
Affects Versions: 3.1.3
Reporter: Alan M. Carroll
Priority: Minor
 Fix For: 3.1.4


setup_socks_servers is IPv4 only. It should be changed to use getaddrinfo() and 
handle IPv6 addresses. This may require changing ParentRecord.

--
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-1168) Remap blind tunnel handling is not IPv6 compliant

[Alan M. Carroll (Created) (JIRA)]

Remap blind tunnel handling is not IPv6 compliant
-

 Key: TS-1168
 URL: https://issues.apache.org/jira/browse/TS-1168
 Project: Traffic Server
  Issue Type: Bug
  Components: Core
Affects Versions: 3.1.3
Reporter: Alan M. Carroll
Priority: Minor
 Fix For: 3.1.4


When a blind tunnel request is received, the hostname is set as the IP address. 
This is hardwired for IPv4. ink_gethostbyname should be replaced by getaddrinfo 
and the logic made IPv6 compliant.

--
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-1163) Raw disks with more than (2^32)-1 sectors (usually 2TB) are not supported on linux

[B Wyatt (Created) (JIRA)]

Raw disks with more than (2^32)-1 sectors (usually 2TB) are not supported on 
linux
--

 Key: TS-1163
 URL: https://issues.apache.org/jira/browse/TS-1163
 Project: Traffic Server
  Issue Type: Bug
  Components: Cache
Reporter: B Wyatt
Assignee: B Wyatt


Due to 32bit integers in both the trafficersever code and the ioctl used to 
determine raw disk size, the number of sectors reported to the cache storage 
system is bound to 0-0x.  If a disk has 512 byte sectors and is larger 
than 2TB it will report (num_sectors % 0x) *  512 bytes avaliable.

--
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-1164) a race condition in cache init

[weijin (Created) (JIRA)]

 a race condition in cache init
---

 Key: TS-1164
 URL: https://issues.apache.org/jira/browse/TS-1164
 Project: Traffic Server
  Issue Type: Bug
  Components: Cache
Affects Versions: 3.0.0, 3.1.1
 Environment: all
Reporter: weijin
Assignee: weijin
 Fix For: 3.1.6


there is a race condition in CacheProcessor::diskInitialized, which may lead to 
cache can not be enabled.  

--
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-1165) Health checks not working

[Igor Brezac (Created) (JIRA)]

Health checks not working
-

 Key: TS-1165
 URL: https://issues.apache.org/jira/browse/TS-1165
 Project: Traffic Server
  Issue Type: Bug
  Components: Core
Affects Versions: 3.1.3
Reporter: Igor Brezac
 Fix For: 3.1.4


Health checks not working

--
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-1160) FATAL: ink_memalign: couldn't allocate 602439680 bytes at alignment 4096 - insufficient memory ts crash

[bettydramit (Created) (JIRA)]

FATAL: ink_memalign: couldn't allocate 602439680 bytes at alignment 4096 - 
insufficient memory   ts crash
-

 Key: TS-1160
 URL: https://issues.apache.org/jira/browse/TS-1160
 Project: Traffic Server
  Issue Type: Bug
  Components: Core
Affects Versions: 3.0.3
 Environment: centos 6.0 x86_64
Reporter: bettydramit


FATAL: ink_memalign: couldn't allocate 602439680 bytes at alignment 4096 - 
insufficient memory
/usr/bin/traffic_server - STACK TRACE: 
/usr/lib64/trafficserver/libtsutil.so.3(ink_fatal_va+0x9d)[0x2ab0905926dd]
/usr/lib64/trafficserver/libtsutil.so.3(ink_fatal+0x88)[0x2ab090592838]
/usr/lib64/trafficserver/libtsutil.so.3(ink_memalign+0x9c)[0x2ab09059414c]
/usr/bin/traffic_server(_ZN9CacheSync9mainEventEiP5Event+0x2c8)[0x644ab8]
/usr/bin/traffic_server(_ZN3Vol12aggWriteDoneEiP5Event+0x5d7)[0x668567]
/usr/bin/traffic_server(_ZN13AIOThreadInfo5startEiP5Event+0x945)[0x6772d5]
/usr/bin/traffic_server(_ZN7EThread7executeEv+0xb86)[0x6ac6a6]
/usr/bin/traffic_server[0x6aa4a2]
/lib64/libpthread.so.0(+0x77f1)[0x2ab0907bd7f1]
/lib64/libc.so.6(clone+0x6d)[0x2ab092e4792d]


--
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-1161) insafe raw device in storage.config

[Zhao Yongming (Created) (JIRA)]

insafe raw device in storage.config
---

 Key: TS-1161
 URL: https://issues.apache.org/jira/browse/TS-1161
 Project: Traffic Server
  Issue Type: Bug
  Components: Core
Reporter: Zhao Yongming


if you system is on /dev/sda and you put /dev/sda into storage.config, TS will 
destroy the data on /dev/sda without any hesitate.

this is proved to be true, please do not try, trust me.

--
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-1162) UnixNetVConnection.cc assertion when accepting a TLS connection

[James Peach (Created) (JIRA)]

UnixNetVConnection.cc assertion when accepting a TLS connection
---

 Key: TS-1162
 URL: https://issues.apache.org/jira/browse/TS-1162
 Project: Traffic Server
  Issue Type: Bug
  Components: Core
Affects Versions: 3.1.4
Reporter: James Peach


Trunk always crashes when accepting a TLS connection:


FATAL: UnixNetVConnection.cc:801: failed assert `vio-mutex-thread_holding == 
this_ethread()`
/opt/ats/bin/traffic_server - STACK TRACE: 
0   libtsutil.3.dylib   0x00010c3e7ee7 ink_fatal + 359
1   libtsutil.3.dylib   0x00010c3e6e22 _ink_assert + 66
2   traffic_server  0x00010b9e6d9a 
_ZN18UnixNetVConnection11set_enabledEP3VIO + 90
3   traffic_server  0x00010b9e681d 
_ZN18UnixNetVConnection8reenableEP3VIO + 93
4   traffic_server  0x00010b7bfcd6 _ZN3VIO8reenableEv + 
54
5   traffic_server  0x00010b9e5cd9 
_ZN18UnixNetVConnection10do_io_readEP12ContinuationxP9MIOBuffer + 297
6   traffic_server  0x00010b792611 
_ZN11VConnection5do_ioEiP12ContinuationxP9MIOBufferi + 129
7   traffic_server  0x00010b9d6da9 
_ZN21SSLNextProtocolAccept9mainEventEiPv + 329
8   traffic_server  0x00010b792229 
_ZN12Continuation11handleEventEiPv + 121
9   traffic_server  0x00010b9e89bd 
_ZN18UnixNetVConnection11acceptEventEiP5Event + 829
10  traffic_server  0x00010b792229 
_ZN12Continuation11handleEventEiPv + 121
11  traffic_server  0x00010ba0905d 
_ZN7EThread13process_eventEP5Eventi + 349
12  traffic_server  0x00010ba09367 
_ZN7EThread7executeEv + 215
13  traffic_server  0x00010ba080ed 
_ZL21spawn_thread_internalPv + 109
14  libsystem_c.dylib   0x7fff8fcb78bf _pthread_start + 335
15  libsystem_c.dylib   0x7fff8fcbab75 thread_start + 13
[Mar 22 21:58:45.009] Manager {0x7fff79b01960} ERROR: 
[LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 6: 
Abort trap: 6


--
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-1157) freelist for TSAPI's and plugin structs

[Leif Hedstrom (Created) (JIRA)]

freelist for TSAPI's and plugin structs
-

 Key: TS-1157
 URL: https://issues.apache.org/jira/browse/TS-1157
 Project: Traffic Server
  Issue Type: New Feature
  Components: TS API
Reporter: Leif Hedstrom
 Fix For: 3.3.0


It could be useful to expose a simple freelist APIs, which lets plugins 
allocate and free simple C structs on a freelist, instead of having to call 
TSmalloc / TSfree.

--
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-1158) Race on mutex switching for NetVConnections in UnixNetVConnection::mainEvent

[John Plevyak (Created) (JIRA)]

Race on mutex switching for NetVConnections in UnixNetVConnection::mainEvent


 Key: TS-1158
 URL: https://issues.apache.org/jira/browse/TS-1158
 Project: Traffic Server
  Issue Type: Bug
  Components: Core
Affects Versions: 3.0.3
 Environment: ALL
Reporter: John Plevyak
Assignee: John Plevyak
 Fix For: 3.1.4


Because of the way session management works, the vio.mutex must be re-verified 
to be identical to the one the lock was taken on after the lock is acquired.  
Otherwise there is a race when the mutex is switched allowing such that the old 
lock is held while the new lock is in not held.

--
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-1159) add compiler hints to debug logging

[James Peach (Created) (JIRA)]

add compiler hints to debug logging
---

 Key: TS-1159
 URL: https://issues.apache.org/jira/browse/TS-1159
 Project: Traffic Server
  Issue Type: Improvement
  Components: Logging
Reporter: James Peach
Assignee: James Peach
Priority: Minor
 Fix For: 3.1.4


Add compiler hints to specify that we usually don't emit diagnostic logging.

--
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-1152) http_ui error,when i get http://localhost/cache/

[bettydramit (Created) (JIRA)]

http_ui error,when i get http://localhost/cache/


 Key: TS-1152
 URL: https://issues.apache.org/jira/browse/TS-1152
 Project: Traffic Server
  Issue Type: Bug
  Components: Web UI
Affects Versions: 3.0.4
 Environment: centos 6 x86_64
Reporter: bettydramit


When i enable http_ui  ，I got follow error (get http://xxx.xxx.xxx.xxx/cache/)

[Mar 19 16:46:17.778] Manager {13989191624} ERROR: 
[WebHttpHandleConnection] /favicon.ico not valid autoconf file
[Mar 19 16:46:17.778] Manager {13989191624} ERROR:  (last system error 11: 
Resource temporarily unavailable)
[Mar 19 16:46:19.089] Manager {13989191624} ERROR: 
[WebHttpHandleConnection] /favicon.ico not valid autoconf file
[Mar 19 16:46:19.090] Manager {13989191624} ERROR:  (last system error 11: 
Resource temporarily unavailable)
[Mar 19 16:46:20.763] Manager {13989191624} ERROR: 
[WebHttpHandleConnection] /favicon.ico not valid autoconf file
[Mar 19 16:46:20.763] Manager {13989191624} ERROR:  (last system error 11: 
Resource temporarily unavailable)
[Mar 19 16:58:21.906] Manager {13989191624} ERROR: 
[WebHttpHandleConnection] /robots.txt not valid autoconf file
[Mar 19 16:58:21.906] Manager {13989191624} ERROR:  (last system error 11: 
Resource temporarily unavailable)
[Mar 19 17:01:43.703] Manager {13989191624} ERROR: 
[WebHttpHandleConnection] /favicon.ico not valid autoconf file
[Mar 19 17:01:43.703] Manager {13989191624} ERROR:  (last system error 11: 
Resource temporarily unavailable)


--
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-1153) On Solaris, link with libumem by default

[Created]

On Solaris, link with libumem by default


 Key: TS-1153
 URL: https://issues.apache.org/jira/browse/TS-1153
 Project: Traffic Server
  Issue Type: Improvement
  Components: Performance
 Environment: Solaris
Reporter: Igor Galić


http://developers.sun.com/solaris/articles/multiproc/multiproc.html

Maybe we should make use of that and link to libumem by default.

--
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-1154) quick_filter on HEAD does not work

[Zhao Yongming (Created) (JIRA)]

quick_filter on HEAD does not work
--

 Key: TS-1154
 URL: https://issues.apache.org/jira/browse/TS-1154
 Project: Traffic Server
  Issue Type: Bug
  Components: HTTP
Reporter: Zhao Yongming
Assignee: weijin


we take quick filter as a good solution for some security concern, but when I 
set it to 0x0733, it does not allow HEAD in, but setting as 0x0723 does that.


Weijin have the patch in our tree: 
https://gitorious.org/trafficserver/taobao/commit/cb23b87d167da4074e047fabc94786003ee94e9a/diffs/db7d0e5be69988b531e8d1e4eea717e6d46df5cd

I will commit if no one complain in 2 days.

--
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-1155) POST requests that are chunked encoding hang when going forward to origin over SSL

[William Bardwell (Created) (JIRA)]

POST requests that are chunked encoding hang when going forward to origin over 
SSL
--

 Key: TS-1155
 URL: https://issues.apache.org/jira/browse/TS-1155
 Project: Traffic Server
  Issue Type: Bug
  Components: HTTP
Affects Versions: 3.0.2
Reporter: William Bardwell


If you make a chunked encoded POST request, e.g.:
curl -H Transfer-Encoding: chunked -d@/etc/ca-certificates.conf 
http://example.com/cgi-bin/cgi.pl
Where ATS is going forward to the origin over SSL, it junk hangs for a little 
while and ends up returning a 502 response.

The problem seems to be code at proxy/http/HttpTransact.cc:5273 which only 
checks for chunked encoding when the scheme is http.  Just removing the extra 
scheme check makes it work for me.

I don't know why it has that check, especially since it is checking for http or 
https right before that.

--
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-1156) Multiple time tags in a log format gets bad results

[Leif Hedstrom (Created) (JIRA)]

Multiple time tags in a log format gets bad results
-

 Key: TS-1156
 URL: https://issues.apache.org/jira/browse/TS-1156
 Project: Traffic Server
  Issue Type: Bug
  Components: Logging
Reporter: Leif Hedstrom
 Fix For: 3.1.4


It seems putting two (or more) date time tags in a custom log generates bad 
results. For example, with one such tag, I see:

{code}
   [%cqtn]

 [19/Mar/2012:14:30:51 -0600] 
{code}

vs

{code}
   [%cqts %cqtn]


  [183876 07/Apr/2028:19:26:39 -0600]
{code}

This is obviously not the correct date now for either tags (the first is not 
correct either). I'm guessing something in the marshalling code might be 
corrupting the timestamp?

--
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-1149) pretty up automate output

[James Peach (Created) (JIRA)]

pretty up automate output
-

 Key: TS-1149
 URL: https://issues.apache.org/jira/browse/TS-1149
 Project: Traffic Server
  Issue Type: Improvement
  Components: Build
Reporter: James Peach
Assignee: James Peach
Priority: Trivial


automake is super ugly by default. Make it pretty.

--
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-1150) Improve on some header handling functionality

[Leif Hedstrom (Created) (JIRA)]

Improve on some header handling functionality
-

 Key: TS-1150
 URL: https://issues.apache.org/jira/browse/TS-1150
 Project: Traffic Server
  Issue Type: Bug
  Components: Core
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
 Fix For: 3.1.4


There are a few performance and functionality improvements we can do around 
header handling.

--
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-1151) in some strange situation, cop will crash

[Zhao Yongming (Created) (JIRA)]

in some strange situation, cop will crash
-

 Key: TS-1151
 URL: https://issues.apache.org/jira/browse/TS-1151
 Project: Traffic Server
  Issue Type: Bug
Reporter: Zhao Yongming
Assignee: Zhao Yongming


we get some strange crash, the manager  cop may die, we are not sure what that 
is, but I'd like to start one Issue here if we have other same issue.

here is the log in /var/log/messages

{code}
Mar 19 10:11:06 cache162.cn77 kernel:: [2510081.212455] [ET_NET 3][319]: 
segfault at 2aaae6e986bc ip 003f7f27bdbe sp 40be2188 error 4 in 
libc-2.5.so[3f7f20+14d000]
Mar 19 10:11:09 cache162.cn77 traffic_manager[305]: {0x7fd3a665c720} FATAL: 
[LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
Mar 19 10:11:09 cache162.cn77 traffic_manager[305]: {0x7fd3a665c720} FATAL:  
(last system error 104: Connection reset by peer)
Mar 19 10:11:09 cache162.cn77 traffic_manager[305]: {0x7fd3a665c720} ERROR: 
[LocalManager::sendMgmtMsgToProcesses] Error writing message
Mar 19 10:11:09 cache162.cn77 traffic_manager[305]: {0x7fd3a665c720} ERROR:  
(last system error 32: Broken pipe)
Mar 19 10:11:09 cache162.cn77 traffic_cop[303]: cop received child status 
signal [305 2816]
Mar 19 10:11:09 cache162.cn77 traffic_cop[303]: traffic_manager not running, 
making sure traffic_server is dead
Mar 19 10:11:09 cache162.cn77 traffic_cop[303]: spawning traffic_manager
Mar 19 10:11:16 cache162.cn77 traffic_manager[1227]: NOTE: --- Manager Starting 
---
Mar 19 10:11:16 cache162.cn77 traffic_manager[1227]: NOTE: Manager Version: 
Apache Traffic Server - traffic_manager - 3.0.2 - (build # 299 on Mar  9 2012 
at 09:55:44)
Mar 19 10:11:16 cache162.cn77 traffic_manager[1227]: {0x7f8ae2f48720} STATUS: 
opened /var/log/trafficserver/manager.log
Mar 19 10:11:23 cache162.cn77 traffic_cop[303]: (cli test) unable to retrieve 
manager_binary
Mar 19 10:11:39 cache162.cn77 traffic_server[1260]: NOTE: --- Server Starting 
---
Mar 19 10:11:39 cache162.cn77 traffic_server[1260]: NOTE: Server Version: 
Apache Traffic Server - traffic_server - 3.0.2 - (build # 299 on Mar  9 2012 at 
09:56:00)
Mar 19 10:11:46 cache162.cn77 traffic_server[1260]: {0x2ad4afd3d970} STATUS: 
opened /var/log/trafficserver/diags.log
Mar 19 10:15:06 cache162.cn77 kernel:: [2510320.713808] [ET_NET 3][1277]: 
segfault at 2aab1cfa6a03 ip 003f7f27bdbe sp 4141c188 error 4 in 
libc-2.5.so[3f7f20+14d000]
Mar 19 10:15:06 cache162.cn77 traffic_manager[1227]: {0x7f8ae2f48720} ERROR: 
[LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 11: 
Segmentation fault
Mar 19 10:15:06 cache162.cn77 traffic_manager[1227]: {0x7f8ae2f48720} ERROR:  
(last system error 2: No such file or directory)
Mar 19 10:15:06 cache162.cn77 traffic_manager[1227]: {0x7f8ae2f48720} ERROR: 
[Alarms::signalAlarm] Server Process was reset
Mar 19 10:15:06 cache162.cn77 traffic_manager[1227]: {0x7f8ae2f48720} ERROR:  
(last system error 2: No such file or directory)
Mar 19 10:15:08 cache162.cn77 traffic_server[2412]: NOTE: --- Server Starting 
---
Mar 19 10:15:08 cache162.cn77 traffic_server[2412]: NOTE: Server Version: 
Apache Traffic Server - traffic_server - 3.0.2 - (build # 299 on Mar  9 2012 at 
09:56:00)
Mar 19 10:15:08 cache162.cn77 traffic_server[2412]: {0x2af4c2ad5970} STATUS: 
opened /var/log/trafficserver/diags.log
Mar 19 10:54:53 cache162.cn77 ops.hdmon.power: [ OK ] Power Unit PSU 1: 
OK;Power Unit PSU 2: OK.
{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] [Created] (TS-1146) RFC 5077 TLS Session tickets

[James Peach (Created) (JIRA)]

RFC 5077 TLS Session tickets


 Key: TS-1146
 URL: https://issues.apache.org/jira/browse/TS-1146
 Project: Traffic Server
  Issue Type: Improvement
  Components: SSL
Reporter: James Peach


For supporting RFC 5077 TLS Session tickets across a ATS cluster, all the 
machines need to have the same server ticket.

See https://github.com/apache/httpd rev 967d943b93498233f0ec81a5b48706fdb6892dfd

--
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-1147) deprecate records.config SSL configuration

[James Peach (Created) (JIRA)]

deprecate records.config SSL configuration
--

 Key: TS-1147
 URL: https://issues.apache.org/jira/browse/TS-1147
 Project: Traffic Server
  Issue Type: Improvement
  Components: SSL
Reporter: James Peach
Priority: Minor


Since ssl_multicert.config is a strict superset of the SSL certificate 
configuration in records.config, we should deprecate configuring SSL 
certificates in records.config and make ssl_multicert.config the One True Way.

--
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-1142) we need to record ram hit in ram cache hit

[Zhao Yongming (Created) (JIRA)]

we need to record ram hit in ram cache hit
--

 Key: TS-1142
 URL: https://issues.apache.org/jira/browse/TS-1142
 Project: Traffic Server
  Issue Type: Improvement
  Components: Cache, Stats
Affects Versions: 3.1.4
Reporter: Zhao Yongming
Assignee: kuotai


we need to record the ram  mem hites in stats

--
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-1144) fox out of tree builds

[James Peach (Created) (JIRA)]

fox out of tree builds
--

 Key: TS-1144
 URL: https://issues.apache.org/jira/browse/TS-1144
 Project: Traffic Server
  Issue Type: Bug
  Components: Build
Reporter: James Peach
Assignee: James Peach


Fixes some minor issues in the build system when building sources in separate 
directory than the obj files.

--
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-1145) clang build fixes

[James Peach (Created) (JIRA)]

clang build fixes
-

 Key: TS-1145
 URL: https://issues.apache.org/jira/browse/TS-1145
 Project: Traffic Server
  Issue Type: Bug
  Components: Build
Reporter: James Peach
Assignee: James Peach
Priority: Minor


A handful of build fixes for svn versions of clang++. It's strict in slightly 
different ways than the current release version.

--
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-1140) Implement HTTP method filtering in ip_allow.config

[Igor Brezac (Created) (JIRA)]

Implement HTTP method filtering in ip_allow.config
--

 Key: TS-1140
 URL: https://issues.apache.org/jira/browse/TS-1140
 Project: Traffic Server
  Issue Type: New Feature
  Components: HTTP
Affects Versions: 3.1.2, 3.1.3
Reporter: Igor Brezac
Priority: Critical
 Fix For: 3.1.3


Implement HTTP method filtering in ip_allow.config (and deprecate 
proxy.config.http.quick_filter.mask)

--
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-1141) Server intercerpt performance problems.

[Leif Hedstrom (Created) (JIRA)]

Server intercerpt performance problems.
---

 Key: TS-1141
 URL: https://issues.apache.org/jira/browse/TS-1141
 Project: Traffic Server
  Issue Type: Improvement
  Components: Core
Reporter: Leif Hedstrom
 Fix For: 3.3.0


It seems server intercept plugins are fairly expensive. A very simple one, 
serving a few bytes out of RAM, can only do in the order of 20K QPS, whereas 
the same server serving out of RAM cache do wo 175k QPS. I know there will be 
overhead in plugin APIs, but almost 10x seems quite high.

--
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-1136) Expose Configuration API such that config files can be written (or scripted) in a glue-language such as Lua

[Created]

Expose Configuration API such that config files can be written (or scripted) in 
a glue-language such as Lua
---

 Key: TS-1136
 URL: https://issues.apache.org/jira/browse/TS-1136
 Project: Traffic Server
  Issue Type: New Feature
  Components: Configuration
Reporter: Igor Galić


To unify and simplify our configuration it would be great to have them in a 
script language.
Lua is an ideal candidate as it is easy to embed and it would make for a 
wonderful - and powerful DSL.

--
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-1138) IpMap::fill does not handle singleton, then range correctly.

[Alan M. Carroll (Created) (JIRA)]

IpMap::fill does not handle singleton, then range correctly.


 Key: TS-1138
 URL: https://issues.apache.org/jira/browse/TS-1138
 Project: Traffic Server
  Issue Type: Bug
  Components: Core
Affects Versions: 3.1.2
Reporter: Alan M. Carroll
Assignee: Alan M. Carroll
Priority: Minor
 Fix For: 3.1.3


If you use IpMap::fill on a singleton, and then a range, the resulting ranges 
can overlap the singleton.

--
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-1139) Expose API such that plugins can easily be written in a glue-language such as Lua.

[Created]

Expose API such that plugins can easily be written in a glue-language such as 
Lua.
--

 Key: TS-1139
 URL: https://issues.apache.org/jira/browse/TS-1139
 Project: Traffic Server
  Issue Type: New Feature
Reporter: Igor Galić


Let's be honest here: our plugin API is great. But woulnd't it be great if we 
didn't just expose it to C/C++ but also to a script language, like Lua?
I think it would be cool if an admin (I think they are be our main target group 
here) could hack up a couple of lines of Lua script and already have a great 
(prototype of a) plugin.

--
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-1132) Clean up usage of HDR_BUF_RONLY_HEAPS

[Leif Hedstrom (Created) (JIRA)]

Clean up usage of HDR_BUF_RONLY_HEAPS
-

 Key: TS-1132
 URL: https://issues.apache.org/jira/browse/TS-1132
 Project: Traffic Server
  Issue Type: Improvement
  Components: Core
Reporter: Leif Hedstrom
 Fix For: 3.1.4


We should clean up the usage of HDR_BUF_RONLY_HEAPS, and not assume it's always 
3. In addition, we should consider making this configurable, via either 
records.config, or at least configure.ac.

--
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-1133) Make remap max-host length configure.ac configurable

[Leif Hedstrom (Created) (JIRA)]

Make remap max-host length configure.ac configurable


 Key: TS-1133
 URL: https://issues.apache.org/jira/browse/TS-1133
 Project: Traffic Server
  Issue Type: Improvement
  Components: Remap API
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
 Fix For: 3.1.3


Right now, we have a hardcoded limit of 256 bytes on the Host matching. We 
should make this configurable.

--
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-1134) TSNetAcceptNamedProtocol should fail if NPN is not supported

[James Peach (Created) (JIRA)]

TSNetAcceptNamedProtocol should fail if NPN is not supported


 Key: TS-1134
 URL: https://issues.apache.org/jira/browse/TS-1134
 Project: Traffic Server
  Issue Type: Bug
  Components: TS API
Reporter: James Peach
Assignee: James Peach
Priority: Minor
 Fix For: 3.2.0


If NPN is not supported by the OpenSSL version, TSNetAcceptNamedProtocol() 
should always fail so that plugins don't' get the wrong idea.

--
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-1135) support wildcard certificates for ServerNameIndication (SNI)

[James Peach (Created) (JIRA)]

support wildcard certificates for ServerNameIndication (SNI)


 Key: TS-1135
 URL: https://issues.apache.org/jira/browse/TS-1135
 Project: Traffic Server
  Issue Type: Improvement
  Components: SSL
Reporter: James Peach


The ServerNameIndication support added in TS-472 doesn't handle wildcard 
certificates. We need to add certificate parsing support to detect wildcard 
certificates and then (if there is not an exact match) choose the certificate 
with the longest wildcard match.

--
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-1127) Wrong assignment of incoming address

[Yakov Kopel (Created) (JIRA)]

Wrong assignment of incoming 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
 Fix For: 3.1.4


In HttpSM.cc file (attach_client_session) there are two lines:
  ink_inet_copy(t_state.client_info.addr, netvc-get_remote_addr());
  t_state.client_info.port = netvc-get_local_port();

instead of:
  ink_inet_copy(t_state.client_info.addr, netvc-get_local_addr());
  t_state.client_info.port = netvc-get_local_port();



--
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-1124) Move a few plugins into main repo.

[Leif Hedstrom (Created) (JIRA)]

Move a few plugins into main repo.
--

 Key: TS-1124
 URL: https://issues.apache.org/jira/browse/TS-1124
 Project: Traffic Server
  Issue Type: New Feature
  Components: Plugins
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
 Fix For: 3.1.3


Moving regex_remap, header_filter and stats_over_http into main git repo (in 
plugins). I've tried to preserve history, but it gets a little wonky due to the 
change in directory structure. But the history is there :).

--
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-1125) POST's with Expect: 100-continue are slowed by delayed 100 response.

[William Bardwell (Created) (JIRA)]

POST's with Expect: 100-continue are slowed by delayed 100 response.


 Key: TS-1125
 URL: https://issues.apache.org/jira/browse/TS-1125
 Project: Traffic Server
  Issue Type: Bug
  Components: HTTP
Affects Versions: 3.0.2
 Environment: TS 3.0.2 going to Apache 2.2 web server
Reporter: William Bardwell
Priority: Minor


Sending a post like:
POST / HTTP/1.1
Host: www.example.com
Content-Length: 10
Expect: 100-continue

directly to the web server immediately sends back:
HTTP/1.1 100 Continue

And then when the post data is sent, a status 200 response comes back.
But when going through ATS the HTTP/1.1 100 Continue is not sent immediately, 
and instead is sent after the POST data has been received.  This is legal, but 
it makes clients that are hoping for a 100 continue to wait a little while 
hoping to get that, ATS should forward that response through immediately.

Note: I see curl using Expect: 100-continue with  1024 bytes of post data, 
but web searching indicates that some Microsoft products also use it.



--
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-1123) Problems building with editline/readline on OSX

[Leif Hedstrom (Created) (JIRA)]

Problems building with editline/readline on OSX
---

 Key: TS-1123
 URL: https://issues.apache.org/jira/browse/TS-1123
 Project: Traffic Server
  Issue Type: Bug
  Components: Build
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
 Fix For: 3.1.3


There seems to be a conflict between editline and readline/history.h.

--
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-1120) Use ink_zero / ats_zero instead of calling memset when zeroing a variable or member.

[Alan M. Carroll (Created) (JIRA)]

Use ink_zero / ats_zero instead of calling memset when zeroing a variable or 
member.


 Key: TS-1120
 URL: https://issues.apache.org/jira/browse/TS-1120
 Project: Traffic Server
  Issue Type: Improvement
  Components: Cleanup
Affects Versions: 3.1.2
Reporter: Alan M. Carroll
Priority: Minor
 Fix For: sometime


We have an inline template, ink_zero(foo) which does memset(foo, 0, 
sizeof(foo)). Because this is easy to mess up with a typo, the inline template 
should be used for safety and clarity. Also, the template should be renamed 
ats_zero to be consistent.

--
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-1117) Remove TS_HAS_PURIFY macro

[Brian Geffon (Created) (JIRA)]

Remove TS_HAS_PURIFY macro
--

 Key: TS-1117
 URL: https://issues.apache.org/jira/browse/TS-1117
 Project: Traffic Server
  Issue Type: Bug
Affects Versions: 3.0.3, 3.1.2
Reporter: Brian Geffon
Assignee: Brian Geffon
 Fix For: 3.1.3


The TS_HAS_PURIFY stuff is confusing and should be removed.

--
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-1116) Fix build issues with clang (particularly on OSX)

[Leif Hedstrom (Created) (JIRA)]

Fix build issues with clang (particularly on OSX)
-

 Key: TS-1116
 URL: https://issues.apache.org/jira/browse/TS-1116
 Project: Traffic Server
  Issue Type: Improvement
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
 Fix For: 3.1.3


We should get it to compile with clang again, specially since on OSX, clang is 
the 'future'.

--
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-1115) Fix build issues with Intel ICC

[Leif Hedstrom (Created) (JIRA)]

Fix build issues with Intel ICC
---

 Key: TS-1115
 URL: https://issues.apache.org/jira/browse/TS-1115
 Project: Traffic Server
  Issue Type: Bug
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
 Fix For: 3.1.3


Get it to compile cleanly, and run, with Intel ICC again.

--
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-1112) traffic_cop may crash at free()

[Zhao Yongming (Created) (JIRA)]

traffic_cop may crash at free()
---

 Key: TS-1112
 URL: https://issues.apache.org/jira/browse/TS-1112
 Project: Traffic Server
  Issue Type: Bug
 Environment: v3.0.x
Reporter: Zhao Yongming
Assignee: weijin


traffic_cop may crash, at memory free, that will leave the manager  server 
alone, or may die with the manager too, leave a system without service.

--
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-1113) In case of caching smaller than 1k size of file, It shoud be increase concurrent users.

[Eric Ahn (Created) (JIRA)]

In case of  caching smaller than 1k size of file,  It shoud be increase 
concurrent users.
-

 Key: TS-1113
 URL: https://issues.apache.org/jira/browse/TS-1113
 Project: Traffic Server
  Issue Type: Improvement
  Components: Cache
Affects Versions: 3.1.1
Reporter: Eric Ahn
Priority: Minor
 Fix For: 3.2.0


If there are a lot 1k sized objects, It's not good performance.


--
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-1110) logstats incorrectly bucketizes all status codes greater than 599 as 5xx

[Manjesh Nilange (Created) (JIRA)]

logstats incorrectly bucketizes all status codes greater than 599 as 5xx


 Key: TS-1110
 URL: https://issues.apache.org/jira/browse/TS-1110
 Project: Traffic Server
  Issue Type: Bug
  Components: Stats
Affects Versions: 3.0.3
Reporter: Manjesh Nilange


logstats incorrectly bucketizes all status codes greater than 599 as 5xx. If 
people use custom status codes (999 for example), this will get counted as a 
5xx status.

--
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-1111) crash in RangeTransform::handle_event

[Zhao Yongming (Created) (JIRA)]

crash in RangeTransform::handle_event
-

 Key: TS-
 URL: https://issues.apache.org/jira/browse/TS-
 Project: Traffic Server
  Issue Type: Bug
Reporter: Zhao Yongming
Assignee: weijin


we have some crashing in range requesting processing, it is on our own tree 
based on 3.0.x, that maybe the root cause of the do_io_close issue, we are 
still look at how to fix that, feedback is welcome
{code}
#0  0x004dc624 in RangeTransform::handle_event (this=0x2aaed0001fb0, 
event=1, edata=value optimized out) at Transform.cc:926
926   Debug(transform_range, RangeTransform destroy: %d, 
m_output_vio ? m_output_vio-ndone : 0);
(gdb) bt
#0  0x004dc624 in RangeTransform::handle_event (this=0x2aaed0001fb0, 
event=1, edata=value optimized out) at Transform.cc:926
#1  0x0069145f in EThread::process_event (this=0x2b332010, 
e=0x591d410, calling_code=1) at I_Continuation.h:146
#2  0x00691b8b in EThread::execute (this=0x2b332010) at 
UnixEThread.cc:218
#3  0x0069092e in spawn_thread_internal (a=0x440bfa0) at Thread.cc:88
#4  0x00359fe0673d in pthread_create@@GLIBC_2.2.5 () from 
/lib64/libpthread.so.0
#5  0x in ?? ()
(gdb) p m_output_vio
$1 = (VIO *) 0x2aaed0029fe8
(gdb) p *m_output_vio
Cannot access memory at address 0x2aaed0029fe8
{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] [Created] (TS-1109) stack dump may crash too

[Zhao Yongming (Created) (JIRA)]

stack dump may crash too


 Key: TS-1109
 URL: https://issues.apache.org/jira/browse/TS-1109
 Project: Traffic Server
  Issue Type: Bug
  Components: Core
Affects Versions: 3.1.2
Reporter: Zhao Yongming
Assignee: weijin


the codes doing stack dump may crash, in this case you will not able to get a 
core file, that will hide most of the rare issues.

--
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-1107) dynamically scale the number of net threads

[James Peach (Created) (JIRA)]

dynamically scale the number of net threads
---

 Key: TS-1107
 URL: https://issues.apache.org/jira/browse/TS-1107
 Project: Traffic Server
  Issue Type: New Feature
  Components: Core, Performance
Reporter: James Peach
Priority: Minor


The number of net threads is calculated once at startup, but we ought to 
consider dynamically scaling the number of threads a runtime based on load.

zwoop: right, that's what I meant (keep a counter of how many times epoll had 
no events, and treat that as an idle thread)
zwoop: probably a multiplier of some setting (thread_idle_seconds or some such)
zwoop: this would be a cool feature, if you have the time for it ;)
zwoop: can keep the original calculations / settings as the upper limit I 
think
zwoop: (the calculations can also easily be configured in records.config, so 
that people can modify that upper limit)
zwoop: an ideal solution (backward compatible) would be to just add one new 
setting, reap_idle_threads_seconds or some such, default to 0 (off). With it 
not set, our normal logic applies. With it set, your stuff takes effect, but 
cap it at whatever the other settings 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] [Created] (TS-1108) Allow to clear a particular cache volume

[Leif Hedstrom (Created) (JIRA)]

Allow to clear a particular cache volume
--

 Key: TS-1108
 URL: https://issues.apache.org/jira/browse/TS-1108
 Project: Traffic Server
  Issue Type: New Feature
  Components: Cache
Reporter: Leif Hedstrom


Today, you can clear the entire cache (either at startup, or via e.g. 
-Cclear_cache). This wipes the entire cache. For someone hosting a small 
number of sites, it might be reasonable to partition the cache (using 
volume.config and hosting.config), such that each site gets a fraction of the 
cache. In such a setup, it would also be reasonable (and usable) to be able to 
clear just a single volume (e..g -Cclear_cache_volume 1   or some such).

Thoughts?

--
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-1105) HttpTrasactCache assertion failure: response-status_get() != HTTP_STATUS_RANGE_NOT_SATISFIABLE

[David Eagen (Created) (JIRA)]

HttpTrasactCache assertion failure: response-status_get() != 
HTTP_STATUS_RANGE_NOT_SATISFIABLE 


 Key: TS-1105
 URL: https://issues.apache.org/jira/browse/TS-1105
 Project: Traffic Server
  Issue Type: Bug
  Components: HTTP
Affects Versions: 3.1.2
 Environment: [Feb  8 09:47:05.828] Manager {0x2ae1ee56bcf0} NOTE: 
[ClusterCom::ClusterCom] Node running on OS: 'Linux' Release: 
'2.6.18-194.3.1.el5'

VMWare VM - 64-bit Centos 5.5
Reporter: David Eagen


FATAL: HttpTransactCache.cc:1317: failed assert `response-status_get() != 
HTTP_STATUS_RANGE_NOT_SATISFIABLE`
/opt/trafficserver/bin/traffic_server - STACK TRACE:
/opt/trafficserver/lib/libtsutil.so.3(ink_fatal_va+0xb6)[0x2b60eecbaebe]
/opt/trafficserver/lib/libtsutil.so.3(ink_fatal+0xe4)[0x2b60eecbb096]
/opt/trafficserver/lib/libtsutil.so.3(_ink_assert+0x37)[0x2b60eecb9357]
/opt/trafficserver/bin/traffic_server(_ZN17HttpTransactCache38match_response_to_request_conditionalsEP7HTTPHdrS1_+0x86)[0x57e504]
/opt/trafficserver/bin/traffic_server(_ZN12HttpTransact25build_response_from_cacheEPNS_5StateE15HTTPWarningCode+0xb0)[0x59a426]
/opt/trafficserver/bin/traffic_server(_ZN12HttpTransact22HandleCacheOpenReadHitEPNS_5StateE+0x112a)[0x59d1e8]
/opt/trafficserver/bin/traffic_server(_ZN6HttpSM32call_transact_and_set_next_stateEPFvPN12HttpTransact5StateEE+0x69)[0x56547d]
/opt/trafficserver/bin/traffic_server(_ZN6HttpSM17handle_api_returnEv+0x130)[0x57925c]
/opt/trafficserver/bin/traffic_server(_ZN6HttpSM14do_api_calloutEv+0x39)[0x57d5a3]
/opt/trafficserver/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x69)[0x5774d1]
/opt/trafficserver/bin/traffic_server(_ZN6HttpSM32call_transact_and_set_next_stateEPFvPN12HttpTransact5StateEE+0x142)[0x565556]
/opt/trafficserver/bin/traffic_server(_ZN6HttpSM17handle_api_returnEv+0x130)[0x57925c]
/opt/trafficserver/bin/traffic_server(_ZN6HttpSM14do_api_calloutEv+0x39)[0x57d5a3]
/opt/trafficserver/bin/traffic_server(_ZN6HttpSM14set_next_stateEv+0x69)[0x5774d1]
/opt/trafficserver/bin/traffic_server(_ZN6HttpSM32call_transact_and_set_next_stateEPFvPN12HttpTransact5StateEE+0x142)[0x565556]
/opt/trafficserver/bin/traffic_server(_ZN6HttpSM21state_cache_open_readEiPv+0x360)[0x5748cc]
/opt/trafficserver/bin/traffic_server(_ZN6HttpSM12main_handlerEiPv+0x2fe)[0x572b1a]
/opt/trafficserver/bin/traffic_server(_ZN12Continuation11handleEventEiPv+0x6f)[0x4d5965]
/opt/trafficserver/bin/traffic_server(_ZN11HttpCacheSM21state_cache_open_readEiPv+0x1c3)[0x552e39]
/opt/trafficserver/bin/traffic_server(_ZN12Continuation11handleEventEiPv+0x6f)[0x4d5965]
/opt/trafficserver/bin/traffic_server(_ZN7CacheVC8callcontEi+0x87)[0x6b03b7]
/opt/trafficserver/bin/traffic_server(_ZN7CacheVC17openReadStartHeadEiP5Event+0xf9b)[0x6aa8c1]
/opt/trafficserver/bin/traffic_server(_ZN12Continuation11handleEventEiPv+0x6f)[0x4d5965]
/opt/trafficserver/bin/traffic_server(_ZN7CacheVC14handleReadDoneEiP5Event+0xae2)[0x6872a8]
/opt/trafficserver/bin/traffic_server(_ZN12Continuation11handleEventEiPv+0x6f)[0x4d5965]
/opt/trafficserver/bin/traffic_server(_ZN19AIOCallbackInternal11io_completeEiPv+0x3c)[0x68e2aa]
/opt/trafficserver/bin/traffic_server(_ZN12Continuation11handleEventEiPv+0x6f)[0x4d5965]
/opt/trafficserver/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x11e)[0x6fcba8]
/opt/trafficserver/bin/traffic_server(_ZN7EThread7executeEv+0x94)[0x6fcd9a]
/opt/trafficserver/bin/traffic_server(main+0x1545)[0x5042cd]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x3933c1d994]
/opt/trafficserver/bin/traffic_server[0x4b46d9]
[Feb  8 09:47:04.784] Manager {0x2afb63582cf0} FATAL: 
[LocalManager::pollMgmtProcessServer] Error in read (errno: 104)
[Feb  8 09:47:04.785] Manager {0x2afb63582cf0} FATAL:  (last system error 104: 
Connection reset by peer)
[Feb  8 09:47:04.785] Manager {0x2afb63582cf0} NOTE: 
[LocalManager::mgmtShutdown] Executing shutdown request.
[Feb  8 09:47:04.785] Manager {0x2afb63582cf0} NOTE: 
[LocalManager::processShutdown] Executing process shutdown request.
[Feb  8 09:47:04.786] Manager {0x2afb63582cf0} ERROR: 
[LocalManager::sendMgmtMsgToProcesses] Error writing message
[Feb  8 09:47:04.786] Manager {0x2afb63582cf0} ERROR:  (last system error 32: 
Broken pipe)
[E. Mgmt] log == [TrafficManager] using root directory '/opt/trafficserver'


--
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-1106) redirect map generates multiple Via: header entries.

[Leif Hedstrom (Created) (JIRA)]

redirect map generates multiple Via: header entries.


 Key: TS-1106
 URL: https://issues.apache.org/jira/browse/TS-1106
 Project: Traffic Server
  Issue Type: Bug
  Components: HTTP
Affects Versions: 3.1.2
Reporter: Leif Hedstrom
 Fix For: 3.1.3


It seems using the redirect rule in remap.config, ends up duplicating the entry 
in the Via: header, e.g.

{code}
Via: http/1.1 kramer.ogre.com (ApacheTrafficServer/3.1.3-unstable [u c s f p 
eS:tNc  i p s ]), http/1.1 kramer.ogre.com (ApacheTrafficServer/3.1.3-unstable 
[u c s f p eS:tNc  i p s ])
{code}

I'm not sure why this happens, if it's duplicating it, or if it's going through 
the SM twice. I know i'm not proxying twice through the box.

--
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-1104) Build problem on solaris

[Leif Hedstrom (Created) (JIRA)]

Build problem on solaris


 Key: TS-1104
 URL: https://issues.apache.org/jira/browse/TS-1104
 Project: Traffic Server
  Issue Type: Bug
  Components: Core
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
 Fix For: 3.1.3


Reported and fixed by Igor Brezac

{code}
--- Store.cc.orig   2012-02-06 10:11:26.365180262 -0500
+++ Store.cc2012-02-06 10:11:56.035330329 -0500
@@ -629,7 +629,7 @@
   blocks = size / STORE_BLOCK_SIZE;
   file_pathname = !((s.st_mode  S_IFMT) == S_IFDIR);

-  Debug(cache_init, Span::init - %s hw_sector_size = %d  size = %
PRId64 , blocks = % PRId64 , disk_id = %d, file_pathname = %d,
filename, hw_sector_size, size, blocks, disk_id, file_pathname);
+  Debug(cache_init, Span::init - %s hw_sector_size = % PRId64 ,
size = % PRId64 , blocks = % PRId64 , disk_id = %d, file_pathname
= %d, filename, hw_sector_size, size, blocks, disk_id,
file_pathname);

 Lfail:
   socketManager.close(fd);
{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] [Created] (TS-1102) Cleanup obsolete debugging code

[Uri Shachar (Created) (JIRA)]

Cleanup obsolete debugging code
---

 Key: TS-1102
 URL: https://issues.apache.org/jira/browse/TS-1102
 Project: Traffic Server
  Issue Type: Bug
  Components: Core, Logging, Performance
Affects Versions: 3.0.2
 Environment: Any
Reporter: Uri Shachar
Priority: Minor


The current Diags.h D/EClosure mechanism is obsolete. ATS requires gcc = 4.1 
for all compilation environments, and it includes variadic argument macro 
support with ##_VA_ARGS_ that deletes the final comma if no arguments are 
provided.
Removing the added layer should also improve performance when high volume 
debugging is turned on.

--
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-1099) review of squid replacement algorithm

[Eric Ahn (Created) (JIRA)]

review of squid replacement algorithm
-

 Key: TS-1099
 URL: https://issues.apache.org/jira/browse/TS-1099
 Project: Traffic Server
  Issue Type: Sub-task
Reporter: Eric Ahn
Priority: Minor




--
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-1100) Coredump at startup when there's a duplicate remap rule

[Nick Kew (Created) (JIRA)]

Coredump at startup when there's a duplicate remap rule
---

 Key: TS-1100
 URL: https://issues.apache.org/jira/browse/TS-1100
 Project: Traffic Server
  Issue Type: Bug
  Components: Core
Affects Versions: 3.1.1
 Environment: Bog standard linux/x86; own build.
Reporter: Nick Kew
Priority: Minor


A minor accident with cutpaste in vi leads to TS coredumping at startup.

I had duplicated a line in remap.config:

map http://myhost:8080/  http://target/

()

map http://myhost:8080/  http://target/

The second instance is line 125 in remap.config, and the dump shows:
FATAL: [ReverseProxy] Unable to add mapping rule to lookup table at line 125
bin/traffic_server - STACK TRACE: 
/usr/local/trafficserver/lib/libtsutil.so.3(ink_fatal_va+0xc7)[0xe21873]
/usr/local/trafficserver/lib/libtsutil.so.3(ink_fatal+0x2b)[0xe218c5]
bin/traffic_server(_ZN10UrlRewrite10BuildTableEv+0x1e48)[0x81e1120]
bin/traffic_server(_ZN10UrlRewriteC1EPKc+0x562)[0x810]
bin/traffic_server(_Z18init_reverse_proxyv+0x41)[0x815500b]
bin/traffic_server(_Z20init_HttpProxyServerv+0xe)[0x818fccc]
bin/traffic_server(main+0xf7f)[0x813b65d]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0x692bd6]
bin/traffic_server[0x80f6001]
Aborted

--
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-1101) traffic_line -x doesn't seem to work

[Leif Hedstrom (Created) (JIRA)]

traffic_line -x doesn't seem to work


 Key: TS-1101
 URL: https://issues.apache.org/jira/browse/TS-1101
 Project: Traffic Server
  Issue Type: Bug
  Components: Management
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
Priority: Blocker
 Fix For: 3.1.2


traffic_line -x doesn't seem to work any more.

--
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-1098) Make RC script support Amazon EC2 Linux AMI

[Leif Hedstrom (Created) (JIRA)]

Make RC script support Amazon EC2 Linux AMI
---

 Key: TS-1098
 URL: https://issues.apache.org/jira/browse/TS-1098
 Project: Traffic Server
  Issue Type: Improvement
  Components: Packaging
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
 Fix For: 3.1.2


Add support to detect the Amazon Linux flavor of RHEL/CentOS that runs in the 
default AMIs.

--
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-1094) TS hangs after repeated requests from the same kept-alive connection

[Wilson Ho (Created) (JIRA)]

TS hangs after repeated requests from the same kept-alive connection


 Key: TS-1094
 URL: https://issues.apache.org/jira/browse/TS-1094
 Project: Traffic Server
  Issue Type: Bug
  Components: Core
Affects Versions: 3.1.0
 Environment: Oracle Enterprise Linux 5.5 64-bit
Reporter: Wilson Ho
Priority: Blocker


When a client submits multiple requests while re-using the same keep-alived 
connection, TS hangs.  Usually, the client eventually times out, and at that 
point TS will be waken up and forwards the request to the original server.  
But by then it's too late and the client already closed connection.

In real life traffic, this bug is very hard to reproduce.  But here is an 
artificial test case.

First, make sure client-side keep alive is on.  My test case uses HTTP (port 
80) GET.

Second, make sure the total header size of the requests is exactly 275 bytes, 
including the carriage returns and line feeds.  One byte more or less would 
fail to reproduce the bug.

Third, repeatedly submit the same request through this keep-alived connection.  
At exactly the 283rd iteration, TS hangs.  Note that if the client opens a new 
connection every time, TS works fine.

There is a second test case, where the header size is exactly 283 bytes, and TS 
hangs at exactly the 275th iteration.  (Does 275 x 283 mean something?)

These magic numbers seem to suggest a memory buffer size (or allocation) 
problem.  I speculate that headers from repeated requests are placed in a 
buffer (or a circular buffer?), and when the total hits a particular size, some 
boundary conditions must have be violated and resulted in memory corruption.

In real life traffic, each request typically has slightly different header 
size, so it is really hard to hit this bug.  I suspect there is a +/- 1 
calculation error in some buffer.

BTW, turning on/off caching does not make any difference.  

--
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-1096) readline support for traffic_shell

[James Peach (Created) (JIRA)]

readline support for traffic_shell
--

 Key: TS-1096
 URL: https://issues.apache.org/jira/browse/TS-1096
 Project: Traffic Server
  Issue Type: Improvement
  Components: Management
Reporter: James Peach
Priority: Minor
 Fix For: 3.1.2


traffic_shell should use readline to support line editing and command history.

--
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-1097) online help for traffic_shell

[James Peach (Created) (JIRA)]

online help for traffic_shell
-

 Key: TS-1097
 URL: https://issues.apache.org/jira/browse/TS-1097
 Project: Traffic Server
  Issue Type: Improvement
  Components: Management
Reporter: James Peach
Priority: Minor
 Fix For: 3.1.2


traffic_shell should have online help for its commands

--
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-1092) Remove server mode SSL termination.

[Alan M. Carroll (Created) (JIRA)]

Remove server mode SSL termination.
---

 Key: TS-1092
 URL: https://issues.apache.org/jira/browse/TS-1092
 Project: Traffic Server
  Issue Type: Improvement
  Components: SSL
Affects Versions: 3.1.1
Reporter: Alan M. Carroll
Assignee: Leif Hedstrom
Priority: Minor
 Fix For: 3.1.4


Checks are done in the SSL configuration to check for server mode 
termination. As far as I can tell it is never actually used anywhere, nor is it 
documented.

--
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-1087) TSHttpTxnOutgoingAddrSet forward declaration does not match implementation

[B Wyatt (Created) (JIRA)]

TSHttpTxnOutgoingAddrSet forward declaration does not match implementation
--

 Key: TS-1087
 URL: https://issues.apache.org/jira/browse/TS-1087
 Project: Traffic Server
  Issue Type: Bug
  Components: TS API
Affects Versions: 3.1.0
Reporter: B Wyatt
Priority: Trivial


ts.h.in lists the following declaration:
{code}TSReturnCode TSHttpTxnOutgoingAddrSet(TSHttpTxn txnp, struct sockaddr 
const* addr);{code}

However, the current implementation has this function sig:
{code}tsapi TSReturnCode TSHttpTxnOutgoingAddrSet(TSHttpTxn txnp, struct 
sockaddr const* addr, socklen_t addrlen);{code}

Trafficserver is unable to load plugins which use this function due to the 
unresolved symbol.

--
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-1089) Allow Plugins to create transparent internal http connections

[B Wyatt (Created) (JIRA)]

Allow Plugins to create transparent internal http connections
-

 Key: TS-1089
 URL: https://issues.apache.org/jira/browse/TS-1089
 Project: Traffic Server
  Issue Type: New Feature
  Components: TS API
Affects Versions: 3.1.0
 Environment: This feature was built on top of a 3.1.0 release 
candidate.  Unfortunately, it will superficially conflict with the IPv6 changes 
(I'm including it in case someone needs to update it before I do)

Reporter: B Wyatt
 Attachments: trans-pluginvc.patch

Plugins can create a fake connection HTTP connection into the proxy and provide 
a logging address.  This feature allows those connections to appear to the rest 
of trafficsever as incoming transparent connections (such as the ones accepted 
by tproxy enabled installations).

--
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