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 web123904

  • 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 tmn.kiosk.processor.common.aspect.LoggingAspect.performTransactionIdCollectingFromGlobalExceptionHandler(LoggingAspect.java:135)[classes/:?] at sun.reflect.GeneratedMethodAccessor356.invoke(Unknown Source)[?:?] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[?:1.7.0] at java.lang.reflect.Method.invoke(Method.java:607)[?:2.6 (08-23-2013)] at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)[spring-aop-4.0.5.RELEASE.jar:4.0.5.RELEASE] at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)[spring-aop-4.0.5.RELEASE.jar:4.0.5.RELEASE] at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:68)[spring-aop-4.0.5.RELEASE.jar:4.0.5.RELEASE] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)[spring-aop-4.0.5.RELEASE.jar:4.0.5.RELEASE] at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:85)[spring-aop-4.0.5.RELEASE.jar:4.0.5.RELEASE] at tmn.kiosk.processor.common.aspect.LoggingAspect.performLogging(LoggingAspect.java:27)[classes/:?] at sun.reflect.GeneratedMethodAccessor82.invoke(Unknown Source)[?:?] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[?:1.7.0] at java.lang.reflect.Method.invoke(Method.java:607)[?:2.6 (08-23-2013)]

    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.