FAQ: WebLogic JMS File Store Management
(Doc ID 1307241.1)
Last updated on JUNE 20, 2024
Applies to:
Oracle WebLogic Server - Version 9.2 and laterInformation in this document applies to any platform.
Purpose
Information and frequently asked questions about JMS File store in WebLogic Server (WLS).
Note:
From the document
Oracle® Fusion Middleware
Configuring and Managing JMS for Oracle WebLogic Server
11g Release 1 (10.3.4)
In place of the deprecated JMS stores (JMS file store and JMS JDBC store), JMS servers now support user-defined WebLogic file stores or JDBC stores, which provide better performance and more capabilities than the legacy JMS stores. (The legacy JMS stores are supported for backward compatibility.)
From the document
Oracle® Fusion Middleware
Configuring and Managing JMS for Oracle WebLogic Server
11g Release 1 (10.3.4)
In place of the deprecated JMS stores (JMS file store and JMS JDBC store), JMS servers now support user-defined WebLogic file stores or JDBC stores, which provide better performance and more capabilities than the legacy JMS stores. (The legacy JMS stores are supported for backward compatibility.)
Questions and Answers
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Questions and Answers |
| How Do You Read the JMS File Store .DAT file? |
| Is There a Way to Check Which Messages Were Processed and Which Messages are Still Persisted and Yet to be Processed in a JMS File Store? |
| Will the JMS File Store Keep Growing in Size Indefinitely, and not Shrink in Size when Messages are Processed? |
| References |