Jmx console reinvoke operation results in 500 error code.

Solution Verified - Updated -

Issue

  • EAP 5.2 JMX console throws 500 error page on reinvocation of operations such as listThreadDump, listMemoryPools etc with the following error stack in server.log.
2013-06-22 19:02:37,957 WARN  [org.jboss.jmx.adaptor.html.HtmlAdaptorServlet] (http-127.0.0.1-8080-2) Received request for invokeOpByName with invalid or missing CSRFToken token. This might indicate that someone is trying CSRF attack on your server.
2013-06-22 19:02:37,958 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jmx-console].[HtmlAdaptor]] (http-127.0.0.1-8080-2) Servlet.service() for servlet HtmlAdaptor threw exception
javax.servlet.ServletException: Operation invoke prohibited.
    at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOpByName(HtmlAdaptorServlet.java:319)
    at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:106)
    at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doGet(HtmlAdaptorServlet.java:81)
          :

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 5.2.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.