[esb-java-dev] [jira] Closed: (ESBJAVA-318) Cache timeout should be
specified in seconds in cache mediator
Evanthika Amarasiri (JIRA)
jira at wso2.org
Tue Dec 18 22:36:04 PST 2007
[ http://wso2.org/jira/browse/ESBJAVA-318?page=all ]
Evanthika Amarasiri closed ESBJAVA-318.
---------------------------------------
Assignee: (was: Ruwan Linton)
Fixed in 1.6-QA-B2. The Cache timeout is specified in second now. The issue will be closed.
> Cache timeout should be specified in seconds in cache mediator
> --------------------------------------------------------------
>
> Key: ESBJAVA-318
> URL: http://wso2.org/jira/browse/ESBJAVA-318
> Project: WSO2 ESB
> Issue Type: Bug
> Affects Versions: 1.5-beta-1
> Environment: Any
> Reporter: Charitha Kankanamge
> Priority: Minor
> Fix For: 1.6-QA-b2
>
>
> Cache timeout should be given in seconds in the cache mediator. Currently it takes millisecond values. Almost all the duration values are specified in seconds in the ESB management console. Therefore it will be better cache mediator settings are also consistent with the rest. It will also be helpful for users if the accepted scale is given in brackets.
> i.e:- Cache Timeout (in seconds)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the Esb-java-dev
mailing list