Interestingly enough it looks like your runtime arguments are null for both username and password according to the exception with the UsernamePasswordToken, and it can't resolve an appropriate constructor. I don't know if that has any correlation to the double login problems you're seeing, but it might.
On Wed, Jan 13, 2010 at 12:25 PM, Gorman, Stephen A. <[email protected]> wrote: > All, > > > > For some reason I started getting a strange error today with Shiro. I don’t > know the reason yet but found that if I put a break point in my def signIn > methon in my AuthController that it was getting called twice during the > login process. When I click login the signIn method gets called and stops on > my break point, then just before the initial application page is displayed > the signIn break point catches again. Is shiro supposed to call signIn > repetitively? Based on my filter I thought that it would be called once and > that was all for the entire session. Can someone educated me? > > > > Thanks in advance. > > > > sg > > > > /** > > * Generated by the Shiro plugin. This filters class protects all URLs > > * via access control by convention. > > */ > > class SecurityFilters { > > def filters = { > > all(uri: "/**") { > > before = { > > // Ignore direct views (e.g. the default main index page). > > if (!controllerName) return true > > > > // Access control by convention. > > accessControl {true} > > } > > } > > } > > } > > > > > > > > > > ERROR errors.GrailsExceptionResolver - groovy.lang.GroovyRuntimeException: > Ambiguous method overloading for method > org.apache.shiro.authc.UsernamePasswordToken#<init>. > > Cannot resolve which method to invoke for [null, null] due to overlapping > prototypes between: > > [class java.lang.String, class java.lang.String] > > [class java.lang.String, class [C]
