spring-websocket

I am creating a sample chat application using the Spring websockets and stomp.js , I am using the tomcat 7.54 but while runing the application I am gettting a async-supported error when browser is making xhr request. Server info: Apache Tomcat/7.0.54 Servlet version: 3.0 JSP version: 2.2 Java version: 1.7.0_25 Web.xml <?xml version="1.0" encoding="UTF-8"?> <web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"> <servlet> <async

I have the following contoller @Controller public class GreetingController { @MessageMapping("/hello") @SendTo("/topic/greetings") public Person greeting(String message) throws Exception { Person person=new Person(); person.setAge(10); return person; } @Autowired private SimpMessagingTemplate template; @RequestMapping(path="/meeting",method=RequestMethod.POST) public @ResponseBody void greet() { this.template.convertAndSend("/topic/greetings", "message"); } } and my configuration is @Configuration @EnableWebSocketMessageBroker public class WebSocketConfig1 extends

I have used spring implementation of sockjs websocket server and unable to transmit message over 8KB, following is the error 2014-02-12 19:36:29,990 - org.springframework.web.socket.sockjs.transport.session.WebSocketServerSockJsSession - DEBUG - SockJS session id=35n41xel was closed, CloseStatus [code=1009, reason=The decoded text message was too big for the output buffer and the endpoint does not support partial messages] Any Idea how can I increase the buffer size I used following factory as spring sockjs leverages tomcat container (App is deployed in tomcat and I also debugged to confirm

I am able to send and receive JSON with STOMP over WebSockets following spring documentation . However performance is poor at large high rates, so I wish to profile the use of binary messages. Spring-WebSockets 4.0 JavaScript client running in Chrome 35 stomp.js 1.7.1 Sending I send messages using SimpMessageTemplate with the necessary broker relay - see spring documentation @Controller public class DemoBinaryController { @Autowired private SimpMessagingtemplate template @Scheduled(fixedDelay = 5000) public void demo() throws Exception { GenericMessage<byte[]> message = new GenericMessage<byte

Hi I need to deploy my Spring Boot app into Wildfly 8.1 and I'm getting the following exception: Caused by: java.lang.RuntimeException: java.lang.ClassCastException: org.apache.tomcat.websocket.server.WsServerContainer cannot be cast to io.undertow.websockets.jsr.ServerWebSocketContainer at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:219) at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:87) at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService

I've searched quite a bit and been unable to find this: Is there a way that a spring websocket stomp server can disconnect a client based on the sessionId (or really based on anything at all)? It seems to me that once a client connects to a server there is nothing that allows the server to disconnect the client. As far as I know the API doesn't provide what you are looking for, on server-side you can only detect disconnect events. If you want to disconnect a certain client I think you must go for a litte workaround, e.g. this one: Write a client-side javascript function that is able to trigger

I would like to understand how convertAndSendToUser works in Spring SockJS+Websocket framework. In client, we would connect as stompClient.connect(login, password, callback()) which will result in connect request with "Stomp credentials" of login and password, that can be seen e.g. if we handle SessionConnectEvent http://www.sergialmar.com/2014/03/detect-websocket-connects-and-disconnects-in-spring-4/ But it remains unclear to me whether this will be the "user" meant in server-side send operation to a queue: simpMessagingTemplate.convertAndSendToUser(username, "/queue/reply", message); The

Shall I use WebSocket on non-80 ports? Does it ruin the whole purpose of using existing web/HTTP infrastructures? And I think it no longer fits the name Web Socket on non-80 ports. If I use WebSocket over other ports, why not just use TCP directly? Or is there any special benefits in the WebSocket protocol itself? And since current WebSocket handshake is in the form of a HTTP UPGRADE request, does it mean I have to enable HTTP protocol on the port so that WebSocket handshake can be accomplished? Shall I use WebSocket on non-80 ports? Does it ruin the whole purpose of using existing web/HTTP