this is one of those things that doesn't make a whole lot of sense to reproduce as most J2EE servers provide this functionality for you to stop long running requests from consuming resources.
The J2EE engine is in a much better position to actually do something about it, nuking the thread in question and cleaning up resources. So it sounds like your in Tomcat if you are referring to mod_jk -- look at the tomcat settings/configuration. Jetty has it in its jetty.xml file. Richard Taylor wrote: > I see that setting the request timeout on a per request basis is not > supported in OpenBD, at least via the cfsettings / requesttimeout > attribute [1]. Two questions: > > 1. Is there any other way to set the timeout for a particular request > in OpenBD? I'm not seeing it and I'm wondering if I'm missing > something. > > 2. Is there a way to set this value (a global request timeout) for all > requests coming in? I see the sessiontimeout in bluedragon.xml but I > don't think that's what we're after. At this point the only way I've > found to timeout requests is by setting the socket_timeout on our > mod_jk setup (or other settings way out "there"). Seems like there > would be a way to set this in OpenBD? --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
