Bugs item #804485, was opened at 2003-09-11 16:50
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=804485&group_id=22866

Category: JBossMQ
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Udo Schwedt (schwedt)
Assigned to: Nobody/Anonymous (nobody)
Summary: JMS message lost on restart

Initial Comment:
Hello all,



the following problem occurs on both JBoss 3.2.1 and

3.2.2RC3. I'm running Sun VM 1.4.1_03-b02 on Win2K Pro.



With a MDB which listens on a queue using the file

based PM, when the server is stopped and started again

while JMS are left to consume, exactly one message is lost.



To reproduce, set up a simple client and MDB. The

client connects to the queue and sends some 50

persistent messages (with an increasing number) to the

queue. The MDB's onMessage() method does nothing but to

trace the received message and sleep for 10 seconds.

When the server is stopped (Ctrl-C) before all messages

were consumed, all messages not consumed yet can be

found in the persistence directory for the queue,

except the message immediately following the latest

consumed message (Dead letter queue is empty).



If the server is restarted, the remaining persisted

messages are processed, but one message is lost.



Also see files in attached ZIP archive: 

- server trace for server 1 (before restart)

- server trace for server 2 (after restart)

- source for the client

- source and XML files MDB

- relevant server configuration files



In the example files, message no. 16 is lost.



BTW: the exception in the server 1 trace:



16:24:59,232 ERROR [JMSContainerInvoker] Exception in

JMSCI message listener

java.lang.NullPointerException

        at

org.jboss.ejb.plugins.jms.JMSContainerInvoker.invoke(JMSContainerInvoker.java:728)

        at

org.jboss.ejb.plugins.jms.JMSContainerInvoker$MessageListenerImpl.onMessage(JMSContainerInvoker.java:1020)

        at

org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:241)

        at

org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:636)

        at

org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:442)

        at org.jboss.mq.SpySession.run(SpySession.java:294)

        at

org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:177)

        at

EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:732)

        at java.lang.Thread.run(Thread.java:536)



occurs on shutdown and looks just like the exception

mentioned in bug no. 781687 - I thought the bug was

already fixed (or didnt the fix make in in 3.2.2RC3)?







----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=804485&group_id=22866


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to