Known Bugs Or Limitations - Red Hat APPLICATION SERVER - JONAS Tutorial

Chapter 10. The Alarm Application
Figure 10-4. Results of the alarm.ear Deployment
e. If you click Deployments > Applications (EAR) again,
right list box, which lists the deployed
If you click Application Container, EJB container, or Web Container under Services, you
will see
alarm.ear
3. Generate alarms: The easiest way is to use the link on the first html page that will run a servlet
that will generate customized alarms. Look at http://$HOSTNAME:9000/alarm/index.html to
start using the web application. If you are asked for authentication, use Username: tomcat
Password: tomcat.
Running Alarm is simply a matter of following the on-screen instructions: to set alarms, click
Click here to generate alarms; to check for alarms, click Filters.
4. As , stop the Red Hat Application Server server:
root
/sbin/service jonas stop

10.6. Known Bugs or Limitations

The first time you run this application, the table will be created in the database. An error message
•
will be printed by the J2EE server because it tries to drop the table, but the table does not exist.
Ignore it.
The display pages are not automatically refreshed when a new alarm is received. To be done in a
•
future version.
Filter names cannot contain "space" characters.
•
Sending many alarm messages concurrently with InstantDB as the database will not work (a dead-
•
lock will lead to a transaction timeout, and a delay on servlet display). This can occur with every
database that cannot handle multithreading properly.
in the tree.
alarm.ear
files.
EAR
45
will appear in the