[
https://issues.apache.org/jira/browse/CAMEL-15320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164505#comment-17164505
]
Omar Al-Safi commented on CAMEL-15320:
--------------------------------------
[~loks007divi] as I understood you, before you were using
{{GooglePubsubConnectionFactory}}, which you can provide that to the component
in order to connect to pubsub. After some reading, apparently that was the case
with the legacy google pubsub library that you need add the authentication
explicitly.
However, this is different with the newer google libraries (which now this
camel component supports), the authentication's heavy lifting happens
automatically by Google's library not by the component (as the case
previously). Meaning if you run within the same GKE, you don't need to set any
authentication. Please refer to this
[link|https://github.com/googleapis/google-cloud-java#authentication] for more
info about the authentication.
Also, please refer again to the [component
docs|https://camel.apache.org/components/latest/google-pubsub-component.html]
as modifications might be needed to be added to have your route working with
3.4.
> grpc errors on camel-google-pubsub with apache camel 3.2.0 or higher
> ---------------------------------------------------------------------
>
> Key: CAMEL-15320
> URL: https://issues.apache.org/jira/browse/CAMEL-15320
> Project: Camel
> Issue Type: Bug
> Components: camel-google-pubsub
> Affects Versions: 3.2.0
> Reporter: SAILOKESH DIVI
> Priority: Minor
>
> 1) The current camel examples utilize GooglePubsubConnectionFactory to
> connect to pubsub till 3.1.0
>
> [https://github.com/apache/camel/blob/camel-3.1.0/components/camel-google-pubsub/src/main/java/org/apache/camel/component/google/pubsub/GooglePubsubConnectionFactory.java]
>
> This has been removed from camel 3.2 and above and camel can't connect to
> pubsub with grpc errors
>
>
> WARNING: [Channel<1>:
> (<topicName>?maxMessagesPerPoll=10&concurrentConsumers=1)] Failed to resolve
> name. status=Status{code=UNAVAILABLE, description=Unable to resolve host
> <topicName>, cause=java.lang.RuntimeException: java.net.UnknownHostException:
> <topicName>: Name or service not known at
> io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:436) at
> io.grpc.internal.DnsNameResolver$Resolve.resolveInternal(DnsNameResolver.java:272)
> at io.grpc.internal.DnsNameResolver$Resolve.run(DnsNameResolver.java:228) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748) Caused by:
> java.net.UnknownHostException: <topicName>: Name or service not known at
> java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method) at
> java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:929) at
> java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1324) at
> java.net.InetAddress.getAllByName0(InetAddress.java:1277) at
> java.net.InetAddress.getAllByName(InetAddress.java:1193) at
> java.net.InetAddress.getAllByName(InetAddress.java:1127) at
> io.grpc.internal.DnsNameResolver$JdkAddressResolver.resolveAddress(DnsNameResolver.java:646)
> at io.grpc.internal.DnsNameResolver.resolveAll(DnsNameResolver.java:404) ...
> 5 more
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
