It looks like JDBC journaling configuration has changed between 5.1.0 and 5.4.1. As per the 5.4.1 xml schema (http://activemq.apache.org/schema/core/activemq-core-5.4.1.xsd) the only likely options appear to be:
<persistenceFactory> <journaledJDBC/> </persistenceFactory> and, <peristenceFactory> <journalPersistenceAdapterFactory/> <persistenceFactory> ==journaledJDBC== I attempted to get the first form working because it closely approximated our existing amq 5.1.0 config and because it matched FUSE documentation(http://fusesource.com/docs/broker/5.4/persistence/FuseMBPersistJDBCJournaled.html): <persistenceFactory> <journaledJDBC dataDirectory="${activemq.base}/data-journaledJDBC" dataSource="#oracle-ds"/> </persistenceFactory> Unfortunately that config results in an IllegalStateException. Cannot convert value of type [org.apache.activemq.store.journal.JournalPersistenceAdapter] to required type [org.apache.activemq.store.PersistenceAdapterFactory] for property 'persistenceFactory': no matching editors or conversion strategy found ==journalPersistenceAdapterFactory== <persistenceFactory> <journalPersistenceAdapterFactory dataDirectory="${activemq.base}/d\ ata-journaled" dataSource="#oracle-ds"/> </persistenceFactory> This config seems to work. AMQ starts up and I see activity in the dir specified by dataDirectory. ==QUESTIONS== - What is the difference between using journaledJDBC and journalPersistenceAdapterFactory? - If journaledJDBC is preferred, are there any suggestions on how to resolve the IllegalStateException? Carlos -- View this message in context: http://activemq.2283324.n4.nabble.com/journaled-JDBC-migrating-from-5-1-0-5-4-1-tp2955346p2955346.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
