|
imq.persist.file.message.max_record_size
|
String
|
1m
|
Maximum-size message to add to message storage file
Any message exceeding this size will be stored in a separate file of
its own.
|
|
|
|
|
The value may be expressed in bytes, kilobytes, or megabytes, using
the following suffixes:
b: Bytes
k: Kilobytes (1024 bytes)
m: Megabytes (1024 × 1024 = 1,048,576
bytes)
An unsuffixed value is expressed in bytes.
|
|
|
|
|
Examples:
1600: 1600 bytes
1600b: 1600 bytes
16k: 16 kilobytes (= 16,384 bytes)
16m: 16 megabytes (= 16,777,216 bytes)
|
|
imq.persist.file.destination.message.filepool.limit
|
Integer
|
100
|
Maximum number of free files available for reuse in destination file
pool
Free files in excess of this limit will be deleted. The broker will
create and delete additional files in excess of the limit as needed.
The higher the limit, the faster the broker can process persistent data.
|
|
imq.persist.file.message.filepool.cleanratio
|
Integer
|
0
|
Percentage of files in free file pools to be maintained in a clean (empty)
state
The higher this value, the less disk space is required for the file
pool, but the more overhead is needed to clean files during operation.
|
|
imq.persist.file.message.cleanup
|
Boolean
|
false
|
Clean up files in free file pools on shutdown?
Setting this property to true saves disk space for
the file store, but slows broker shutdown.
|
|
imq.persist.file.sync.enabled
|
Boolean
|
false
|
Synchronize in-memory state with physical storage device?
Setting this property to true eliminates data loss
due to system crashes, but at a cost in performance.
Note –
If running Sun Cluster
and the Sun Cluster Data Service for Message Queue, set this property to true for brokers on all cluster nodes.
|
|
imq.persist.file.transaction.memorymappedfile.enabled
|
Boolean
|
true
|
Use memory-mapped file to store transaction data?
Setting this property to true improves performance
at the cost of increased memory usage. Set to false for
file systems that do not support memory-mapped files.
|
