Below properties if we add in composite.xml then instances will be dehydrated
By setting these properties we can achieve lot of performance
...
<component name="myBPELServiceComponent">
....
<property name="bpel.config.inMemoryOptimization">true</property>
<property name="bpel.config.completionPersistPolicy">faulted</property>
</component>
bpel.config.inMemoryOptimization
Default value is false. This property can only be set to true if it does not have
dehydration points. Activities like wait, receive, onMessage, and onAlarm create
dehydration points in the process
bpel.config.completionPersistPolicy
This property configures how the instance data is saved. It can only be set at the
BPEL service component level. The following values are available:
■ on (default): The completed instance is saved normally.
■ deferred: The completed instance is saved, but with a different thread and
in another transaction.
■ faulted: Only the faulted instances are saved.
■ off: No instances of this process are saved.
This "dehydration" issue, interesting to me..
ReplyDeleteHi,
ReplyDeleteWe have a BPEL that integrates with service using Request-reply JMS adapters. When the soa-infra schema of the db i close to getting full (>96% ish), we see that there is a severe slowness in such request -reply integration points where the response is picked up from the queue with a delay. As a result, huge number of messages get clogged in teh response queues and the process instances timeout. Any suggestions?