Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exceptions when connecting to server over wrong protocol #6

Open
thomashub opened this issue Mar 6, 2013 · 0 comments
Open

Exceptions when connecting to server over wrong protocol #6

thomashub opened this issue Mar 6, 2013 · 0 comments

Comments

@thomashub
Copy link

To reproduce: start the ChatServer example that comes with hookup. Connect (with, for example, http://www.websocket.org/echo.html) to wss://host:port, i.e. using the secure websocket protocol.

The server throws the following exception, after which it does not accept any new connections:

SEVERE: Exception during connection.
java.lang.IllegalArgumentException: empty text
    at org.jboss.netty.handler.codec.http.HttpVersion.<init>(HttpVersion.java:97)

When another client was already connected, it stays connected, but when it sends a message the server throws both the above error again, and also the following:

Mar 06, 2013 1:19:14 AM org.jboss.netty.channel.socket.nio.AbstractNioWorker
WARNING: Unexpected exception in the selector loop.
java.lang.IllegalArgumentException: unsupported message type: class org.jboss.netty.handler.codec.http.websocketx.TextWebSocketFrame
    at org.jboss.netty.channel.socket.nio.SocketSendBufferPool.acquire(SocketSendBufferPool.java:53)

It seems to me that the wss:// connection attempt should be rejected if it cannot be handled, causing no issues for the future state of the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant