Bug 239073 - [dstore][multithread] assignCacheJar() is to be done after setClient()
Summary: [dstore][multithread] assignCacheJar() is to be done after setClient()
Status: RESOLVED FIXED
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.0.1   Edit
Assignee: David McKnight CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords: contributed
Depends on:
Blocks:
 
Reported: 2008-06-30 23:33 EDT by Noriaki Takatsu CLA
Modified: 2008-07-02 13:33 EDT (History)
1 user (show)

See Also:

Attachments
In multithread, the cache jar should be assigned after setClient() is called (1.61 KB, patch)
2008-06-30 23:42 EDT, Noriaki Takatsu CLA 		mober.at+eclipse: iplog+
Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Noriaki Takatsu CLA 2008-06-30 23:33:05 EDT 
In multithread environment, the cache jar must not be assigned
until DataStore.setClient() is called.
That's because if the cache jar is assigned before calling DataStore.setClient(), the jar will be placed in the wrong location.

The ralated bug is 231639.
Comment 1 Noriaki Takatsu CLA 2008-06-30 23:42:46 EDT 
Created attachment 106202 [details]
In multithread, the cache jar should be assigned after setClient() is called

Legal Message:
 I, {Noriaki Takatsu}, declare that I developed attached code from scratch, 
 without referencing any 3rd party materials except material licensed under 
 the EPL. 
 I am authorized by my employer to make this contribution under the EPL.
Comment 2 Martin Oberhuber CLA 2008-07-01 10:47:32 EDT 
I see no problem with the patch.
Comment 3 David McKnight CLA 2008-07-02 10:02:54 EDT 
I've committed the patch to cvs.