Home Forums Oozie Possible memory leak while stopping ozzie.

This topic contains 2 replies, has 2 voices, and was last updated by  Jayashankar VS 11 months, 3 weeks ago.

  • Creator
    Topic
  • #31237

    Jayashankar VS
    Participant

    Team,
    I see a memory leak WARN message when stopping ozzie as a result the JDBC driver is forcibly unregistered during shutdown. May not be a critical issue but thought to give a heads-up in case this turns out to be a major one in the log run. Here is the snippet from the catalina.out log.

    SEVERE: The web application [/oozie] appears to have started a thread named [MySQL Statement Cancellation Timer] but has failed to stop it. This is very likely to create a memory leak.

    INFO: Pausing Coyote HTTP/1.1 on http-11000
    Aug 9, 2013 5:18:46 PM org.apache.catalina.core.StandardService stop
    INFO: Stopping service Catalina
    17:18:46,741 INFO Services:539 – Shutdown
    Aug 9, 2013 5:18:46 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
    SEVERE: The web application [/oozie] registered the JDBC driver [org.apache.derby.jdbc.AutoloadedDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    Aug 9, 2013 5:18:46 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
    SEVERE: The web application [/oozie] registered the JDBC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    Aug 9, 2013 5:18:46 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
    SEVERE: The web application [/oozie] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    Aug 9, 2013 5:18:46 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
    SEVERE: The web application [/oozie] appears to have started a thread named [MySQL Statement Cancellation Timer] but has failed to stop it. This is very likely to create a memory leak.
    Aug 9, 2013 5:18:46 PM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
    SEVERE: The web application [/oozie] created a ThreadLocal with key of type [org.apache.oozie.util.XLog$Info$1] (value [org.apache.oozie.util.XLog$Info$1@4cc7014c]) and a value of type [org.apache.oozie.util.XLog.Info] (value [org.apache.oozie.util.XLog$Info@1d264bf5]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.
    Aug 9, 2013 5:18:47 PM org.apache.coyote.http11.Http11Protocol destroy
    INFO: Stopping Coyote HTTP/1.1 on http-11000

    Thanks,
    Jay

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

  • Author
    Replies
  • #31551

    Jayashankar VS
    Participant

    Hi Yi,
    Yes, MySQL is the back-end DB for Ozzie. Well, when tomcat is shutting down it will eventually try to close the JDBC connectivity as well which is quite normal. But in this case tomcat is unable to disconnect from MySQL in the first attempt may be due to a Ozzie job that got locked and in the subsequent attempt it forces to release the connection from MySQL.

    Thanks,
    Jay

    Collapse
    #31421

    Yi Zhang
    Moderator

    Hi Jay,

    Is mysql the backend database for oozie? Looks like oozie is closing its jdbc connection before it shuts down itself?

    Thanks,
    Yi

    Collapse
Viewing 2 replies - 1 through 2 (of 2 total)