Author: Wolf-Dieter Fink
Level: Advanced
Technologies: Asynchronous EJB
Summary: The ejb-asynchronous
quickstart demonstrates the behavior of asynchronous EJB invocations by a deployed EJB and a remote client and how to handle errors.
Target Product: WildFly
Source: https://github.com/wildfly/quickstart/
The ejb-asynchronous
quickstart demonstrates the behavior of asynchronous EJB invocations in WildFly Application Server. The methods are invoked by both an EJB in the deployment and by a remote client. The quickstart also shows error handling if the asynchronous method invocation fails.
The example is composed of 2 Maven modules, each with a shared parent. The modules are as follows:
ejb
: This module contains the EJB's and will be deployed to the serverclient
: This module contains a remote EJB clientThe root pom.xml
builds each of the submodules in the above order and deploys the archive to the server.
The application this project produces is designed to be run on WildFly Application Server 11 or later.
All you need to build this project is Java 8.0 (Java SDK 1.8) or later and Maven 3.3.1 or later. See Configure Maven for WildFly 11 to make sure you are configured correctly for testing the quickstarts.
In the following instructions, replace WILDFLY_HOME
with the actual path to your WildFly installation. The installation path is described in detail here: Use of WILDFLY_HOME and JBOSS_HOME Variables.
For Linux: WILDFLY_HOME/bin/standalone.sh
For Windows: WILDFLY_HOME\bin\standalone.bat
mvn clean install wildfly:deploy
ejb/target/ejb-asynchronous-ejb.jar
to the running instance of the server.Check whether the application is deployed successfully.
cd client
mvn exec:exec
Note: This quickstart requires quickstart-parent
artifact to be installed in your local Maven repository. To install it, navigate to quickstarts project root directory and run the following command:
mvn clean install
Check the client output
INFO: The server log should contain a message at (about) <date>, indicating that the call to the asynchronous bean completed.
INFO: Got the async result as expected => returning at <date>, duration was 200ms
INFO: Got the async result as expected after wait => returning at <date>, duration was 1500ms
INFO: Catch the expected Exception of the asynchronous execution!
INFO: Results of the parallel (server) processing : [returning at <date> duration was 5000ms, returning at <date>, duration was 3000ms]
Check the server log.
There should be two INFO log messages for the fireAndForget
invocation:
'fireAndForget' Will wait for 15000ms
and 15sec later (the client should be finished at this time)
action 'fireAndForget' finished
mvn wildfly:undeploy
You can also start the server and deploy the quickstarts or run the Arquillian tests from Eclipse using JBoss tools. For general information about how to import a quickstart, add a WildFly server, and build and deploy a quickstart, see Use JBoss Developer Studio or Eclipse to Run the Quickstarts.
This quickstart consists of multiple projects, so it deploys and runs differently in JBoss Developer Studio than the other quickstarts.
ejb-asynchronous-ejb
project and choose Run As
--> Maven Install
.ejb-asynchronous-ejb
project and choose Run As
--> Run on Server
.ejb-asynchronous-client
project and choose Run As
--> Java Application
.Select Java Application
window, choose AsynchronousClient - org.jboss.as.quickstarts.ejb.asynchronous.client
and click OK
.Console
window.ejb-asynchronous-ejb
project and choose Run As
--> Maven build
. Enter wildfly:undeploy
for the Goals
and click Run
.If you want to debug the source code of any library in the project, run the following command to pull the source into your local repository. The IDE should then detect it.
mvn dependency:sources