You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Dhiraj Bokde (JIRA)" <ji...@apache.org> on 2015/03/20 22:40:38 UTC

[jira] [Closed] (CAMEL-8517) Salesforce session handling must declare shared fields volatile

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

Dhiraj Bokde closed CAMEL-8517.
-------------------------------
    Resolution: Fixed

Fix merged to branches
 master
 camel-2.12.x
 camel-2.13.x
 camel-2.14.x
 camel-2.15.x


> Salesforce session handling must declare shared fields volatile
> ---------------------------------------------------------------
>
>                 Key: CAMEL-8517
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8517
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-salesforce
>    Affects Versions: 2.13.4, 2.14.2, 2.15.0
>            Reporter: Dhiraj Bokde
>            Priority: Minor
>              Labels: camel-salesforce, salesforce
>             Fix For: 2.14.3, 2.15.1
>
>
> The fields accessToken and instanceUrl in class SalesforceSession could be modified in another thread that does a session refresh, hence they must be declared volatile to synchronize access. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)