[jira] [Created] (POOL-275) BaseProxyHandler.pooledObject is not volatile or synch, so is not guaranteed to be safely published.
Sebb created POOL-275: - Summary: BaseProxyHandler.pooledObject is not volatile or synch, so is not guaranteed to be safely published. Key: POOL-275 URL: https://issues.apache.org/jira/browse/POOL-275 Project: Commons Pool Issue Type: Bug Reporter: Sebb BaseProxyHandler.pooledObject is not volatile or synch, so is not guaranteed to be safely published. The class Javadoc does not state whether it is intended to be thread-safe or not, but I would expect the class might be called from multiple threads. One solution would be to make the field volatile. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (POOL-274) Update asm-util to 5.0.3 from 4.0
[
https://issues.apache.org/jira/browse/POOL-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved POOL-274.
---
Resolution: Fixed
{noformat}commit -m "[POOL-274] Update asm-util to 5.0.3 from 4.0."
C:/vcs/svn/apache/commons/trunks-proper/pool/pom.xml
C:/vcs/svn/apache/commons/trunks-proper/pool/src/changes/changes.xml
SendingC:/vcs/svn/apache/commons/trunks-proper/pool/pom.xml
Sending
C:/vcs/svn/apache/commons/trunks-proper/pool/src/changes/changes.xml
Transmitting file data ...
Committed revision 1622064.
{noformat}
> Update asm-util to 5.0.3 from 4.0
> -
>
> Key: POOL-274
> URL: https://issues.apache.org/jira/browse/POOL-274
> Project: Commons Pool
> Issue Type: Improvement
>Affects Versions: 2.2
> Environment: Apache Maven 3.2.3
> (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T16:58:10-04:00)
> Maven home: C:\Java\apache-maven-3.2.3
> Java version: 1.7.0_65, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_65\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>Reporter: Gary Gregory
>Assignee: Gary Gregory
> Fix For: 2.3
>
>
> Update asm-util to 5.0.3 from 4.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (POOL-274) Update asm-util to 5.0.3 from 4.0
Gary Gregory created POOL-274: - Summary: Update asm-util to 5.0.3 from 4.0 Key: POOL-274 URL: https://issues.apache.org/jira/browse/POOL-274 Project: Commons Pool Issue Type: Improvement Affects Versions: 2.2 Environment: Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T16:58:10-04:00) Maven home: C:\Java\apache-maven-3.2.3 Java version: 1.7.0_65, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.7.0_65\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" Reporter: Gary Gregory Assignee: Gary Gregory Fix For: 2.3 Update asm-util to 5.0.3 from 4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (POOL-273) Update cglib to 3.1 from 3.0
[
https://issues.apache.org/jira/browse/POOL-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved POOL-273.
---
Resolution: Fixed
{noformat}
commit -m "[POOL-273] Update cglib to 3.1 from 3.0. "mvn test" OK."
C:/vcs/svn/apache/commons/trunks-proper/pool/pom.xml
C:/vcs/svn/apache/commons/trunks-proper/pool/src/changes/changes.xml
SendingC:/vcs/svn/apache/commons/trunks-proper/pool/pom.xml
Sending
C:/vcs/svn/apache/commons/trunks-proper/pool/src/changes/changes.xml
Transmitting file data ...
Committed revision 1622059.
{noformat}
> Update cglib to 3.1 from 3.0
>
>
> Key: POOL-273
> URL: https://issues.apache.org/jira/browse/POOL-273
> Project: Commons Pool
> Issue Type: Improvement
>Affects Versions: 2.2
> Environment: Apache Maven 3.2.3
> (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T16:58:10-04:00)
> Maven home: C:\Java\apache-maven-3.2.3
> Java version: 1.7.0_65, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_65\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>Reporter: Gary Gregory
>Assignee: Gary Gregory
> Fix For: 2.3
>
>
> Update cglib to 3.1 from 3.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (POOL-273) Update cglib to 3.1 from 3.0
Gary Gregory created POOL-273: - Summary: Update cglib to 3.1 from 3.0 Key: POOL-273 URL: https://issues.apache.org/jira/browse/POOL-273 Project: Commons Pool Issue Type: Improvement Affects Versions: 2.2 Environment: Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T16:58:10-04:00) Maven home: C:\Java\apache-maven-3.2.3 Java version: 1.7.0_65, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.7.0_65\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" Reporter: Gary Gregory Assignee: Gary Gregory Fix For: 2.3 Update cglib to 3.1 from 3.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JCS-119) replace synchronized blocks by java locks or concurrenhashmap
[ https://issues.apache.org/jira/browse/JCS-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14117979#comment-14117979 ] Romain Manni-Bucau commented on JCS-119: [~yogu13] sure and yes java 6 > replace synchronized blocks by java locks or concurrenhashmap > - > > Key: JCS-119 > URL: https://issues.apache.org/jira/browse/JCS-119 > Project: Commons JCS > Issue Type: Improvement >Reporter: Romain Manni-Bucau > Fix For: jcs-2.0 > > > A cache is typically used in a concurrent environment. Since Java 6 using a > ReentrantLock is faster than synchronized so can be interesting to replace > synchronized blocks by a lock. > Places i'm thinking about: > * CompositeCache > * AbstractDoubleLinkedListMemoryCache > * LHMLRUMemoryCache > * DoubleLinkedList > * LRUMap > * SingleLinkedList > * SortedPreferentialArray > Some places where replacing a HashMap by a ConcurrentHashMap can allow to get > rid of synchronized without needing a lock: > * CacheEventQueue > * AbstractDiskCache > * CacheWatchRepairable > There are other places but this is the main I saw. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
