I'm not trying to discount the issue, you are not alone in reporting it (and I very well could have something different in my configuration). I'm just trying to help track down the reproduce case.
Any idea if the EnvironmentLoaderListener getting called initialized first in your case? I'm using your "tomcat-web" example to test with On Fri, Mar 8, 2019 at 12:53 AM Francois Papon <[email protected]> wrote: > It's weird because I'm not the only one who have this error... > > I used oracle-jdk-8 and Tomcat 9.0.6. > > Can you tried with my example repo? > > https://github.com/fpapon/shiro-labs/tree/master/tomcat-web > > May be I'm missing something... > > François Papon > [email protected] > > Le 07/03/2019 à 23:49, Brian Demers a écrit : > > I still cannot reproduce this. > > > > I tried with 8.5.32 and 9.0.16 (with OpenJDK Runtime Environment > > Corretto-11.0.2.9.1 and OpenJDK 64-Bit Server VM Corretto-8.202.08.2) > > > > Side note: only Tomcat 8.0 is EOL, 7, 8.5, and 9 are _active_ > > > > On Wed, Mar 6, 2019 at 1:10 PM Francois Papon < > [email protected]> > > wrote: > > > >> Hi Thibault, > >> > >> Can you make a test by adding this in the shiro.ini file? > >> > >> under the [main] section: > >> > >> filterChainResolver = > >> org.apache.shiro.web.filter.mgt.PathMatchingFilterChainResolver > >> > >> regards, > >> > >> François Papon > >> [email protected] > >> > >> Le 06/03/2019 à 22:05, Thibault TIGEON a écrit : > >>> The solution is to add this configuration in the shiro.ini file: > >>> > >>> filterChainResolver = > >>> org.apache.shiro.web.filter.mgt.PathMatchingFilterChainResolver > >
