search

man2015 / red5phone

Automatically exported from code.google.com/p/red5phone
0 stars 0 forks source link

8 new established socket pairs that never closed after each phone call #73

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
We had found a strange problem when we tested the red5phone.
After starting the red5phone server, we use "netstat" to monitor network
port usage.
(ps. we had use "netstat -b" to confirm these sockets are established by
java process)

When we make phone calls from the web page, the established socket pairs
continue growing.
It seems to establish 8 new socket pairs that never closed after each phone
call.

after 1 call
  TCP    127.0.0.1:54336        james:54337            ESTABLISHED
  TCP    127.0.0.1:54337        james:54336            ESTABLISHED
  TCP    127.0.0.1:54338        james:54339            ESTABLISHED
  TCP    127.0.0.1:54339        james:54338            ESTABLISHED
  TCP    127.0.0.1:54340        james:54341            ESTABLISHED
  TCP    127.0.0.1:54341        james:54340            ESTABLISHED
  TCP    127.0.0.1:54342        james:54343            ESTABLISHED
  TCP    127.0.0.1:54343        james:54342            ESTABLISHED

after the 2nd call
  TCP    127.0.0.1:54336        james:54337            ESTABLISHED
  TCP    127.0.0.1:54337        james:54336            ESTABLISHED
  TCP    127.0.0.1:54338        james:54339            ESTABLISHED
  TCP    127.0.0.1:54339        james:54338            ESTABLISHED
  TCP    127.0.0.1:54340        james:54341            ESTABLISHED
  TCP    127.0.0.1:54341        james:54340            ESTABLISHED
  TCP    127.0.0.1:54342        james:54343            ESTABLISHED
  TCP    127.0.0.1:54343        james:54342            ESTABLISHED

  TCP    127.0.0.1:54354        james:54355            ESTABLISHED
  TCP    127.0.0.1:54355        james:54354            ESTABLISHED
  TCP    127.0.0.1:54356        james:54357            ESTABLISHED
  TCP    127.0.0.1:54357        james:54356            ESTABLISHED
  TCP    127.0.0.1:54358        james:54359            ESTABLISHED
  TCP    127.0.0.1:54359        james:54358            ESTABLISHED
  TCP    127.0.0.1:54360        james:54361            ESTABLISHED
  TCP    127.0.0.1:54361        james:54360            ESTABLISHED

Does anyone notice this problem and know the reason?

Original issue reported on code.google.com by chengwei...@gmail.com on 19 Oct 2009 at 7:51

GoogleCodeExporter commented 9 years ago 
I noticed this problem too...it keeps growing and will only close if you 
restart 
red5. I'm using windows, does linux have this issue too?

Original comment by eleoson....@gmail.com on 21 Oct 2009 at 3:39

GoogleCodeExporter commented 9 years ago 
Hi,
I do confirm the problem also on linux , i don't think this issue should be
considered as "Medium"  the application is not usable for mass production,  
after a
number of calls Red5 crash because of the too many pipes opened. For now i fix 
the
problem creating a cron job to restart Red5 every 1 hour. But it is not so clean
solution. Hope somebody could fix this issue asap.

Regards
Fabio

Original comment by galdifa...@gmail.com on 11 Apr 2010 at 11:18

GoogleCodeExporter commented 9 years ago 
This might have smething to do with this issue as well -> 
RED5 doesn't properly Unregister peers from SIP proxy

http://code.google.com/p/red5phone/issues/detail?id=126&start=100

Original comment by g1dan...@googlemail.com on 13 Sep 2010 at 2:38