camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zoran Regvart (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-11212) Don't allow Salesforce HTTP client to stop with outstanding requests
Date Fri, 28 Apr 2017 16:01:04 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-11212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Zoran Regvart updated CAMEL-11212:
----------------------------------
    Fix Version/s:     (was: 2.19.1)
                       (was: 2.20.0)
                   2.19.0

> Don't allow Salesforce HTTP client to stop with outstanding requests
> --------------------------------------------------------------------
>
>                 Key: CAMEL-11212
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11212
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-salesforce
>            Reporter: Zoran Regvart
>            Assignee: Zoran Regvart
>             Fix For: 2.19.0
>
>
> The Salesforce component uses Jetty asynchronous client throughout. There is a race condition
that might occur if the component's HTTP client is stopped while one or more requests are
still in progress. The result of which could be inconsistencies in execution.
> This was seen in the implementation of the connectivity validation in the ping check
which creates the {{SalesforceHttpClient}} and {{DefaultRestClient}} and starts/stops then
in a small time frame.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message