Connection factory properties
The following tables list all the properties that you can set for connection factories:
- General
- Connection
- Reconnection
- Channels
- SSL
- Exits
- Broker
- Temporary queues
- Temporary topics
- Subscriber
- Extended
- Advanced tuning
For each property, there is a brief description of when you might need to configure the property. The tables also give the equivalent long and short names to use in the JMS Administration command line tool. The properties that are available in the Properties dialog depend on which messaging provider the connection factory uses. For more information about the JMS Administration command line tool, see Using the WebSphere MQ JMS administration tool in the IBM® online IBM WebSphere® MQ product documentation.
General page
The following table lists the properties that you can set on the General page of the Connection Factory properties dialog.
| Property | Meaning | Long name | Short name |
|---|---|---|---|
| Name | This is the name of the object. | NAME | |
| Description | Type a description of the object. | DESCRIPTION | DESC |
| Class name | This shows the class name that is implemented by the connection factory. | ||
| Messaging provider | This shows whether the connection factory uses MQ transport (Bindings or Client) or Real-time transport (Direct or Direct HTTP). | ||
| Transport | This shows the transport type used for the connection. Bindings is a direct connection to
the queue manager that is on the same computer as the JMS client; Client is a client connection using
TCP/IP (the queue manager can be on the same or different computer); Direct is a direct connection to a broker
of WebSphere MQ Event Broker, WebSphere Business
Integration Event Broker, WebSphere Business Integration
Message Broker, WebSphere Event Broker, or WebSphere Message
Broker; Direct HTTP is a direct
connection using HTTP tunneling. Although this field is read-only,
you can change the transport type if there is an alternative transport
type available for the messaging provider; for more information, see Changing the transport type used
for connections. |
TRANSPORT | TRAN |
| Provider version | Select, or type, the version, release, modification
level and fix pack of the queue manager to which this client is intended
to connect. If you type the value, use one of the following formats:
A value of "7" or greater indicates that this is intended
as a WebSphere MQ Version 7.0 ConnectionFactory
for connections to a WebSphere MQ Version 7.0 queue
manager. A value lower than 7 (for example "6.0.2.0"), indicates that
it is intended for use with queue managers earlier than Version 7.0.
The default value, |
PROVIDERVERSION | PVER |
| Client identifier | The client identifier is used to uniquely identify the application
connection for durable subscriptions. Type an identifier for the client |
CLIENTID | CID |
| Max buffer size | Type the maximum number of received messages that can be stored
in an internal message buffer while waiting to be processed by the
client application. This property applies only when the Transport property has the value Direct and Direct
HTTP. The default is 1000. |
MAXBUFFSIZE | MBSZ |
Connection page
The following table lists the properties that you can set on the Connection page of the Connection Factory properties dialog. Edit the properties on the Connection page to set the connection details for connections created by this connection factory.
| Property | Meaning | Long name | Short name |
|---|---|---|---|
| Base queue manager | Select or type the name of the queue manager to connect to. If your application uses a client channel definition table to connect to a queue manager, see the section about using a client channel definition table in Chapter 12 Writing WebSphere MQ JMS 1.1 applications in WebSphere MQ Using Java. | QMANAGER | QMGR |
| Broker queue manager | This property can be used in a WebSphere MQ Version 7.0 JMS client but has no effect on a WebSphere MQ Version 7.0 queue manager. Select or type the name of the queue manager on which the broker is running. |
BROKERQMGR | BQM |
| Connection list | Comma separated list of HOSTNAME(PORT) connection addresses.
The list is tried in order, once per each connection retry attempt. HOSTNAME can be a DNS name or IP address. PORT defaults to 1414. |
CLIENTRECONNECTHOSTS | CRHOSTS |
| Proxy host name | Type the host name of the proxy server for a direct connection. | PROXYHOSTNAME | PHOST |
| Proxy port | Type the port number of the proxy server for a direct connection. The default is 443. | PROXYPORT | PPORT |
| Coded character set ID | Type the coded character set ID (CCSID) to be used on connections. For optimum performance, the value of this property should be the same as the value of the Coded Character Set ID attribute (Queue manager properties) of the base queue manager. | CCSID | CCS |
| Multicast | Specify whether messages are delivered to message consumers using multicast transport. Multicast transport is applicable only to topic destinations and can be used only when the connection factory uses Direct IP transport. The default value is Disabled, which means that messages are not delivered to a message consumer using multicast transport. Click Enabled to deliver messages to the message consumer using multicast transport. The topic must be configured for reliable multicast in the broker; a reliable quality of service is used if the topic is configured for reliable multicast. |
MULTICAST | MULTI |
|
Click Reliable to deliver messages to the message consumer using multicast transport with a reliable quality of service. The topic must be configured for reliable multicast in the broker; if the topic is not configured for reliable multicast, you cannot create a message consumer for the topic. Click Not reliable to deliver messages using multicast transport but without using a reliable quality of service. The topic must be configured for multicast in the broker; a reliable quality of service is not used, even if the topic is configured for reliable multicast. |
|||
| Local address | For a connection to a queue manager, specify either the local network interface to be used, or the local port (or range of local ports) to be used, or both. The channel binds to the address locally. Use the format ipaddress(low-port, high-port), where ipaddress is the IP address specified in IPv4 dotted decimal, IPv6 hexadecimal, or alphanumeric host name format. For example, 127.0.0.1 specifies the IPv4 address with any port; 127.0.0.1(1000) specifies the IPv4 address and a specific port; 127.0.0.1(1000,2000) specifies the IPv4 address and a range of ports; (1000) specifies a port only. If you are using a direct connection to a broker, this property is relevant only when multicast is used. Specify the local network interface to be used, as an IP address or as a host name, but do not specify any port number. | LOCALADDRESS | LA |
| Connect options | Select how the application connects to the queue manager. Click Standard for the nature of the binding between the application and the queue manager to depend on the platform on which the queue manager is running and how the queue manager is configured. Click Shared for the application and the local queue manager agent to run in separate units of execution but share some resources. Click Isolated for the application and the local queue manager agent to run in separate units of execution. Click Fastpath for the application and the local queue manager agent to run in the same unit of execution. Click Serial queue manager for the application to request exclusive use of the connection tag within the scope of the queue manager. Click Serial queue-sharing group for the application to request exclusive use of the connection tag within the scope of the queue-sharing group to which the queue manager belongs. |
CONNOPT | CNOPT |
|
Click Restricted queue manager for the application to request shared use of the connection tag but restricting the shared use of the connection tag within the scope of the queue manager. Click Restricted queue-sharing group for the application to request the shared use of the connection tag but restricting the shared use of the connection tag within the scope of the queue-sharing group to which the queue manager belongs. The |
|||
| Connection tag | This is a tag that the queue manager associates with the resources that are updated by the application within a unit of work while the application is connected to the queue manager. The connection tag is supported only by z/OS queue managers. | CONNTAG | CNTAG |
| Share conversations allowed | Click Yes (the default value) to specify that a client connection can share its socket with other JMS connections from the same process to the same queue manager, if the channel definitions match. Otherwise, click No. | SHARECONVALLOWED | SCA |
Reconnection page
| Property | Meaning | Long name | Short name |
|---|---|---|---|
| Options |
|
CLIENTRECONNECTOPTIONS | CROPT |
| Timeout | Interval in seconds before reconnection retries cease. The default is 1800 seconds (30 minutes). | CLIENTRECONNECTTIMEOUT | CRT |
Channels page
The following table lists the properties that you can set on the Channel page of the Connection Factory properties dialog. Edit the properties on the Channel page to configure how the JMS client connects to the queue manager.
| Property | Meaning | Long name | Short name |
|---|---|---|---|
| Channel | Select or type the name of the server-connection channel to
use to connect the client to the queue manager. To use Select to enter
the name, you must have already entered a value for the Base
Queue Manager property on the Connection page, and
the selected queue manager must be running. You must set a value for
either the Channel property or for the Client
Channel Definition Table URL property but not both. |
CHANNEL | CHAN |
| Client channel definition table URL | Enter the uniform resource locator (URL) that identifies the
name and location of the file that contains the client channel definition
table and specifies how the file can be accessed. You must set a value
for either the Channel property or for the Client
Channel Definition Table URL property but not both. |
CCDTURL | CCDT |
| Header compression | Click Edit then select the list of techniques that can be used for compressing header data on a connection. | COMPHDR | HC |
| Message compression | Click Edit then select the list of techniques that can be used for compressing message data on a connection. | COMPMSG | MC |
SSL page
The following table lists the properties that you can set on the SSL page of the Connection Factory properties dialog. Edit the properties on the SSL page to configure the SSL details for securing client connections and direct connections to the broker.
| Property | Meaning | Long name | Short name |
|---|---|---|---|
| Direct SSL authentication | To enable SSL authentication for a direct connection, click Certificate. To disable authentication, user name authentication, and password authentication, click Basic. | DIRECTAUTH | DAUTH |
| CipherSuite | Select the CipherSuite to use for an SSL connection. The CipherSuite
must match the CipherSpec of the server-connection channel that is
specified in the Channel property on the Channels page. If you
do not select a CipherSuite, the FIPS Required, Certificate
Revocation List, Peer Name,
and Reset Count properties are ignored. |
SSLCIPHERSUITE | SCPHS |
| FIPS required | Click Yes to specify that an SSL connection must use a CipherSuite that is supported by the IBM Java JSSE FIPS provider (IBMJSSEFIPS). Click No if an SSL connection can use any CipherSuite. | SSLFIPSREQUIRED | SFIPS |
| Certificate revocation list | Enter a list of certificate revocation list servers to check for SSL certificate revocation. | SSLCRL | SCRL |
| Peer name | Type a distinguished name skeleton that must match that
provided by the queue manager. The SSL peer name must also match the
SSL peer name of the server-connection channel that is specified in
the Channel property on the Channels page. |
SSLPEERNAME | SPEER |
| Reset count | Enter the total number of bytes sent and received by a connection before the secret key that is used for encryption is negotiated. | SSLRESETCOUNT | SRC |
Exits page
The following table lists the properties that you can set on the Exits page of the Connection Factory properties dialog. User exits are code modules that you provide yourself to do additional processing on the message data (for example, encryption or data compression). Edit the properties on the Exits page to change the default location of client exit code modules that are run when called.
| Property | Meaning | Long name | Short name |
|---|---|---|---|
| Send exit name | Enter the name of the channel send exit or the sequence of send exits to be run in succession. Each entry in the list must be either the name of a class that implements the WebSphere MQ Java interface MQSendExit (for a channel send exit written in Java), or a string in the format libraryName(entryPointName) (for a channel send exit not written in Java). | SENDEXIT | SDX |
| Send exit initialization | Enter the user data that is passed to channel send exits when they are called. You can enter one or more items of user data separated by commas. | SENDEXITINIT | SDXI |
| Receive exit name | Enter the name of the channel receive exit, or a sequence of receive exits, to be called. Each entry in the list must be either the name of a class that implements the WebSphere MQ Java interface MQReceiveExit (for a channel receive exit written in Java), or a string in the format libraryName(entryPointName) (for a channel receive exit not written in Java). | RECEXIT | RCX |
| Receive exit initialization | Enter the user data that is passed to channel receive exits when they are called. You can enter one or more items of user data separated by commas. | RECEXITINIT | RCXI |
| Security exit name | Type either the name of a class that implements the WebSphere MQ Java interface MQSecurityExit (for a channel security exit written in Java) or a string in the format libraryName(entryPointName) (for a channel security exit not written in Java). | SECEXIT | SCX |
| Security exit initialization | Type the user data that is passed to the channel security exit when it is called. | SECEXITINIT | SCXI |
Broker page
The following table lists the properties that you can set on the Broker page of the Connection Factory properties dialog. Edit the properties on the Broker page to provide details of the publish/subscribe broker.
| Property | Meaning | Long name | Short name |
|---|---|---|---|
| Broker subscription message queue | This property can be used in a WebSphere MQ Version 7.0 JMS client but has no effect on a WebSphere MQ Version 7.0 queue manager. It has the effect on earlier versions of the queue manager. Select or type the name of the queue from which non-durable subscription messages are received. The default queue isSYSTEM.JMS.ND.SUBSCRIBER.QUEUE.
To use Select to enter the name, you must have already selected a
value for the Base Queue Manager property
on the Connection page,
and the selected queue manager must be running. |
BROKERSUBQ | BSUB |
| Broker CC subscription message queue | This property can be used in a WebSphere MQ Version 7.0 JMS client but has no effect on a WebSphere MQ Version 7.0 queue manager. Select or type the name of the queue from which non-durable subscription messages are retrieved for a ConnectionConsumer. The default queue isSYSTEM.JMS.CC.SUBSCRIBER.QUEUE.
To use Select to enter the name, you must have already selected a
value for the Base Queue Manager property
on the Connection page,
and the selected queue manager must be running.For more information, see the BROKERSUBQ property in the IBM online IBM WebSphere MQ product documentation. |
BROKERCCSUBQ | CCSUB |
| Broker control queue | This property can be used in a WebSphere MQ Version 7.0 JMS client but has no effect on a WebSphere MQ Version 7.0 queue manager. Select or type the name of the broker's control queue. To use Select to enter the name, you must have already selected a value for theBroker Queue
Manager property on the Connection page, and
the selected queue manager must be running. |
BROKERCONQ | BCON |
| Publication stream | This property can be used in a WebSphere MQ Version 7.0 JMS client but has no effect on a WebSphere MQ Version 7.0 queue manager. Select or type the name of the queue where published messages are sent (the stream queue). The default queue isSYSTEM.BROKER.DEFAULT.STREAM.
To use Select to enter the name, you must have already selected a
value for the Broker Queue Manager property
on the Connection page,
and the selected queue manager must be running. |
BROKERPUBQ | BPUB |
| Broker version | This property can be used in a WebSphere MQ Version 7.0 JMS client but has no effect on a WebSphere MQ Version 7.0 queue manager. Select the version of the broker being used. Click V1 to use a WebSphere MQ publish/subscribe broker, or to use a broker of WebSphere MQ Integrator, WebSphere MQ Event Broker, WebSphere Business Integration Event Broker, WebSphere Business Integration Message Broker, WebSphere Event Broker, or WebSphere Message Broker in compatibility mode; this is the default value if theTransport property is set to Bindings or Client.
Click V2 to use a broker
of WebSphere MQ Integrator, WebSphere MQ
Event Broker, WebSphere Business Integration Message
Broker, WebSphere Event Broker, or WebSphere Message
Broker in native mode; this is the default value if the Transport property is set to Direct or DirectHTTP. |
BROKERVER | BVER |
| Publication acknowledgment interval | This property can be used in a WebSphere MQ Version 7.0 JMS client but has no effect on a WebSphere MQ Version 7.0 queue manager. Enter the number of messages that are published by a publisher before the WebSphere MQ JMS client requests an acknowledgment from the broker. If you lower the value of this property, the client requests acknowledgments more often and, therefore, the performance of the publisher decreases. If you raise the value, the client takes a longer time to throw an exception if the broker fails. This property is relevant only if theTransport property has the value Bindings or Client.
The default value is 25. |
PUBACKINT | PAI |
Temporary queues page
The following table lists the properties that you can set on the Temporary queues page of the Connection Factory properties dialog. Edit the properties on the Temporary queues page to specify how the JMS temporary queues are dynamically defined.
| Property | Meaning | Long name | Short name |
|---|---|---|---|
| Temporary model queue | Select or type the name of the model queue from which JMS temporary
queues are created. To use Select to enter the name, you must have
already selected a value for the Base
Queue Manager property on the Connection page, and
the selected queue manager must be running. |
TEMPMODEL | TM |
| Temporary queue prefix | Type the prefix that is used to form the name of a WebSphere MQ dynamic queue. The rules for
forming the prefix are the same as those for forming the contents
of the DynamicQName field in a WebSphere MQ
object descriptor (MQOD) but the last non-blank character must be
an asterisk (*). If no value is specified for the property, the value
used is CSQ.* on z/OS,
and AMQ.* on other platforms. |
TEMPQPREFIX | TQP |
Temporary topics page
The following table lists the properties that you can set on the Temporary topics page of the Connection Factory properties dialog. Edit the properties on the Temporary topics page to specify how the JMS temporary topics are dynamically defined.
| Property | Meaning | Long name | Short name |
|---|---|---|---|
| Temporary topic prefix | Type the prefix that is used to form the name of a temporary topic. When creating temporary topics, JMS generates a topic string of the form TEMP/TEMPTOPICPREFIX/unique_id, or if this property is left with the default value, just TEMP/unique_id. | TEMPTOPICPREFIX | TTP |
Subscriber page
The following table lists the properties that you can set on the Subscriber page of the Connection Factory properties dialog. Edit the properties on the Subscriber page to manage subscribers and subscriptions.
| Property | Meaning | Long name | Short name |
|---|---|---|---|
| Message selection | This property can be used in a WebSphere MQ Version 7.0 JMS client but has no effect on a WebSphere MQ Version 7.0 queue manager. To specify that message selection is done by the JMS client application, click Client. To specify that message selection is done by the broker, click Broker. If theTransport property on
the General page has
the value Direct, message selection
is always done by the broker and the value of the Message Selection property is ignored.
Message selection by the broker is not supported when the Broker Version property on the Broker page has the value V1. |
MSGSELECTION | MSEL |
| Sparse subscriptions | This property can be used in a WebSphere MQ Version 7.0 JMS client but has no effect on a WebSphere MQ Version 7.0 queue manager. This property controls the message retrieval policy of a TopicSubscriber object. To specify that subscriptions receive frequent matching messages, click No. To specify that subscriptions receive infrequent matching messages, click Yes. |
SPARSESUBS | SSUBS |
| Subscription store | This property can be used in a WebSphere MQ Version 7.0 JMS client but has no effect on a WebSphere MQ Version 7.0 queue manager. Select the location where WebSphere MQ JMS should store persistent data relating to active subscriptions. To store subscription information on the queues SYSTEM.JMS.ADMIN.QUEUE and SYSTEM.JMS.PS.STATUS.QUEUE, click Queue. To store subscription information in the publish/subscribe broker and not on queues, click Broker. To dynamically select a queue-based or broker-based subscription store depending on the release levels of WebSphere MQ and the publish/subscribe broker that is installed, click Migrate, which is selected by default. For more information about subscription stores, see Writing WebSphere MQ classes for JMS applications in the IBM online IBM WebSphere MQ product documentation. |
SUBSTORE | SS |
| Cleanup level | This property can be used in a WebSphere MQ Version 7.0 JMS client but has no effect on a WebSphere MQ Version 7.0 queue manager. Select the cleanup level for subscription stores for which theSubscription Store property
on the Broker page is
set to Broker or Migrate. |
CLEANUP | CL |
| Cleanup interval | This property can be used in a WebSphere MQ Version 7.0 JMS client but has no effect on a WebSphere MQ Version 7.0 queue manager. Type the number of milliseconds interval between background runs of the publish/subscribe cleanup utility. |
CLEANUPINT | CLINT |
| Clone support | Specify whether two or more instances of the same durable topic subscriber can run simultaneously. Note that enabling clone support contravenes the JMS 1.1 specification. To specify that only one instance of a durable topic subscriber can run at a time, click Disabled. This is the default value. To specify that two or more instances of the same durable topic subscriber can run simultaneously, each instance running in a separate Java virtual machine (JVM), click Enabled. | CLONESUPP | CLS |
| Status refresh interval | This property can be used in a WebSphere MQ Version 7.0 JMS client but has no effect on a WebSphere MQ Version 7.0 queue manager. Type the number of milliseconds interval between refreshes of the long-running transaction that detects when a subscriber loses its connection to the queue manager. This property is relevant only if theSubscription
Store property on the Broker
page has the value Queue.
For more information about subscription stores, see Writing WebSphere MQ classes for JMS
applications in the IBM online IBM WebSphere MQ product documentation |
STATREFRESHINT | SRI |
| Wildcard format | Specify which version of wildcard syntax is
to be used. Click Only character wildcards to use only character wildcards (for consistency with applications that previously used Broker Version 1; see the Broker version property). Click Only topic wildcards to use only topic level wildcards, which are used in Broker Version 2. |
WILDCARDFORMAT | WCFMT |
Extended page
The following table lists the properties that you can set on the Extended page of the Connection Factory properties dialog. Edit the properties on the Extended page to change further properties of the connection factory object.
| Property | Meaning | Long name | Short name |
|---|---|---|---|
| Message batch size | This property can be used in a WebSphere MQ Version 7.0 JMS client but has no effect on a WebSphere MQ Version 7.0 queue manager. Type the maximum number of messages to be taken from a queue in one packet when using asynchronous message delivery. The default is 10. |
MSGBATCHSZ | MBS |
| Message retention | Specify whether the connection consumer keeps unwanted messages on the input queue. To keep unwanted messages on the input queue, click Yes. To deal with unwanted messages according to their disposition options, click No. | MSGRETENTION | MRET |
| Polling interval | This property can be used in a WebSphere MQ Version 7.0 JMS client but has no effect on a WebSphere MQ Version 7.0 queue manager. Type the number of milliseconds interval that elapses before each message listener tries again to get a message from its queue when each message listener within a session has no suitable message on its queue. The default is 5000. If there is frequently no suitable message available for any of the message listeners in the session, consider increasing the value of the property. |
POLLINGINT | PINT |
| Rescan interval | This property can be used in a WebSphere MQ Version 7.0 JMS client but has no effect on a WebSphere MQ Version 7.0 queue manager. Type the number of milliseconds interval before the WebSphere MQ JMS client returns to the beginning of the queue when searching for a suitable message. When a message consumer in the point-to-point domain uses a message selector to select which messages it wants to receive, the WebSphere MQ JMS client searches the WebSphere MQ queue for suitable messages in the sequence determined by theMessage
Delivery Sequence property of the queue (see Queue properties). When the
client finds a suitable message and delivers it to the consumer, the
client resumes the search for the next suitable message from its current
position in the queue. The client continues to search the queue in
this way until it reaches the end of the queue, or until the interval
of time in milliseconds, as determined by the value of this property,
has expired. In each case, the client returns to the beginning of
the queue to continue its search, and a new time interval commences. |
RESCANINT | RINT |
| Fail if quiesce | To specify that calls to certain methods fail if the queue manager is in a quiescing state, click Yes. If an application detects that the queue manager is quiescing, the application can complete its immediate task and close the connection, allowing the queue manager to stop. To specify that no method call fails because the queue manager is in a quiescing state, click No. If you click No, an application cannot detect that the queue manager is quiescing so the application might continue to perform operations against the queue manager and, therefore, prevent the queue manager from stopping. | FAILIFQUIESCE | FIQ |
| Syncpoint all gets | To specify that all gets should be performed under syncpoint, click Yes. To specify that all gets should not be performed under syncpoint, click No. | SYNCPOINTALLGETS | SPAG |
| Target client matching | Specify whether a reply message, sent to the queue identified
by the JMSReplyTo header field of an incoming message, has an MQRFH2
header only if the incoming message has an MQRFH2 header. To specify
that if an incoming message does not have an MQRFH2 header, the Target Client property on the destination
queue is set to MQ, click Yes. If the incoming message does
have an MQRFH2 header, the Target Client property
is set to JMS instead. To specify
that the Target Client property
of the destination queue is always set to JMS,
click No. |
TARGCLIENTMATCHING | TCM |
| Asynchronous error check interval | Type the number of send calls to allow between checking for asynchronous put errors, within a single non-transacted JMS session. The minimum value is 0; the value can be any positive integer. | SENDCHECKCOUNT | SCC |
Advanced tuning page
The following table lists the properties that you can set on the Advanced tuning page of the Connection Factory properties dialog. Edit the properties on the Advanced tuning page to configure advanced settings. For most systems, the default settings are appropriate.
| Property | Meaning | Long name | Short name |
|---|---|---|---|
| Process duration | This property can be used in a WebSphere MQ Version 7.0 JMS client but has no effect on a WebSphere MQ Version 7.0 queue manager. To specify that a subscriber can give no guarantee about how quickly it can process any message it receives, click Unknown (the default value). To specify that a subscriber guarantees to process any message it receives before returning control to the WebSphere MQ JMS client, click Short. |
PROCESSDURATION | PROCDUR |
| Optimistic publication | This property can be used in a WebSphere MQ Version 7.0 JMS client but has no effect on a WebSphere MQ Version 7.0 queue manager. To specify that when a publisher publishes a message, the WebSphere MQ JMS client does not return control to the publisher until it has completed all the processing associated with the call and can report the outcome to the publisher, click No (the default value). To specify that when a publisher publishes a message, the WebSphere MQ JMS client returns control to the publisher immediately, before it has completed all the processing associated with the call and can report the outcome to the publisher, click Yes (the WebSphere MQ JMS client reports the outcome only when the publisher commits the message). |
OPTIMISTICPUBLICATION | OPTPUB |
| Outcome notification | This property can be used in a WebSphere MQ Version 7.0 JMS client but has no effect on a WebSphere MQ Version 7.0 queue manager. To specify that when a subscriber acknowledges or commits a message, the WebSphere MQ JMS client does not return control to the subscriber until it has completed all the processing associated with the call and can report the outcome to the subscriber, click Yes (the default value). To specify that when a subscriber acknowledges or commits a message, the WebSphere MQ JMS client returns control to the subscriber immediately, before it has completed the call and can report the outcome to the subscriber, click No. |
OUTCOMENOTIFICATION | NOTIFY |
| Receive isolation | This property can be used in a WebSphere MQ Version 7.0 JMS client but has no effect on a WebSphere MQ Version 7.0 queue manager. To specify that a subscriber receives only the messages on the subscriber queue that have been committed, click Committed (the default value). To specify that a subscriber can receive messages that have not been committed on the subscriber queue, click Uncommitted. The value ofUncommitted has an effect only if the Process Duration property has the value Short. |
RECEIVEISOLATION | RCVISOL |