Hey Vince, Most likely DB tuning and/or connection lifecycle coordination b/w the connection factory used by ActiveMQ and the database instance. Can’t rule out a bad or flaky database either. If the customer is struggling with keeping the connection pool tuned and consistent, adding more systems is going to increase the surface area for troubleshooting.
Have them open a JIRA and share what they can on the connection settings. Also, they’ll need to coordinate with their DB team to provide some indication as to why the locking is occurring from the DB point of view. Thanks, Matt Pavlovich > On May 24, 2021, at 7:19 PM, Vince Cox <v...@perforce.com> wrote: > > Thanks for replying so quickly Matt. > > Customer is not having and issue with the data in the DB. The issue shows > itself when ActiveMQ randomly has failover events when the lock is in the DB. > It’s using the same connection pool as the store. Seems to be some type of > contention and master slave pair fails over. > > Vince > > Get Outlook for iOS<https://aka.ms/o0ukef> > ________________________________ > From: Matt Pavlovich <mattr...@gmail.com> > Sent: Monday, May 24, 2021 7:43:54 PM > To: users@activemq.apache.org <users@activemq.apache.org> > Subject: Re: ActiveMQ multiple JDBC data sources in same configuration > > Hello Vince- > > Are you able to detail out the use case and rationale for separating the data > store from the locker? On the surface that sounds like creating an extra > runtime coupling with a distributed system— generally that approach creates > more aggregate downtime. > > Thanks, > Matt Pavlovich > >> On May 24, 2021, at 3:42 PM, Vince Cox <v...@perforce.com> wrote: >> >> 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. >
