Re: JDBC persistence is silently falling back to KahaDB, if an error occurs
That's great, thank you for doing that. Tim On Tue, Mar 13, 2018 at 12:45 AM, swclhard wrote: > JIRA issue was created: > > https://issues.apache.org/jira/browse/AMQ-6926 > > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html >
Re: JDBC persistence is silently falling back to KahaDB, if an error occurs
JIRA issue was created: https://issues.apache.org/jira/browse/AMQ-6926 -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: JDBC persistence is silently falling back to KahaDB, if an error occurs
Would you be willing to submit a bug in JIRA for this issue? Tim On Mar 12, 2018 10:39 AM, "swclhard" wrote: > Looks like an issue with vm connector. > > Now we are working around by using the tcp connector. In case that password > is wrong, no broker is available and incoming requests are refused. > > We will use a startup Singleton bean to check, if broker is available, so > that startup fails, if there is something wrong. > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html >
Re: JDBC persistence is silently falling back to KahaDB, if an error occurs
Looks like an issue with vm connector. Now we are working around by using the tcp connector. In case that password is wrong, no broker is available and incoming requests are refused. We will use a startup Singleton bean to check, if broker is available, so that startup fails, if there is something wrong. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html