http://www.bea.com/ns/weblogic/920/domain
element synchronous-write-policy

Model

<synchronous-write-policy>annonymous type derived from string</synchronous-write-policy>

Disallowed substitutions (block)

none (extensions, restrictions and substitutions are allowed)

Substitution group exclusion (final)

none (extensions and restrictions are allowed)

Usage

Documentation

The disk write policy that determines how the file store writes data to disk.

This policy also affects the JMS file store's performance, scalability, and reliability. The valid policy options are:

• Direct-Write

  File store writes are written directly to disk. This policy is supported on Solaris, HP-UX, and Windows. On Windows systems, this option generally performs faster than the Cache-Flush option writes.

• Disabled

  Transactions are complete as soon as their writes are cached in memory, instead of waiting for the writes to successfully reach the disk. This policy is the fastest, but the least reliable (that is, transactionally safe). It can be more than 100 times faster than the other policies, but power outages or operating system failures can cause lost and/or duplicate messages.

• Cache-Flush

  Transactions cannot complete until all of their writes have been flushed down to disk. This policy is reliable and scales well as the number of simultaneous users increases.

Privileges: Read/Write

Default Value: Direct-Write

MBean Attribute: JMSFileStoreMBean.SynchronousWritePolicy

Fundamental Facets

equality, non-numeric, unbounded, unordered, countable infinite value space

White Space Processing

preserve

Enumeration Facet

"Disabled", "Cache-Flush", "Direct-Write"