|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 960 | minor | always | 02-22-06 14:40 | 07-26-06 19:02 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | urgent | OS Version: | |||
| Status: | closed | Product Version: | 3.0.17 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.0.20 | ||
|
|
|||||
| 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 http://cargo.codehaus.org/ [^] * using ./httpd.sh 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? |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |