netbeans.org has a http monitor module that can record and playback of http requests, plugged into netbeans' web development framework. I think you could just download just that module and manually install it into your tomcat, and use the UI from netbeans to do the record/playback. It actually can be installed into any newer application server that is up to date in its servlet support.
go to http://monitor.netbeans.org for more details --George On 7/15/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > That's a really interesting question... I don't know of anything that > exists, although I'm quite certain something does. :) > > I can however think it through, and its probably not a huge chore to build... > > As you mentioned, a filter would probably do the trick nicely... if we > assume your app only deals in POSTs and GETs of basic user input (because > things like multiparts and such would complicate matters a bit), then it's > really just a simple filter that iterates over all parameters and stores > them. Just a simple CSV file of name=value pairs would suffice, with each > line being a request. > > Then it should be a simple matter to write a Java app using the standard > JDK classes to run through that CSV file and make the requests with the > parameters you recorded. > > -- > Frank W. Zammetti > Founder and Chief Software Architect > Omnytex Technologies > http://www.omnytex.com > > On Fri, July 15, 2005 1:28 pm, Will Hartung said: > > With Apache JMeter, they have a proxy that you can use to record a session > > with the server, and you can then use that as a basis for load testing and > > what not. > > > > What I'm looking for is something similar, but something that I can > > ideally > > place in Tomcat (as a Valve perhaps, or a Servlet filter). Basically, > > something that records the entire incoming request and then stores it out > > in > > a format that can later be played back by another tool. > > > > The problem is that we have a server than has a production memory leak, > > and > > the profilers are basically worthless in production. > > > > But if I can place a logger and record a days traffic, and then replay it > > against a test server (with all the monitoring etc.), then I can more > > easily > > reproduce the problem without heavily impacting performance of the > > production server. > > > > Anyone have any ideas? > > > > Regards, > > > > Will Hartung > > ([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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
