[jira] [Updated] (CAMEL-11705) Camel-Caffeine: ExpireAfterAccess set two times instead of ExpireAfterWrite

2017-08-25 Thread Andrea Cosentino (JIRA) 

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

Andrea Cosentino updated CAMEL-11705:
-
Fix Version/s: 2.20.0

> Camel-Caffeine: ExpireAfterAccess set two times instead of ExpireAfterWrite
> ---
>
> Key: CAMEL-11705
> URL: https://issues.apache.org/jira/browse/CAMEL-11705
> Project: Camel
>  Issue Type: Bug
>  Components: camel-caffeine
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
> Fix For: 2.20.0
>
>
> In both CaffeineCache and CaffeineLoadCache we have
> {code}
> builder.expireAfterAccess(configuration.getExpireAfterAccessTime(), 
> TimeUnit.SECONDS);
> builder.expireAfterAccess(configuration.getExpireAfterWriteTime(), 
> TimeUnit.SECONDS);
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11705) Camel-Caffeine: ExpireAfterAccess set two times instead of ExpireAfterWrite

2017-08-25 Thread Andrea Cosentino (JIRA) 

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

Andrea Cosentino updated CAMEL-11705:
-
Component/s: camel-caffeine

> Camel-Caffeine: ExpireAfterAccess set two times instead of ExpireAfterWrite
> ---
>
> Key: CAMEL-11705
> URL: https://issues.apache.org/jira/browse/CAMEL-11705
> Project: Camel
>  Issue Type: Bug
>  Components: camel-caffeine
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
> Fix For: 2.20.0
>
>
> In both CaffeineCache and CaffeineLoadCache we have
> {code}
> builder.expireAfterAccess(configuration.getExpireAfterAccessTime(), 
> TimeUnit.SECONDS);
> builder.expireAfterAccess(configuration.getExpireAfterWriteTime(), 
> TimeUnit.SECONDS);
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-11705) Camel-Caffeine: ExpireAfterAccess set two times instead of ExpireAfterWrite

2017-08-25 Thread Andrea Cosentino (JIRA) 

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

Andrea Cosentino updated CAMEL-11705:
-
Description: 
In both CaffeineCache and CaffeineLoadCache we have

{code}
builder.expireAfterAccess(configuration.getExpireAfterAccessTime(), 
TimeUnit.SECONDS);
builder.expireAfterAccess(configuration.getExpireAfterWriteTime(), 
TimeUnit.SECONDS);
{code}

  was:
In both CaffeineCache and CaffeineLoadCache we have

{code}

builder.expireAfterAccess(configuration.getExpireAfterAccessTime(), 
TimeUnit.SECONDS);

builder.expireAfterAccess(configuration.getExpireAfterWriteTime(), 
TimeUnit.SECONDS);
{code}


> Camel-Caffeine: ExpireAfterAccess set two times instead of ExpireAfterWrite
> ---
>
> Key: CAMEL-11705
> URL: https://issues.apache.org/jira/browse/CAMEL-11705
> Project: Camel
>  Issue Type: Bug
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>
> In both CaffeineCache and CaffeineLoadCache we have
> {code}
> builder.expireAfterAccess(configuration.getExpireAfterAccessTime(), 
> TimeUnit.SECONDS);
> builder.expireAfterAccess(configuration.getExpireAfterWriteTime(), 
> TimeUnit.SECONDS);
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)