ContextListener starting twice

[Allen Williams]

I have a very simple context listener that just sets a context variable at initialization. The action is here:

public class dbConPoolListener implements ServletContextListener
    {
    public void contextInitialized(ServletContextEvent e)
        {
        log.write("\n************\ndbConPoolListener::ContextInitialized");
 
        ServletContext sc= e.getServletContext();
        String nm= sc.getInitParameter("dbName");
        log.write("Got db name: " + nm);
        String dbname= "jdbc/" + nm;
 
        try
            {
            Context ctx= new InitialContext();
            if(ctx==null)
                {
                log.write("dbConPoolListener::ContextInitialized failed to get InitialContext");
                return;
                }
 
            Context ectx = (Context)ctx.lookup("java:comp/env");
            if(ectx==null)
                {
                log.write("dbConPoolListener::ContextInitialized failed to get environment context");
                return;
                }
 
            DataSource ds= (DataSource)ectx.lookup(dbname);
            if(ds==null)
                {
                log.write("dbConPoolListener::ContextInitialized failed to get datasource");
                return;
                }
            sc.setAttribute("DBCPool", ds);
            sc.setAttribute("dbUtils", new dbUtils(sc));
            }
        catch(NamingException ex)
            {
            log.printException(ex, "dbConPoolListener::contextInitialized: ");
            }
 
        log.write("dbConPoolListener::Seems to have run OK\n*******************\n");
        }

Note the "log.write" at the very end. In addition, the dbUtils constructor has a print statement. Here is the deployment descriptor from the web.xml (and I did a search to make sure it is the only one):

  <listener>
    <listener-class>
      dbMgr.dbConPoolListener
    </listener-class>
  </listener>

When this listener is run at initialization, here is what I get in the log file:

SEVERE: No Store configured, persistence disabled

************
dbConPoolListener::ContextInitialized
Jun 23 16:40:45: Got db name: infoisland

Initializing dbUtils with sc; sc, ds= org.apache.catalina.core.ApplicationContextFacade@ed662d null
Jun 23 16:40:45: dbUtils::initPool
Jun 23 16:40:45: dbConPoolListener::Seems to have run OK
******************

Jun 23, 2007 4:40:45 PM org.apache.catalina.session.PersistentManagerBase start
SEVERE: No Store configured, persistence disabled

************
dbConPoolListener::ContextInitialized
Jun 23 16:40:45: Got db name: infoisland

Initializing dbUtils with sc; sc, ds= org.apache.catalina.core.ApplicationContextFacade@b122a1 null
Jun 23 16:40:45: dbUtils::initPool
Jun 23 16:40:45: dbConPoolListener::Seems to have run OK
*******************

Jun 23, 2007 4:40:46 PM org.apache.coyote.http11.Http11BaseProtocol start

In other words, it looks like it is running twice. Any ideas why this would be? In my server.xml, I do have two Contexts with the same docbase. Is that what's causing this?

TIA,
anw

[Bear Bibeault]

Well, yeah. Two contexts means two web apps.

[Ben Souther]

A typical cause for this is an app that is both configured in either server.xml or with a context fragment; and that is located in the tomcat/webapps directory (where it will be auto deployed).