[jira] [Created] (TS-1152) http_ui error,when i get http://localhost/cache/

2012-03-19 Thread 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

2012-03-19 Thread 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] [Assigned] (TS-1148) support systemd init system

2012-03-19 Thread Assigned 

 [ 
https://issues.apache.org/jira/browse/TS-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Igor Galić reassigned TS-1148:
--

Assignee: Igor Galić

 support systemd init system
 ---

 Key: TS-1148
 URL: https://issues.apache.org/jira/browse/TS-1148
 Project: Traffic Server
  Issue Type: Improvement
  Components: Packaging
Reporter: Jan-Frode Myklebust
Assignee: Igor Galić
 Fix For: 3.0.3

 Attachments: 0001-TS-1148-Support-systemd-activation-of-ATS.patch, 
 0002-TS-1148-Support-systemd-activation-of-ATS.patch


 ATS should support systemd init system for managing the trafficserver 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] [Commented] (TS-1153) On Solaris, link with libumem by default

2012-03-19 Thread Leif Hedstrom (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/TS-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13232608#comment-13232608
 ] 

Leif Hedstrom commented on TS-1153:
---

Probably won't make any difference at all on most setups. :) However, it could 
make it easier for plugins to improve performance, so I'd suggest you do what 
we do with tcmalloc / jemalloc; Add another option to configure.ac, e.g. 
--with-libumem.


 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ć
  Labels: memory

 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] [Commented] (TS-1153) On Solaris, link with libumem by default

2012-03-19 Thread Commented 

[ 
https://issues.apache.org/jira/browse/TS-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13232618#comment-13232618
 ] 

Igor Galić commented on TS-1153:


The question is just really: Should we have it be the default on Solaris?

Also: Once I have a few days time to port ATS to Sparc it *will* make a 
difference.
..you know, with 128 CPUs/Cores/Threads and all...

I'm pretty sure that ATS would deliver some kick-ass performance on those 
machines.

 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ć
  Labels: memory

 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

2012-03-19 Thread 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] [Commented] (TS-1154) quick_filter on HEAD does not work

2012-03-19 Thread Leif Hedstrom (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/TS-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13232716#comment-13232716
 ] 

Leif Hedstrom commented on TS-1154:
---

We should make sure TS-1140 also gets this fix, if it's broken there.

 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] [Commented] (TS-1154) quick_filter on HEAD does not work

2012-03-19 Thread Leif Hedstrom (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/TS-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13232714#comment-13232714
 ] 

Leif Hedstrom commented on TS-1154:
---

Not sure what happened here, but with TS-1140, quick filter will die (finally). 
Unless this is also broken on 3.0.x, I'd suggest we won't bother fixing this.

 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

2012-03-19 Thread 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

2012-03-19 Thread 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] [Commented] (TS-1156) Multiple time tags in a log format gets bad results

2012-03-19 Thread Leif Hedstrom (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/TS-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13232988#comment-13232988
 ] 

Leif Hedstrom commented on TS-1156:
---

It might actually be the cqts marshalling that's broken, even logging just cqts 
shows bad reqults (compared to e.g. cqtq)

 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] [Commented] (TS-1114) Crash report: HttpTransactCache::SelectFromAlternates

2012-03-19 Thread John Plevyak (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/TS-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13233161#comment-13233161
 ] 

John Plevyak commented on TS-1114:
--

This patch has been committed to 3.0.x and master branches.  Please verify and 
mark this fixed if your testing confirms that the problem is gone.

 Crash report: HttpTransactCache::SelectFromAlternates
 -

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

 Attachments: cache_crash.diff


 it may or may not be the upstream issue, let us open it for tracking.
 {code}
 #0  0x0053075e in HttpTransactCache::SelectFromAlternates 
 (cache_vector=0x2aaab80ff500, client_request=0x2aaab80ff4c0, 
 http_config_params=0x2aaab547b800) at ../../proxy/hdrs/HTTP.h:1375
 1375((int32_t *)  val)[0] = m_alt-m_object_key[0];
 {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] [Commented] (TS-1152) http_ui error,when i get http://localhost/cache/

2012-03-19 Thread James Peach (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/TS-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13233190#comment-13233190
 ] 

James Peach commented on TS-1152:
-

I'm not sure if http_ui is still supported or known to be working. Maybe ask on 
the users@ mailing list if other people are successfully using http_ui.

 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] [Commented] (TS-1114) Crash report: HttpTransactCache::SelectFromAlternates

2012-03-19 Thread John Plevyak (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/TS-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13233191#comment-13233191
 ] 

John Plevyak commented on TS-1114:
--

 Not in 3.0.x yet.  Need to get agreement on a backport.

 Crash report: HttpTransactCache::SelectFromAlternates
 -

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

 Attachments: cache_crash.diff


 it may or may not be the upstream issue, let us open it for tracking.
 {code}
 #0  0x0053075e in HttpTransactCache::SelectFromAlternates 
 (cache_vector=0x2aaab80ff500, client_request=0x2aaab80ff4c0, 
 http_config_params=0x2aaab547b800) at ../../proxy/hdrs/HTTP.h:1375
 1375((int32_t *)  val)[0] = m_alt-m_object_key[0];
 {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] [Assigned] (TS-1135) support wildcard certificates for ServerNameIndication (SNI)

2012-03-19 Thread James Peach (Assigned) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TS-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

James Peach reassigned TS-1135:
---

Assignee: James Peach

 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
Assignee: 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] [Commented] (TS-1135) support wildcard certificates for ServerNameIndication (SNI)

2012-03-19 Thread James Peach (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/TS-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13233194#comment-13233194
 ] 

James Peach commented on TS-1135:
-

RFC 6125 discusses how clients should match wildcard certs.

I'm going to implement matching for the leftmost wildcard only, i.e. *.foo.org, 
*.bar.foo.org. Wildcard names like f*bar.org will not be supported and I'll see 
whether I can reject these when we load them.

 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
Assignee: 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] [Commented] (TS-1152) http_ui error,when i get http://localhost/cache/

2012-03-19 Thread bettydramit (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/TS-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13233200#comment-13233200
 ] 

bettydramit commented on TS-1152:
-

ooo.
thanks

2012/3/20 James Peach (Commented) (JIRA) j...@apache.org



 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