So, it's gotta be something simple I'm missing. I decided to construct a trivial test of parallel deployment.
Couldn't be simpler (http://www.javacodegeeks.com/2011/06/zero-downtime-deployment-and-rollback.html?m=1): $ mkdir WEB-INF $ echo "" > WEB-INF/web.xml $ echo 'old version ' > index.jsp $ jar cf foo##001.war WEB-INF index.jsp $ echo 'NEW version ' > index.jsp $ jar cf foo##002.war WEB-INF index.jsp 1) Copy foo##001.war to webapps & visit /foo. Results as expected ('old version'). 2) Copy foo##002.war to webapps & reload /foo. Results surprise me ('NEW version ') What am I missing here? -- Jonathan Rosenberg Founder & Executive Director Tabby's Place, a Cat Sanctuary http://www.tabbysplace.org/ On Fri, Aug 12, 2011 at 4:08 AM, Pid <p...@pidster.com> wrote: > On 12/08/2011 04:01, Jonathan Rosenberg wrote: >> Trying to fall asleep and just had a thought on my problem: are >> context-param values shared across different context versions (as >> implemented in parallel deployment)? > > Nope. The apps are self-contained. > > C > > > > >> -- >> JR >> On Aug 11, 2011 6:10 PM, "Jonathan Rosenberg" <j...@tabbysplace.org> wrote: >>> BTW: I'm using >>> >>> Apache Tomcat/7.0.6 JDK 1.6.0_22-b04 >>> >>> on Linux. >>> >>> -- >>> Jonathan Rosenberg >>> Founder & Executive Director >>> Tabby's Place, a Cat Sanctuary >>> http://www.tabbysplace.org/ >>> >>> >>> On Thu, Aug 11, 2011 at 6:00 PM, Jonathan Rosenberg <j...@tabbysplace.org> >> wrote: >>>> Great idea. I just retested aith Firebug & the JSESSIONIDs are >> identical. >>>> >>>> Ideas, anyone? >>>> >>>> -- >>>> Jonathan Rosenberg >>>> Founder & Executive Director >>>> Tabby's Place, a Cat Sanctuary >>>> http://www.tabbysplace.org/ >>>> >>>> >>>> On Thu, Aug 11, 2011 at 5:01 PM, Mark Thomas <ma...@apache.org> wrote: >>>>> On 11/08/2011 21:56, Jonathan Rosenberg wrote: >>>>>> Following up on my post the other day ... I figured out a clean way to >>>>>> generate a Catalog##~~~.war Grails app that just yields an outage >>>>>> page. >>>>>> >>>>>> Today I deployed & tested & sessions are not behaving as I expected. >>>>>> Here's what I have >>>>>> >>>>>> 1) Deployed Catalog##0002.war.& started. >>>>>> 2) Access app (/Catalog) & start a session (confirmed in Tomcat >> Manager). >>>>>> 3) Deploy Catalog##~~~.war & started. >>>>>> 4) Access app again (/Catalog). I immediately get the outage page. >>>>>> 5) Stop Catalog##~~~. >>>>>> 5) Access /Catalog. Session is back. >>>>>> >>>>>> I was expecting to see the original app, not an outage page. I >>>>>> checked in Manager & it shows 1 session associated with Catalog##0002 >>>>>> and none with Catalog##~~~, as expected. >>>>>> >>>>>> Am I confused as to what should be happening? >>>>> >>>>> Use fiddler, firebug or similar to look at the headers being sent to >>>>> Tomcat. Check the session IDs match up. >>>>> >>>>> Mark >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >>>>> For additional commands, e-mail: users-h...@tomcat.apache.org >>>>> >>>>> >>>> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
