activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-3504) NullPointerException on websocket connection
Date Sat, 22 Oct 2011 22:22:32 GMT

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

Timothy Bish resolved AMQ-3504.
-------------------------------

    Resolution: Fixed

Updated to Jetty 7.5.1.v20110908 which has the latest Web Socket updates.  
                
> NullPointerException on websocket connection
> --------------------------------------------
>
>                 Key: AMQ-3504
>                 URL: https://issues.apache.org/jira/browse/AMQ-3504
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.x
>         Environment: 5.6.0 snapshot from Sat Sep 17 03:47:30, chrome 14.0.835.163, firefox
6
>            Reporter: Gunnar Kristjansson
>              Labels: websocket
>             Fix For: 5.6.0
>
>
> When connecting from chrome or firefox 6 over websockets, I get the Null pointer below.
It does not happen on firefox 5 or safari . My guess would be that the chrome and ff 6 are
implementing a newer version of the websocket spec that is incompatible with the version that
the activemq implements.     
> 2011-09-19 09:18:33,931 | WARN  | /stomp | org.eclipse.jetty.util.log | qtp1545215993-39
> java.lang.NullPointerException
>         at org.apache.activemq.transport.ws.StompServlet.doGet(StompServlet.java:51)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
>         at org.eclipse.jetty.websocket.WebSocketServlet.service(WebSocketServlet.java:73)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
>         at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:527)
>         at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:423)
>         at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
>         at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:930)
>         at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:358)
>         at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:183)
>         at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:866)
>         at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
>         at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113)
>         at org.eclipse.jetty.server.Server.handle(Server.java:351)
>         at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:594)
>         at org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:1042)
>         at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:549)
>         at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:211)
>         at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:424)
>         at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:241)
>         at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436)
>         at java.lang.Thread.run(Thread.java:680)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message