[XSTR-677] Exception when using StringConverter from multiple threads

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Not A Bug
Affects Version/s: 1.4.1
Fix Version/s: None
Component/s: Converters
Labels:
None

JDK version and platform:
Java HotSpot Server VM "1.6.0_07"; Linux

Description

Sharing a StringConverter between multiple threads leads to exceptions (sometimes ArrayIndexOutOfBoundsException, sometimes ConcurrentModificationException). In our scenario, the cache used by the converter is given to the converter's toString() method.
I attach a minimal test case that reproduces the problem on my machine on almost every run.

Thanks for fixing this issue!

Options
- Sort By Name
- Sort By Date
- Ascending
- Descending
- Download All

Attachments

MinimalStringConverterTest.java

11/Oct/11 9:52 AM

0.9 kB

Michael Pradel

Activity

Hide

Permalink

Jörg Schaible added a comment - 11/Oct/11 11:30 AM

This is by design. If you provide a map yourself, you have to ensure that it is synchronized, if you intent to use the converter instance in parallel. If the StringConverter initializes the map itself, it will use a synchronized one to support the most common use case.

Show

Jörg Schaible added a comment - 11/Oct/11 11:30 AM This is by design. If you provide a map yourself, you have to ensure that it is synchronized, if you intent to use the converter instance in parallel. If the StringConverter initializes the map itself, it will use a synchronized one to support the most common use case.

People

Assignee:

Jörg Schaible

Reporter:

Michael Pradel

Votes:

0 Vote for this issue

Watchers:

1 Start watching this issue

Dates

Created:

11/Oct/11 9:52 AM

Updated:

11/Oct/11 11:30 AM

Resolved:

11/Oct/11 11:30 AM