<div dir="ltr">Hello,<div><br></div><div>One question, why did my application work fine on Erlang 17.5.x branch?</div><div><br></div><div>If I want to set this <span style="font-size:12.8px">session_lifetime option, where should put it?</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">So there is no use that I should build the erlang 18 from maint branch?</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Thanks,</span></div><div><span style="font-size:12.8px">Sethy</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 21, 2015 at 2:51 PM, Ingela Andin <span dir="ltr"><<a href="mailto:ingela.andin@gmail.com" target="_blank">ingela.andin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello,<br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">2015-09-20 15:24 GMT+02:00 Sereysethy TOUCH <span dir="ltr"><<a href="mailto:touch.sereysethy@gmail.com" target="_blank">touch.sereysethy@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hello,<div><br></div><div>I did as what you told me by getting a shell console on the node.</div><div><br></div><div>I run memory(). and see ets ate the most memory. And it increased overtime. I run ets:i(). and I found out the ssl_manager took a big chunk of what memory used.</div><div><br></div><div><div>32794 client_ssl_otp_session_cache ordered_set 0 89 ssl_manager</div><div>36891 server_ssl_otp_session_cache ordered_set 1564 67995 ssl_manager</div><div>40993 httpc_manager__session_cookie_db bag 0 299 httpc_manager</div></div><div><br></div><div>So I think there is a problem with ssl_manager in Erlang OTP 18.</div><div><br></div><div>Any workarounds?</div><div><br></div></div></blockquote><div><br></div><div><br></div></span><div>Ok, the bug I fixed with the session table is on the client side. But your big ets table is on the server side. </div><div>Session data is by default fairly long lived (24 h that is the max recommended time to keep a session by the RFC), </div><div>you can set the ssl application variable session_lifetime to make its lifetime shorter which should mitigate your problem. </div><div>We have a backlog item to make a configurable threshold of max sessions allowed to be stored in the table, which I am sure will be</div><div>implemented fairly soon but alas not for 18.1.</div><div><br></div><div>Regards Ingela Erlang/OTP Team - Ericsson AB</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class=""><div dir="ltr"><div></div><div>Sethy</div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Sep 20, 2015 at 2:22 AM, Jesper Louis Andersen <span dir="ltr"><<a href="mailto:jesper.louis.andersen@gmail.com" target="_blank">jesper.louis.andersen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><span><br><div class="gmail_quote">On Sat, Sep 19, 2015 at 6:34 PM, Sereysethy TOUCH <span dir="ltr"><<a href="mailto:touch.sereysethy@gmail.com" target="_blank">touch.sereysethy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">I just recently updated Erlang to latest version OTP 18 on Ubuntu server. It uses cowboy (websocket), ranch, ssl, erlydtl & rabbitmq. It used to work fine in OTP 17. The program is correctly compiled but during the execution the memory kept increasing. I need to restart the process every one or two hours to free some memory.</blockquote></div><br></span>1. Get a shell console on the node</div><div class="gmail_extra">2. call 'memory().' in the shell</div><div class="gmail_extra">3. If it reports ets as the winner, call</div><div class="gmail_extra">4. ets:i().</div><div class="gmail_extra"><br></div><div class="gmail_extra">This will give you a nice overview for where to look and verify it is the SSL problem.<span><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div>J.</div>
</font></span></div></div>
</blockquote></div><br></div>
</div></div><br></span><span class="">_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br>
</span><a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
<br></blockquote></div><br></div></div>
</blockquote></div><br></div>