The helloworld-mdb
quickstart uses JMS and EJB Message-Driven Bean (MDB) to create and deploy JMS topic and queue resources in {productName}.
The helloworld-mdb
quickstart demonstrates the use of JMS and EJB Message-Driven Bean in {productNameFull}.
This project creates two JMS resources:
-
A queue named
HELLOWORLDMDBQueue
bound in JNDI asjava:/queue/HELLOWORLDMDBQueue
-
A topic named
HELLOWORLDMDBTopic
bound in JNDI asjava:/topic/HELLOWORLDMDBTopic
../shared-doc/system-requirements.adoc ../shared-doc/use-of-jboss-home-name.adoc ../shared-doc/start-the-standalone-server.adoc ../shared-doc/build-and-deploy-the-quickstart.adoc
Look at the {productName} console or server log and you should see log messages corresponding to the deployment of the message-driven beans and the JMS destinations:
INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "helloworld-mdb.war" (runtime-name: "helloworld-mdb.war")
...
INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/queue/HELLOWORLDMDBQueue
INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/queue/HELLOWORLDMDBQueue
INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/topic/HELLOWORLDMDBTopic
INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-3) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/topic/HELLOWORLDMDBTopic
INFO [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0042: Started message driven bean 'HelloWorldQueueMDB' with 'activemq-ra.rar' resource adapter
INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0042: Started message driven bean 'HelloWorldQTopicMDB' with 'activemq-ra.rar' resource adapter
...
INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 87) WFLYUT0021: Registered web context: '/helloworld-mdb' for server 'default-server'
INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "helloworld-mdb.war" (runtime-name : "helloworld-mdb.war")
The application will be running at the following URL: http://localhost:8080/{artifactId}/ and will send some messages to the queue.
To send messages to the topic, use the following URL: http://localhost:8080/{artifactId}/HelloWorldMDBServletClient?topic
Look at the {productName} console or Server log and you should see log messages like the following:
INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-9 (ActiveMQ-client-global-threads-1189700957)) Received Message from queue: This is message 5
INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-6 (ActiveMQ-client-global-threads-1189700957)) Received Message from queue: This is message 1
INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-7 (ActiveMQ-client-global-threads-1189700957)) Received Message from queue: This is message 4
INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-5 (ActiveMQ-client-global-threads-1189700957)) Received Message from queue: This is message 2
INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-4 (ActiveMQ-client-global-threads-1189700957)) Received Message from queue: This is message 3
../shared-doc/undeploy-the-quickstart.adoc ../shared-doc/run-the-quickstart-in-jboss-developer-studio.adoc
Note
|
Within {JBDSProductName}, make sure you define a server runtime environment that uses the standalone-full.xml configuration file.
|
You can choose to deploy and run this quickstart in a managed domain or on a standalone server. The sections below describe how to configure and start each type of server.
Before you begin:
-
If it is running, stop the {productName} server.
-
If you plan to test using a standalone server, back up the standalone server configuration file:
{jbossHomeName}/standalone/configuration/standalone-full-ha.xml
-
If you plan to test using a managed domain, back up the following files:
{jbossHomeName}/domain/configuration/domain.xml {jbossHomeName}/domain/configuration/host.xml
After you have completed testing this quickstart, you can replace these files to restore the server to its original configuration.
You configure the server by running the install-domain.cli
script provided in the root directory of this quickstart.
-
Review the
install-domain.cli
file in the root of this quickstart directory. This script creates the server group and servers and configures messaging clustering for testing this quickstart. You will note it does the following:-
Stops the servers
-
Creates a server-group to test ActiveMQ Clustering
-
Adds 2 servers to the server-group
-
Configures ActiveMQ clustering in the full-ha profile
-
Deploys the
helloworld-mdb.war
archive -
Restarts the servers.
-
-
Open a terminal, navigate to the root directory of this quickstart, and run the following command to run the script:
$ {jbossHomeName}/bin/jboss-cli.sh --connect --file=install-domain.cli
NoteFor Windows, use the {jbossHomeName}\bin\jboss-cli.bat
script.You should see
"outcome" ⇒ "success"
for all of the commands. -
Restart the server in a managed domainas described above.
If you choose to run standalone servers instead of a managed domain, you will need two instances of the application server.
Application server 2 must be started with a port offset parameter provided to the startup script as -Djboss.socket.binding.port-offset=100
.
Since both application servers must be configured in the same way, you must configure the first server and then clone it.
-
Open a terminal and navigate to the root of the {productName} directory.
-
Start the {productName} server with the standalone full HA profile, which supports messaging and high availability, by typing the following command.
$ {jbossHomeName}/bin/standalone.sh -c standalone-full-ha.xml
NoteFor Windows, use the {jbossHomeName}\bin\standalone.bat
script.
-
Review the
install-standalone.cli
file in the root of this quickstart directory. This script configures clustering for a standalone server. You will note it does the following:-
Enables console logging. By default, the full HA profile does not log to the console, so this script enables it.
-
Enables clustering and sets a cluster password
-
Enables clustering in the RemoteConnectionFactory
-
Deploys the
helloworld-mdb.war
archive -
Reloads the server configuration
-
-
Open a terminal, navigate to the root directory of this quickstart, and run the following command to run the script:
$ {jbossHomeName}_1/bin/jboss-cli.sh --connect --file=install-standalone.cli
NoteFor Windows, use the {jbossHomeName}_1\bin\jboss-cli.bat
script.
You should see "outcome" ⇒ "success"
for all of the commands.
After you have successfully configured the server, you must make a copy of this {productName} directory structure to use for the second server.
-
Stop the server.
-
Make a copy of this {productName} directory structure to use for the second server.
-
Remove the following directories from the cloned instance:
{jbossHomeName}_2/standalone/data/activemq/bindings/ {jbossHomeName}_2/standalone/data/activemq/journal/ {jbossHomeName}_2/standalone/data/activemq/largemessages/
When you start the servers, you must pass the cluster password on the command line to avoid the warning AMQ222186: unable to authorise cluster control
.
$ {jbossHomeName}_1/bin/standalone.sh -c standalone-full-ha.xml
$ {jbossHomeName}_2/bin/standalone.sh -c standalone-full-ha.xml -Djboss.socket.binding.port-offset=100
Note
|
For Windows, use the {jbossHomeName}_1\bin\standalone.bat and {jbossHomeName}_2\bin\standalone.bat scripts.
|
The application will be running at the following URL: http://localhost:9080/helloworld-mdb/HelloWorldMDBServletClient.
It will send some messages to the queue.
To send messages to the topic, use the following URL: http://localhost:9080/helloworld-mdb/HelloWorldMDBServletClient?topic
The application will be running at the following URL: http://localhost:8080/helloworld-mdb/HelloWorldMDBServletClient.
It will send some messages to the queue.
To send messages to the topic, use the following URL: http://localhost:8080/helloworld-mdb/HelloWorldMDBServletClient?topic
Look at the {productName} server console or log and you should see log messages like the following:
[Server:quickstart-messagingcluster-node1] INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-8 (ActiveMQ-client-global-threads-1067469862)) Received Message from queue: This is message 1
[Server:quickstart-messagingcluster-node1] INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-8 (ActiveMQ-client-global-threads-1067469862)) Received Message from queue: This is message 3
[Server:quickstart-messagingcluster-node1] INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-6 (ActiveMQ-client-global-threads-1067469862)) Received Message from queue: This is message 5
[Server:quickstart-messagingcluster-node2] INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-8 (ActiveMQ-client-global-threads-1771031398)) Received Message from queue: This is message 2
[Server:quickstart-messagingcluster-node2] INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-7 (ActiveMQ-client-global-threads-1771031398)) Received Message from queue: This is message 4
Note that the logging indicates messages have arrived from both node 1, quickstart-messagingcluster-node1
, as well as node 2, quickstart-messagingcluster-node2
.
You will see the following warnings in the server logs. You can ignore these warnings as they are intended for production servers.
WARNING [org.jgroups.protocols.UDP] (Thread-0 (ActiveMQ-server-ActiveMQServerImpl::serverUUID=c79278db-56e6-11e5-af50-69dd76236ee8-1573164340)) JGRP000015: the send buffer of socket DatagramSocket was set to 1MB, but the OS only allocated 212.99KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux)
WARNING [org.jgroups.protocols.UDP] (Thread-0 (ActiveMQ-server-ActiveMQServerImpl::serverUUID=c79278db-56e6-11e5-af50-69dd76236ee8-1573164340)) JGRP000015: the receive buffer of socket DatagramSocket was set to 20MB, but the OS only allocated 212.99KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
WARNING [org.jgroups.protocols.UDP] (Thread-0 (ActiveMQ-server-ActiveMQServerImpl::serverUUID=c79278db-56e6-11e5-af50-69dd76236ee8-1573164340)) JGRP000015: the send buffer of socket MulticastSocket was set to 1MB, but the OS only allocated 212.99KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux)
WARNING [org.jgroups.protocols.UDP] (Thread-0 (ActiveMQ-server-ActiveMQServerImpl::serverUUID=c79278db-56e6-11e5-af50-69dd76236ee8-1573164340)) JGRP000015: the receive buffer of socket MulticastSocket was set to 25MB, but the OS only allocated 212.99KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
After the server has been running for a period of time, you might see the following warnings in the server log, which are followed by a stacktrace. You can ignore these warnings as this is is a known issue and is harmless. See JBEAP-794 for more information.
WARN [org.infinispan.topology.ClusterTopologyManagerImpl] (transport-thread--p15-t6) ISPN000197: Error updating cluster member list: org.infinispan.util.concurrent.TimeoutException: Replication timeout for <application-name>
When you are finished testing, use the following instructions to undeploy the quickstart.
-
Make sure you have started the {productName} server in a managed domain as described above.
-
Open a terminal, navigate to the root directory of this quickstart, and run the following command to undeploy the helloworld-mdb quickstart:
$ {jbossHomeName}/bin/jboss-cli.sh --connect --file=undeploy-domain.cli
NoteFor Windows, use the {jbossHomeName}\bin\jboss-cli.bat
script.
-
Make sure you start the {productName} server as described above.
-
Open a terminal, navigate to the root directory of this quickstart, and run the following command to undeploy the helloworld-mdb quickstart:
$ {jbossHomeName}/bin/jboss-cli.sh --connect --file=undeploy-standalone.cli
NoteFor Windows, use the {jbossHomeName}\bin\jboss-cli.bat
script.
You can remove the domain configuration by manually restoring the back-up copies the configuration files or by running the JBoss CLI Script.
Important
|
This method ensures the server is restored to its prior configuration. |
-
If it is running, stop the {productName} server.
-
Restore the
{jbossHomeName}/domain/configuration/domain.xml
and{jbossHomeName}/domain/configuration/host.xml
files with the back-up copies of the files. Make sure you replace{jbossHomeName}
with the path to your server.
Important
|
This script returns the server to the default configuration, which might not match the server configuration that existed prior to testing this quickstart. If you were not running with the default configuration before testing this quickstart, you should follow the intructions above to manually restore the domain configuration to its previous state. |
-
Start the {productName} server by typing the following:
$ {jbossHomeName}/bin/jboss-cli.sh --connect --file=install-domain.cli
NoteFor Windows, use the {jbossHomeName}\bin\jboss-cli.bat
script. -
Open a new terminal, navigate to the root directory of this quickstart, and run the following command, replacing
{jbossHomeName}
with the path to your server.$ {jbossHomeName}/bin/jboss-cli.sh --connect --file=remove-domain.cli
NoteFor Windows, use the {jbossHomeName}\bin\jboss-cli.bat
script.This script removes the server configuration that was done by the
install-domain.cli
script. You should see the following result following the script commands.The batch executed successfully
Important
|
If the
Simply wait a few seconds and run the command a second time. |
You can remove the domain configuration by manually restoring the back-up copies the configuration files or by running the JBoss CLI Script.
Important
|
This method ensures the server is restored to its prior configuration. |
-
If they are running, stop both {productName} servers.
-
Restore the
{jbossHomeName}_1/standalone/configuration/standalone-full-ha.xml
file with the back-up copies of the file. Make sure you replace{jbossHomeName}_1
with the path to your server.
Important
|
This script returns the server to the default configuration, which might not match the server configuration that existed prior to testing this quickstart. If you were not running with the default configuration before testing this quickstart, you should follow the intructions above to manually restore the standalone configuration to its previous state. |
-
Start the {productName} server by typing the following:
$ {jbossHomeName}_1/bin/standalone.sh -c standalone-full-ha.xml
NoteFor Windows, use the {jbossHomeName}_1\bin\standalone.bat
script. -
Open a new terminal, navigate to the root directory of this quickstart, and run the following command, replacing
{jbossHomeName}_1
with the path to your server.$ {jbossHomeName}_1/bin/jboss-cli.sh --connect --file=remove-standalone.cli
NoteFor Windows, use the {jbossHomeName}_1\bin\jboss-cli.bat
script.This script removes the server configuration that was done by the
install-standalone.cli
script. You should see the following result following the script commands:The batch executed successfully