Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Error log when starting tomcat. I have wookie webapp in tomcat/webapps directory.

org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory wookie
org.apache.catalina.core.StandardContext startInternal
SEVERE: Error listenerStart

These are the three lines related to listener in web.xml




Does it make sense to anyone of you?

I have more information

org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class org.apache.wookie.server.ContextListener
java.lang.IllegalStateException: Transaction not initiated or already closed
        at org.apache.wookie.beans.jpa.JPAPersistenceManager.close(
        at org.apache.wookie.beans.util.PersistenceManagerFactory.closePersistenceManager(
        at org.apache.wookie.beans.util.PersistenceManagerFactory.initialize(
        at org.apache.wookie.server.ContextListener.contextInitialized(
        at org.apache.catalina.core.StandardContext.listenerStart(
        at org.apache.catalina.core.StandardContext.startInternal(
        at org.apache.catalina.util.LifecycleBase.start(
        at org.apache.catalina.core.ContainerBase.addChildInternal(
        at org.apache.catalina.core.ContainerBase.addChild(
        at org.apache.catalina.core.StandardHost.addChild(
        at org.apache.catalina.startup.HostConfig.deployDirectory(
        at org.apache.catalina.startup.HostConfig.deployDirectories(
        at org.apache.catalina.startup.HostConfig.deployApps(
        at org.apache.catalina.startup.HostConfig.start(
        at org.apache.catalina.startup.HostConfig.lifecycleEvent(
        at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(
        at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(
        at org.apache.catalina.util.LifecycleBase.setState(
        at org.apache.catalina.util.LifecycleBase.setState(
        at org.apache.catalina.core.ContainerBase.startInternal(
        at org.apache.catalina.core.StandardHost.startInternal(
        at org.apache.catalina.util.LifecycleBase.start(
        at org.apache.catalina.core.ContainerBase.startInternal(
        at org.apache.catalina.core.StandardEngine.startInternal(
        at org.apache.catalina.util.LifecycleBase.start(
        at org.apache.catalina.core.StandardService.startInternal(

Update::: SOLUTION
The above error was caused in my PC due to incorrect servletEngine.context.conf.dir path. servletEngine.context.conf.dir=CATALINA_HOME/conf (incorrect)
servletEngine.context.conf.dir=CATALINA_HOME/conf/Catalina/localhost (correct)
/Catalina/localhost after conf is necessary

share|improve this question
up vote 0 down vote accepted

Have you done all the pre-requisite steps before deploying the webapp as per this list?

share|improve this answer
yes, several times over and with all different combinations eg. used both mysql / mysql5 for db.type. – vivek.m Oct 18 '10 at 13:57
servletEngine.context.conf.dir=CATALINA_HOME/conf/Catalina/localhost ..... /Catalina/localhost after conf is necessary. I do not understand why! conf.dir should need CATALINA_HOME/conf. What's catalina and purpose of localhost file in it. If I will need to run tomcat and apache on different servers, I think there will be many problems again. And why just one improper path created so very much of trouble is beyond me. Anyway, thanks for your answer. you were right. mistake was totally on my side :-) – vivek.m Oct 19 '10 at 9:45
@vivek.m: Well, you fixed it yourself. You could edit your question to add this solution as an update - so it will be useful for future googlers. – JoseK Oct 20 '10 at 5:20

Have you checked disk space? I had a similar issue deploying a web-app and found that my /var partition was at 100% and gave these type of warnings.

share|improve this answer
thanks gdurham. I will keep that in mind for future problems. :) This time source of problem was improper configuration of conf dir path – vivek.m Oct 19 '10 at 9:40

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.