Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-19161

camel-salesforce - Connection issue when using lazy login

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 3.11.1
    • 4.0.0
    • camel-salesforce
    • None
    • Unknown

    Description

      When we enable lazy login, we end up with an exception of type:

      2023-03-16 16:49:40,743 [main           ] WARN  SalesforceComponent            - Missing property packages, getSObject* operations will NOT work without property rawPayload=true
      2023-03-16 16:49:53,432 [main           ] INFO  SalesforceSession              - Login at Salesforce loginUrl: https://login.salesforce.com/services/oauth2/token
      2023-03-16 16:50:28,009 [main           ] INFO  SalesforceSession              - Login successful
      2023-03-16 16:50:33,456 [forceHttpClient] WARN  SubscriptionHelper             - Handshake failure: {failure={exception=java.lang.IllegalArgumentException: Invalid protocol null, message={ext={replay=true}, supportedConnectionTypes=[long-polling], channel=/meta/handshake, id=1, version=1.0}, connectionType=long-polling}, channel=/meta/handshake, id=1, successful=false}
      2023-03-16 16:50:33,457 [forceHttpClient] INFO  SubscriptionHelper             - Handshaking after unexpected disconnect from Salesforce...
      2023-03-16 16:50:57,019 [forceHttpClient] WARN  SubscriptionHelper             - Handshake failure: {failure={exception=java.lang.IllegalArgumentException: Invalid protocol null, message={ext={replay=true}, supportedConnectionTypes=[long-polling], channel=/meta/handshake, id=2, version=1.0}, connectionType=long-polling}, channel=/meta/handshake, id=2, successful=false}
      2023-03-16 16:51:00,769 [forceHttpClient] WARN  SubscriptionHelper             - Handshake failure: {failure={exception=java.lang.IllegalArgumentException: Invalid protocol null, message={ext={replay=true}, supportedConnectionTypes=[long-polling], channel=/meta/handshake, id=3, version=1.0}, connectionType=long-polling}, channel=/meta/handshake, id=3, successful=false}
      

      After a deeper investigation, it is due to the fact that when creating the BayeuxClient during startup, it calls component.getSession().getInstanceUrl() to build the Url used by the client to connect but the instance Url is null as long as it not connected.

      Attachments

        Activity

          People

            jeremyross Jeremy Ross
            nfilotto Nicolas Filotto
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: