You're suggesting I replace a 4.x deployment with a development snapshot... right.... I'm totally new to ActiveMQ, so can probably be excused for finding this sort of solution quite worrying.
You didn't say whether you considered the exception important by the way. Google doesn't suggest it to be a known issue as you seem to think. And I'm not sure why 5.0 would be considered the release target for 4.x issues either?? What is the issue reference or number you're referring to? rajdavies wrote: > > this really looks like a known issue - I'd recommend using a > ActiveMQ 5.0 pre-release SNAPSHOT - http://people.apache.org/repo/m2- > snapshot-repository/org/apache/activemq/apache-activemq/5.0-SNAPSHOT/ > > cheers, > > Rob > > 'Go Get Integrated - ride the Camel! - http://activemq.apache.org/ > camel/' > http://rajdavies.blogspot.com/ > > > > On Jul 25, 2007, at 11:06 AM, nick_b wrote: > >> >> 4.1.1 >> >> In checking this I've discovered that it's reverted to running >> under Java >> 1.4.2_11, if that's at all relevant. I'll switch it back to 1.5 now. >> >> >> rajdavies wrote: >>> >>> Which version of ActiveMQ are you using ? >>> >>> cheers, >>> >>> Rob >>> 'Integration for the 21st Century - get on the Camel!! - http:// >>> activemq.apache.org/camel/' >>> http://rajdavies.blogspot.com/ >>> >>> >>> >> >> -- >> View this message in context: http://www.nabble.com/ >> JournalPersistenceAdapter-errors-tf4140546s2354.html#a11779666 >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> > > > -- View this message in context: http://www.nabble.com/JournalPersistenceAdapter-errors-tf4140546s2354.html#a11802624 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
