Return-Path: X-Original-To: apmail-mina-dev-archive@www.apache.org Delivered-To: apmail-mina-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DDB1AECC4 for ; Tue, 26 Feb 2013 10:16:13 +0000 (UTC) Received: (qmail 50733 invoked by uid 500); 26 Feb 2013 10:16:13 -0000 Delivered-To: apmail-mina-dev-archive@mina.apache.org Received: (qmail 50636 invoked by uid 500); 26 Feb 2013 10:16:13 -0000 Mailing-List: contact dev-help@mina.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mina.apache.org Delivered-To: mailing list dev@mina.apache.org Received: (qmail 50622 invoked by uid 99); 26 Feb 2013 10:16:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Feb 2013 10:16:13 +0000 Date: Tue, 26 Feb 2013 10:16:12 +0000 (UTC) From: "Robert McNamara (JIRA)" To: dev@mina.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (VYSPER-340) Problems Performing WebSocket Handshake MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Robert McNamara created VYSPER-340: -------------------------------------- Summary: Problems Performing WebSocket Handshake Key: VYSPER-340 URL: https://issues.apache.org/jira/browse/VYSPER-340 Project: VYSPER Issue Type: Question Components: extension Affects Versions: 0.7 Environment: Windows Server 2008 R2 Reporter: Robert McNamara I=E2=80=99m having an issue performing a successful handshake. Weather runn= ing Vysper from the batch file or embedded in a simple Java Server (my own = or one of the prepackaged examples), I get the same error condition upon at= tempting to connect from a JavaScript client (my own or one of the prepacka= ged examples). The error the returns is a HTTP 405 Response, reported in Ch= rome's console as =E2=80=9CUnexpected response code: 405=E2=80=9D. CONFIGURATION OF SERVER: =E2=80=98spring-config.xml=E2=80=99 has the following additions: And in the server constructor:=20 (OR) CONFIGURATION OF EMBEDDED SERVER: The embedded server, developed with Eclipse Juno and coded as per the examp= le on the Vysper homepage (and as per the packaged examples): org.eclipse.jetty.server.Server@1f8ec00 STOPPED +-SelectChannelConnector@0.0.0.0:8080 +-qtp8256952{8<=3D6<=3D8/254,0} +-HandlerCollection@148fb3f started +-ResourceHandler@191ce2a started +-ServletContextHandler@1f05ce9@1f05ce9/ws,null started +-{} +-{} +-SessionHandler@11f25f3 started +-ServletHandler@1f4899c started +-[/ws]=3D>org.apache.vysper.xmpp.extension.websockets.XmppW= ebSocketServlet-29347786{} POSSIBLE START ERROR CONDITION: The Server appears to start properly, only with the following possible prob= lem reported (on both standalone and embedded servers): org.eclipse.jetty.server.Server@2af081 STOPPED +-SelectChannelConnector@0.0.0.0:8080 +-qtp29384701{8<=3D6<=3D8/254,0} +-ServletContextHandler@32efa7@32efa7/ws,null started +-{} +-{} +-SessionHandler@1fbfd6 started +-ServletHandler@6b9c84 started +-[/ws]=3D>org.apache.vysper.xmpp.extension.websockets.XmppWebSo= cketServlet-23860799{} ATTEMPTING CONNECTION ERRORS: When attempting to connect from the client the following is logged in both = types of server instance: 17:04:02,137 | DEBUG | org.eclipse.jetty.util.log | REQUEST /ws/ws on org= .eclipse.jetty.server.nio.SelectChannelConnector$3@c3615b 17:04:02,137 | DEBUG | org.eclipse.jetty.util.log | sessionManager=3Dorg.= eclipse.jetty.server.session.HashSessionManager@1767f84 17:04:02,137 | DEBUG | org.eclipse.jetty.util.log | session=3Dnull 17:04:02,137 | DEBUG | org.eclipse.jetty.util.log | servlet=3Dorg.apache.= vysper.xmpp.extension.websockets.XmppWebSocketServlet-29347786 17:04:02,137 | DEBUG | org.eclipse.jetty.util.log | servlet holder=3D 17:04:02,137 | DEBUG | org.eclipse.jetty.util.log | chain=3D 17:04:02,137 | DEBUG | org.eclipse.jetty.util.log | RESPONSE /ws/ws 405 17:04:02,137 | DEBUG | org.eclipse.jetty.util.log | EOF And to the Chrome console on the client side: Unexpected response code: 405 Event {clipboardData: undefined, cancelBubble: false, returnValue: true, = srcElement: WebSocket, defaultPrevented: false=E2=80=A6} CloseEvent {reason: "", code: 1006, wasClean: false, clipboardData: undef= ined, cancelBubble: false=E2=80=A6} Any suggestions on how to proceed? Thanks, Rob -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira