Re: ChangeNotification from dneumann
Re: ChangeNotification from dneumann
- Subject: Re: ChangeNotification from dneumann
- From: Guido Neitzer <email@hidden>
- Date: Thu, 26 Jan 2006 17:48:08 +0100
On 26.01.2006, at 17:28 Uhr, Jerry W. Walker wrote:
I'm fairly sure the company used the framework on other systems
that were more heavily used, but can't answer that question directly.
It may be, that something special in our configuration has forced the
problems - we often do a lot of EO updates in automated processes
(adding large chunks of EOs to a relationship and so on). The
deadlocks always happened, when automated tasks (mostly one special
method) processed large amount of data as fast as the box was able to
do. I was not able to re-produce the problems on my dev machine, but
we had about one or two deadlocks a day on our production system when
we had heavy traffic.
We disabled ERChangeNotificationJMS and from this day on we haven't
seen ANY deadlock at all. And the traffic on the site has tripled
since than. I also looked at other aspects of the code and I'm fairly
sure that our code is clean - at least in the methods that were
mostly involved in the deadlocks.
I don't want to blame ERChangeNotficiation, it does a terrific job -
as long as the applications stay responsive. I don't know whether
special situations in our applications may have caused interactions
with the change notifications and the EO traffic it generates. To
many "perhaps" and "maybe" for me for a production application.
I thought of not broadcasting the snapshot, instead sending around
only the global ids of the changed objects and simply invalidate them
so that they get fetched from database again, but I had no time for
testing this. Some day I will try it.
cug
--
PharmaLine, Essen, GERMANY
Software and Database Development
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden