Adrian, thanks for your response. I am aware of the temp message in that version. But this is not original problem in my opinion. I configured a DurableSubscriber for the Topic to keep all the messages in the table. The system is definitely not using temporary topics. It seems that these messages (TXOP='T') are cached while the database is down and (some of them) stored in the table when the database is up again. What I don't understand is why. We do not want transactional JMS for this particular topic so we are using java:ConnectionFactory to send the error logs from an EJB to the JMS system. The messages are deilvered to the JMS and picked up by the MDB although the dtabase is down. So there is actually no need for caching and persisting them at all.
Upgrading to a newer version is unfortunately not an option at this stage. Some configuration bits in 3.2.5 are stored in different configuration files in different directories than in 3.2.2. For the customer this makes it a new release instead of a patch, which means they would have to start the whole test cycle again. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3851150#3851150 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3851150 ------------------------------------------------------- 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
