Re: Connecting to IBM MQ Cloud using camel JMS component

Hi, What you are describing is direct MQ channel, no MQ JMS. It’s possible to use JMS with IBM MQ but using JMS channel. So, you create the connection factory like this: > class="com.ibm.mq.jms.MQQueueConnectionFactory"> > > > > > > >

Re: Google pubsub component broken in 3.2.0 ?

Hi Omar Sure, I have created CAMEL-15064. HTH JeanPierre >

Re: Basic authentication of WAB using Jaas in Karaf

Thanks Alex, the API now is working after removing the "httpRegistry" part. Now I've the next issue. My org.ops4j.pax.web.context-admin.cfg looks like bundle.symbolicName=api.xml login.config.authMethod=BASIC login.config.realmName=karaf context.id=default security.constraint.1.url =

Connecting to IBM MQ Cloud using camel JMS component

Hello community Has anyone tried connecting to IBM Cloud MQ via camel jms component? I see it needs an implementation of javax.jms.ConnectionFactory. One of the implementations provided of above interface by IBM is com.ibm.mq.jms.MQConnectionFactory. The MQ cloud provides following information

problem when using basic Auth with sslcontext and proxy Auth using camel-http4

Dear Team, need your help to resolve this issue. I have a requirement to implement proxy authentication with basic auth. but while i was adding proxyAuthUsername and ProxyAuthPassword i am getting HTTP 401 error from target server. below is the http end point : https4://

Re: [SECURITY] New security advisory CVE-2020-11972 released for Apache Camel

Let me add the credit too Credit: This issue was discovered by Colm O. HEigeartaigh from Apache Software Foundation -- Andrea Cosentino  -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2

[SECURITY] New security advisory CVE-2020-11973 released for Apache Camel

A new security advisory has been released for Apache Camel, that is fixed in the recent 2.25.1 and 3.2.0 releases. CVE-2020-11973: Apache Camel Netty enables Java deserialization by default Severity: MEDIUM Vendor: The Apache Software Foundation Versions Affected: Camel 2.25.0, Camel 3.0.0 to

[SECURITY] New security advisory CVE-2020-11972 released for Apache Camel

A new security advisory has been released for Apache Camel, that is fixed in the recent 2.25.1 and 3.2.0 releases. CVE-2020-11972: Apache Camel RabbitMQ enables Java deserialization by default Severity: MEDIUM Vendor: The Apache Software Foundation Versions Affected: Camel 2.25.0, Camel 3.0.0

[SECURITY] New security advisory CVE-2020-11971 released for Apache Camel

A new security advisory has been released for Apache Camel, that is fixed in the recent 2.25.1 and 3.2.0 releases. CVE-2020-11971: Apache Camel JMX Rebind Flaw Vulnerability Severity: MEDIUM Vendor: The Apache Software Foundation Versions Affected: Camel 2.25.0, Camel 3.0.0 to 3.1.0. The

Re: Google pubsub component broken in 3.2.0 ?

Hi Jean, I recall there was major work being done on this component and indeed, it looks to me like a bug with the associated work that was being done. Can you please file this issue as bug report under https://issues.apache.org/jira/browse/CAMEL in order to be investigated further? Regards,

Google pubsub component broken in 3.2.0 ?

Hi all Previously I used Camel 3.0.0 for my mixture of google-pubsub and google-mail routes. I've tried to update to Camel 3.2.0 but pubsub part is not working, with no error message. I've traced with debugger. I think the issue is with bad version of Guava library. Anyway, here is a simple

InvalidPayloadException: No body available of type ... concurrency issue?

Camel: 2.15.3 (I know «outdated») When I «call» one of our routes "concurrently" I am getting: java.lang.reflect.UndeclaredThrowableException: null at ch.mysign.prj.interfaces.campaign.$Proxy54.getCodeMessage(Unknown Source) at