Administration Console Online Help
|
 |
 |
|
|
Server --> Services --> JMS
Tasks Related Topics Attributes
Overview
On this tab, you can define whether to use the default JMS connection factories and configure the size of the JMS execute thread pool.
Default JMS Connection Factories
WebLogic Server defines two default connection factories, which can be looked up using the following JNDI names:
weblogic.jms.ConnectionFactoryweblogic.jms.XAConnectionFactory(the XA Connection Factory Enabled attribute is switched on for enabling JTA user-transactions)
An XA factory is required for JMS applications to use JTA user-transactions, but is not required for transacted sessions. All other preconfigured attributes for the default connection factories are set to the same default values as a user-defined connection factory. If the preconfigured settings of the default factories are appropriate for your application, you do not need to configure any additional factories for your application.
Note: When using the default connection factories, you have no control over targeting the WebLogic Server instances where the connection factory may be deployed. However, you can disable the default connection factories on a per-server basis. To deploy a connection factory on independent servers, on specific servers within a cluster, or on an entire cluster, you need to configure a connection factory and specify the appropriate server targets.
On the server, incoming JMS related requests execute in the JMS execute queue/thread pool. Additional work that cannot be completed in the request thread is forwarded to the "default" execute queue.
Tasks
Configuring a JMS Connection Factory
Related Topics
"WebLogic JMS Fundamentals" in Programming WebLogic JMS
"Using Transactions With WebLogic JMS" in Programming WebLogic JMS
"Developing a WebLogic JMS Application" in Programming WebLogic JMS
"Tuning WebLogic Server" and "Tuning WebLogic Server Applications" in the Performance and Tuning Guide.
