| Exit Print View | |
Sun GlassFish Enterprise Server v3 Administration Guide |
|
|
|
1. Overview of Enterprise Server Administration
Default Settings and Locations
Instructions for Administering Enterprise Server
4. Administering the Virtual Machine for the Java Platform
6. Administering Web Applications
7. Administering the Logging Service
8. Administering the Monitoring Service
9. Administering Life Cycle Modules
10. Extending Enterprise Server
Part II Security Administration
11. Administering System Security
12. Administering User Security
13. Administering Message Security
Part III Resources and Services Administration
14. Administering Database Connectivity
15. Administering EIS Connectivity
16. Administering Internet Connectivity
17. Administering the Object Request Broker (ORB)
18. Administering the JavaMail Service
19. Administering the Java Message Service (JMS)
Administering JMS Physical Destinations
To Create a JMS Physical Destination
To List JMS Physical Destinations
To Purge Messages From a Physical Destination
To Delete a JMS Physical Destination
Administering JMS Connection Factories and Destinations
To Create a Connection Factory or Destination Resource
To Delete a Connection Factory or Destination Resource
Administering Connection Addressing
Setting JMS Connection Pooling
Configuring Resource Adapters for JMS
To Configure the Generic Resource Adapter
20. Administering the Java Naming and Directory Interface (JNDI) Service
21. Administering Transactions
When you start Enterprise Server, the JMS service is available but is not
loaded until it is needed (for example, when you create a JMS
resource). Use the 
jms-ping(1)subcommand to check if the JMS service is running or, if
it is not yet running, to start it. If thejms-ping subcommand is unable
to contact a built-in JMS service, an error message is displayed.
If you encounter problems, consider the following:
View the Enterprise Server log file, typically located at domain-dir/logs/server.log.
If a the log file indicates that a Message Queue broker did not respond to a message, stop the broker and then restart it.
View the broker log, typically available at as-install/domains/domain1/imq/instances/imqbroker/log/log.txt.
For JMS REMOTE mode, be sure to start Message Queue brokers first, then Enterprise Server.
If all Message Queue brokers are down, it takes 30 minutes for Enterprise Server to go down or up when you are using the default values in JMS. You can change the default values for this timeout. For example:
asadmin set domain1.jms-service.reconnect-interval-in-seconds=5
|
|