SmartFox Server 2X Web Socket Problem

[mete2221]

SmartFox Server 2X closing Web Socket's connection with 1006 error code.
This problem usually happens while large packet transmission

Error writing to client: { Id: 144, Type: WEBSOCKET, Logged: Yes, IP: 127.0.0.1:54572 }
java.lang.InterruptedException
at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1326)
at java.util.concurrent.Semaphore.tryAcquire(Semaphore.java:409)
at org.apache.tomcat.util.net.SocketWrapperBase.vectoredOperation(SocketWrapperBase.java:1451)
at org.apache.tomcat.util.net.SocketWrapperBase.write(SocketWrapperBase.java:1403)
at org.apache.tomcat.util.net.SocketWrapperBase.write(SocketWrapperBase.java:1374)
at org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer.doWrite(WsRemoteEndpointImplServer.java:91)
at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.writeMessagePart(WsRemoteEndpointImplBase.java:494)
at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.startMessage(WsRemoteEndpointImplBase.java:381)
at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendBytesByCompletion(WsRemoteEndpointImplBase.java:151)
at org.apache.tomcat.websocket.WsRemoteEndpointAsync.sendBinary(WsRemoteEndpointAsync.java:65)
at sfs2x.ws.tomcat.websocket.SFS2XWSService._write(SFS2XWSService.java:338)
at sfs2x.ws.tomcat.websocket.SFS2XWSService.write(SFS2XWSService.java:331)
at com.smartfoxserver.bitswarm.websocket.tomcat.WebSocketBinaryProtocolCodec.onPacketWrite(WebSocketBinaryProtocolCodec.java:121)
at com.smartfoxserver.bitswarm.core.BitSwarmEngine.writeToWebSocket(BitSwarmEngine.java:421)
at com.smartfoxserver.bitswarm.core.BitSwarmEngine.write(BitSwarmEngine.java:402)
at com.smartfoxserver.bitswarm.io.Response.write(Response.java:70)
at com.smartfoxserver.v2.api.response.SFSResponseApi.sendExtResponse(SFSResponseApi.java:84)
at com.smartfoxserver.v2.api.SFSApi.sendExtensionResponse(SFSApi.java:1534)
at com.game.main.service.SFSResponseService.sendResponse(SFSResponseService.java:45)
at com.game.main.service.SFSResponseService.sendResponse(SFSResponseService.java:37)
at com.game.main.service.ResponseService.sendResponse(ResponseService.java:24)
at com.game.main.handler.WalkHandler$WalkWorker.run(WalkHandler.java:187)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

[Lapo]

Hi,
can you give us an example of a packet that would cause this issue?

Thanks

[mete2221]

Hi,
can you give us an example of a packet that would cause this issue?

Thanks

Packet Encoded as Base64

"AIgEd/ugBIV4nK1XyXLiSBCF7o6YvvQc+hN0nT5oo8NyhA/sRm3JrFrqpg0JUwJCLJbU4b+cD5osWgJcsgw45uIyBfUy82Xmy6rvlc+V6up79rda+eJaG+vr3//+ZraL2c6L1h5z+5uZewlzyzxzzA9mYYWwxfQnilJX67CxXXvRwyycbZhbrsb+YKZbjBfeeg0ffzDREnvwH1Ov390xL+TzMjwChlY09zaA4S6X0a/9lktshNaKmOhygdNsiGNBXiEeb/sjh31sOYvePe47IV5YuijJ6URUms4/rcFSbo7jJ6vbWTmzxhzppiTzamjwvdhI4QzB4tcne+7UHjk+6uIEcAU5aYiwxsrM8b0xuwBM33uCdTwHew7YaQOGD2t9q8J3qAXfjZxd32d/NQfzG5MPAsvoAZ4W9kfuE8LSTNFuUsCdwz6cUwCHnG8nsFcDW8+w/oQ1IXhuusfzLYLbFFlyjvgjJzfvxZYYvDxVj3FweRwE81UcT72Px4GlwEgncG64cgCL2PPIufEAMOcEC9YlrD3wtyH88buxJDE+PMFvuoO93YdUVJv+XO531aWp4wTwMAI8h9emhHcqBv5/4UlQsUG4p3xX6Tx/jJ8UaTfsMceTLMcmzcvzZbzIO695ml+5dqjLEe1vO/O3l/nbzvB67+C1WeNYhxzFb0w4ecXv6I34Q0nM8+ZCXTz+qXHiY62Al2R4s8vxjAOHRf8e6fzneLPy/Bjpm/0hlPp6rC3ugtqaQo9z5/PfFov5n5zJv5uYOhegUNqW9/SAqtn2GUwucEM8RV1pbRr1Mj0SKF/jjIfkhIeZLfg5x6ypB6yZ9dVjoU6V63wUGtjWZWwIOHC7nahEC3I+E8pHtsTHZ6RzM6RJqaWjnb3A2JnlGlancxWXYMdnsCNXVzmLk+Y2H8Pceltnru4xXQ0As2Yaw8BKMo6pOsh1kaylmK/7YmMaaAUcc27YSWzg2eA3O/t+yBEbWa+kB+2h7BX68CIdHmKLj8Fmg0NFrU8LdUNm9vV6zCJ9s7Y06dnVzeK8SudUrpUL59VpfaqB3Y1XeS6U1Kcx0yv7Z2PqtQjpYtaPiliYe7Q2nakZi8c1U0fY7Ry0mVUSmt+8LwcXasdm5emdEBnD/aze13ZLoWPns9jZC3snsgwMGqfBXGpn8Q9SKv59bZyt75P4HWEY2OEgzmKn58iBz8fr8BLzoBkTer7nmslfGHcK2rZFLTk4aHtBN/0S3eyV36PutdCA+kRJob84+l6rtuof6S/oKzR1eGldnHkTeo6wyuginXjFi6m7U9dQWaJHTrjh7HstOmhEYf6ZWQzmhbMFuOGkDTJk8B1hG0uRLcig2zF37GeHzi1X0s+lMYD+T21dSyAHPNJrU4uXEkvQ1q6+znucrvFEpbk6V5OQA0PQfrpv47MF/LK5M/bf42ofi6nHb+UjLtyhr9Qph+8soF53dkcKYPacxpFkNva9+vo9Rt/TCzm/eYB7jtMS78i7csfcwpN0RZaXl0o1+lKpfEorVedr5S94t5JnZ6Vqfa58g61P1f8Ac8wIbAA="

[Lapo]

This doesn't look like a valid packet. Either something is missing or it's invalid data.
Can you show us how the Extension is generating/creating the data?
(if you prefer to do it privately send me a private message)

Also, I have tested sending a 330KB image from Extension to client, via the BlueBox, and it did not flinch. I don't think it's a matter of packet size.

Thanks

[Lapo]

One more thing, if there's a proxy between client and server, like a reverse proxy you might want to double check it's configuration especially in terms of timeouts. If I remember correctly you were using Cloudflare as part of your network setup.

[mete2221]

One more thing, if there's a proxy between client and server, like a reverse proxy you might want to double check it's configuration especially in terms of timeouts. If I remember correctly you were using Cloudflare as part of your network setup.

I am not using a proxy. (Like Cloudflare)
I sent a private message.