How to get make thread class instance if they are cached for next time

Question

I have a context class. So I create an instance of a class. Since this class performs tough and costly mathematical operation I don't want to do it every time. So I am caching the class.

What if as I am creating a new instance what if another thread comes and get the same instance from the cache?

Is there any solution to this problem...?

Can you show some code? Otherwise I'd say, just synchronize the class provider... — fge, Dec 16 '11 at 13:57
you have a simple [synchronization problem](http://docs.oracle.com/javase/tutorial/essential/concurrency/sync.html) !! — Santosh, Dec 16 '11 at 14:03
Loading a class is not costly, even if you have many lines. But executing a long process may be costly. You don't cache classes, you cache data. You cache an instance of an object in order not to have to load it (usually, caching is done on database data). Maybe I didn't understood your problem, please me more precise and use the correct terms. — Jean-Philippe Briend, Dec 16 '11 at 14:05

score 0 · Answer 1 · answered Dec 16 '11 at 14:07

0

Since you have not mentioned any code, the simplest suggestion is make your class Immutable. This means the state of class, once initialized cannot be changed. Request you to post some sample/representative code.

answered Dec 16 '11 at 14:07

Santosh

17,667
4
54
79

score 0 · Answer 2 · answered Dec 16 '11 at 14:59

0

Depends on cache implementation. Highly depends on which parts of it you can control.

answered Dec 16 '11 at 14:59

RokL

2,663
3
22
26

score 0 · Answer 3 · edited May 23 '17 at 11:48

I believe you are talking about protecting your cache from race conditions. Race conditions happen when two or more threads are accessing a shared resource (in this case your cache) at the same time without proper protection.

There are many ways that you can protect your cache from improper multithreaded access. Without having the details or showing us some code, it's hard to be specific but consider some of the following techniques.

Use of the synchronized keyword of course could help protect the cache from race conditions. The thread adding the instance of your class to cache would synchronize on the cache when it is inserted. Threads getting the instance from the cache would synchronize as well.
If the instance of your class should only be used by one thread at a time then you could use a BlockingQueue with a size of one. The instance of your class could be added to the queue and the threads would wait until one gets the instance. When done it would put it back in the BlockingQueue letting the next thread get the class.
Make sure that the instance of your class is fully initialized when it is put into the cache.

If you edit your question and provide a code sample or more details we can help you better.

Joonas Pulakka · Answer 4 · 2011-12-16T15:13:37.390

You could create a thread-local cache to avoid sharing cached instances with different threads:

class CostyThingCache { 

    static ThreadLocal<CostyClass> cache = new ThreadLocal<CostyClass>() {

        // This gets called once ever per thread:
        @Override
        protected CostyClass initialValue() {
            return new CostyClass();
        }

    };

    static CostyClass getCostyThing() {
        return cache.get();
    }

}

Alternatively, serialize (synchronize) access to the costy object and create only one of them. Which of these alternatives is better depends totally on what you're actually doing.

How to get make thread class instance if they are cached for next time

4 Answers4