Hi, Ok - I have read the Wiki, and understand the problem a lot better now. Using the org.jboss.mq.pm.none.PersistenceManager in place of the default JDBC/Hypersonic combination has improved the response of the send() orders of magnitude. We can endure lost messages so this approach might be the best way to go for us.
Apparently this PM does not come bundled with 3.2.3 however, although I managed to obtain the appropriate class files from the 3.2.5 distribution. I would be interested to know why the Oracle based PM setup does not work (as pe my other thread). I might try the latest 3.2.6 release to see if that resolves the SQLException on a write. Thanks and regards, Andrew View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3851675#3851675 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3851675 ------------------------------------------------------- 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
