java.lang.NullPointerException

This exception has no message.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web123955

  • via Terracotta by unnutz, 11 months ago
    This exception has no message.
  • This exception has no message.
  • This exception has no message.
  • Stack trace

    • java.lang.NullPointerException at org.springframework.aop.aspectj.RuntimeTestWalker$InstanceOfResidueTestVisitor.instanceOfMatches(RuntimeTestWalker.java:172)[org.springframework.aop.jar:3.0.1.RELEASE] at org.springframework.aop.aspectj.RuntimeTestWalker$ThisInstanceOfResidueTestVisitor.thisInstanceOfMatches(RuntimeTestWalker.java:221)[org.springframework.aop.jar:3.0.1.RELEASE] at org.springframework.aop.aspectj.RuntimeTestWalker.testThisInstanceOfResidue(RuntimeTestWalker.java:90)[org.springframework.aop.jar:3.0.1.RELEASE] at org.springframework.aop.aspectj.AspectJExpressionPointcut.matches(AspectJExpressionPointcut.java:307)[org.springframework.aop.jar:3.0.1.RELEASE] at org.springframework.aop.support.MethodMatchers$IntersectionMethodMatcher.matches(MethodMatchers.java:236)[org.springframework.aop.jar:3.0.1.RELEASE] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:160)[org.springframework.aop.jar:3.0.1.RELEASE] at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)[org.springframework.aop.jar:3.0.1.RELEASE] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)[org.springframework.aop.jar:3.0.1.RELEASE] at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)[org.springframework.aop.jar:3.0.1.RELEASE] at $Proxy131.createPlan(Unknown Source)[na:na] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[na:1.6.0_18] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)[na:1.6.0_18] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)[na:1.6.0_18] at java.lang.reflect.Method.invoke(Method.java:597)[na:1.6.0_18] at cc.catalysts.cp.server.impl.ApiManager.invoke(ApiManager.java:150)[cp-kernel.jar:1.3.10.03.24.17.45.10-dev] at cc.catalysts.cp.remoting.impl.ApiAdapter.invoke(ApiAdapter.java:47)[cp-kernel.jar:1.3.10.03.24.17.45.10-dev] at cc.catalysts.cp.remoting.red5.Red5ApiAdapter.invoke(Red5ApiAdapter.java:85)[cp-plugin-red5.jar:1.3.10.03.24.17.48.01-dev]

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.