That is not correct. It is part of the design of the way the jdbc pm works.
Non persistent messages added to store via the cache don't survive a restart. The cache does not fail just because it couldn't remove the persistent copy at acknowledgement time. It will let the restart tidy it up. The problem in earlier versions was that it was issuing an invalid sql statement | delete from jms_messages where txop='T' and txid=null | which some databases allow, but Oracle interprets correctly. It should have been | delete from jms_messages where txop='T' and txid IS null | It was something I fixed a while ago, but the code had regressed. Since the txid being null is irrelevent anyway, later versions do | delete from jms_messages where txop='T' | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3852077#3852077 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3852077 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
