Mantis Bugtracker

Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0000960 [Resin] minor always 02-22-06 14:40 07-26-06 19:02
Reporter ferg View Status public  
Assigned To ferg
Priority urgent Resolution fixed  
Status closed   Product Version 3.0.17
Summary 0000960: .war redeployment
Description (rep by Mike Gleeson)

What?s the recommended way to deploy webapps within Resin containers? The options I?m aware of are
 * using JMX
 * using a deployment product like [^]
 * using ./ stop/start/restart
 * touch the webapp?s web.xml (not tested personally)
 * simply drop in a new war file to the resin home webapps directory

With the last item, this historically is a working feature from Resin 2, but on Fedora Core 3 running Java 1.5 it does the following:
  * existing webapp running ok with 60 or so threads
  * drop in the war file
  * existing webapp threads are not killed off
  * webapp starts up, thread count now about 90, jvm state inconsistent
  * dropping in further war files exhausts memory, et cetera

I would think that stop/restart provides a clean process to bring up the webapp within the jvm, especially for monitoring that the webapp has started correctly, however it would be nice to simply drop in a war file and walk away. Is there a configuration option or perhaps a coding concern regarding singletons and threads as to why this is not currently working correctly?
Additional Information
Attached Files

- Relationships

There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
02-22-06 14:40 ferg New Issue
07-26-06 19:02 ferg Assigned To  => ferg
07-26-06 19:02 ferg Status new => closed
07-26-06 19:02 ferg Resolution open => fixed
07-26-06 19:02 ferg Fixed in Version  => 3.0.20
07-26-06 19:02 ferg Description Updated

Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
27 total queries executed.
24 unique queries executed.
Powered by Mantis Bugtracker