My guess is that is something specific to the Grails plugin. It doesn't sound like it should be expected though.
Is it just the first request after starting your app or the first request per user? On Tue, Apr 3, 2018 at 9:21 AM, matero <mat...@gmail.com> wrote: > Hi, > > We're using shiro to secure a Grails application, and it works > fantastically > :) > But we have noted that grails controllers (and only the controllers) are > consuming too much time to init the first time they are accessed. > After fine tunning loggers and debugging we've find out that part of the > problem *seems* to be related to some kind of shiro configuration. This is > what logs are stating: > > 2018-04-03 10:10:13.247 DEBUG --- [ http-nio-8080-exec-4] > o.s.b.f.s.DefaultListableBeanFactory : Returning cached instance of > singleton bean > 'org.springframework.transaction.config.internalTransactionAdvisor' > 2018-04-03 10:10:13.247 DEBUG --- [ http-nio-8080-exec-4] > o.s.b.f.s.DefaultListableBeanFactory : Returning cached instance of > singleton bean 'shiroAttributeSourceAdvisor' > 2018-04-03 10:10:15.478 DEBUG --- [ http-nio-8080-exec-4] > .p.b.ServiceInitLoggingBeanPostProcessor : Initialized > ***.platform.security.UserController in 4507 ms > > as you can see, between accessing the shiroAttributeSourceAdvisor and > statig > that the bean is fully initiallized, there's more than 2 seconds. > Depending on the controller, this lapse goes from 2s to almost 5s. > I'm thinking that there's a missconfiguration on our shiro side. > > I've looked at our realm and the AuthorizationAttributeSourceAdvisor but > all > seems to be working ok. > > Can someone tell me if this is the expected behavior or what should I check > to look for some missconfig or a hint to improve this times, it would be > awesome. > > Regards, > Juanjo > > > > > > -- > Sent from: http://shiro-user.582556.n2.nabble.com/ >
