On Jul 13, 2011, at 5:31 PM, Chuck Hill wrote: > > On 2011-07-13, at 5:21 PM, Kevin wrote: > >> I have an app that tends to lock up when a particular page is loaded. This >> page fetches and accesses over 1500 records from a FrontBase DB. > > As long as it is not a lot over 1,500 that should not cause a delay as > significant at this. Turn on SQL logging and check the log. It could be > that it is fetching those rows and then firing off many single row faults. > Or you might have a corrupt index or a unoptimizable query against a large > table / complex joins. > > > >> When the problem happens I typically see a broken socket in the webobjects >> log file, and if I look in the FB manager the state column shows "tb swp" >> where the others show only "swp". > > t means Open Transaction > b means Busy > > So FrontBase is evaluating a query to return the result. That suggests a > corrupt index or a unoptimizable query. > > >> Also CPU usage is quite high when in this state. > > App or database usage? > > >> It will stay this way until I kill it, or the app dies. If I kill that >> transaction and try again, most of the time it will work fine. Sometimes I >> have to restart the app. >> >> Any ideas how I can track this problem down. And does anyone know what the >> letters indicate in the state field. I think there is a clue there, but I >> can't find those letters in the docs so I don't know what they indicate. > > > Check the SQL issued from the app first. Then try the same SQL directly in > FB.
Thanks Chuck. I will try your suggestions and see where that leads. - Kevin _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
