[baseten-users] Unstable Behaviour with Notifications and fast DB Updates/Fetches

[Michael Ruepp]

Hi Tuuka,

I have functionality in my App which depends heavily on kBXUpdate,  
Insert and Delete notifications from the context which trigger a small  
amount of database updates, but the Software behaves quite unstable  
since the latest Framework Updates (or maybe the implementation of the  
notification functionality)

(Eg. NSNotification receives in a short amount of time kBXInsert, then  
triggers a setPrimitiveValue ForKey into the same context, then  
Receives another kBXUpdate, then triggers change of a class variable  
and inbetween (in a very short amount of time), another function  
receives an nsarray from the BXSyncarraycontroller with a Fetch  
Predicate with the "hopefully" updated values from the nsnotification  
function.

In this case, there is also a GUI only client App involved which  
triggers the notification by inserting or updating rows in the database.

I have the context switched to autocommit yes, and the AutoFetch of  
the BXSyncarraycontroller also to yes.

I use the 1399 Automatic Build.



I get lots of mach_msg_trap errors as well as SIGABRT Errors when  
using the NSNotifications with the BXSyncArray Controllers but mostly  
I get  frequent crashes  with "poll" and Postgres Calls involved.

(Due to Maillist limits I´will provide you with the screenshot if you  
send me a direct email address).

Funny is, that when I compile it with i386 or with x86_64, the errors  
change and with i386 it seems to be overall more stable but not as  
much as expected.

Maybe it can be that some framework operations are not finished while  
the software starts another one, I am not sure.

How can I ensure that the context and the notification are in a proper  
state before I continue with some operations?







Cheers,

Mike


_________________
michael ruepp
michael at ruepp.at
fon +41 76 593 04 49
skype michaelruepp

CONFIDENTIALITY NOTICE
This message (including any attachments transmitted with it) contains  
confidential information and is intended only for the individual named  
herein. If you are not the herein named addressee you should not  
disseminate, distribute, copy or otherwise make use of this message.  
Please notify the sender immediately by e-mail if you have received  
this message by mistake, and delete it from your systems.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basetenframework.org/pipermail/baseten-users/attachments/20091013/7af409b5/attachment.htm>