DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35160>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35160





------- Additional Comments From [EMAIL PROTECTED]  2006-12-18 08:12 -------
Created an attachment (id=19280)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=19280&action=view)
Rewrite log from a scenario that dumps core

Here is the rewrite log.

The is scenario is the following:

First I launch Apache Bench with a concurrency level of 1 from client
10.1.66.16.

/u01/opt/apache2/bin/ab -C ADPEHCRELEASE=000001 -H "Connection: close" -c 1 -n
50000 http://labelle16.gsi.fr:8080/index.html

So far everything seems to go well. No cores, no messages about "uri already
rewritten". Then I launch the loop containg the curl invocations from client
10.1.32.163.

while [ 1 ] ; do curl -H "Pragma:" --header "Cookie: ADPEHCRELEASE=000001"
--dump-header /tmp/hdr2  http://labelle16:8080/index.html ; done

That is when the "uri already rewritten" start appearing and there are numerous
core cumps. Contrary to what I thought there are a lot more core cumps than
"uri already rewritten" messages.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to