-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OutOfMemoryError #33
Comments
Hi @ProChirathF, without further info it looks like working as intended. A size of 1048576 could be quite a lot for a buffer depending on the element you are storing and the number of actors instantiated. From what I understood clients are not able to cope with the outgoing message rate and the entire flow is back pressured all the way up till your Actor wrapped by the ActorFlow. Usually you would end up implementing rate-limiting mechanisms within your Actor to stop producing messages if downstream is back pressuring, but unluckily ActorFlow doesn't give any mean to detect it. What I can suggest is to try out I hope this helps. Since this doesn't look like related to play2-sockjs, I'll be closing the issue. Feel free to re-open it if you have more findings that could lead to a memory leak within paly2-sockjs. |
@fdimuccio I have Implemented a custom flow using Source.actorRefWithAck (akka v2.5), which sends a 'ack' back to the user WebSocket actor after emitting the message to the downstream. This bachpressure mechanism together with a sensible inputBuffer on the source allows message throttling. Thank you for your advice!. Thanks |
I am using SockJS with Play2.7 & I am seeing OutOfMemeory crashes intermittently. We never experienced this issue with Play2.5.
SockJS router is handled with an actor(WebSocketActor). WebSocketActor receives a very high volume of messages, hence large buffer is used(1048576) is defined for ActorFlow.actorRef
SockJs router
Any thoughts or guidance is highly appreciated.
The text was updated successfully, but these errors were encountered: