Hi Birthe, I’m not sure if this is the best way, but it’s what first comes to mind.
You could override WOApplication’s takeValuesFromRequest or invokeAction (or both, using the former if available and the latter otherwise) and save the current time in the WOContext’s userInfo before calling super. Then in WOApplication’s appendToResponse, after calling super, you could log the URL, the elapsed time, and any other useful info you might have access to (from WOContext you can get to session, for instance). You could also if desired put a threshold on min duration to be logged, to avoid logging every request. Just a though. We have something similar keeping track of long response times using WOSession’s awake and sleep, so that’s another avenue for session-based requests. Hope this helps! Regards, Mark On Aug 7, 2017, at 7:58 AM, Birthe Berland <b...@complimenta.com<mailto:b...@complimenta.com>> wrote: Hi, From time to time we experience requests that take too long time. From the Apache log we can see the url causing the problem. Is there a way to find out which component/action it corresponds to? We have trouble locating the action from the dot notification. Med venlig hilsen Birthe Berland Complimenta Tel.: 8830 7600 <logo.png> _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com<mailto:Webobjects-dev@lists.apple.com>) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/mark.morris%40experian.com This email sent to mark.mor...@experian.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
