[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3641) Built-in async mechanism always returns null for Future.get()

Pete Muir (JIRA) jira-events at lists.jboss.org
Mon Nov 3 17:52:31 EST 2008

     [ https://jira.jboss.org/jira/browse/JBSEAM-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir updated JBSEAM-3641:

    Fix Version/s: 2.1.2.CR1
         Assignee:     (was: Pete Muir)

Yes, there is a fundamental mismatch of ideas here.

1) java.util.concurrent expects you to return a real value from your async method which can be got from Future.get()
2) Runnable can't return a result, whilst callable can.

> Built-in async mechanism always returns null for Future.get()
> -------------------------------------------------------------
>                 Key: JBSEAM-3641
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3641
>             Project: Seam
>          Issue Type: Bug
>          Components: Async
>    Affects Versions: 2.0.2.SP1, 2.1.0.GA
>         Environment: Linux, JBoss 4.2.2 GA
>            Reporter: Gabriel Goïc
>             Fix For: 2.1.2.CR1
> When trying to use the built-in async mechanism, I'm unable to obtain the result of the asynchronous task using Future.get(). This always returns null.
> TimerServiceDispatcher seems to be installed , the asynchronous task runs perfectly. No error or misconfiguration has been seen even running in DEBUG or TRACE logging mode.
> Code, observations and bug are detailed here:
> http://www.seamframework.org/Community/AsynchronousFuturegetNull

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list