Destroying a message producer

Question

We have a Sun MQ JMS provider which provides us destinations. The process is something like this:
1. There is a queue, where a message is posted.
2. I have a java consumer, which listens on this queue. (via JNDI lookup).
3. I do some processes and based on the status (success or failure) i put a response message in a different queue(Q2).
4. This Q2 is obtained from the JMS message header (getJMSReplyTo()).
5. sender = session.createSender(Q2);
sender.send(msg, javax.jms.DeliveryMode.PERSISTENT, message.getJMSPriority(), getLifetime());6. message is the textMessage obtained from Q1.
7. In a finally block, i am calling sender.close(); The session is still open and will be used for the next message received from Q1.
All is well and good, except for the fact that number of producers on Q2 is getting accumulated for every send() call. The sender.close() is executed(i debugged in eclipse and no JMS exception for the close() call).
The problem here is in the JMS provider, we have a limitation of 100 producers on Q2. Since every send() call leaves a producer on Q2, after 100 replies, i am getting an error on the SunMQ side "producer cannot be added to the queue. Limit of 100 producers will be exceeded".
This results in a JMS Exception during the session.createSender(Q2) line.
I don't know what i am missing here, and i am pretty new to JMS (as you might have imagined by now).
Do we have to explicitly close the session also along with the sender.close() or do we have to do anything other than closing the sender ?
I'd be happy to hear some suggestions and opinions.

Answer 1

Hmm, so the culprit here is the sender#close() method
The standard JMS API, doesn't say anything about the close() operation. It must be implementation specific, in your case SunMQ,
You should be getting into the API and look for the details on what the close() method actually does, whether it really destroys the message producer or not
As Far As developing a JMS Client, I do this way
• Get a ConnectionFactory and Destination
• Create a Connection and Session
• Create a MessageConsumer
• Create a MessageProducer
• Create message/s
• Send message/s
• Receive message/s synchronously or asynchronously
• Exit Session and Connection
Wonder why you would like to have a new Producer each time, but that depends on you and your requirement :)
Cheers,
Edited by: anamupota on Jan 22, 2009 7:53 AM