com.tibco.tibjms.connect.attempts
|
|
Specifies the number of reconnection attempts, and the interval between each attempt to connect to the JMS server.
The value must use the format:
attempts,retry interval.
For example:
10,500 means 10 attempts, with a 500 millisecond interval between each retry attempt.
This property is used only for channels that have a TIBCO Enterprise Message Service provider.
- Note
- Use either
be.jms.reconnect.timeout or
com.tibco.tibjms.connect.attempts. If you set both the properties, then
com.tibco.tibjms.connect.attempts takes precedence.
Default is
2, 500.
Note: The property does not work for the JNDI connection.
|
be.jms.reconnect.timeout
|
|
Specifies the retry interval (in seconds) for reconnecting to the JMS server when the connection is broken.
A value of zero (0) means do not retry. Any other value means keep retrying (with no limit to number of retries), and use the specified interval between each attempt.
- Note
- Unacknowledged messages (Events) are resent to the TIBCO BusinessEvents engine, which may result in duplicate events.
- Note
- Use either
be.jms.reconnect.timeout or
com.tibco.tibjms.connect.attempts. If you set both the properties, then
com.tibco.tibjms.connect.attempts takes precedence.
Default is 0 (zero)
|
be.jms.reconnect.msgCodes
|
|
Specifies a case-insensitive character pattern that matches all error messages or error codes that will cause a reconnect attempt.
This property is used for JMS channels with providers other than TIBCO Enterprise Message Service.
Default is * (that is, the wildcard matched by any characters.)
|
be.channel.tibjms.queue.disabled
be.channel.tibjms.topic.disabled
|
|
By default, be-engine connects to all defined channels on startup, including those not mentioned in the CDD file. This is because such channels can be used as output channels. However this is not always desired.
To disable queue or topic connections for specific JMS channels, add the following properties as appropriate. Enter the project path to the JMS channel as the individual value. Use commas or spaces as the delimiter. Use forward slashes in the project path. For example:
be.channel.tibjms.queue.disabled=channels/1jmschannel, channels/3jmschannel
be.channel.tibjms.topic.disabled=channels/2jmschannel channels/4jmschannel
|
be.channel.jms.unified
|
|
By default, TIBCO BusinessEvents creates two connections to a JMS server, with the client IDs.
Set this property value to
true for all agents to create a single connection with the same client ID as specified in the channel resource properties, or in the JMS Connection shared resource, if used. In the unified mode only a single value is required.
Note: When the connection is configured using a JMS Connection shared resource, ensure that the topic and queue connection factories on the JMS Connection shared resource Advanced tab match each other. Also, when using TIBCO Enterprise Message Service, use GenericConnectionFactory for both.
|
be.channel.jms.disallow.dup.clientid
|
|
Specifies whether the duplicate client ID can be used in the engine. When enabled, the engine fails to start when a duplicate client ID is encountered, even if the duplicate client ID is in the second engine.
If the
be.channel.jms.disallow.dup.clientid property is enabled in the default mode (not the unified mode), the JMS channel needs two client IDs (whitespace separated) to startup successfully (one for the queue connection, and one for the topic connection). In the unified mode, only one client ID is required.
|
be.channel.jms.sender.session.pool.maxsize
|
|
Specifies the maximum pool size for the JMS sender session pool. Once set, it activates the JMS sender session pool for each JMS channel in the project. By default no sender session pool is created, and a single shared session is used by sending functions per channel. This property is applicable for the non-transacted mode only. The minimum allowed value of the property is
1.
|