Charlie Alfred <[EMAIL PROTECTED]>:
> If you want to add the requirement of supporting an app server cluster,
> and the statistics being collected are not per-server stats, then it
> seems appropriate to keep the stats in an EntityBean and store them
> in a DBMS for transaction protection.
I was the original poster for this thread. Yes, the application will run on
a couple (5-6) Sun servers, but entity beans is not an option, I'm afraid.
there will be upwards of hundred or even more small transactions against the
singleton per second. The current, old, non-EJB system stores such
information directly in the database, and that's the bottleneck. A solution
that involves persistence would also persist the information between server
restarts, while it shouldn't. The old solution has a startup job that resets
particular fields for all the rows in the 30+ GB-size database.
/Robert
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
