JB, My customer has gone this route and ActiveMQ started, however only the first data source listed (dsmain in your example) was used. Both the messages and locker were using only one datasource.
Any thoughts around that? Regards, Vince On 5/25/21, 12:14 AM, "Jean-Baptiste Onofre" <j...@nanthrax.net> wrote: Hi Vince, It’s possible to have different datasource: one for the main message store, one for the lease locker. As JDBC leaser locker extends persistent adapter, you can pass a datasource. Something like this should work: <persistenceAdapter> <jdbcPersistenceAdapter dataDirectory="${activemq.data}" dataSource="#dsmain" lockKeepAlivePeriod="5000"> <locker> <lease-database-locker dataSource="#dslock" lockAcquireSleepInterval="10000"/> </locker> </jdbcPersistenceAdapter> </persistenceAdapter> You can take a look on https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fblog.nanthrax.net%2F%3Fp%3D422&data=04%7C01%7CVCox%40perforce.com%7Ce18f02c053d0429288b508d91f3367fe%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C637575128536001839%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Lwm3sFt4A01ljkYDnNEyw4o0msVoW2xK%2BBO24tToKKo%3D&reserved=0 <https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fblog.nanthrax.net%2F%3Fp%3D422&data=04%7C01%7CVCox%40perforce.com%7Ce18f02c053d0429288b508d91f3367fe%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C637575128536001839%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Lwm3sFt4A01ljkYDnNEyw4o0msVoW2xK%2BBO24tToKKo%3D&reserved=0> Regards JB > Le 24 mai 2021 à 22:42, Vince Cox <v...@perforce.com> a écrit : > > Are there any future plans with ActiveMQ that will provide separate data source (using JDBC) to handle leader activity and message traffic? We are aware we can use kahaDB and JDBC, but we’d like to have a separate JDBC sources for our message store and our lock. > > Thank you. > > Vince > > > This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately. > CAUTION: This email originated from outside of the organization. Do not click on links or open attachments unless you recognize the sender and know the content is safe. This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.