[
https://issues.apache.org/jira/browse/CAMEL-15320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162210#comment-17162210
]
SAILOKESH DIVI commented on CAMEL-15320:
----------------------------------------
[~acosentino] We are currently running camel in production kubernetes(pod
running camel) listening on pubsub
with 2.25.0 where we build GooglePubsubConnectionFactory as described in the
example and it works fine
Due to open source vulnerabilities we are forced to upgrade to 3.4.0
Till 3.1.0 the GooglePubsubConnectionFactory class is still there so there is
no issue
>From 3.2.0 this class is removed and now we see these issues unable to connect
>to pubsub.
[~acosentino] How is the new handshake handled this error is actually happening
on the component. i followed the same pattern described in one of your IT tests
[https://github.com/apache/camel/blob/camel-3.4.0/components/camel-google-pubsub/src/test/java/org/apache/camel/component/google/pubsub/PubsubTestSupport.java#L72-L79]
Is there anything I am missing here ?
> 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: examples
> 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-2.25.2/examples/camel-example-google-pubsub/src/main/java/org/apache/camel/example/google/pubsub/PubsubUtil.java#L36]
>
> 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)