Bug 748990

Description of problem:

Section 2.5 Sender Capacity and Replay requires more details.  At no point does it show how to program sending asynchronous messages and doesn't show the code to check the available capacity or the unsettled messages.

Example this paragraph requires more details:
"The sender can be queried for the available space (the unused capacity), and for the current count of unsettled messages (those held in the replay list pending confirmation by the server). When the unsettled count is zero, all messages on that sender have been successfully sent."

Something like this would be better:
"The sender can be queried for the available space (the unused capacity) using the Sender class method getAvailable(). The current count of unsettled messages (those held in the replay list pending confirmation by the server) can be checked using the Sender class method getUnsettled()." 

It should include some coding example and explicitly mention the appropriate methods and classes. 

Some notes below on an example.

Depending on what you want to do the following is helpful. Assume you've setCapacity to some number.

e.g. sender.setCapacity(MY_CAPACITY);  // set MY_CAPACITY set using and arg 
                                       // not using a #define ;-)

Then:
        bool resend = true;
        while (resend)
        {
          if (sender.getAvailable()>0)
          {
            sender.send(message,false);
            resend = false;
          }
          else
          {
            //  May wish to do nothing here or send to log
            std::cout << "Warning: Capacity full. Retry" << std::endl;
          }
        }

You can check how many are outstanding by using getUnsettled().

e.g. at the end you might want to:

if (sender.getUnsettled())
{
    session.synch();
} 


I will try to rewrite this section and add examples. I'll upload a doc with the info because I may wish to include a table with C++ and Python APIs.

BTW what does a Java developer do for this? Is it part of JMS?  I don't remember MessageProducer having such an API.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: