Hello Again, I was wondering if someone could give me some help with this. I think using a connector is probably the way to go to solve this problem; however, I'm not sure where to start. How do I create my own connector and the plumb it into Tomcat so it will be used. I will be using a separate port other than 8080 for the devices that will be sending and receiveing data so, if possible, I would like to leave the default connector on port 8080.
Again, I don't want to reimplement the code that parses the HTTP. All I need to do is count the number of bytes arriving and being sent so if I can reuse code from an existing connector, that would be great. Thanks, Dave. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Costin Manolache Sent: October 22, 2007 04:50 PM To: Dave Rathnow Cc: Tomcat Developers List Subject: Re: Measuring bytes sent and received from and to Tomcat Well, if you want absolute byte - connector seems the only place, there are space and tabs beeing skipped when parsing headers, etc. If you are ok with an estimate - the AccessLogValve is ok, add all the header lengths + method + http/1.1. You'll miss bytes for encodings, spaces. Re. where to add - each connector is different on how it reads/parse the message, you probably want to do it close to the 'read()' call, save it somewhere associated with the request ( a note or attribute ) and read it in a valve or filter. Costin On 10/22/07, Dave Rathnow <[EMAIL PROTECTED]> wrote: > > > I looked at connectors but wasn't sure if this was what I wanted. To > avoid anther wild goose chase I decided to ask. Can you point me in > the direction of some documentation where I might be able to get started? > > Dave. > > -----Original Message----- > From: Costin Manolache [mailto:[EMAIL PROTECTED] > Sent: October 22, 2007 04:28 PM > To: Tomcat Developers List > Subject: Re: Measuring bytes sent and received from and to Tomcat > > 'bytes' should be counted at a lower level, in connector. I'm not sure > this is something generic enough - but you can make some changes to > your tomcat, where read() is done from socket. > > I guess it would be nice to have a JMX graph with bytes/sec in/out. > > Costin > 'bytes' > > On 10/22/07, Dave Rathnow <[EMAIL PROTECTED]> wrote: > > > > > > We looked at using a valve but we weren't sure if it would work. > > Correct me if I'm wrong, but it appears as though valves are chained > > together in a calling sequence and that some valves could change the > > content of the request or response. This means we may not get an > > accurate measure of the number of total number bytes that make up > > the request. > > > > Also, the AccessLogValve has a pattern code to get the number of > > bytes > > > sent, excluding the HTTP headers, but does not have a pattern code > > to get the number of bytes sent, including the HTTP headers, which > > is what we really need. > > > > Have I missed something? > > > > Dave. > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > > Of Yoav Shapira > > Sent: October 22, 2007 02:36 PM > > To: Tomcat Developers List > > Subject: Re: Measuring bytes sent and received from and to Tomcat > > > > Hey, > > > > On 10/22/07, Dave Rathnow <[EMAIL PROTECTED]> wrote: > > > Is there a way we can do the same thing with Tomcat? It's simple > > > for us to measure the number of byte in the payload of the HTTP > > > request/response, however that isn't enough. We need to know the > > > total number of bytes being sent and received for each HTTP request. > > > > > > Can someone suggest a way I could get an accurate count of these > > bytes? > > > > You can probably start with the AccessLogValve that ships with Tomcat: > > http://tomcat.apache.org/tomcat-6.0-doc/config/valve.html > > > > Out of the box it will get you the complete bytes in the response. > > See the above docs on how to configure that. If you want to log the > > complete bytes on the request, I think you'll have to extend the > > Valve, but it should be pretty easy to do. > > > > Yoav > > > > -------------------------------------------------------------------- > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For > > additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -------------------------------------------------------------------- > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For > > additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
