en.help.ref-jmsconnectionnew.html Maven / Gradle / Ivy
New JMS Connection Factory
Use the New JMS Connection Factory page to create a new JMS connection factory.
The New JMS Connection Factory page contains the following options.
- JNDI Name
-
A unique JNDI name that identifies the resource. By convention, the name begins with a resource-type indicator and a slash, such as concurrent/, jdbc/, or jms/.
- Resource Type
-
The type of the connection factory. Available choices are jakarta.jms.ConnectionFactory, jakarta.jms.QueueConnectionFactory, and jakarta.jms.TopicConnectionFactory.
- Description
-
A description of the connection factory.
- Status
-
The status of the connection factory. The connection factory can be enabled or disabled. This option is enabled by default.
- Initial and Minimum Pool Size
-
The minimum number of connections in the pool for the connection factory. The default value is 8.
- Maximum Pool Size
-
The maximum number of connections in the pool for the connection factory. The default value is 32.
- Pool Resize Quantity
-
The number of connections to be removed when pool idle timeout expires. The default value is 2.
- Idle Timeout
-
The maximum time in seconds that a connection can remain idle in the pool. The default value is 300.
- Max Wait Time
-
The amount of time the application requesting a connection will wait before getting a connection timeout. The default value is 60000.
- On Any Failure
-
If the Close All Connections checkbox is selected, GlassFish Server will close all connections in the pool and reestablish them if a single connection fails. This option is disabled by default.
- Transaction Support
-
The chosen transaction support overrides the transaction support attribute in the resource adapter associated with this connection pool in a downward compatible way. In other words, it can support a lower transaction level than that specified in the resource adapter, or the same transaction level as that specified in resource adapter, but it cannot specify a higher level.
The value may be any of the following:
- XATransaction
-
The resource can be used for transactions that involve the use of more than one resource within a transaction scope. This value is the default for a JMS connection factory.
For example, transactions may involve this resource plus a JDBC resource, a connector resource, or another JMS connection factory resource. This value offers the most flexibility. A resource that is configured as XATransaction will participate in two-phase commit operations.
- LocalTransaction
-
The resource can be used either for transactions that involve only one resource within the transaction scope or as the last agent in a distributed transaction that involves more than one XA resource.
This value offers significantly better performance. A resource that is configured as LocalTransaction will not be used in two-phase commit operations.
- NoTransaction
-
The resource can never participate in transactions. This setting is of limited use in JMS applications.
- Connection Validation
-
If the Required checkbox is selected, connections are validated before being given to the application. If a resource's validation fails, it is destroyed, and a new resource is created and returned. This option is disabled by default.
- Additional Properties
-
Additional properties for the connection factory.
For information on available properties, see Properties Specific to JMS Connection Factories.
- Targets
-
(This option is displayed if any clusters or standalone instances have been created in the domain.)
Clusters and standalone instances for resource. Move desired targets to the Selected Targets column using the Add and Add All buttons. Move any unneeded targets to the Available Targets column using the Remove and Remove All buttons.
Related Tasks
-
-
-
Related asadmin Commands
Copyright © 2005, 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices