geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dain Sundstrom <>
Subject Re: [jira] Created: (GERONIMO-132) Adds deployments based on their modification time
Date Mon, 22 Dec 2003 02:12:53 GMT
> The problem is with the DependencyService and scanner. When the 
> scanner picks up a file it's handed over to a planner. The planner 
> tries to deploy it and it succeeds, but see this:
>     [java] 23:44:00,803 DEBUG [JettyWebApplication] 
> jetty:role=WebApplication, 
> uri="file:/c:/projects/geronimo/target/geronim
> o-DEV/deploy/jetty/geronimo-web-console.war" State changed from 
> stopped to starting
>     [java] 23:44:00,844 TRACE [DependencyService] Checking if parent 
> is running: parent=jetty:role=WebContainer
>     [java] 23:44:00,844 TRACE [DependencyService] Cannot run because 
> parent is not running: parent=jetty:role=WebContainer
> which means that although the war was to have deployed, it simply 
> failed as the dependency (WebContainer) was not up. The next time the 
> scanner runs it won't pick up the war as the modification time hasn't 
> changed since the last scan.
> It leds me to a conclusion that it may be a bug with the deployment as 
> a file/directory may be deployed more than once to succeed if there's 
> a dependency that is not started yet.

I just want to clear this one up.  This is not a problem with the 
deployment planner.  The job of the deployment planner it bring a 
deployment into the starting state, after that it is the component 
should watch the system state and transition to running at the 
appropriate time.  The specific problem here is the WebContainer did 
not transition to the running state, which means you need to look 
somewhere else for the real problem.


  * Dain Sundstrom
  * Partner
  * Core Developers Network

View raw message