activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-4263) [ActiveMQ web-console] HTTP ERROR 405 instead of clear warning message in case Topic\Queue name did not set when trying to create.
Date Wed, 30 Oct 2013 14:05:30 GMT

     [ https://issues.apache.org/jira/browse/AMQ-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen resolved AMQ-4263.
------------------------------

       Resolution: Won't Fix
    Fix Version/s: 5.9.0
         Assignee: Claus Ibsen

The old web console is deprecated. From AMQ 5.9 onwards hawtio is the new console.

> [ActiveMQ web-console] HTTP ERROR 405 instead of clear warning message in case Topic\Queue
name did not set when trying to create.
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-4263
>                 URL: https://issues.apache.org/jira/browse/AMQ-4263
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.7.0
>         Environment: ActiveMQ modules are used in Karaf 2.2.9 OSGi container
>            Reporter: Roman Minko
>            Assignee: Claus Ibsen
>            Priority: Minor
>              Labels: osgi, web-console
>             Fix For: 5.9.0
>
>         Attachments: name_null_create_topic.JPG
>
>
> 1. In Karaf console:
> features:addUrl mvn:org.apache.activemq/activemq-karaf/5.7.0/xml/features
> features:install activemq-spring
> features:install activemq-web-console
> activemq:create-broker
> 2. After install and start the web console with embedded broker going to use it at
> http://localhost:8181/activemqweb/
> 3. Go to topic/queue page. If the name is null, click the "create" button, will get the
following exception:
> {code}
> HTTP ERROR 405
> Problem accessing /activemqweb/500.html. Reason:
>     HTTP method POST is not supported by this URL
> Caused by:
> java.lang.IllegalArgumentException: No JMSDestination parameter specified
> 	at org.apache.activemq.web.DestinationFacade.getValidDestination(DestinationFacade.java:112)
> 	at org.apache.activemq.web.DestinationFacade.addDestination(DestinationFacade.java:56)
> 	at org.apache.activemq.web.controller.CreateDestination.handleRequest(CreateDestination.java:38)
> 	at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
> 	at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:790)
> 	at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:719)
> 	at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:669)
> 	at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:585)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> 	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:652)
> 	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1329)
> 	at org.apache.activemq.web.AuditFilter.doFilter(AuditFilter.java:59)
> 	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
> 	at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:83)
> 	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
> 	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
> 	at org.apache.activemq.web.filter.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:96)
> 	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
> 	at com.opensymphony.sitemesh.webapp.SiteMeshFilter.obtainContent(SiteMeshFilter.java:129)
> 	at com.opensymphony.sitemesh.webapp.SiteMeshFilter.doFilter(SiteMeshFilter.java:77)
> 	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
> 	at org.ops4j.pax.web.service.internal.WelcomeFilesFilter.doFilter(WelcomeFilesFilter.java:193)
> 	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
> 	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:445)
> 	at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:70)
> 	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
> 	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:559)
> 	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
> 	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1038)
> 	at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:117)
> 	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:374)
> 	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:189)
> 	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:972)
> 	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
> 	at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:74)
> 	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
> 	at org.eclipse.jetty.server.Server.handle(Server.java:363)
> 	at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:483)
> 	at org.eclipse.jetty.server.BlockingHttpConnection.handleRequest(BlockingHttpConnection.java:53)
> 	at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:931)
> 	at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:992)
> 	at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:856)
> 	at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240)
> 	at org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:72)
> 	at org.eclipse.jetty.server.nio.BlockingChannelConnector$BlockingChannelEndPoint.run(BlockingChannelConnector.java:298)
> 	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
> 	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
> 	at java.lang.Thread.run(Unknown Source)
> {code}
> If input the name for a new queue/topic, no this issue. It happens only when keep the
name is null.
> Pop-up window or something else will be good instead of given an exception page to the
user.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message