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)?

--
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
>>>
>>>
>>

Reply via email to