Anonymous | Login | Signup for a new account | 03-31-2025 18:28 PDT |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0003482 | [Resin] | minor | always | 05-06-09 09:46 | 05-06-09 19:33 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 4.0.1 | Product Version | |||||
Product Build | |||||||||
Summary | 0003482: web-app versioning with ROOT | ||||||||
Description |
(rep by sibyj) I've turned on web-app versioning using: Its working great for non-ROOT named war files and will deploy and direct new user sessions to the newest version of the web-app, without having to restart Resin. For the ROOT web-app, however, I have to restart Resin in order for it to recognize the latest version i.e. If I copy an updated war into webapps like ROOT-1.2.2.war, it will deploy the war file but new user sessions are still directed to the old version. Is this functionality restricted to only non-ROOT web-apps or is this a bug? |
||||||||
Steps To Reproduce | |||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed. 25 unique queries executed. |