You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Romain Manni-Bucau (JIRA)" <ji...@apache.org> on 2013/05/17 11:53:16 UTC

[jira] [Closed] (OPENEJB-2017) @Asynchronous methods execute sequentially, although being invoked asynchronously

     [ https://issues.apache.org/jira/browse/OPENEJB-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Romain Manni-Bucau closed OPENEJB-2017.
---------------------------------------

    Resolution: Not A Problem
      Assignee: Romain Manni-Bucau
    
> @Asynchronous methods execute sequentially, although being invoked asynchronously
> ---------------------------------------------------------------------------------
>
>                 Key: OPENEJB-2017
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-2017
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: ejb31
>    Affects Versions: 4.6.0
>            Reporter: Reinis Vicups
>            Assignee: Romain Manni-Bucau
>         Attachments: infiniteloop.zip, synchronousasync.zip
>
>
> A BaringController that is @Singleton, @Startup is invoked periodically through @Schedule method.
> In the @Schedule method of BaringController an @Asynchronous method of a @Stateful BaringWorker is being invoked.
> What I observe (see attached replication project) in log output (solely console output) is that although @Schedule method of BaringController is invoked DURING execution of @Asynchronous method of worker, the consecutive invocations of @Asynchronous method are sequencial!
> In other words - @Schedule method of BaringController is invoked during execution of @Asynchronous but the consecutive invocations of @Asynchronous "wait" until previous invocation is complete.
> Thus effectively I have only one running @Asynchronous thread at any given time.
> As I understood from comments in irc this should not be the case.
> Thanks and best regards
> Reinis

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira