JMS Connection Factory Help

Class: com.sybase.jms.server.ConnectionFactory (JMS Connection Factory) EAServer 6.3 Help

Description Allows configuration of JMS generic connection factories for the Sybase JMS provider. Connection factories do not need to be preconfigured unless their properties require non-default values. A JMS client using the Sybase JMS initial context factory (com.sybase.jms.client.InitialContectFactory) can look up preconfigured connection factories by name. To look up connection factories which have not been preconfigured, the client must use a JNDI name ending with "ConnectionFactory" (but not ending with "QueueConnectionFactory" or "TopicConnectionFactory").
See also: JMS Queue Connection Factory, JMS Topic Connection Factory.

Configuration See Set Properties Task.

Properties batchPersistentMessages, batchTransactionCommits, clientID, commandBatchSize, commandBatchWait, disableTransientExceptions, receiveBatchSize, temporaryQueueTemplate, temporaryTopicTemplate

Files Repository/Instance/com/sybase/jms/server/ConnectionFactory/*.properties

Class: com.sybase.jms.server.ConnectionFactory (JMS Connection Factory)	EAServer 6.3 Help

Description	Allows configuration of JMS generic connection factories for the Sybase JMS provider. Connection factories do not need to be preconfigured unless their properties require non-default values. A JMS client using the Sybase JMS initial context factory (com.sybase.jms.client.InitialContectFactory) can look up preconfigured connection factories by name. To look up connection factories which have not been preconfigured, the client must use a JNDI name ending with "ConnectionFactory" (but not ending with "QueueConnectionFactory" or "TopicConnectionFactory"). See also: JMS Queue Connection Factory, JMS Topic Connection Factory.
Configuration	See Set Properties Task.
Properties	batchPersistentMessages, batchTransactionCommits, clientID, commandBatchSize, commandBatchWait, disableTransientExceptions, receiveBatchSize, temporaryQueueTemplate, temporaryTopicTemplate
Files	Repository/Instance/com/sybase/jms/server/ConnectionFactory/*.properties

Property: batchPersistentMessages (Batch Persistent Messages)

Description Allows client-side batching of persistent messages. This may improve throughput for applications that send many persistent messages, but should only be used when the client can resend (potentially) lost messages upon reconnection. See also: commandBatchSize, commandBatchWait

Default Value false

Legal Values false, true

Property: batchPersistentMessages (Batch Persistent Messages)
Description	Allows client-side batching of persistent messages. This may improve throughput for applications that send many persistent messages, but should only be used when the client can resend (potentially) lost messages upon reconnection. See also: commandBatchSize, commandBatchWait
Default Value	false
Legal Values	false, true

Property: batchTransactionCommits (Batch Transaction Commits)

Description Allows client-side batching of transaction commits. This may improve throughput for applications that use transacted sessions, but should only be used when the client can resend (potentially) lost messages upon reconnection. If, for any transaction, all of a client's sent messages are derived from messages received in the same transaction, then this option can be safely enabled even though client failure might result in batched transaction commits not being sent to the server. This is because upon client restart, messages that were previously received but not acknowledged will be received again, and any lost transactions can thus be reissued. See also: commandBatchSize, commandBatchWait.

Default Value false

Legal Values false, true

Property: batchTransactionCommits (Batch Transaction Commits)
Description	Allows client-side batching of transaction commits. This may improve throughput for applications that use transacted sessions, but should only be used when the client can resend (potentially) lost messages upon reconnection. If, for any transaction, all of a client's sent messages are derived from messages received in the same transaction, then this option can be safely enabled even though client failure might result in batched transaction commits not being sent to the server. This is because upon client restart, messages that were previously received but not acknowledged will be received again, and any lost transactions can thus be reissued. See also: commandBatchSize, commandBatchWait.
Default Value	false
Legal Values	false, true

Property: clientID (Client ID)

Description Optional. When a JMS client uses a connection factory with an unspecified clientID, the JMS client will use its TCP/IP host name as a default clientID. If this is insufficient, the client can either use the javax.jms.Connection.setClientID method, or the administrator can create a distinct connection factory for each client (though this is not recommended as it may make the administrator unnecessarily busy).

Property: clientID (Client ID)
Description	Optional. When a JMS client uses a connection factory with an unspecified clientID, the JMS client will use its TCP/IP host name as a default clientID. If this is insufficient, the client can either use the `javax.jms.Connection.setClientID` method, or the administrator can create a distinct connection factory for each client (though this is not recommended as it may make the administrator unnecessarily busy).

Property: commandBatchSize (Command Batch Size)

Description Some communication between a JMS client and the corresponding JMS server can be batched to improve overall message throughput (possibly at the expense of increasing message delivery times). The commandBatchSize property allows configuration of the maximum number of commands that may be contained in a batch. A value of zero indicates that the client should use a builtin default (e.g. 20).
Recommendation: check which value gives the best performance in your environment. Different client applications might benefit from different values. Values that are too large may cause the client to consume excessive amounts of memory. A reasonable starting value for experimentation would be 20.

Default Value 0

Minimum Value 0

Maximum Value 2147483647

Property: commandBatchSize (Command Batch Size)
Description	Some communication between a JMS client and the corresponding JMS server can be batched to improve overall message throughput (possibly at the expense of increasing message delivery times). The commandBatchSize property allows configuration of the maximum number of commands that may be contained in a batch. A value of zero indicates that the client should use a builtin default (e.g. 20). Recommendation: check which value gives the best performance in your environment. Different client applications might benefit from different values. Values that are too large may cause the client to consume excessive amounts of memory. A reasonable starting value for experimentation would be 20.
Default Value	0
Minimum Value	0
Maximum Value	2147483647

Property: commandBatchWait (Command Batch Wait)

Description Some communication between a JMS client and the corresponding JMS server can be batched to improve overall message throughput (possibly at the expense of increasing maximum response times). The commandBatchWait property allows configuration of the maximum time (in milliseconds) that the client will wait for a batch to fill up before sending it to the server incompletely filled.
Recommendation: check which value gives the best performance in your environment. Different client applications might benefit from different values. Values that are too large may cause the unacceptable delays in message delivery. A reasonable starting value for experimentation would be 1 (millisecond).

Default Value 1

Minimum Value 1

Maximum Value 2147483647

Property: commandBatchWait (Command Batch Wait)
Description	Some communication between a JMS client and the corresponding JMS server can be batched to improve overall message throughput (possibly at the expense of increasing maximum response times). The commandBatchWait property allows configuration of the maximum time (in milliseconds) that the client will wait for a batch to fill up before sending it to the server incompletely filled. Recommendation: check which value gives the best performance in your environment. Different client applications might benefit from different values. Values that are too large may cause the unacceptable delays in message delivery. A reasonable starting value for experimentation would be 1 (millisecond).
Default Value	1
Minimum Value	1
Maximum Value	2147483647

Property: disableTransientExceptions (Disable Transient Exceptions)

Description Transient exceptions occur when the JMS client runtime determines that the failure or restart of a server might have resulted in loss of some non-persistent messages. The client can handle these exceptions when they occur, or by installing an exception listener (using the javax.jms.Connection.setExceptionListener method). Or if it is of no concern to the client when non-persistent messages may have been lost, the disableTransientExceptions property can be set to true.

Default Value false

Legal Values false, true

Property: disableTransientExceptions (Disable Transient Exceptions)
Description	Transient exceptions occur when the JMS client runtime determines that the failure or restart of a server might have resulted in loss of some non-persistent messages. The client can handle these exceptions when they occur, or by installing an exception listener (using the javax.jms.Connection.setExceptionListener method). Or if it is of no concern to the client when non-persistent messages may have been lost, the disableTransientExceptions property can be set to true.
Default Value	false
Legal Values	false, true

Property: receiveBatchSize (Receive Batch Size)

Description The JMS client runtime may receive messages in batches to reduce overheads of communication with the JMS server. A value of zero indicates that the client should use a builtin default (e.g. 20).
Recommendation: check which value gives the best performance in your environment. Different client applications might benefit from different values. Values that are too large may cause the client to consume excessive amounts of memory. A reasonable starting value for experimentation would be 20.

Default Value 0

Minimum Value 0

Maximum Value 2147483647

Property: receiveBatchSize (Receive Batch Size)
Description	The JMS client runtime may receive messages in batches to reduce overheads of communication with the JMS server. A value of zero indicates that the client should use a builtin default (e.g. 20). Recommendation: check which value gives the best performance in your environment. Different client applications might benefit from different values. Values that are too large may cause the client to consume excessive amounts of memory. A reasonable starting value for experimentation would be 20.
Default Value	0
Minimum Value	0
Maximum Value	2147483647

Property: temporaryQueueTemplate (Temporary Queue Template)

Description The name of a message queue whose properties will be used as a template in the construction of JMS temporary queues by any sessions associated with this connection factory.

Default Value javax.jms.TemporaryQueue

Property: temporaryQueueTemplate (Temporary Queue Template)
Description	The name of a message queue whose properties will be used as a template in the construction of JMS temporary queues by any sessions associated with this connection factory.
Default Value	javax.jms.TemporaryQueue

Property: temporaryTopicTemplate (Temporary Topic Template)

Description The name of a message topic whose properties will be used as a template in the construction of JMS temporary topics by any sessions associated with this connection factory.

Default Value javax.jms.TemporaryTopic

Property: temporaryTopicTemplate (Temporary Topic Template)
Description	The name of a message topic whose properties will be used as a template in the construction of JMS temporary topics by any sessions associated with this connection factory.
Default Value	javax.jms.TemporaryTopic