Hi Subikar,
Thanks Subikar. We've looked through the logs and we can see lots of
exceptions and errors with regards to the SIP. These appear as
log-red5\sip.log(156100): 2009-12-09 16:45:25,732 [NioProcessor-2]
ERROR org.red5.server.webapp.sip.RTMPUser - RTMPUser stopStream
exception java.lang.NullPointerException
log-red5\sip.log(156110): 2009-12-09 16:45:25,733 [NioProcessor-1]
ERROR org.red5.server.webapp.sip.RTMPUser - RTMPUser stopStream
exception java.lang.NullPointerException
log-red5\sip.log(156128): 2009-12-09 16:45:25,736 [NioProcessor-2]
ERROR org.red5.server.webapp.sip.RTMPUser - RTMPUser stopStream
exception java.lang.NullPointerException
log-red5\sip.log(156144): 2009-12-09 16:45:25,742 [NioProcessor-1]
ERROR org.red5.server.webapp.sip.RTMPUser - RTMPUser stopStream
exception java.lang.NullPointerException
and
log-red5\sip.log(74776): 2009-11-22 14:12:29,515 [NioProcessor-12]
DEBUG o.r.s.webapp.sip.RTPStreamSender - RTPStreamSender - Exception
- -> java.lang.ArrayIndexOutOfBoundsException
log-red5\sip.log(74777): 2009-11-22 14:12:29,515 [NioProcessor-15]
DEBUG o.r.s.webapp.sip.RTPStreamSender - RTPStreamSender - Exception
- -> java.lang.ArrayIndexOutOfBoundsException
log-red5\sip.log(74778): 2009-11-22 14:12:29,557 [NioProcessor-15]
DEBUG o.r.s.webapp.sip.RTPStreamSender - RTPStreamSender - Exception
- -> java.lang.ArrayIndexOutOfBoundsException
log-red5\sip.log(74779): 2009-11-22 14:12:29,557 [NioProcessor-12]
DEBUG o.r.s.webapp.sip.RTPStreamSender - RTPStreamSender - Exception
- -> java.lang.ArrayIndexOutOfBoundsException
log-red5\sip.log(74780): 2009-11-22 14:12:29,599 [NioProcessor-15]
DEBUG o.r.s.webapp.sip.RTPStreamSender - RTPStreamSender - Exception
- -> java.lang.ArrayIndexOutOfBoundsException
We've been going through the SIP code and systematically hunting down
and fixing these bugs. Needless to say, 0.63 should be much less
resource intensive for VoIP. Another problem is the amount of logging
that the SIP code creates. In 0.63 we've added a parameter to /usr/
share/red5/webapps/sip/WEB-INF/bigbluebutton-sip.properties to reduce
the logging
# If you want mjsip stack (red5/log/*access*.log) to minimize the
amount of logs it
# generates, set this to a lower value (e.g. 3).
sipStackDebugLevel=3
For the moment, the best course of action is to add a cron job that
restarts red5 once a day. In parallel, we'll let you know as soon as
0.63 is ready for testing.
Regards,... Fred
On Dec 11, 7:44 am, Subikar Burman <
subikar....@gmail.com> wrote:
> Hi Fred,
>
> Nice to chat with you. As per your request here is the log files zip of
> those folder.
>
>
http://www.soberfolk.org/log-red5.ziphttp://www.soberfolk.org/logs-tomcat6.zip
> > >
bigbluebutton-...@googlegroups.com<bigbluebutton-dev%2Bunsubscr
i...@googlegroups.com><bigbluebutton-dev%2Bunsubscr
> > >
bigbluebutton-...@googlegroups.com<bigbluebutton-dev%2Bunsubscr
i...@googlegroups.com><bigbluebutton-dev%2Bunsubscr
>
bigbluebutton-...@googlegroups.com<bigbluebutton-dev%2Bunsubscr
i...@googlegroups.com>
> .
> For more options, visit this group athttp://
groups.google.com/group/bigbluebutton-dev?hl=en.