On October 24, 2018 3:50:59 PM UTC, "Robert J. Carr" <rjc...@gmail.com> wrote:
>> > * if the server is shut down and restarted then everything seems to
>> >disappear, as I then get a 403 when trying to access the protected
>page
>>
>> Expected behaviour here will depend on whether a server shutdown
>shuts
>down Tomcat cleanly. From your description it sounds like it does not.
>
>I just re-ran my test getting the same result, i.e., after a server
>restart
>a previously accessible request now gives a 403. Looking at the logs,
>the
>shutdown seems fine (i.e., nothing above INFO), and there were only a
>few
>lines, but this one might be relevant:
>
>INFO [localhost-startStop-2]
>org.apache.catalina.core.ApplicationContext.log SessionListener:
>contextDestroyed()
Not obviously relevant.
>On subsequent startup there are a lot more logs, but one warning that
>doesn't seem relevant:
>
>WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin
>[SetPropertiesRule]{Server/Service/Engine/Realm/Realm/CredentialHandler}
>Setting property 'keyLength' to '256' did not find a matching property.
>
>But maybe it is?
Something isn't right in the config but I don't think it will affect this.
> There was also this session relevant line:
>
>INFO [localhost-startStop-1]
>org.apache.catalina.core.ApplicationContext.log SessionListener:
>contextInitialized()
Not obviously relevant.
>So not sure what is going on. I'll see if I can figure out if that
>WARNING
>is causing issues. Thanks for the guidance, but please let me know if
>there's anything else I can look at.
Take a look at the raw http. That might give you some clues particularly with
session values.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
