[
https://issues.apache.org/jira/browse/POOL-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924578#action_12924578
]
Phil Steitz commented on POOL-174:
----------------------------------
It is not obvious to me that these classes need to be thread-safe. The pools
using them need to be threadsafe, but I don't immediately see why the config
classes need to be threadsafe. Could be I am missing something here. What use
cases do you have in mind for concurrent access to Config classes?
> Configuration classes must be thread-safety
> -------------------------------------------
>
> Key: POOL-174
> URL: https://issues.apache.org/jira/browse/POOL-174
> Project: Commons Pool
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Simone Tripodi
> Assignee: Simone Tripodi
> Fix For: 2.0
>
>
> New Configuration classes added with POOL-173 have to be made thread-safety
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
