[ 
https://issues.apache.org/jira/browse/TUSCANY-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518496
 ] 

Kelvin Goodson commented on TUSCANY-1006:
-----------------------------------------

Before we get too far down the line with using the backport ConcurrentHashMap I 
have finally been able to access a page that refers to a license and I think 
there may be an issue

Info from ....
http://www.mvnrepository.com/artifact/backport-util-concurrent/backport-util-concurrent/3.0

maven artifacts are available from maven repo at 
http://ibiblio.org/pub/packages/maven2/backport-util-concurrent/backport-util-concurrent/
the jars there do not contain license files

but the web page says the license is 
http://creativecommons.org/licenses/publicdomain

this license isn't directly mentioned in 
http://people.apache.org/~cliffs/3party.html
and the discussion in ....
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200610.mbox/[EMAIL 
PROTECTED]
doesn't lead me to a firm conclusion either,  but it certainly doesn't give me 
a warm feeling

> ChangeSummaryImpl.cachedSDOObjectChanges appears to not be thread safe
> ----------------------------------------------------------------------
>
>                 Key: TUSCANY-1006
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1006
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SDO Implementation
>    Affects Versions: Java-SDO-beta1
>         Environment: Sun JDK 1.4.2_11, 2-CPU server
>            Reporter: Ron Gavlin
>            Priority: Critical
>             Fix For: Java-SDO-beta1
>
>
> I have an application in which multiple threads access a shared 
> ChangeSummaryImpl. Each thread invokes ChangeSummaryImpl.getOldValues() 
> repeatedly. This causes one or more of the threads to enter an infinite 
> "while (true) -" loop in HashMap.get(Object) with the following stack trace:
> HashMap.get(Object) line: 323
> ChangeSummaryImpl.getOldValues(DataObject) line: 481
> ...
> I suspect this occurs because the access to HashMap cachedSDOObjectChanges is 
> not synchronized. 
> I have been unable as of yet to create a simple test case that demonstrates 
> the problem. In the meantime, I will try to implement a short-term fix by 
> changing line 93 of ChangeSummaryImpl 
> from
> protected HashMap cachedSDOObjectChanges = new HashMap();
> to
> protected Map cachedSDOObjectChanges = Collections.synchronizedMap(new 
> HashMap());
> I will let you know if that fixes the problem. Any insight or assistance you 
> can offer concerning this problem is appreciated. This is a show-stopper 
> problem for us.
> Regards,
> - Ron

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to