[concurrency-interest] Backport concurrency util in EJB

Dhanji R. Prasanna dhanji at gmail.com
Wed Dec 13 03:11:56 EST 2006

If you have access to a JEE 1.4+ container you can use the timer EJB to
schedule multiple concurrent jobs from the original request (set firstDate
to sysdate to start immediately). These will run asynchronously and safely
within the EJB container.


On 12/13/06, OKeeffe, Michael K <MOKEEFFE at amfam.com> wrote:
> >-----Original Message-----
> >>
> >> if the codes only depending on database access, how safe is
> >it to use
> >> backport concurrent util? (as the EJB spec clearly disencourage
> >> spawning thread).
> >>
> >The problem is that an EJB container maintains informations associated
> >with threads
> >in order to manage transactions, security etc.
> >
> >more here, http://blog.w1c.ca/?p=92
> >and google: batch processing J2EE
> >>
> According to this blog, until the spec catches up (and it seems it
> hasn't), the only acceptable way to do this is with vendor APIs, for
> example:
> http://www.devwebsphere.com/devwebsphere/2003/11/async_beans_int.html
> _______________________________________________
> Concurrency-interest mailing list
> Concurrency-interest at altair.cs.oswego.edu
> http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/attachments/20061213/fb6323a9/attachment.html 

More information about the Concurrency-interest mailing list