You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Ramesh Venkitaswaran (Jira)" <ji...@apache.org> on 2020/07/18 20:45:00 UTC

[jira] [Commented] (CAMEL-15064) Messages no more received from Google Pubsub

    [ https://issues.apache.org/jira/browse/CAMEL-15064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160541#comment-17160541 ] 

Ramesh Venkitaswaran commented on CAMEL-15064:
----------------------------------------------

This issue still seems to persist with camel 3.4.1 When I don't pass GOOGLE_APPLICATION_CREDENTIALS, it silently comes up without any errors, whereas, with Camel 3.1.0, it errors out as expected

> Messages no more received from Google Pubsub
> --------------------------------------------
>
>                 Key: CAMEL-15064
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15064
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-google-pubsub
>    Affects Versions: 3.2.0
>         Environment: * macOS 10.15.4
>  * OpenJDK 11.0.6 2020-01-14
>  * I've been able to reproduce the issue on Ubuntu 16, same JDK
>            Reporter: Jean-Pierre Matsumoto
>            Assignee: Omar Al-Safi
>            Priority: Major
>             Fix For: 3.4.0
>
>
> With Camel 3.2.0, my route does not receive the messages from Google Pubsub. The exact same route works well if I downgrade to 3.1.0.
> I've created following test case to reproduce easily the issue:
> {code:java}
> @Component
> public class SimplePubsubRouteBuilder extends RouteBuilder {
>   @Override
>   public void configure() throws Exception {
>     from("google-pubsub://project-id:subs-name")
>       .to("log:myLog?showHeaders=true");
>   }
> }{code}
> Result with *Camel 3.2.0*: nothing happens, no errors even with DEBUG log
>  level.
> Result with *Camel 3.1.0*: error 404 as expected since Pubsub subscription
>  path is invalid.
> I've tried to fix the issue myself with no success. But by tracing with debugger, I think the issue is because of bad version of Guava library.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)