You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Vince Cox <VC...@perforce.com> on 2021/06/01 13:19:48 UTC

Re: ActiveMQ multiple JDBC data sources in same configuration

JB,

I am investigating this as well. Have you made any other discoveries?

Thank you. I appreciate your time.

Vince

On 5/25/21, 4:08 PM, "Jean-Baptiste Onofre" <jb...@nanthrax.net> wrote:

    Hmm,

    Which ActiveMQ version ?

    It might inherit the main ds from the persistence adapter. I will check tomorrow my time.

    Regards
    JB

    > Le 25 mai 2021 à 18:03, Vince Cox <VC...@perforce.com> a écrit :
    >
    > 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" <jb...@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&amp;data=04%7C01%7CVCox%40perforce.com%7C230af87a86d34051ffb808d91fb8bbc4%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C637575701286906268%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=AU%2F8myyTjqpnA18yYCNe%2BOpkLpB8LtSytRIr3FlQx0I%3D&amp;reserved=0 <https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fblog.nanthrax.net%2F%3Fp%3D422&amp;data=04%7C01%7CVCox%40perforce.com%7C230af87a86d34051ffb808d91fb8bbc4%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C637575701286906268%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=AU%2F8myyTjqpnA18yYCNe%2BOpkLpB8LtSytRIr3FlQx0I%3D&amp;reserved=0>
    >
    >    Regards
    >    JB
    >
    >> Le 24 mai 2021 à 22:42, Vince Cox <VC...@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.
    >



    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.