A.E: race conditions because no synchronization possible?

udoderk — Sun, 17 Feb 2013 12:51:07 GMT

Hi everybody, i look at org.activiti.explorer.ExplorerApp classpublic class ExplorerApp extends Application implements HttpServletRequestListener { private static final long serialVersionUID = -1L; // Thread local storage of instance for each user protected static ThreadLocal<ExplorerApp>

Re: A.E: race conditions because no synchronization possible?

frederikherema1 — Mon, 18 Feb 2013 08:51:00 GMT

That makes sense… if we add "load-on-statup" parameter in web.xml, the web-application-context will be initialize when he container starts so the servlet init will be called once before the servlet actually starts serving.

The load-on-startup element indicates that this servlet should be loaded (instantiated and have its init() called) on the startup of the web application. The optional contents of these element must be an integer indicating the order in which the servlet should be loaded. If the value is a negative integer, or the element is not present, the container is free to load the servlet whenever it chooses. If the value is a positive 128 integer or 0, the container must load and initialize the servlet as the application is deployed. The container must guarantee that servlets marked with lower integers are loaded before servlets marked with higher integers. The container may choose the order of loading of servlets with the same load-on-start-up value.

However, I imagine the most containers to have a mechanism that prevents the init() to be called twice for the same servlet (when multiple incoming HTTP-calls are done to it when not yet initialized). This is a servlet-specific issue and is independent of the way we handle the thread-local storage of the ExplorerApplication.

topic Re: A.E: race conditions because no synchronization possible? in Alfresco Archive

A.E: race conditions because no synchronization possible?

Re: A.E: race conditions because no synchronization possible?