1 Reply Latest reply on Jan 12, 2012 2:55 AM by jaikiran

    Logging Formatters throwing NullPointerException.

    whitingjr

      Hi,

       

      I am using AS7.1 built from master as of 10 Jan. When I have a debugger attached with a breakpoint on NullPointerException it is trapping on the Formatters object.

       

      The version of logging is 3.1.0.CR2

       

      Should the Formatters object be throwing an exception when an error message is being logged ?

       

      Regards,

       

      Jeremy

       

      This is the call stack

       

      Daemon Thread [Thread-3 (group:HornetQ-client-global-threads-83613815)] (Suspended (exception NullPointerException))   

          Formatters$12.renderExtended(StringBuilder, StackTraceElement, Map<String,String>) line: 452   

          Formatters$12.renderRaw(StringBuilder, ExtLogRecord) line: 385   

          Formatters$12(Formatters$JustifyingFormatStep).render(StringBuilder, ExtLogRecord) line: 146   

          PatternFormatter(MultistepFormatter).format(ExtLogRecord) line: 86   

          PatternFormatter(ExtFormatter).format(LogRecord) line: 35   

          ConsoleHandler(WriterHandler).doPublish(ExtLogRecord) line: 49   

          ConsoleHandler(ExtHandler).publish(LogRecord) line: 64   

          LoggerNode.publish(ExtLogRecord) line: 283   

          LoggerNode.publish(ExtLogRecord) line: 291   

          LoggerNode.publish(ExtLogRecord) line: 291   

          LoggerNode.publish(ExtLogRecord) line: 291   

          LoggerNode.publish(ExtLogRecord) line: 291   

          Logger.logRaw(ExtLogRecord) line: 649   

          Logger.log(String, Level, String, ExtLogRecord$FormatStyle, Object[], Throwable) line: 600   

          JBossLogManagerLogger.doLogf(Logger$Level, String, String, Object[], Throwable) line: 54   

          JBossLogManagerLogger(Logger).logf(String, Logger$Level, Throwable, String, Object, Object) line: 2112   

          EjbLogger_$logger.invocationFailed(String, Method, Throwable) line: 149   

          LoggingInterceptor.processInvocation(InterceptorContext) line: 64   

          InterceptorContext.proceed() line: 288   

          ChainedInterceptor.processInvocation(InterceptorContext) line: 61   

          ViewService$View.invoke(InterceptorContext) line: 165   

          ViewDescription$1.processInvocation(InterceptorContext) line: 173   

          InterceptorContext.proceed() line: 288   

          ChainedInterceptor.processInvocation(InterceptorContext) line: 61   

          ProxyInvocationHandler.invoke(Object, Method, Object[]) line: 72   

          MessageListener$$$view20.onMessage(Message) line: not available   

          NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]   

          NativeMethodAccessorImpl.invoke(Object, Object[]) line: 57   

          DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43   

          Method.invoke(Object, Object...) line: 616   

          MessageEndpointInvocationHandler.doInvoke(Object, Method, Object[]) line: 140   

          MessageEndpointInvocationHandler(AbstractInvocationHandler).invoke(Object, Method, Object[]) line: 73   

          $Proxy89.onMessage(Message) line: not available   

          HornetQMessageHandler.onMessage(ClientMessage) line: 278   

          ClientConsumerImpl.callOnMessage() line: 866   

          ClientConsumerImpl.access$100(ClientConsumerImpl) line: 44   

          ClientConsumerImpl$Runner.run() line: 983   

          OrderedExecutorFactory$OrderedExecutor$1.run() line: 100   

          ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1110   

          ThreadPoolExecutor$Worker.run() line: 603   

          Thread.run() line: 679   

        • 1. Re: Logging Formatters throwing NullPointerException.
          jaikiran

          Jeremy Whiting wrote:

           

           

          Should the Formatters object be throwing an exception when an error message is being logged ?

          Ideally they shouldn't. Especially not a NullPointerException. You might want to bring this to the attention of James or David and maybe file a JIRA in the JBoss Logging project.

          1 of 1 people found this helpful