JMS Transport (com.soa.jms)
JMS configuration properties
The time in milliseconds between read operations when there is a failure. A restart is not required if this is changed.
The amount of time that the polling thread will wait before tearing down the connection and rebuilding it when ther is no activity. This is useful for clients that do not report server restarts properly. A value of 0 disables this behavior. A restart is not required if this is changed.
Allow poll timeout behavior to be completely disabled. This is equivalent to setting a poll timeout of 0, but this is now defaulted to disabled. A restart is not required if this is changed.
The number of listener threads per endpoint. This is the number of polling threads that will be created for each listener. Note that each request is handled in a separate thread.
The timeout that each polling thread will use when attempting a read operation. A restart is not required if this is changed.
Control whether responses are set with the correlation ID of the incoming request or with the request message ID. A restart is not required if this is changed.
Control whether JMS listeners operate in a polling fashion or whether they register as JMS MessageListeners. Polling offers better resiliency in the face of broker restarts for some providers where the client libraries may not always detect that the broker has disappeared. For AMQPO this is ignored, AMQP is always non-polled. This requires a restart if any connections have been made to a JMS broker.
The mximum number of request processing threads.
The minimum number of request processing threads.
The request processing thread idle time in milliseconds.
The connection strategy controls how connections are managed. This can be either on a per-provider basis, which will try to minimize the number of connections. Or per-endpoint, which will create a connection for each endpoint, which can mean a connection per destination.
The default acknowledge mode. This can be overridden on a per-endpoint basis. If client mode is selected, any received messages will only be acknowledged after they have been successfully processed.
The maximum size of the session pool.
The minimum size of the session pool.
The maximum idle time in milliseconds for a session before it is closed and removed from the pool.
Should JMS 'header' properties be treated as transport headers?