Re: Apache Camel and IBM MQ

Or on a general-purpose question site like StackOverflow, as I suggested to you last week when you asked what appears to be the same question. (The other) Tim On Mar 12, 2018 10:24 AM, "Timothy Bish" wrote: > On 03/12/2018 12:20 PM, Gupta Bharat wrote: > >> Hello, >> >>

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

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

Re: Apache Camel and IBM MQ

On 03/12/2018 12:20 PM, Gupta Bharat wrote: Hello, Issue: I am routing a message from active mq topic to Ibm mq queue, using Apache camel as the medium between these two. Apache camel is used for intermediate routing and for transformations. I am setting JMSDestination in message header as

Apache Camel and IBM MQ

Hello, Issue: I am routing a message from active mq topic to Ibm mq queue, using Apache camel as the medium between these two. Apache camel is used for intermediate routing and for transformations. I am setting JMSDestination in message header as some topic name(eg: FMP/1.0/a/bguxmb). But when

JDBC persistence is silently falling back to KahaDB, if an error occurs

We are using ActiveMQ 5.15.3 with Wildfly 10. Integration was done as instructed here: http://www.mastertheboss.com/jboss-server/jboss-jms/integrate-activemq-with-wildfly In general it is working fine, but we have found an issue with JDBC persistence. If the password of our db user is wrong,

Re: mKahaDB - no clean-up because of ACKs

Hello Tim. Thanks for the hint about the XA transactions. There were indeed 2 XA transactions hanging in the kahaDB files. After I committed them via JConsole the store was cleaned-up. Joachim -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html