Databases
StackOverflow2013
Postsdbo
POWhy Spring Context not gracefully closed?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy Spring Context not gracefully closed?
    primarykey
    data
    text
    <p>On <code>stop</code> or <code>undeploy/redeploy</code> of a <code>Spring framework 3.0.5</code> based web application following error is logged in <code>Tomcat7's catalina.out</code>:</p> <pre><code>SEVERE: The web application [/nomination##1.0-qa] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@4f43af8f]) and a value of type [org.springframework.security.core.context.SecurityContextImpl] (value [org.springframework.security.core.context.SecurityContextImpl@ffffffff: Null authentication]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak. </code></pre> <p>I initially thought of implementing <code>ServletContextListener</code> and <code>close()</code> the context there. However, found <code>ContextLoaderListener</code> which implements <code>ServletContextListener</code> is set up like so in <code>web.xml</code>:</p> <pre><code>&lt;listener&gt; &lt;listener-class&gt;org.springframework.web.context.ContextLoaderListener&lt;/listener-class&gt; &lt;/listener&gt; </code></pre> <p>From Javadocs:</p> <pre><code>**contextDestroyed** public void contextDestroyed(ServletContextEvent event) Close the root web application context. Specified by: contextDestroyed in interface ServletContextListener </code></pre> <p>So, my question is why the ThreadLocal not cleanly freed by <code>ContextLoaderListener.contextDestroyed()</code>?</p> <p>We are running into <code>PermGen</code> errors and while investigating found this. There is code similar to the following in a few places:</p> <pre><code>ApplicationContext context = WebApplicationContextUtils .getWebApplicationContext(se.getSession().getServletContext()); MyBeanClass x = context.getBean( "myBean", MyBeanClass.class); x.someMethod(); </code></pre> <p>I wonder if the above snippet is stopping a clean shutdown? Any pointers will be greatly appreciated.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USkmansoor
    1. USkmansoor
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POWhy Spring Context not gracefully closed?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhy Spring Context not gracefully closed?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhy Spring Context not gracefully closed?
      1. USMihai Danila
      1. VTFavorite
    1. COI started having this error when breaking my root application context into two. Instead of a single root context with two child servlet contexts, I now have a root context for bootstrap (with the same two child servlet contexts) and I programmatically create a child context later on. The security configuration continues to stay in the root application context in this design, but the leak warnings have appeared now. Clearly this is related in my case to the splitting of the root application context in two.
      singulars
      1. POWhy Spring Context not gracefully closed?
      1. USMihai Danila
    2. CO@Mihai Danila I only have a single application context.
      singulars
      1. POWhy Spring Context not gracefully closed?
      1. USkmansoor
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload