Okay, looking at the source with a stack trace doesn't help me. I'm betting spring is mangling the stack trace like it usually does.
Nope, it's much more interesting than that. Inspektr is likely eating the meaningful exception since it's throwing an NPE from a finally block that's being executed after a catch block, and the NPE is superseding the exception that would have been thrown from the catch block. See the following thread for a lot more context and a patch you might be able to try:
https://groups.google.com/forum/?fromgroups#!topic/jasig-cas-user/CPE0mqhDbAE
Can anyone make sense of this stack trace? I'm sure there's no code on line 1 of CentralAuthenticationServiceImpl.java :D
That's likely due to bytecode enhancement produced by aspectj class proxies for the Spring AOP machinery. The "aroundBody" entries in the stack trace are further evidence that's the cause:
at org.jasig.cas.CentralAuthenticationServiceImpl.delegateTicketGrantingTicket_aroundBody6(CentralAuthenticationServiceImpl.java:272) at org.jasig.cas.CentralAuthenticationServiceImpl.delegateTicketGrantingTicket_aroundBody7$advice(CentralAuthenticationServiceImpl.java:44) at org.jasig.cas.CentralAuthenticationServiceImpl.delegateTicketGrantingTicket(CentralAuthenticationServiceImpl.java:1)
Mismatched line numbers are a common occurrence when debugging classes like CentralAuthenticationServiceImpl that have AOP pointcuts defined on them. No doubt it's frustrating.
M -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
