- Re: Regarding restricting number of ins tant for MDB - 2004-07-22 - By Kamaraj, Pushparaj
Back
Igor,
What type of MDB you used?. Is it Bean managed / Container managed?.
> -- --Original Message-- --
> From: Igor Cunko [SMTP:icunko@(protected)]
> Sent: Monday, July 19, 2004 5:17 PM
> To: J2EEPATTERNS-INTEREST@(protected)
> Subject: [SPAM] - Re: [SPAM] - Re: Regarding restricting number of
> instant for MDB - Found word(s) list error in the Text body. - Found
> word(s) list error in the subject
>
> > -- --Original Message-- --
> > From: An interest list for Sun Java Center J2EE Pattern Catalog
> > [mailto:J2EEPATTERNS-INTEREST@(protected)] On Behalf Of Stefan Frank
> > Sent: Monday, July 19, 2004 5:12 AM
> > To: J2EEPATTERNS-INTEREST@(protected)
> > Subject: Re: [SPAM] - Re: Regarding restricting number of instant for
> MDB
> > - Found word(s) list error in the Text body.
> >
> > I'd really like to hear, wether somebody is currently using MDB for this
> > kind of "task-farming": We tried this in a similar project and ended up
> > with all sorts of dead-lock-problems: Make sure, that you *really*
>
> In application we have there is a lot of processes which can take hours in
> some case (building complex tree, huge resulting data sets), except
> profile
> updates all other interactions in system are done via MDB-s. In order to
> throttle number of concurrent jobs (some external systems can't handle
> load)
> we are limiting number of MDBs available at given stage. All together we
> have around 25 MDBs corresponding to different system/process
> combinations,
> also interesting benefits are you can prioritize processing so we are able
> to bump process up/down in processing chain if needed and because of
> persistence in queue our application can start exactly at correct point
> after restart (if needed) , customer loves this restart ability. This
> application is in production for almost 2 years pumping around 25000
> records
> per sec. Granted you better know how transactions are related otherwise
> you
> are in for surprise.
>
> Igor
>
> ====================================================================
> Companion Site: http://www.corej2eepatterns.com
> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
> List Archive:
> http://archives.java.sun.com/archives/j2eepatterns-interest.html
> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
> listserv@(protected)
>
__ ____ ____ ____ ____ ____ ____ ____ ______
Confidential: This electronic message and all contents contain information
from Syntel, Inc. which may be privileged, confidential or otherwise
protected from disclosure. The information is intended to be for the
addressee only. If you are not the addressee, any disclosure, copy,
distribution or use of the contents of this message is prohibited. If you
have received this electronic message in error, please notify the sender
immediately and destroy the original message and all copies.
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
