private HttpServletRequest request;
private WebContext(){}

public static WebContext newInstance(HttpServletRequest request){
//case 1:correct
//        WebContext wc = new WebContext();
//        wc.request = request;

//case 2：incorrect
//（to resolve multiply creat WebContext object within one request）
WebContext wc = wcHolder.get();
if(wc==null){
wc = new WebContext();
wc.request = request;
wcHolder.set(wc);
}
return wc;
}

case 1 is correct.

but case 2

first tomcat request..
second request may get the WebContext object which belong to first req.
when step 2 happened，WebContext’s request object had diabled.
then problem happened when operate on the wc and the request object！
the question is:

is one tomcat request is one Thread not right?
how correct above code ?

## comment

Seeing code that captures a reference to an HttpServletRequest leads me to believe that, very soon, you will be posting a question about why your application is behaving strangely, usually confusing a response for one request as another. Be very careful when capturing a reference to a request object somewhere like a ThreadLocal. – Christopher Schultz 3 hours ago

yes，you are right.the problem had happened ,when refresh page repeatly,because get previous request obj by threadLocal.get(). i guess tomcat just assign the same thread for the repeatly browser request that moment.then app throw nullpoint error,i invoke request.getSession().getAtt.. – wangshao 2 hours ago

thanks@John Bollinger,@Christopher Schultz.now the problem had resolved. invoke WebContext.reset(),then method do ThreadLocal.remove(), within spring interceptor.preHandle method.ps thanks more patient for my bad english.i am try better.:) – wangshao 2 hours ago

is one ThreadLocal bind on Thread not right?
A ThreadLocal binds a separate object to each thread, yes. That’s its purpose.

is one tomcat request is one Thread not right?
Each request is handled by exactly one thread, but I’m fairly certain that Tomcat does not spawn a new thread for each request. It uses a thread pool.

Also, different requests in the same session may be served by different threads.

how correct above code ?
If the previous answers don’t explain it then I don’t know, because it’s not clear in what way you consider the behavior you observe to be incorrect.

Nevertheless, if your intent is for each request to have exactly one WebContext, unique to it, then ThreadLocals seem a poor choice for managing that. Request attributes, on the other hand, are designed for exactly that purpose. See ServletRequest.getAttribute(), ServletRequest.setAttribute(), etc..

## 参考资料

stack overflow跳点

• 本文已收录于以下专栏：

### 相关文章推荐

• 2014-09-13 12:46
• 1.07MB
• 下载

• 2011-07-31 10:20
• 46KB
• 下载