Never mind, it appears the problem was due to how the install was run, there was another section that was overriding the web.xml using an older version, not the one distributed with 5.13.0. On Wed, Feb 10, 2016 at 12:47 PM James A. Robinson <jim.robin...@gmail.com> wrote:
> I'm working on upgrading from activemq 5.11.0 to 5.13.0. When I make an > HTTP GET request against the older version of the service, when the queue > doesn't have any pending messages, the request hangs until one is ready. > On the newer version it returns a fatal status 500 error and throws an > exception: > > Server Error > Caused by: java.lang.IllegalStateException: !asyncSupported > at org.eclipse.jetty.server.Request.startAsync(Request.java:2058) > at > org.eclipse.jetty.continuation.Servlet3Continuation.suspend(Servlet3Continuation.java:170) > at > org.apache.activemq.web.MessageServlet.handleContinuation(MessageServlet.java:276) > > It appears that the newer versions of Jetty don't explicitly enable > async. Changing webapps/api/WEB-INF/web.xml to add > <async-supported>true</async-supported> appeared to resolve the issue, but > I'm wondering why that wasn't defined in the first place? Is there is some > other configuration that ought to have been toggled to prevent the error? > > Jim > >
