JMS messages lost

Question

Hi,
I´ve a JMS example put into a Weblogic 9.2 system.
I´ve a persistent store to store my messages, I´m using a Queue.
I´ve a message listener to write my message into a specific table in my BD.
The creation of the messages work great, the messages are created and apear in the specific table.
But i´ve created a on/off switch to the message consuming, and this is my problem. When i turn off the message consuming, and the messaging producer continues, when i turn on the consuming only the first message is consumed, the rest of the messages are lost...
Anyone has any idea what is going on???
This is how i start a JMS connection :
             try {
               InitialContext jndi = new InitialContext();
               // Look up a JMS connection factory
               QueueConnectionFactory conFactory = (QueueConnectionFactory)
                                   jndi.lookup(this.queueDetail.getConnFactoryJNDI());
               //Create a JMS connection
               this.queueConnection = conFactory.createQueueConnection();
               this.queueSession =
                         queueConnection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
               if(this.isClustered)                    
                    this.queue = this.queueSession.createQueue(this.queueDetail.getQueueModuleQueue());
               else
                    this.queue = (Queue)jndi.lookup(this.queueDetail.getQueueJNDI());
          } catch (NamingException e) {
               // TODO Auto-generated catch block
               e.printStackTrace();
          } catch (JMSException e) {
               // TODO Auto-generated catch block
               e.printStackTrace();
          }cheers

Answer 1

Hello Subhankar,
Which Weblogic version are you using? What are the configuration parameters of the JMS queue you defined? During server shutdown/restart, do you see any errors in the server log?
I would suggest you to raise a case with support as it may require an inspection of your environment and settings to find out the root cause.
Regards,
Anuj