Service integration custom properties

Use custom properties to configure advanced settings for service integration objects such as messaging engines.

You can use the custom properties page to define the following service integration properties:

Messaging engine custom properties

Set these properties in the messaging engine custom properties panel in the administrative console. To access this panel, click Service integration -> Buses -> bus_name -> [Topology] Messaging engines -> engine_name -> [Additional Properties] Custom properties

sib.msgstore.storeFullWaitForCheckPoint [Fix Pack 13 or later]

This property determines the action a messaging engine takes when a file store is full and applications try to send further messages.

When a file store is full, the messaging engine carries out a checkpoint of the log file to reconcile all message sends and receives since the last checkpoint. This process might take some time to complete. Between the time when the file store becomes full and the time when the checkpoint is complete, if applications try to send a message, the messaging engine throws the exception ObjectStoreFullException and issues message CWSOM1042E.

When an application thread that is sending a message finds that the file store is full, it requests a checkpoint. The default behavior, with the property value set to false, is that the application thread then throws the exception ObjectStoreFullException to the application immediately and returns. You can select an alternative behavior by setting the property value to true. With this property value, the application thread does not throw the exception, but waits until the checkpoint has completed. If the checkpoint frees space in the file store, the application thread proceeds and sends the messages before returning. If the file store is still full after the checkpoint, the application thread throws the exception to the application.

Set the property value to true, and make application threads wait for the checkpoint to be completed, if your applications delete all the messages in the file store, and so they logically know that the file store is no longer full. Although the applications must still wait until the checkpoint is complete, they do not receive exceptions while the checkpoint is being carried out, and they do not have to retry the send.

Data type Boolean
Default False

sib.wsrm.tokenLockTimeout

This property affects WS-ReliableMessaging managed qualities of service. Set this property on the messaging engine that is specified in the policy binding for the WS-ReliableMessaging application.

This property is the amount of time, in milliseconds, that a lock is held on a WS-ReliableMessaging message. If a server fails while processing a message, the lock is released at the end of this timeout period, so that other servers can continue the processing. If the original server recovers before the timeout period ends, it continues processing the message. The lock is released at the end of the timeout period even if the message is still being processed.

If your system is processing large messages, you might want to increase the value of this property. For example, if a message takes 12 minutes to process, the lock is released 2 minutes before processing is complete. To avoid this situation, change the property to a value that is greater than 12 minutes.

If your system is processing small messages, you might want to decrease the value of this property, so that if a failure occurs the lock is released more quickly, and other servers can continue the processing without delay.

[z/OS] Note:

If a servant region ends abnormally while processing a message, the control region starts a new servant region, which must wait for the message lock to be released before it can continue processing the message. If the servant region is inactive for too long, the control region ends it and starts another servant region. Also, if the servant region takes a long time to process a message, the control region might perceive the servant region to be inactive, and end it.

The amount of time that a servant region can remain inactive until the control region ends it is affected by various timeouts, such as the control_region_wlm_dispatch_timeout property. Examine the configuration of your system to determine what this period of time is for that system.

To avoid the control region ending the servant region before the message has been processed, set the value of the token lock timeout property to be less than the amount of time that the servant region can be inactive.

Data type Milliseconds
Default 600000 (10 minutes)



Related reference
[z/OS] Timeout properties summary
Related information
WS-ReliableMessaging policy binding
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Jun 11, 2013 8:40:09 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v701sca&product=was-nd-mp&topic=rjj_custom_props
File name: rjj_custom_props.html