My application is basically a content-based router that will route MMS events.
The logger I'm using is the one that comes with the SASL " error_logger " OTP environment
Problem:
I use the client to create MMS events with default values. This client (in Java) has the ability to send a high load of events to several threads
I send 100 events in 10 threads (each thread sending 10 MMS messages) to my router written in erlang / OTP.
The problem is that when such a high load is received by my router, my Logger freezes , that is, it stops updating my log file. But the router is still able to route events.
The conclusions I came up with are:
1) The planning task in erlang when receiving such a high load of events (a separate erlang process for each event).
2) A very unlikely state of a dead position.
3) Perhaps this is due to the sending of events in several threads, and not by sending them. But I assume that the router will be connected to several mailboxes of the service provider, so I thought about sending events to streams.
Can anyone help in demystifying the problem?