Re: Configuring ERChangeNotification/JMS Help needed
Re: Configuring ERChangeNotification/JMS Help needed
- Subject: Re: Configuring ERChangeNotification/JMS Help needed
- From: Guido Neitzer <email@hidden>
- Date: Sun, 30 Oct 2005 10:07:43 +0100
Hi.
I have used ERChangeNotificationJMS and it worked VERY well if not
too much traffic (1) was going on. I had experienced deadlocks in
several places of my app where I was pretty sure to do everything right.
Since I disabled the framework not one deadlock has showed up
anymore. As I have changed nothing else and the traffic has went up
by a fair amount, I'm sure the deadlocks where related to the change
notifications (the framework).
So, what other tips do you have?
I simply re-read "mission-critical" values from the DB when they are
needed to be up-to-date and let the DB do the caching. I know that
database turnarounds are expensive, but it worked very well (and fast
enough) for me.
Currently I can't recommend using ERChangeNotificationJMS, but
perhaps I have made something wrong which comes only to the daylight
when the framework is active. So you or others may get other results.
I had about one deadlock every three days in the admin app, I have de-
actived the framework and since then never had a deadlock anymore
(okay, one crash in the FrontBase JDBC driver, that took down ALL
applications on this machine).
cug
(1) "too much" were about 30 users heavily updating values in the
"admin application" while about 100 visitor sessions were active. The
problem came up mostly in methods where one change of a value
required iterating over a lot of EOs and changing them --> heavy
notification traffic during a very short time. Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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