| Skip Navigation Links | |
| Exit Print View | |
|
Oracle GlassFish Server 3.1 Administration Guide |
1. Overview of GlassFish Server Administration
Default Settings and Locations
Instructions for Administering GlassFish 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. Writing and Running JavaScript Clients to Monitor GlassFish Server
10. Administering Life Cycle Modules
11. Extending and Updating GlassFish Server
Part II Resources and Services Administration
12. Administering Database Connectivity
13. Administering EIS Connectivity
14. Administering Internet Connectivity
15. Administering the Object Request Broker (ORB)
16. Administering the JavaMail Service
17. Administering the Java Message Service (JMS)
Updating the JMS Service Configuration
Setting Message Queue Broker Properties in the JMS Service Configuration
Configuring Embedded and Local JMS Hosts
Administering JMS Connection Factories and Destinations
To Create a Connection Factory or Destination Resource
To Delete a Connection Factory or Destination Resource
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
Special Situations When Using the JMS Service
Using the Generic Resource Adapter for JMS to Integrate Supported External JMS Providers
Configuring GenericJMSRA for Supported External JMS Providers
To Deploy and Configure GenericJMSRA
GenericJMSRA Configuration Properties
Using GenericJMSRA with WebLogic JMS
Deploy the WebLogic Thin T3 Client JAR in GlassFish Server
Configure WebLogic JMS Resources for Integration
Create a Resource Adapter Configuration for GenericJMSRA to Work With WebLogic JMS
Deploy the GenericJMSRA Resource Archive
Configuring an MDB to Receive Messages from WebLogic JMS
Accessing Connections and Destinations Directly
Limitations When Using GenericJMSRA with WebLogic JMS
Configuration Reference of GenericJMSRA Properties for WebLogic JMS
Using GenericJMSRA with IBM WebSphere MQ
Preliminary Setup Procedures for WebSphere MQ Integration
Configure the WebSphere MQ Administered Objects
Create a Resource Adapter Configuration for GenericJMSRA to Work With WebSphere MQ
Deploy the GenericJMSRA Archive
Create the Connection Factories and Administered Objects in GlassFish Server
Configuring an MDB to Receive Messages from WebSphere MQ
18. Administering the Java Naming and Directory Interface (JNDI) Service
19. Administering Transactions
If you encounter problems, consider the following:
Use the jms-ping(1) subcommand to confirm that the Message Queue broker is running.
View the GlassFish Server log file. For server, the Domain Administrations Server (DAS), the log is available at domain-dir/logs/server.log; for other GlassFish instances, the log is available at as-install/nodes/node-name/instance-name/logs/server.log.
If the log file indicates that a Message Queue broker acting as a Remote JMS host did not respond to a message, stop the broker and then restart it.
View the broker log. For a broker associated with the Domain Administration Server (DAS), the log is available at domain-dir/imq/instances/imqbroker/log/log.txt; for brokers associated with other GlassFish instances, the log is available at as-install/nodes/node-name/instance-name/imq/instances/mq-instance-name/log/log.txt.
For Remote type JMS hosts, be sure to start Message Queue brokers first, then GlassFish Server instances.
If all Message Queue brokers are down, it can take up to 30 minutes for GlassFish 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
|