Mantis - Resin
Viewing Issue Advanced Details
123 minor always 04-25-05 00:00 05-11-05 00:00
user141  
 
normal  
closed 3.0.12  
3.0.12 fixed  
none    
none 3.0.13  
0000123: <dependency-check-interval> does not seem to work with Resin 3.0.12
RSN-114
I have:

  <dependency-check-interval>2s</dependency-check-interval>

in my resin.conf. However, when I drop a WAR file in webapps/ it takes roughly 57 seconds for Resin to discover there's a new file to deploy. Here's the log of my application:

[00:55:55.396][info][sin.Resin3xContainer] Resin 3.0.12 started
[00:55:55.477][info][.resin.ResinDeployer] Deploying [C:\Documents and Settings\Vincent Massol\.maven\repository\cargo\wars\simple-war-0.5-SNAPSHOT.war] to [C:\dev\cargo\samples\java\target\maven\resin3x\testWarHotDeployment\container\webapps]...
[00:55:55.587][dbug][URLDeployableMonitor] Checking URL [http://localhost:8280/simple-war-0.5-SNAPSHOT/index.jsp] [^] for status...
[00:55:55.587][dbug][URLDeployableMonitor] Status: response message [Not Found], response code [404]
[00:55:55.697][dbug][URLDeployableMonitor] Checking URL [http://localhost:8280/simple-war-0.5-SNAPSHOT/index.jsp] [^] for status...
[00:55:55.707][dbug][URLDeployableMonitor] Status: response message [Not Found], response code [404]
[...]
[00:56:51.487][dbug][URLDeployableMonitor] Checking URL [http://localhost:8280/simple-war-0.5-SNAPSHOT/index.jsp] [^] for status...
[00:56:51.487][dbug][URLDeployableMonitor] Status: response message [Not Found], response code [404]
[00:56:51.597][dbug][URLDeployableMonitor] Checking URL [http://localhost:8280/simple-war-0.5-SNAPSHOT/index.jsp] [^] for status...
[00:56:52.979][dbug][URLDeployableMonitor] URL [http://localhost:8280/simple-war-0.5-SNAPSHOT/index.jsp] [^] is responding...

This was working fine on Resin 3.0.9. I've just made the upgrade to 3.0.12 and I'm surprised to discover this.

I would have thought that Resin would check every 2 seconds.

Thanks
-Vincent

Notes
(0000144)
ferg   
04-25-05 00:00   
The timer that checks for .war updates is on a 60s timer.

The class-update-interval checks for updates for a new request on the 2s interval. So if there's no activity (i.e. waiting for a timer), the new .war may not be detected for teh 60s.

If a request comes in before that 60s, the .war will be checked for an update, i.e. you can always force the 2s interval with a new request.
(0000145)
user141   
04-25-05 00:00   
Thanks for the answer but I don't understand: As you can see in the output above, I send a request every 100ms and still this does not trigger a .war check.
(0000146)
user141   
04-25-05 00:00   
Please note that all this was working fine with Resin 3.0.9 and before. My code has not been changed and I have verified that it still work fine with Resin 3.0.9 and Resin 2.x.
(0000147)
sam   
04-25-05 00:00   
Need to check again, given Vincent's statement regarding requests being made every 100ms.
(0000148)
ferg   
04-25-05 00:00   
Because the deployment code has been completely redone for 3.0.13, this bug is closed. If the problem reappears, a new bug needs to be opened against 3.0.13.