autobahn and tomcat

#1

Hello,

I’m using Tomcat 7.0.28 as a WS server. Is it interoperable with autobahn? Here is the stack trace:

07-05 14:38:19.260: D/de.tavendo.autobahn.WebSocketReader(915): created

07-05 14:38:19.260: D/de.tavendo.autobahn.WebSocketConnection(915): WS reader created and started

07-05 14:38:19.260: D/de.tavendo.autobahn.WebSocketReader(915): running

07-05 14:38:19.270: D/de.tavendo.autobahn.WebSocketWriter(915): created

07-05 14:38:19.270: D/de.tavendo.autobahn.WebSocketConnection(915): WS writer created and started

07-05 14:38:20.021: D/de.tavendo.autobahn.WebSocketConnection(915): opening handshake received

07-05 14:38:20.021: I/xxx(915): Status: Connected to ws://10.0.2.2:8080/xxx/xxx

07-05 14:38:20.021: D/de.tavendo.autobahn.WebSocketReader(915): run() : WebSocketException (de.tavendo.autobahn.WebSocketException: RSV != 0 and no extension negotiated)

07-05 14:38:20.030: D/de.tavendo.autobahn.WebSocketConnection(915): fail connection [code = 4, reason = WebSockets protocol violation

07-05 14:38:20.030: D/de.tavendo.autobahn.WebSocketReader(915): quit

07-05 14:38:20.030: D/de.tavendo.autobahn.WebSocketReader(915): ended

07-05 14:38:20.030: D/de.tavendo.autobahn.WebSocketWriter(915): ended

07-05 14:38:20.041: I/MDMClientActivity(915): Connection lost.

0 Likes

#2

Hello,

I'm using Tomcat 7.0.28 as a WS server. Is it interoperable with
autobahn? Here is the stack trace:

...

WebSocketException (de.tavendo.autobahn.WebSocketException: RSV != 0 and
no extension negotiated)
07-05 14:38:20.030: D/de.tavendo.autobahn.WebSocketConnection(915): fail
connection [code = 4, reason = WebSockets protocol violation

Tomcat seems to violate the WS protocol by sending WS frames with RSV bits set when no WS extension had been negotiated.

Are you enabling any WS extensions in Tomcat?

Which AutobahnAndroid version?

To verify whether Tomcat is actually doing wrong or AutobahnAndroid has a bug, you might want to test Tomcat for protocol compliance using
AutobahnTestsuite

http://autobahn.ws/testsuite

Hope that helps ..

···

Am 05.07.2012 21:03, schrieb birk:

0 Likes

#3

Thanks. Turned out to be user error.

···

On Thursday, July 5, 2012 4:11:58 PM UTC-4, Tobias Oberstein wrote:

Am 05.07.2012 21:03, schrieb birk:

Hello,

I’m using Tomcat 7.0.28 as a WS server. Is it interoperable with

autobahn? Here is the stack trace:

WebSocketException (de.tavendo.autobahn.WebSocketException: RSV != 0 and

no extension negotiated)

07-05 14:38:20.030: D/de.tavendo.autobahn.WebSocketConnection(915): fail

connection [code = 4, reason = WebSockets protocol violation

Tomcat seems to violate the WS protocol by sending WS frames with RSV
bits set when no WS extension had been negotiated.

Are you enabling any WS extensions in Tomcat?

Which AutobahnAndroid version?

To verify whether Tomcat is actually doing wrong or AutobahnAndroid has
a bug, you might want to test Tomcat for protocol compliance using

AutobahnTestsuite

http://autobahn.ws/testsuite

Hope that helps …

0 Likes

#4

Hello,

Would you mind sharing how the issue was resolved? (I am getting the same error).

···

On Tuesday, 10 July 2012 21:23:06 UTC+2, birk wrote:

Thanks. Turned out to be user error.

On Thursday, July 5, 2012 4:11:58 PM UTC-4, Tobias Oberstein wrote:

Am 05.07.2012 21:03, schrieb birk:

Hello,

I’m using Tomcat 7.0.28 as a WS server. Is it interoperable with

autobahn? Here is the stack trace:

WebSocketException (de.tavendo.autobahn.WebSocketException: RSV != 0 and

no extension negotiated)

07-05 14:38:20.030: D/de.tavendo.autobahn.WebSocketConnection(915): fail

connection [code = 4, reason = WebSockets protocol violation

Tomcat seems to violate the WS protocol by sending WS frames with RSV
bits set when no WS extension had been negotiated.

Are you enabling any WS extensions in Tomcat?

Which AutobahnAndroid version?

To verify whether Tomcat is actually doing wrong or AutobahnAndroid has
a bug, you might want to test Tomcat for protocol compliance using

AutobahnTestsuite

http://autobahn.ws/testsuite

Hope that helps …

0 Likes

#5

In my case it was missconfiguration of the tomact. More exactly:

wsChat

de.ago.emeeter.servlets.SOMENONEXISTINGCLASSNAME



wsChat
/websocket/chat

Maybe you should check you tomcat log files

···

Am Mittwoch, 17. Oktober 2012 21:04:32 UTC+2 schrieb Frans:

Hello,

Would you mind sharing how the issue was resolved? (I am getting the same error).

On Tuesday, 10 July 2012 21:23:06 UTC+2, birk wrote:

Thanks. Turned out to be user error.

On Thursday, July 5, 2012 4:11:58 PM UTC-4, Tobias Oberstein wrote:

Am 05.07.2012 21:03, schrieb birk:

Hello,

I’m using Tomcat 7.0.28 as a WS server. Is it interoperable with

autobahn? Here is the stack trace:

WebSocketException (de.tavendo.autobahn.WebSocketException: RSV != 0 and

no extension negotiated)

07-05 14:38:20.030: D/de.tavendo.autobahn.WebSocketConnection(915): fail

connection [code = 4, reason = WebSockets protocol violation

Tomcat seems to violate the WS protocol by sending WS frames with RSV
bits set when no WS extension had been negotiated.

Are you enabling any WS extensions in Tomcat?

Which AutobahnAndroid version?

To verify whether Tomcat is actually doing wrong or AutobahnAndroid has
a bug, you might want to test Tomcat for protocol compliance using

AutobahnTestsuite

http://autobahn.ws/testsuite

Hope that helps …

0 Likes