MessageDriven Bean problem.Working but the queues r not getting cleared

Question

I have written a simple message driven bean.It just sends a message to an another queue myadapterqueue
on getting a message .
It is working. But the problem is if I restart my application server then it again reads the messages which had been sent to it earlier.Also the queue size is
not getting to 0 bytes after it has consumed messages.
My application server is JBOSS2.4.3
I think I have to specify some attributes in the
descriptor files.But how??????????????
Here is my code
import java.util.*;
import javax.ejb.*;
import javax.jms.*;
import javax.naming.*;
public class MyMessageBean implements javax.ejb.MessageDrivenBean,javax.jms.MessageListener
     private QueueConnection connect=null;
     private QueueSession session=null;
     private QueueSender sender =null;
private Queue sendQueue=null;
private MessageDrivenContext ctx = null;
     public void setMessageDrivenContext(MessageDrivenContext mdc){
          System.out.println ("In setMessageDrivenContext--------------");
          this.ctx=mdc;
     public void ejbCreate(){
          try{
               System.out.println ("Message bean Created--------------");
               InitialContext jndi=new InitialContext();
               QueueConnectionFactory queueFactory=(QueueConnectionFactory) jndi.lookup("ConnectionFactory");
               connect=queueFactory.createQueueConnection();
               session=connect.createQueueSession (true,Session.AUTO_ACKNOWLEDGE);
               System.out.println ("After session creation--------------");
               sendQueue=(Queue)jndi.lookup("queue/myadapterqueue");
               System.out.println("************ queue/myadapterqueue");
          sender=session.createSender (sendQueue);
          System.out.println ("Before Connection start--------------");
          connect.start();
          }catch(javax.jms.JMSException jmse){
               System.out.println ("In ejbcreate exception-------------------");
               throw new javax.ejb.EJBException();
          }catch(javax.naming.NamingException jne){
               System.out.println ("In ejbcreate exception-------------------");
               throw new javax.ejb.EJBException();
     public void ejbRemove(){
          try{
          System.out.println("ejbRemove done");
          connect.close ();
               this.ctx=null;
          }catch (javax.jms.JMSException jmse){
               System.out.println ("In ejbremove exception-------------------");
               System.out.println("ejbRemove excetion");
               throw new javax.ejb.EJBException();
     public void onMessage(Message msg){
          try{
          this.sender.send (msg);
          this.session.commit();
          System.out.println(" Message");
     }catch(javax.jms.JMSException jmse ){
          jmse.printStackTrace();
here are my descriptors
ejb-jar.xml
<?xml version="1.0"?>
<!DOCTYPE ejb-jar>
<ejb-jar>
<enterprise-beans>
<message-driven>
<ejb-name>MyMessageBean</ejb-name>
<ejb-class>MyMessageBean</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
</message-driven>
</enterprise-beans>
</ejb-jar>
and the correspong xml file for the application server here is jboss.xml
?xml version="1.0" encoding="UTF-8"?>
<jboss>
<enterprise-beans>
     <message-driven>
          <ejb-name>MyMessageBean</ejb-name>
          <configuration-name>Standard Message Driven Bean</configuration-name>
          <destination-jndi-name>queue/MyMessageBeanQ</destination-jndi-name>
     </message-driven>
</enterprise-beans>
</jboss>

Answer 1

it is unclear whether you are commiting on the first queue or second one.
but it appears like you have created a transactional problem across the two queues. although you commit on the first queue, this commit is not extended to the second queue.
things will be fine unless you get an exception of shutdown.
if you shut your message provider down first then you cannot send the message to the second queue. (assuming that queue 2 is also on the same server)
if you shut your MB app server down then you may be in the middle of accepting a onMessage callback from the first queue.
do you have another MB that registers this one as a listener, or are you infact sending a message back onto the same queue...
public void onMessage(Message msg){
try{
     this.sender.send (msg);
     //your server may shutdown here and leave messages on the first queue. and send extra messages on the second.
        this.session.commit();
        System.out.println(" Message");
} catch(javax.jms.JMSException jmse ){
        jmse.printStackTrace();
}