Deleting the Connection Factory
Deleting the Connection Factory
For examples showing how to deploy Java EE applications on two different systems, see
and
Deleting the Connection Factory and Stopping the Server
You will need the connection factory jms/JupiterConnectionFactory in
However, if you wish to delete it, go to the producer directory
and type the following command:
ant delete-remote-factory
Remember to delete the connection factory on both systems.
You can also use Ant targets in the producer/build.xml file to delete the destinations and
connection factories you created in
. However, it is recommended that you keep them, because they
will be used in most of the examples in
After you have created them, they will be available whenever you restart the Application Server.
To delete the class and JAR files for each program using NetBeans IDE, right-click each project
and choose Clean Project.
To delete the class and JAR files for each program using Ant, type the following:
ant clean
You can also stop the Application Server, but you will need it to run the sample programs in the
next section.
Creating Robust JMS Applications
This section explains how to use features of the JMS API to achieve the level of reliability and
performance your application requires. Many people choose to implement JMS applications
because they cannot tolerate dropped or duplicate messages and require that every message be
received once and only once. The JMS API provides this functionality.
The most reliable way to produce a message is to send a PERSISTENT message within a
transaction. JMS messages are PERSISTENT by default. A transaction is a unit of work into which
you can group a series of operations, such as message sends and receives, so that the operations
either all succeed or all fail. For details, see
and
The most reliable way to consume a message is to do so within a transaction, either from a
queue or from a durable subscription to a topic. For details, see
Creating Robust JMS Applications
Chapter 31 · The Java Message Service API
935
