Weld 1.1 in GFv3.1 and asynchronous methods

[ossaert]

Hi,

In GFv3.1 I marked a method being asynchronous:

@Inject
@JobEvent
private Event<String> jobActor;
...

@Asynchronous
@PermitAll
@TransactionAttribute(TransactionAttributeType.REQUIRED)
public void doImport(
....
this.jobManager.fire(uuidJob);
}


On the observer side I have:


public void finishJob(
@JobEvent
@Observes(notifyObserver = Reception.ALWAYS,
during = TransactionPhase.AFTER_SUCCESS)
final String uuid) {
....
}

I also have a method to handle the FAIL event.

Now, this code functioned properly in GFv3.0.1 and with an older Weld. The import job was running async and when the job was finished or failed, the observer was called to set a flag.

In GFv3.1 with Weld 1.1 I get the following error message:

WELD-000401 Failure while notifying an observer of event ....

Anyway, the problem is the @Asynchronous annotation. When I remove this annotation, then the code functions, but of course, block the import-thread. On the other hand, when I keep the @Asynchronous annotation and remove the "during=AFTER_SUCCES", then the code also function, but with a false outcome of course.

What happened to Weld to have this behaviour? Is this a bug, or is this wanted? Does this imply that Weld does NOT work with Asynchronous methods anymore?

Greetings,
Jan

[ossaert]

Anyone? This bug does really impact my project since I cannot fire an asynchronous method anymore, or at least, react on the AFTER_SUCCESS event.

Greetings
Jan

[alesj]

WELD-000401 Failure while notifying an observer of event ....

What's the cause of this?

[ossaert]

It is caused by the @Asynchronous annotation. When removing this annotation, it works, but of course, the method is not async anymore. I currently rolled back to an older version of Weld where it functioned since my project is relying on the asynchronous method which fires an event. Should this issue be filed as a bug?

Greetings
Jan

[alesj]

It is caused by the @Asynchronous annotation. When removing this annotation, it works, but of course, the method is not async anymore.

I mean, is there some stacktrace. Or why exactly does this addition break it, or why it works when it's not there.

[ossaert]

There is no exception thrown at all. It is just the error-line.

Greetings
Jan

[alesj]

Try and see what that e is in DeferredEventNotification class

      catch (Exception e)
      {
         log.error(ASYNC_OBSERVER_FAILURE, event);
         xLog.throwing(Level.DEBUG, e); // <--- HERE
      }

[ossaert]

I made a small sample project. You can easily see that it functions when the asynchronous annotation is removed.

You can download it here: http://www.4eachother.de/AsyncWebApp.zip

Greetings
Jan

[alesj]

Does it work for you in JBoss6?

[ossaert]

I do not have the JBoss environment here to test. Could you deploy the project on an instance?

J.

[alesj]

I do not have the JBoss environment here to test.

• http://sourceforge.net/projects/jboss/files/JBoss/JBoss-6.0.0.Final/

[ossaert]

I do not have the time to install JBoss now. I was hoping one of you could deploy this small WAR file and see what happens.

Greetings
Jan

[alesj]

I do not have the time to install JBoss now.

Install JBoss --> download + unzip + run "JBOSS_HOME/bin/./run.sh"

Test your app --> drop it to JBOSS_HOME/server/default/deploy/

[nagelfarweld]

I have a similar issue (as posted in its own thread) because I need to use @Observes(during=TransactionPhase.AFTER_COMPLETION which leads to the same error. It worked fine in GFv3.01 and the Weld version that comes with it. So far we haven't found a solutiong for this problem