Thanks for the tips chaps. I've popped everything into an executor pool now and the notifications now behave how as i want them to. But now i've run back into an issue (bug?) with ERXFetchSpecificationBatchIterator which throws a wobbly when running in a thread :-(
http://lists.apple.com/archives/webobjects-dev/2009/Mar/msg00029.html Simon 2009/3/10 Mike Schrag <[email protected]> >> >> Is that normal behavior ? The java docs don't talk about the sequence of >> events, but I presumed that the notifier would just makes it's notification >> then get on with whatever it has to do next and not care about what the >> listeners are doing, or how long it takes them to do it. > > this is normal ... receipt of notifications happens in-thread with the event > dispatch, which is actually required in some cases, since WO/EOF use > notifications in several cases for synchronous events (when a new eoadaptor > channel is needed, for instance). > >> Do i just need to stick the listeners job into a thread to get it to run in >> the background ? > > I would personally recommend using a Java 1.5 ExecutorPool rather than doing > anything with your own threads (you don't want to kill your app because > you're spawning tons of threads by accident). > > ms > > _______________________________________________ > 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/simon%40potwells.co.uk > > This email sent to [email protected] _______________________________________________ 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]
