PERSISTENT and NON_PERSISTENT. A client marks a message as persistent if it feels that the application will have problems if the message is lost in transit. A client marks a message as non-persistent if an occasional lost message is tolerable. Clients use delivery mode to tell a JMS provider how to balance message transport reliability with throughput.
| Member Name | Description |
|---|---|
| NON_PERSISTENT | This is the lowest-overhead delivery mode because it does not require that the message be logged to stable storage. The level of JMS provider failure that causes a NON_PERSISTENT message to be lost is not defined. A JMS provider must deliver a |
| PERSISTENT | This delivery mode instructs the JMS provider to log the message to stable storage as part of the client's send operation. Only a hard media failure should cause a PERSISTENT message to be lost. |
Namespace: WebLogic.Messaging
Assembly: WebLogic.Messaging (in WebLogic.Messaging.dll)