List of usage examples for org.springframework.messaging.simp.config ChannelRegistration taskExecutor
public TaskExecutorRegistration taskExecutor()
From source file:configuration.WebSocketConfig.java
@Override public void configureClientOutboundChannel(ChannelRegistration registration) { registration.taskExecutor().corePoolSize(100).maxPoolSize(100); }
From source file:com.devnexus.ting.config.WebSocketConfig.java
@Override public void configureClientOutboundChannel(ChannelRegistration registration) { registration.taskExecutor().corePoolSize(4).maxPoolSize(10); }
From source file:org.lightadmin.logging.configurer.config.WebSocketConfiguration.java
@Override public void configureClientOutboundChannel(ChannelRegistration registration) { registration.taskExecutor().corePoolSize(4).maxPoolSize(8); }
From source file:org.lightadmin.logging.configurer.config.WebSocketConfiguration.java
@Override public void configureClientInboundChannel(ChannelRegistration registration) { registration.taskExecutor().corePoolSize(4).maxPoolSize(8); }
From source file:com.cb.config.WebSocketConfig.java
/** * Configure the {@link org.springframework.messaging.MessageChannel} used * for outgoing messages to WebSocket clients. By default the channel is * backed by a thread pool of size 1. It is recommended to customize thread * pool settings for production use.// w w w .j a v a 2 s . co m */ @Override public void configureClientOutboundChannel(ChannelRegistration registration) { registration.taskExecutor().corePoolSize(4).maxPoolSize(10); }
From source file:opensnap.config.WebSocketConfig.java
@Override public void configureClientOutboundChannel(ChannelRegistration registration) { registration.taskExecutor().corePoolSize(1).maxPoolSize(1); }
From source file:de.metas.ui.web.websocket.WebSocketConfig.java
@Override public void configureClientOutboundChannel(final ChannelRegistration registration) { ///* ww w . j a v a2 s .c o m*/ // IMPORTANT: make sure we are using only one thread for sending outbound messages. // If not, it might be that the messages will not be sent in the right order, // and that's important for things like WS notifications API. // ( thanks to http://stackoverflow.com/questions/29689838/sockjs-receive-stomp-messages-from-spring-websocket-out-of-order ) registration.taskExecutor().corePoolSize(1).maxPoolSize(1); }