Grails support for Togglz?

ron rittinger

unread,

Oct 27, 2014, 10:43:39 AM10/27/14

to togglz...@googlegroups.com

I'd like to add the togglz infrastructure to my grails 2.3.5 project (which uses maven to manage my dependencies).

Is this possible? Can someone provide an example?

ron rittinger

unread,

Oct 28, 2014, 1:16:52 PM10/28/14

to togglz...@googlegroups.com

always getting the same error no matter how I try to configure the FeatureManager:

2014-10-28 13:11:15,236 [http-bio-8080-exec-4] ERROR errors.GrailsExceptionResolver - IllegalStateException occurred when processing request:

Could not find the FeatureManager. For web applications please verify that the TogglzFilter starts up correctly. In other deployment scenarios you will typically have to implement a FeatureManagerProvider as described in the 'Advanced Configuration' chapter of the documentation.. Stacktrace follows:

Message: Could not find the FeatureManager. For web applications please verify that the TogglzFilter starts up correctly. In other deployment scenarios you will typically have to implement a FeatureManagerProvider as described in the 'Advanced Configuration' chapter of the documentation.

also creating an implementation of the TogglzBootstrap class:

@Component("togglzBootstrap")

public class TogglzBootstraper implements TogglzBootstrap {

public FeatureManager createFeatureManager(){

return new FeatureManagerBuilder().togglzConfig(new MyTogglzConfiguration()).build();

}

Which is called (as I added debug statements within the MyTogglzConfiguration class) but nothing works.

Christian Kaltepoth

unread,

Oct 30, 2014, 4:16:25 AM10/30/14

to togglz...@googlegroups.com

Could you tell us more about your setup. Which dependencies did you add to your project? Did you add anything to web.xml manually?

--

Christian Kaltepoth

Blog: http://blog.kaltepoth.de/

Twitter: http://twitter.com/chkal

GitHub: https://github.com/chkal

ron rittinger

unread,

Oct 30, 2014, 8:27:03 AM10/30/14

to togglz...@googlegroups.com

Even though this is a grails project, we use maven to manage our dependencies. The following dependencies are found in my pom:

togglz-core
togglz-servlet
togglz-spring
togglz-console
togglz-slf4j

Once I adjusted the log level to debug, I see the following in the console:

2014-10-29 15:40:57,154 [http-bio-8080-exec-1] DEBUG context.FeatureContext - No cached FeatureManager for class loader: org.grails.plugins.tomcat.ParentDelegatingClassLoader@42404f33

2014-10-29 15:40:57,157 [http-bio-8080-exec-1] DEBUG context.FeatureContext - Found 5 FeatureManagerProvider implementations...

2014-10-29 15:40:57,157 [http-bio-8080-exec-1] DEBUG context.FeatureContext - No FeatureManager provided by org.togglz.core.context.ThreadLocalFeatureManagerProvider

2014-10-29 15:40:57,162 [http-bio-8080-exec-1] DEBUG context.FeatureContext - No FeatureManager provided by org.togglz.core.context.BeanFinderFeatureManagerProvider

2014-10-29 15:40:57,163 [http-bio-8080-exec-1] DEBUG context.FeatureContext - No FeatureManager provided by org.togglz.core.context.StaticFeatureManagerProvider

2014-10-29 15:40:57,163 [http-bio-8080-exec-1] DEBUG context.FeatureContext - No FeatureManager provided by org.togglz.core.context.ContextClassLoaderFeatureManagerProvider

2014-10-29 15:40:57,163 [http-bio-8080-exec-1] DEBUG context.JNDIFeatureManagerProvider - FeatureMananger not found: Name [FeatureManager] is not bound in this Context. Unable to find [FeatureManager].

2014-10-29 15:40:57,163 [http-bio-8080-exec-1] DEBUG context.FeatureContext - No FeatureManager provided by org.togglz.core.context.JNDIFeatureManagerProvider

I know my 'TogglzConfig' implementation is being loaded by spring as I added a print statement in the no args constructor.

I think the problem is, where Grails loads it's spring beans is not the same place Togglz is looking for them? I'm looking at the source code for the BeanFinderFeatureManagerProvider class to see how this works.

And no, our Grails projects normally do not have a web.xml file that I modify (it's generated when producing our WAR).

I've also tried creating my own FeatureManagerProvider, my own TogglzBootstrap class, etc. but it's always the same issue .... my classes are instantiated via Spring but the togglz infrastructure never sees them.

On Monday, October 27, 2014 10:43:39 AM UTC-4, ron rittinger wrote:

Christian Kaltepoth

unread,

Oct 30, 2014, 2:09:16 PM10/30/14

to togglz...@googlegroups.com

It would be interesting to see what happens in this class:

https://github.com/togglz/togglz/blob/master/spring/src/main/java/org/togglz/spring/spi/SpringBeanFinder.java#L13

That's the code that should "find" your Spring managed TogglzBootstrap class.

ron rittinger

unread,

Oct 30, 2014, 2:43:30 PM10/30/14

to togglz...@googlegroups.com

I copied code from Togglz into my controller, the bottom bit is from the SpringBeanFinder and in my Controller, it finds the been. Below is my code and the output to the console:

The code in the controller (I just used a dummy action to trigger this logic):

Iterator<FeatureManagerProvider> iterator = ServiceLoader.load(FeatureManagerProvider.class).iterator();

while (iterator.hasNext()) {

println "Looking for FeatureManagerProvider="+iterator.next()

}

iterator = ServiceLoader.load(BeanFinder.class).iterator();

while (iterator.hasNext()) {

def beanFinder = iterator.next()

println "found a BeanFinder: $beanFinder"

Collection<FeatureManager> result = beanFinder.find(FeatureManager.class, null);

if (result != null) {

println "Found a featureManager, result=$result"

}

iterator = ServiceLoader.load(FeatureManager.class).iterator();

while (iterator.hasNext()) {

println "Looking for FeatureManager="+iterator.next()

}

println "end of our ServiceLoader logic"

def context = servletContext

def clazz = FeatureManager.class

// use the Spring API to obtain the WebApplicationContext

WebApplicationContext applicationContext = null;

Collection<Object> result = new ArrayList<Object>();

if (context instanceof ServletContext) {

applicationContext = WebApplicationContextUtils.getWebApplicationContext((ServletContext) context);

}

if (applicationContext == null) {

applicationContext = ContextLoader.getCurrentWebApplicationContext();

}

// may be null if Spring hasn't started yet

if (applicationContext != null) {

// ask spring about beans of this type

result.addAll(applicationContext.getBeansOfType(clazz).values());

}

println "result=$result"

==================================

and from the console:

==================================

|Loading Grails 2.3.5

|Configuring classpath

.

|Environment set to development

.................................

|Packaging Grails application

...............

|Compiling 1 source files

...............................

|Running Grails application

in MyTogglzConfiguration.constructor

in MyTogglzConfiguration.getStateRepository

in MyTogglzConfiguration.getFeatureClass

in MyTogglzConfiguration.getUserProvider

in MyFeatureManagerProvider.constructor

in MyTogglzBootstrapper.constructor

|Server running. Browse to http://localhost:8080/GrailsTest

Looking for FeatureManagerProvider=org.togglz.core.context.ThreadLocalFeatureManagerProvider@6fb15612

Looking for FeatureManagerProvider=org.togglz.core.context.BeanFinderFeatureManagerProvider@4ba294ce

Looking for FeatureManagerProvider=org.togglz.core.context.JNDIFeatureManagerProvider@45984163

Looking for FeatureManagerProvider=org.togglz.core.context.StaticFeatureManagerProvider@562b2efc

Looking for FeatureManagerProvider=org.togglz.core.context.ContextClassLoaderFeatureManagerProvider@25b3a1b4

found a BeanFinder: org.togglz.servlet.spi.ServletContextBeanFinder@25534253

Found a featureManager, result=[]

found a BeanFinder: org.togglz.spring.spi.SpringBeanFinder@278102ae

Found a featureManager, result=[]

end of our ServiceLoader logic

result=[togglz.MyFeatureManager@646fdbc6, togglz.MyFeatureManagerService@433c6c40]

2014-10-30 14:38:58,931 [http-bio-8080-exec-1] DEBUG context.FeatureContext - No cached FeatureManager for class loader: org.grails.plugins.tomcat.ParentDelegatingClassLoader@28f67ca7

2014-10-30 14:38:58,933 [http-bio-8080-exec-1] DEBUG context.FeatureContext - Found 5 FeatureManagerProvider implementations...

2014-10-30 14:38:58,933 [http-bio-8080-exec-1] DEBUG context.FeatureContext - No FeatureManager provided by org.togglz.core.context.ThreadLocalFeatureManagerProvider

2014-10-30 14:38:58,934 [http-bio-8080-exec-1] DEBUG context.FeatureContext - No FeatureManager provided by org.togglz.core.context.BeanFinderFeatureManagerProvider

2014-10-30 14:38:58,934 [http-bio-8080-exec-1] DEBUG context.FeatureContext - No FeatureManager provided by org.togglz.core.context.StaticFeatureManagerProvider

2014-10-30 14:38:58,934 [http-bio-8080-exec-1] DEBUG context.FeatureContext - No FeatureManager provided by org.togglz.core.context.ContextClassLoaderFeatureManagerProvider

2014-10-30 14:38:58,934 [http-bio-8080-exec-1] DEBUG context.JNDIFeatureManagerProvider - FeatureMananger not found: Name [FeatureManager] is not bound in this Context. Unable to find [FeatureManager].

2014-10-30 14:38:58,934 [http-bio-8080-exec-1] DEBUG context.FeatureContext - No FeatureManager provided by org.togglz.core.context.JNDIFeatureManagerProvider

Error |

2014-10-30 14:38:58,968 [http-bio-8080-exec-1] ERROR errors.GrailsExceptionResolver - IllegalStateException occurred when processing request: [GET] /GrailsTest/book/welcome

Could not find the FeatureManager. For web applications please verify that the TogglzFilter starts up correctly. In other deployment scenarios you will typically have to implement a FeatureManagerProvider as described in the 'Advanced Configuration' chapter of the documentation.. Stacktrace follows:

Message: Could not find the FeatureManager. For web applications please verify that the TogglzFilter starts up correctly. In other deployment scenarios you will typically have to implement a FeatureManagerProvider as described in the 'Advanced Configuration' chapter of the documentation.

Line | Method

->> 49 | getFeatureManager in org.togglz.core.context.FeatureContext

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

| 20 | isActive in togglz.MyFeatures

| 69 | doCall . . . . . in test.BookController$_closure1

| 200 | doFilter in grails.plugin.cache.web.filter.PageFragmentCachingFilter

| 63 | doFilter . . . . in grails.plugin.cache.web.filter.AbstractFilter

| 1145 | runWorker in java.util.concurrent.ThreadPoolExecutor

| 615 | run . . . . . . . in java.util.concurrent.ThreadPoolExecutor$Worker

^ 724 | run in java.lang.Thread

ron rittinger

unread,

Oct 30, 2014, 2:50:09 PM10/30/14

to togglz...@googlegroups.com

I notice null is passed to the BeanFinder:
Collection<FeatureManager> result = iterator.next().find(FeatureManager.class, null);

(this is within the getFeatureManager method of the BeanFinderFeatureManagerProvider class).

If I use null in my sample code, the FeatureManager is not found. if I use a different context in my test code (the servletContext) the featureManager is found.

ron rittinger

unread,

Oct 30, 2014, 2:54:49 PM10/30/14

to togglz...@googlegroups.com

I also tried to supply my own FeatureManagerProvider but using the ServiceLoader within Grails doesn't appear to work. There is a single post on another forum (and copied elsewhere) where someone complains about this (ServiceLoader not working in grails) but no one has a fix.

If I could use my own FeatureManagerProvider, I think I could get it to work.

Pulling my hair out, I REALLY need this to work as we plan on using the same togglz infrastructure to toggle funtionality on/off in our service and Grails apps. Thanks a LOT for helping me with this.

Christian Kaltepoth

unread,

Oct 31, 2014, 9:19:06 AM10/31/14

to togglz...@googlegroups.com

Hey,

maybe it helps if I explain some general and important concepts of the inner workings of Togglz. I think this may help to find the root cause of this problem.

The main class in Togglz is the FeatureManager. You have basically three options on how to handle the feature Manager

Let Togglz create and manage the FeatureManager: With this option Togglz will automatically create and instance of FeatureManager and use it for the application. To allow you to tell Togglz about how it should create the FeatureManager, you can provide either an implementation of TogglzConfig or TogglzBootstrap. Togglz will perform this initialization when TogglzFilter.init() gets called by the container. It will then try to find TogglzConfig or TogglzBootstrap using the BeanFinder SPI. In most deployment scenarios Togglz will find Spring managed implementations of these interface and use them for building the FeatureManager.
Let Togglz use an already existing FeatureManager: In this scenario you can use the IoC container of choice (like Spring, CDI, Guice) to manage the lifecycle of the FeatureManager. Togglz will try to find this managed instance and use it instead of creating its own instance. If you are using Spring you can either use
FeatureManagerFactory if use prefer XML configuration or use FeatureManagerBuilder together with Springs's Java Config style.
Use a custom strategy to lookup an existing FeatureManager: You can always use a custom strategy to lookup the FeatureManager. To do so just implement a FeatureManagerProvider that obtains the FeatureManager from wherever you want.

In most cases users typically use the first approach. However, there are deployment scenarios for with the first option doesn't work well. Especially if the TogglzFilter is initialized by the container BEFORE Spring starts up. In this case you should try the second option. To force Togglz to skip the creation of its own FeatureManager, you have to set the context parameter org.togglz.FEATURE_MANAGER_PROVIDED to "true". See this page for details:

http://www.togglz.org/documentation/advanced-config.html

I hope this helps a bit.

Christian

ron rittinger

unread,

Oct 31, 2014, 9:43:19 AM10/31/14

to togglz...@googlegroups.com

I tried option #1 first, which is of course the easiest. I was able to configure my Spring MVC application (provides RESTFul services for my Grails app) in under 5 minutes. Had Togglz installed, configured (all I did was add a MyFeatures and MyTogglzConfig class) and it worked.

I tried the same with Grails but Togglz can't find MyTogglzConfig class even though I know it was loaded by the Spring underpinnings found in Grails.I think it has something do with different contexts or class loaders or something like that.

Once the easy path failed, I tried everything else I could think of but it's always the same problem. The togglz infrastructure can't find any Spring beans within Grails.

I don't think it's a togglz problem really, more likely something Grails is doing wrong or slightly different from a pure Spring (no Grails) implementation.

As a result, I'm punting. I'm going to configure togglz in my Spring MVC App and make a separate, custom REST call from my Grails app to obtain the togglz data. I'l have to implement my own toggling tag libs/if checks/etc.

PS> it would be great if you created a Togglz plugin for Grails. Grails has at least two other "toggling" plugins but Togglz is much more robust (nice console and different persistence options). I'd be happy to help you test it!

Thanks for all your help.

Christian Kaltepoth

unread,

Nov 1, 2014, 7:13:54 AM11/1/14

to togglz...@googlegroups.com

Hey,

I don't think there will be a Grails integration module without some kind of community contribution in the near future. Especially because I'm not familiar with Grails. However, any kind of contribution is welcome.

But I really think that your problem with the Togglz + Grails integration is caused by the fact that the SpringBeanFinder cannot find the current WebApplicationContext. It looks like this line doesn't work:

https://github.com/togglz/togglz/blob/master/spring/src/main/java/org/togglz/spring/spi/SpringBeanFinder.java#L26

This works fine in a standard Spring environment. I've no idea why it doesn't work for your app. However, I'm really sure that there is a way to get the ApplicationContext in Grails. I just did some research and it looks like something like this _could_ work:

ApplicationContext context = GrailsWebUtil.currentApplication().getMainContext();

So you could try to create a custom BeanFinder similar to the SpringBeanFinder and use this code to lookup the ApplicationContext. If this works, this would be a perfect first feature for a Grails integration module. ;)

Christian

ron rittinger

unread,

Nov 6, 2014, 10:38:21 AM11/6/14

to togglz...@googlegroups.com

I'm unable to integrate togglz into my "real" spring project as well. I'm able to integrate toggles in a clean, simple Spring project but anymore more complicated and something is getting in the way. Below is from my logs from my working example:

DEBUG [localhost-startStop-1] (Slf4jLogProvider.java:42) - Found 5 FeatureManagerProvider implementations...

DEBUG [localhost-startStop-1] (Slf4jLogProvider.java:42) - No FeatureManager provided by org.togglz.core.context.ThreadLocalFeatureManagerProvider

DEBUG [localhost-startStop-1] (Slf4jLogProvider.java:42) - No FeatureManager provided by org.togglz.core.context.BeanFinderFeatureManagerProvider

DEBUG [localhost-startStop-1] (Slf4jLogProvider.java:42) - No FeatureManager provided by org.togglz.core.context.StaticFeatureManagerProvider

DEBUG [localhost-startStop-1] (Slf4jLogProvider.java:42) - No FeatureManager provided by org.togglz.core.context.ContextClassLoaderFeatureManagerProvider

DEBUG [localhost-startStop-1] (Slf4jLogProvider.java:42) - FeatureMananger not found: Name [FeatureManager] is not bound in this Context. Unable to find [FeatureManager].

DEBUG [localhost-startStop-1] (Slf4jLogProvider.java:42) - No FeatureManager provided by org.togglz.core.context.JNDIFeatureManagerProvider

DEBUG [localhost-startStop-1] (Slf4jLogProvider.java:42) - Could not find any existing FeatureManager

DEBUG [localhost-startStop-1] (Slf4jLogProvider.java:42) - Starting FeatureManager bootstrap process

DEBUG [localhost-startStop-1] (AbstractBeanFactory.java:246) - Returning cached instance of singleton bean 'myTogglzConfig'

DEBUG [localhost-startStop-1] (Slf4jLogProvider.java:42) - FeatureManager has been created: FeatureManager[MyFeatures]

notice the "Starting FeatureManager bootstrap process". The FeatureManagerProviders are unable to find a custom feature manager (which is correct) and a default one is created for me, which is what I want. And it works.

Below is from my Spring application that does not work:

2014-11-06 10:34:12,943 DEBUG [org.togglz.core.context.FeatureContext] - Found 5 FeatureManagerProvider implementations...

2014-11-06 10:34:12,943 DEBUG [org.togglz.core.context.FeatureContext] - No FeatureManager provided by org.togglz.core.context.ThreadLocalFeatureManagerProvider

2014-11-06 10:34:12,948 DEBUG [org.togglz.core.context.FeatureContext] - No FeatureManager provided by org.togglz.core.context.BeanFinderFeatureManagerProvider

2014-11-06 10:34:12,948 DEBUG [org.togglz.core.context.FeatureContext] - No FeatureManager provided by org.togglz.core.context.StaticFeatureManagerProvider

2014-11-06 10:34:12,948 DEBUG [org.togglz.core.context.FeatureContext] - No FeatureManager provided by org.togglz.core.context.ContextClassLoaderFeatureManagerProvider

2014-11-06 10:34:12,948 DEBUG [org.togglz.core.context.JNDIFeatureManagerProvider] - FeatureMananger not found: Name [FeatureManager] is not bound in this Context. Unable to find [FeatureManager].

2014-11-06 10:34:12,948 DEBUG [org.togglz.core.context.FeatureContext] - No FeatureManager provided by org.togglz.core.context.JNDIFeatureManagerProvider

2014-11-06 10:34:12,950 DEBUG [org.springframework.web.servlet.mvc.method.annotation.ExceptionHandlerExceptionResolver] - Resolving exception from handler [public

and an exception is thrown.

Why isn't the bootstrap process happening?

ron rittinger

unread,

Nov 6, 2014, 3:38:39 PM11/6/14

to togglz...@googlegroups.com

Sorry that I'm a bit off topic now as I can't get it to work in a working, more complex, Spring MVC application.

Would it be possible to get some more logging added to the startup process of togglz?

I never see this output in my log: Togglz 2.0.1.Final started

More logging in the TogglzFilter and bootstrapping process would be very helpful.

I'm in a web 3.0 container, yet the TogglzFilter does not appear to be loaded.

On Monday, October 27, 2014 10:43:39 AM UTC-4, ron rittinger wrote:

Christian Kaltepoth

unread,

Nov 10, 2014, 11:26:45 AM11/10/14

to togglz...@googlegroups.com

Could you please post the full stacktrace you are getting? It would be interesting to see _what_ is triggering the first feature manager lookup...

ron rittinger

unread,

Nov 10, 2014, 2:34:31 PM11/10/14

to togglz...@googlegroups.com

Below is the stacktrace when I hit the following test code:

if( MyFeatures.FEATURE_ONE.isActive()){

System.out.println("Feature one is active");

}

Up until this point, the log contains no errors.

2014-11-10 14:26:28,384 DEBUG [org.springframework.web.servlet.mvc.method.annotation.ExceptionHandlerExceptionResolver] - Invoking @ExceptionHandler method: public org.springframework.http.ResponseEntity<?> com.elsevier.aesvc.ErrorHandler.handleException(java.lang.Exception)

java.lang.IllegalStateException: Could not find the FeatureManager. For web applications please verify that the TogglzFilter starts up correctly. In other deployment scenarios you will typically have to implement a FeatureManagerProvider as described in the 'Advanced Configuration' chapter of the documentation.

at org.togglz.core.context.FeatureContext.getFeatureManager(FeatureContext.java:49)

at togglz.MyFeatures.isActive(MyFeatures.java:18)

at com.elsevier.aesvc.config.country.v1.CountryController.getCountryList(CountryController.java:203)

at com.elsevier.aesvc.config.country.v1.CountryController$$FastClassByCGLIB$$8ae27989.invoke(<generated>)

at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)

at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:698)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)

at org.springframework.aop.framework.adapter.MethodBeforeAdviceInterceptor.invoke(MethodBeforeAdviceInterceptor.java:51)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

at org.springframework.aop.framework.adapter.AfterReturningAdviceInterceptor.invoke(AfterReturningAdviceInterceptor.java:51)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

at org.springframework.aop.aspectj.AspectJAfterThrowingAdvice.invoke(AspectJAfterThrowingAdvice.java:55)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)

at com.elsevier.aesvc.aop.SecurityAspect.security(SecurityAspect.java:149)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)

at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)

at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

at org.springframework.aop.framework.adapter.MethodBeforeAdviceInterceptor.invoke(MethodBeforeAdviceInterceptor.java:51)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:631)

at com.elsevier.aesvc.config.country.v1.CountryController$$EnhancerByCGLIB$$c5e9732c.getCountryList(<generated>)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at org.springframework.web.method.support.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:219)

at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:132)

at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:104)

at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:745)

at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:686)

at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:80)

at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:925)

at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:856)

at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:936)

at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:827)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:621)

at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:812)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)

at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)

at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)

at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)