Opened 7 years ago

Closed 3 years ago

#1529 closed defect (fixed)

Error 500 after clicking on config

Reported by: nextloop Owned by: zzz
Priority: minor Milestone: 0.9.36
Component: apps/console Version: 0.9.18
Keywords: Cc:
Parent Tickets: Sensitive: no


I also manually checked for updates before, and it started to update via bittorrent

Fehler 500: /configupdate Server Error

     at org.eclipse.jetty.server.session.AbstractSession.checkValid(
     at org.eclipse.jetty.server.session.HashedSession.checkValid(
     at org.eclipse.jetty.server.session.AbstractSession.getAttribute(
     at net.i2p.router.web.jsp.configupdate_jsp._jspService(
     at org.apache.jasper.runtime.HttpJspBase.service(
     at javax.servlet.http.HttpServlet.service(
     at org.eclipse.jetty.servlet.ServletHolder.handle(
     at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
     at net.i2p.servlet.filters.XSSFilter.doFilter(
     at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
     at org.eclipse.jetty.servlet.ServletHandler.doHandle(
     at org.eclipse.jetty.server.handler.ScopedHandler.handle(
     at org.eclipse.jetty.server.session.SessionHandler.doHandle(
     at org.eclipse.jetty.server.handler.ContextHandler.doHandle(
     at org.eclipse.jetty.servlet.ServletHandler.doScope(
     at org.eclipse.jetty.server.session.SessionHandler.doScope(
     at org.eclipse.jetty.server.handler.ContextHandler.doScope(
     at org.eclipse.jetty.server.handler.ScopedHandler.handle(
     at org.eclipse.jetty.server.handler.HandlerWrapper.handle(
     at net.i2p.router.web.LocaleWebAppHandler.handle(
     at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(
     at org.eclipse.jetty.server.handler.HandlerCollection.handle(
     at org.eclipse.jetty.server.handler.HandlerWrapper.handle(
     at org.eclipse.jetty.server.Server.handle(
     at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(
     at org.eclipse.jetty.server.AbstractHttpConnection.content(
     at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(
     at org.eclipse.jetty.http.HttpParser.parseNext(
     at org.eclipse.jetty.http.HttpParser.parseAvailable(
     at org.eclipse.jetty.server.AsyncHttpConnection.handle(
     at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(
     at org.eclipse.jetty.util.thread.QueuedThreadPool$

I2P version: 0.9.18-0
Java version: Oracle Corporation 1.7.0_75 (OpenJDK Runtime Environment 1.7.0_75-b13)
Wrapper version: 3.5.25
Server version: 8.1.16.v20140903
Servlet version: Jasper JSP 2.1 Engine
Platform: Linux i386 3.16.0-30-generic
Processor: Core (Yonah) (pentiumm)
Jbigi: Locally optimized library loaded from file
Encoding: UTF-8
Charset: UTF-8


Change History (5)

comment:1 Changed 7 years ago by zzz

Component: unspecifiedapps/console

This happens from time to time, but most of them are now caught in formhandler.jsi, Not sure how to fix this one.

Note: corresponds to line 21 in configupdate.jsp. At the session.getAttribute() call.

comment:2 Changed 6 years ago by zzz

Milestone: undecided0.9.21

The whole mechanism of storing a "context id" in the session or in a form parameter, storing it in each helper or handler, retrieving it, etc. is overwrought and not at all useful. Trying to make the console work with multiple in-JVM router contexts is a fantasy. Helpers and handlers can just get the static global context, or try to grab onto RouterConsoleRunner?'s one. But there's lots of static accesses to the context elsewhere in the console. Not an issue for Android or in embedded applications, where we don't use the console. Nor would we in MultiRouter? tests, or vmContext.

Even if we rip all that out, still some work to find every place where a session is referenced and wrap it in try/catch. But most of it is this contextID foolishness.

comment:3 Changed 3 years ago by zzz

Owner: set to zzz
Status: newaccepted

comment:4 Changed 3 years ago by zzz

Milestone: 0.9.370.9.36

Wrap all getAttribute() / setAttribute() in try/catch, in fd4151ac4943788f0cb9c5d4746f4806a0368b3f to be 0.9.35-19

…but then ctxID will be null and ContextHelper? will throw ISE so not sure this is an improvement… for further research…

comment:5 Changed 3 years ago by zzz

Resolution: fixed
Status: acceptedclosed

No, it will return first available context. Declaring fixed.

Note: See TracTickets for help on using tickets.