Your client application can take programmatic control of WS-ReliableMessaging sequences. This helps manage resources on the server, for example by removing sequences after a client application has finished messaging. You can add code to create sequences, send acknowledgement requests, close sequences, terminate sequences and wait until sequences are complete.
By closing sequences programmatically, you limit the number of open sequences a single client has to support in a single JVM at one time. This helps avoid the problem described in the following troubleshooting tip: A client receives an out of memory exception message when working with large numbers of open sequences.
For your client application to gain programmatic control over reliable messaging sequences, it needs access to a WSRMSequenceManager instance. Use the following code fragment to achieve this:
import com.ibm.wsspi.wsrm.WSRMSequenceManager; import com.ibm.wsspi.wsrm.WSRMSequenceManagerFactory; ......... // Get the factory WSRMSequenceManagerFactory factory = WSRMSequenceManagerFactory .getInstance(); // Get the sequence manager instance WSRMSequenceManager sequenceManager = factory.createWSRMSequenceManager();
To control WS-ReliableMessaging sequences programmatically, add code to your client application as described in the following steps:
In this information ...Subtopics
| IBM Redbooks, demos, education, and more |