You use Java™ Message Service (JMS) servers to manage queue and topic resources, and to maintain information about queue stores.
JMS servers and modules provide messaging support. If you use WebLogic Server, you cannot use the loop-back messaging technique for errors that occur in the continuous message processing mode. With WebLogic Server, you cannot set an error queue to be the error queue for itself. Therefore, the error queue clogs after a few errors, depending on the maximum messages per session value of the connection factory.
Because the WebLogic Server error queue clogs after a few errors, only the errors in the front of the queue are processed. The remaining messages are not processed, unless the error messages are deleted. To avoid this issue, set the maximum messages per session value to -1 for the continuous queue connection factory. The -1 value indicates that there is no limit on the number of messages. However, the number of messages is still limited by the amount of remaining virtual storage for the process.
You can set up the following queues:
Queue | Description |
---|---|
Sequential inbound queue | Data comes into the system from external systems that must be run in the order that it is received |
Sequential outbound queue | Data goes out of the system to external systems |
Continuous inbound queue | Data comes into the system from external systems that must not be processed in the order that it is received. It can be run in parallel by multiple message-driven beans (MDBs). |