I guess my question is, a JSP is compiled into a single servlet instance that serve multiple requests. How do I make it threadsafe?
相关问题
- Delete Messages from a Topic in Apache Kafka
- Jackson Deserialization not calling deserialize on
- How to maintain order of key-value in DataFrame sa
- StackExchange API - Deserialize Date in JSON Respo
- Difference between Types.INTEGER and Types.NULL in
Servlets are meant to be immutable. Either no state exists outside of method calls (the servlet is stateless), or any such state will never change (so the state that each thread sees is always the same).
It's extremely simple to write a threadsafe servlet: never use instance variables. Use method-local variables.
JSPs are compiled into servlets. All JSP variables are method local (stack) variables hence they are thread safe.
If you directly add a thread-unsafe attribute to a servlet class, it will cease to be thread safe.
Try this: <%@ page isThreadSafe="true" %>
Just don't assign request/session specific data as global/static variables. So as long as you don't use scriptlet declarations
<%! %>
which you assign with request/session specific data and you don't put request/session data in application scope (i.e. as attribute ofServletContext
), then you're safe.See also: