Perf4J

Nullpointer exception on Servlet access

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 0.9.10
  • Fix Version/s: 0.9.12
  • Labels:
    None
  • Environment:
    WAS 6.1.0.21
  • Number of attachments :
    0

Description

I get this nullpointer, possibly because I don't have any request parameters or bad configuration, but a more informative message than nullpointer would be preferable in such situations:

[5/10/09 22:44:02:390 CEST] 00000029 ServletWrappe E SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: perf4j. Exception thrown : java.lang.NullPointerException
at org.perf4j.servlet.AbstractGraphingServlet.writeChart(AbstractGraphingServlet.java:103)
at org.perf4j.servlet.AbstractGraphingServlet.doGet(AbstractGraphingServlet.java:63)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1143)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:591)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3453)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:815)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1466)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:119)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:267)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:196)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:751)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:881)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)

Activity

Hide
Alex Devine added a comment -

This NPE was thrown when a graphName specified either as a request parameter or servlet init param was unknown. There was a problem with the code to check for unknown graph names. This has been fixed so now the response displays a message stating that the graph name is unknown.

Fix is revision 73.

Show
Alex Devine added a comment - This NPE was thrown when a graphName specified either as a request parameter or servlet init param was unknown. There was a problem with the code to check for unknown graph names. This has been fixed so now the response displays a message stating that the graph name is unknown. Fix is revision 73.

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: