From: Denis F. <df...@de...> - 2009-10-31 11:32:31
|
On Sat, Oct 31, 2009 at 1:45 AM, Ramsey Lee Gurley <rg...@ma...> wrote: > > On Oct 30, 2009, at 6:28 AM, Denis Frolov wrote: > >> Hi Ramsey, >> >> On Fri, Oct 30, 2009 at 5:19 AM, Ramsey Lee Gurley <rg...@ma...> >> wrote: >>> >>> Hi Ricardo, >>> >>> I had to track one of these down recently at work. It was easy to find >>> in >>> my case. Try adding these to your Properties file >>> >>> log4j.category.er.extensions.ERXEC.LockLogger=DEBUG >> >>> log4j.category.er.extensions.ERXEC.LockLoggerTrace=DEBUG >> >> This one was not used anywhere so I deleted it yesterday. >> >>> log4j.category.er.extensions.ERXEC.LockTrace=DEBUG >>> >>> Once you do that, you can simply get the ERXEC object id on the warn >>> statement and find backwards on your console log to get the stack trace >>> where it was originally locked. If you're able to reproduce this error, >>> you >>> can pinpoint the problem. You might need to turn off you log line limit >>> in >>> Eclipse to see it though. >>> >>> BTW, Denis, I'm using D2W with autolocking. I never see any of these >>> messages using D2W. Am I doing something wrong? (^_^) Is this something >>> that is reproducible? >> >> I'm seeing a bunch of these warns upon each load of an inspect page >> with a couple of embedded list pages. Which results in megabytes of >> useless logs each day. > > > Interesting... I have an embedded list configuration on both my calendar and > edit relationship pages, but they don't seem to exhibit this behavior. Is > there something special about that particular page or does it happen on all > your embedded lists? Are you running 5.4.3? How about your ec properties? I am still on 5.3.x, but will upgrade to 5.4.x soon and will check with this version as well. > I have > > # ERXEC > er.extensions.ERXApplication.useEditingContextUnlocker=true > er.extensions.ERXEC.defaultAutomaticLockUnlock=true > er.extensions.ERXEC.useSharedEditingContext=false > er.extensions.ERXEC.defaultCoalesceAutoLocks=true > er.extensions.ERXEC.useUnlocker=true > er.extensions.ERXEC.safeLocking=true > > I'm not even sure which of those are even necessary any longer, but that's > what I'm using at the moment. I'm using: er.extensions.ERXEC.safeLocking=true This should be enough to enable autolock, coalesce autlocks and unlocker. > > >>> ( To be perfectly honest, I do have one place in my own D2W framework >>> that >>> throws these, but it is because I'm doing something that is probably >>> really >>> stupid with ERJavaMail. With the exception of that one spot, I never >>> ever >>> see them.) >>> >>> Ramsey >>> >>> >>> On Oct 29, 2009, at 2:32 PM, Ricardo J. Parada wrote: >>> >>>> >>>> On Oct 29, 2009, at 2:27 PM, Denis Frolov wrote: >>>> >>>>> One possible reason is that ERXEC's autounlocker is cleaning up the >>>>> locks left by D2W page refresh. More info by Anjo: >>>>> >>>>> http://www.mail-archive.com/web...@li.../msg24413.html >>>>> >>>> >>>> This app does not use D2W. >>>> >>>>> By the way, I've lowered the log level earlier today since this looks >>>>> like a normal job of unlocker and shouldn't have WARN level. So, this >>>>> log entry should go away if you update your copy of Wonder. >>>> >>>> I'll try it. >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA >>>> is the only developer event you need to attend this year. Jumpstart your >>>> developing skills, take BlackBerry mobile applications to market and >>>> stay >>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now! >>>> >>>> >>>> http://p.sf.net/sfu/devconference_______________________________________________ >>>> Wonder-disc mailing list >>>> Won...@li... >>>> https://lists.sourceforge.net/lists/listinfo/wonder-disc >>> >>> > > |