top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

standalone use of Tomcat 8 websocket-api.jar getWebSocketContainer returning null

+1 vote
610 views

I'm trying to use the Tomcat8 jsr client functionality in a standalone java client. I'm trying to use the minimal number of jars, so I gabbed websocket-api.jar ONLY. When I call ContainerProvider.getWebSocketContainer(), it returns null. Do I need another jar to resolve this on the client?

posted Aug 22, 2013 by Kumar Mitrasen

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

Yes. You need tomcat-websocket.jar (the implementation) and its dependencies (tomcat-juli.jar and tomcat-util.jar). It is possible to split the implementation into client and server but we haven't done that. It isn't like the JARs are that big anyway.

answer Aug 22, 2013 by Garima Jain
Similar Questions
+1 vote
Tomcat 8 Websocket API: Cookies & Headers

I'm trying to figure out how to get access to the cookies and headers passed up in the Websocket handshake request on Tomcat 8.

In Tomcat 7 the whole HttpServletRequest was passed into the WebSocketServlet. createWebSocketInbound method so it was easy to grab from the request headers. In Tomcat 8 the querystring and URI are both exposed by the javax.websocket.Session passed to ServerEndPoint.onOpen, but I don't see a mechanism for getting the cookies or headers.

We are integrating Websocket connections into an existing web app and want to use the cookies set by our web app in the Websocket connection process.

+2 votes
Tomcat: Accessing ServletContext from WebSocket endpoint

Is there a standard way to access ServletContext from a WebSocket ServerEndpoint ?

+2 votes
Tomcat Websocket failover

In our current generation web application we used session replication with tomcat clustering. (and a load balancer). That way, we received an auto fail-over when a client sends an ajax request to a tomcat node that failed.

In our next generation web application, We would like to have a similar behavior, only with web-sockets. So my questions are :

1) Is it possible ?
2) Does it involve websocket-session replication? if so, are there any guides on how to do that?

+3 votes
Are there any websocket-specific tomcat 7 connector settings?

As we start load testing our jsr-356 applications, I'd like to find out if there are any websocket-specific connector settings we should be aware of for tuning the underlying websocket connection processing. Since this is a tcp socket at the end of the day, I'm assuming all the socket.* options still apply if needed.

+1 vote
Tomcat closes websocket without any error receiving WebSocket ContinuationFrames

Has anyone had a large WS message sent as the response to an outbound call? We have a scenario where the request causes a 300K WS message to be sent back as the "response". The client is sending multiple WS continuation frames and after a couple of frames are successfully sent, Tomcat just closes the websocket connection. I the response fits in a single frame, it's fine. Where can I look to try and troubleshoot this?

...