JMS File Store --> Configuration

JMS File Store --> Configuration

Tasks Related Topics Attributes

Overview

This tab defines general configuration attributes for a JMS file store. A JMS file store consists of a disk-based file that is used for storing persistent messages and durable subscribers.

Tasks

Creating a JMS File Store

Related Topics

WebLogic JMS Fundamentals in Programming WebLogic JMS
Improving JMS File Store Performance

Attributes

Attribute Label

Description

Value Constraints
Name The name of this JMS file store configuration. WebLogic Server uses an MBean to implement and persist the configuration.MBean: weblogic.management.
configuration.
JMSFileStoreMBeanAttribute: Name

Synchronous Write Policy A user-defined policy that determines how the JMS file store writes data to disk. This policy also affects the JMS file store's performance, scalability, and reliability. The valid policy options are: 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. Direct-Write - File store writes are written directly to disk. This policy is supported on Solaris and Windows. If this policy is set on an unsupported platform, the file store automatically uses the Cache-Flush policy instead.
With on-disk caching enabled, the Direct-Write policy can be 2-5 times faster than the Cache-Flush policy, except in highly scalable cases where it may be slightly slower.

With on-disk caching disabled, the Direct-Write policy is faster than the Cache-Flush policy in one-to-many cases, but is much slower otherwise.

The Direct-Write policy scales well with on-disk caching enabled, but does not scale with it disabled. (Solaris does not allowing enabling the on-disk cache for direct writes).
Default: Cache-FlushValid values:
Disabled

Cache-Flush

Direct-Write
Dynamic: yes
Synchronous Write Policy(cont.) Warning! Although the use of the Direct-Write policy is transactionally reliable on Solaris systems, Windows systems may leave transaction data in the on-disk cache without writing it to disk immediately. For more information, see Disabling the On-Disk Cache For a Disk Drive on Windows 2000.Note: If the JMS file store is used exclusively for paging non-persistent messages to disk, the Synchronous Write Policy is ignored. MBean: weblogic.management.
configuration.
JMSFileStoreMBeanAttribute: SynchronousWritePolicy

Directory The pathname to the valid file-system directory where the JMS file store is kept. This attribute is not dynamically configurable. MBean: weblogic.management.
configuration.
JMSFileStoreMBeanAttribute: Directory

Attribute Label	Description	Value Constraints
Name	The name of this JMS file store configuration. WebLogic Server uses an MBean to implement and persist the configuration.MBean: weblogic.management. configuration. JMSFileStoreMBeanAttribute: Name
Synchronous Write Policy	A user-defined policy that determines how the JMS file store writes data to disk. This policy also affects the JMS file store's performance, scalability, and reliability. The valid policy options are: 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. Direct-Write - File store writes are written directly to disk. This policy is supported on Solaris and Windows. If this policy is set on an unsupported platform, the file store automatically uses the Cache-Flush policy instead. With on-disk caching enabled, the Direct-Write policy can be 2-5 times faster than the Cache-Flush policy, except in highly scalable cases where it may be slightly slower. With on-disk caching disabled, the Direct-Write policy is faster than the Cache-Flush policy in one-to-many cases, but is much slower otherwise. The Direct-Write policy scales well with on-disk caching enabled, but does not scale with it disabled. (Solaris does not allowing enabling the on-disk cache for direct writes).	Default: Cache-FlushValid values: Disabled Cache-Flush Direct-Write Dynamic: yes
Synchronous Write Policy(cont.)	Warning! Although the use of the Direct-Write policy is transactionally reliable on Solaris systems, Windows systems may leave transaction data in the on-disk cache without writing it to disk immediately. For more information, see Disabling the On-Disk Cache For a Disk Drive on Windows 2000.Note: If the JMS file store is used exclusively for paging non-persistent messages to disk, the Synchronous Write Policy is ignored. MBean: weblogic.management. configuration. JMSFileStoreMBeanAttribute: SynchronousWritePolicy
Directory	The pathname to the valid file-system directory where the JMS file store is kept. This attribute is not dynamically configurable. MBean: weblogic.management. configuration. JMSFileStoreMBeanAttribute: Directory