Undeploy the Example Application
Undeploy the Example Application
Name: Jack Verdon
Equipment: Pager
Office number: 20
Waiting for 3 message(s)
New hire event processed:
Employee ID: 27
Name: Fred Tudor
Equipment: Pager
Office number: 51
Waiting for 2 message(s)
New hire event processed:
Employee ID: 28
Name: Fred Martin
Equipment: Desktop System
Office number: 141
Waiting for 1 message(s)
New hire event processed:
Employee ID: 29
Name: Mary Stuart
Equipment: Pager
Office number: 238
The output from the message-driven beans and the entity class appears in the server log,
wrapped in logging information.
For each employee, the application first creates the entity and then finds it. You may see
runtime errors in the server log, and transaction rollbacks may occur. The errors occur if both
of the message-driven beans discover at the same time that the entity does not yet exist, so they
both try to create it. The first attempt succeeds, but the second fails because the bean already
exists. After the rollback, the second message-driven bean tries again and succeeds in finding
the entity. Container-managed transactions allow the application to run correctly, in spite of
these errors, with no special programming.
You can run the application client repeatedly.
Undeploy the application after you finish running the client. To undeploy the application,
follow these steps:
1. Click the Runtime tab.
2. Expand the Servers node.
3. Expand the Sun Java System Application Server node.
4. Expand the Applications node.
5. Expand the Enterprise Applications node.
6. Right-click clientmdbentity and choose Undeploy.
To remove the generated files, right-click the clientmdbentity project and choose Clean
Project.
A Java EE Application That Uses the JMS API with an Entity
The Java EE 5 Tutorial · September 2007
976
