Malvern, if the problem persists, could you please file a JIRA issue? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095
On Tue, Jun 4, 2013 at 9:04 AM, Alexei Fedotov <[email protected]> wrote: > It seems the same problem with RTMPS here > http://markmail.org/thread/4t3jhgphslrk32yr > > > -- > With best regards / с наилучшими пожеланиями, > Alexei Fedotov / Алексей Федотов, > http://dataved.ru/ > +7 916 562 8095 > > > On Tue, Jun 4, 2013 at 7:50 AM, Maxim Solodovnik <[email protected]> > wrote: >> >> sorry for the late reply, >> I'll try for double-check >> >> >> On Sun, Jun 2, 2013 at 1:43 PM, Malvern Star <[email protected]> >> wrote: >> >> > Hi all, >> > >> > I've been trying to deploy the latest OpenMeetings 2.1.0 but without >> > much >> > success. I have, as far as I'm aware, correctly configured the software, >> > and set it up with a commercially signed certificate to use RTMPS and >> > HTTPS. However, after some random length of time in a conference room >> > (up >> > to 20 minutes or so so far, but can be as little as 30 seconds), the >> > room >> > locks up and my red5.log displays the following message(s) or similar: >> > >> > [Red5_Scheduler_Worker-3] WARN o.r.server.net.rtmp.RTMPConnection - >> > Closing RTMPMinaConnection from xxx.xxx.xxx.xxx : 51904 to >> > www.<oursite>.org:5443 (in: 10341680 out 24640359 ), with id 5, due to >> > too >> > much inactivity (1663994 ms), last ping sent 1000 ms ago >> > >> > HTTPS is running on port 8443, RTMPS is running on port 5443. This >> > occurs >> > whether the system has a firewall running or not, so it does not appear >> > to >> > be a firewall misconfiguration. I have tried both using the precompiled >> > binaries and compiling from source. I have tried on Ubuntu 12.04 LTS >> > Server >> > and CentOS 6.4. >> > >> > Has anybody encountered this problem, and if so does anybody know what >> > to >> > do about it? Googling has not turned up much except a list of people >> > having >> > the same problem who were unable to resolve the situation, and there was >> > one reference to it being a known bug but being long since resolved. >> > >> > Malvern. >> >> >> >> >> -- >> WBR >> Maxim aka solomax > >
