We think things seem stable with the timeout at the moment, but a big
<br>
problem I think we have is reestablishing the socket after the timeout
<br>
happens and drops the connection (the tcp connection to rabbitmq). I
<br>
believe this requires a restart of OpenSIPS to get messages flowing to
<br>
rabbitmq again. This isn't preventing us with moving forward, it's more of
<br>
a nuissance at the moment than anything, and the core hanging problem seems
<br>
to have been fixed with this pull request.
<br>
<br>
It's a problem we really haven't had a lot of time to work on right now,
<br>
but Frank's changes have at least prevented OpenSIPS from possibly hanging
<br>
processing due to rabbitmq falling behind/becoming unavailable. The other
<br>
thing we want to see added (and might add ourselves and contribute when we
<br>
have time) is more than the default exchange configuration, being able to
<br>
configure more than the default user/password in the connect url, etc --
<br>
just minor enhancements. I think Frank made a pull request around being
<br>
able to configure routing to an exchange other than default, but we haven't
<br>
really had a lot of time to test that either and I didn't see that one
<br>
accepted.
<br>
<br>
I hope this helps.
<br>
<br>
<br>
On Tue, Mar 11, 2014 at 6:00 AM, Răzvan Crainea <notifications@github.com>wrote:
<br>
<br>
> Any updates on this? Are you still experiencing any issues?
<br>
>
<br>
> —
<br>
> Reply to this email directly or view it on GitHub<https://github.com/OpenSIPS/opensips/issues/81#issuecomment-37279231>
<br>
> .
<br>
>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>Reply to this email directly or <a href='https://github.com/OpenSIPS/opensips/issues/81#issuecomment-37367416'>view it on GitHub</a>.<img src='https://github.com/notifications/beacon/5479561__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcxMDIwNzg0NiwiZGF0YSI6eyJpZCI6MTcyOTc0NDR9fQ==--9f077dfda29885567f7d3f02f7b8cddfe4cb3e35.gif' height='1' width='1'></p>