activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Trenaman (JIRA)" <>
Subject [jira] Commented: (AMQ-2740) NullPointerException in Web Console when using an existing browser session with a restarted broker instance
Date Wed, 19 May 2010 09:01:26 GMT


Adrian Trenaman commented on AMQ-2740:

Just another note on this - if you explicitly refresh the browser page before you do a delete,
then the error goes away. This supports my suspicion about this being down to stale session

> NullPointerException in Web Console when using an existing browser session with a restarted
broker instance
> -----------------------------------------------------------------------------------------------------------
>                 Key: AMQ-2740
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.3.2
>         Environment: Windows
>            Reporter: Adrian Trenaman
> As per summary above. If you have a browser open to the web console, and create a queue
it works OK. However, if you then restart the broker adn then try and perform an action like
deleting the queue (from the web console) then you'll see the NPE in the broker's log. 
> {code}
> ERROR | Nested in org.springframework.web.util.NestedServletException: Request processing
failed; nested exception is java.lang.NullPointerException:
> java.lang.NullPointerException
>         at org.apache.activemq.web.handler.BindingBeanNameUrlHandlerMapping.getHandlerInternal(
>         at org.springframework.web.servlet.handler.AbstractHandlerMapping.getHandler(
>         at org.springframework.web.servlet.DispatcherServlet.getHandler(
>         at org.springframework.web.servlet.DispatcherServlet.doDispatch(
>         at org.springframework.web.servlet.DispatcherServlet.doService(
>         at org.springframework.web.servlet.FrameworkServlet.processRequest(
>         at org.springframework.web.servlet.FrameworkServlet.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$CachedChain.doFilter(
>         at org.springframework.web.filter.RequestContextFilter.doFilterInternal(
>         at org.springframework.web.filter.OncePerRequestFilter.doFilter(
>         at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(
>         at org.apache.activemq.web.filter.ApplicationContextFilter.doFilter(
>         at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(
>         at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(
>         at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(
>         at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(
>         at org.mortbay.jetty.servlet.ServletHandler.handle(
>         at
>         at org.mortbay.jetty.servlet.SessionHandler.handle(
>         at org.mortbay.jetty.handler.ContextHandler.handle(
>         at org.mortbay.jetty.webapp.WebAppContext.handle(
>         at org.mortbay.jetty.handler.ContextHandlerCollection.handle(
>         at org.mortbay.jetty.handler.HandlerCollection.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
>         at org.mortbay.thread.BoundedThreadPool$
> {code} 
> I think this has something to do with stale session secrets, and is a consequence of
support that was put in to protect ActiveMQ against CSRF (cross-site request forgery) attacks.
The original CSRF error was alarming; this error, however, is a plain old NPE and we should
fix it.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message