accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Created] (ACCUMULO-2631) Excessively large number of minutes for trace page prints exception
Date Fri, 04 Apr 2014 15:48:14 GMT
Josh Elser created ACCUMULO-2631:

             Summary: Excessively large number of minutes for trace page prints exception
                 Key: ACCUMULO-2631
             Project: Accumulo
          Issue Type: Bug
          Components: monitor
    Affects Versions: 1.5.1
            Reporter: Josh Elser
            Priority: Minor
             Fix For: 1.5.2, 1.6.1

I wanted to get "all" the traces on my dev instance in the monitor so I changed the "minutes"
query parameter to something like "99999".

When I submitted the page, I got an exception printed to the browser:

java.lang.IllegalArgumentException: Start key must be less than end key in range (start:1457aa24105
: [] 9223372036854775807 false, start:1452d6ac6a5%00; : [] 9223372036854775807 false)
	at org.apache.accumulo.server.monitor.servlets.trace.Summary.pageBody(
	at org.apache.accumulo.server.monitor.servlets.BasicServlet.doGet(
	at javax.servlet.http.HttpServlet.service(
	at javax.servlet.http.HttpServlet.service(
	at org.mortbay.jetty.servlet.ServletHolder.handle(
	at org.mortbay.jetty.servlet.ServletHandler.handle(
	at org.mortbay.jetty.servlet.SessionHandler.handle(
	at org.mortbay.jetty.handler.ContextHandler.handle(
	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(
	at org.mortbay.jetty.handler.HandlerWrapper.handle(
	at org.mortbay.jetty.Server.handle(
	at org.mortbay.jetty.HttpConnection.handleRequest(
	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(
	at org.mortbay.jetty.HttpParser.parseNext(
	at org.mortbay.jetty.HttpParser.parseAvailable(
	at org.mortbay.jetty.HttpConnection.handle(
	at org.mortbay.thread.QueuedThreadPool$

We should be catching this before it happens so we can print a meaningful error message. My
hunch is that submitting a "minutes" value that's greater than the "number of minutes stored"
is throwing this error -- if that's the case, it would be nice to have an excessively large
value just return everything.

This message was sent by Atlassian JIRA

View raw message