I can confirm there are problems with RTMPS version of Screensharing applet. Not sure right now what is wrong :( I'm working on it
On Fri, Dec 14, 2012 at 12:13 PM, Maxim Solodovnik <[email protected]>wrote: > can you try Revision > 1421672 ? > > on my machine start - stop - start was not working correctly ... now it > should. > Haven't tried https yet :( > > > On Fri, Dec 14, 2012 at 7:29 AM, Maxim Solodovnik <[email protected]>wrote: > >> I work as expected on my Ubuntu last night after the fix. I'll >> doublecheck on windows today >> On Dec 14, 2012 6:50 AM, "[email protected]" <[email protected]> >> wrote: >> >>> I am sorry, after doing an SVN update, starting the recording did work. >>> Stopping somehow didn't. >>> Same to screensharing. I could start it. I could verify locally that it >>> works. But hitting the pause button did not stop anything. >>> The only way to stop sharing or recording was to close the entire >>> screensharing client. >>> >>> Sebastian >>> >>> >>> 2012/12/14 [email protected] <[email protected]> >>> >>>> Also the regular Scrensharing does not work for me with trunk on OSX >>>> with Java 1.7_09 >>>> I think it there is (at least one) issue with the latest RTMPClient >>>> library of Red5. >>>> SSL might be affected too, however if that is another, the same (or no >>>> issue at all with SSL in latest RTMPClient) I can't say. >>>> >>>> Does Screensharing and Recording with latest trunk work for you Maxim? >>>> >>>> Sebastian >>>> >>>> >>>> 2012/12/14 Vsevolod <[email protected]> >>>> >>>>> I am sory, but it does not work. >>>>> As there is not new nightly build in >>>>> https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/, >>>>> I used svn to get source, so I got it and compiled with ant. () >>>>> >>>>> But when I try to use screensharing, if I click button "share" or >>>>> "record" nothing happened in java application, i have in server log >>>>> messages, ending with (debug ssl enabled): >>>>> >>>>> trigger seeding of SecureRandom >>>>> done seeding SecureRandom >>>>> Using SSLEngineImpl. >>>>> Allow unsafe renegotiation: false >>>>> Allow legacy hello messages: true >>>>> Is initial handshake: true >>>>> Is secure renegotiation: false >>>>> Using SSLEngineImpl. >>>>> Allow unsafe renegotiation: false >>>>> Allow legacy hello messages: true >>>>> Is initial handshake: true >>>>> Is secure renegotiation: false >>>>> pool-11-thread-5, WRITE: TLSv1 Application Data, length = 1 >>>>> pool-11-thread-5, WRITE: TLSv1 Application Data, length = 4 >>>>> >>>>> In java console on desktop I see >>>>> >>>>> DEBUG 12-13 22:29:50.316 CoreScreenShare.java 24985 224 >>>>> org.apache.openmeetings.screen.webstart.CoreScreenShare [AWT-EventQueue-0] >>>>> - captureScreenStart >>>>> >>>>> after about 8 seconds in java console window on desktop I see >>>>> >>>>> DEBUG 12-13 22:29:55.919 RTMPSScreenShare.java 30588 78 >>>>> org.apache.openmeetings.screen.webstart.RTMPSScreenShare [NioProcessor-8] >>>>> - >>>>> connection closed >>>>> DEBUG 12-13 22:29:55.920 CoreScreenShare.java 30589 308 >>>>> org.apache.openmeetings.screen.webstart.CoreScreenShare [NioProcessor-8] - >>>>> ScreenShare stopStream >>>>> >>>>> And in server log : >>>>> 2012-12-13 19:30:33,275 [pool-11-thread-3] INFO >>>>> o.r.s.n.r.codec.RTMPProtocolDecoder - Action userservice.refreshSession >>>>> 2012-12-13 19:30:35,579 [Red5_Scheduler_Worker-3] WARN >>>>> o.r.server.net.rtmp.RTMPConnection - Closing RTMPMinaConnection from >>>>> 193.178.34.39 : 52364 to null (in: 0 out: 0), with id 9 due to long >>>>> handshake >>>>> >>>>> RITE: TLSv1 Alert, length = 2 >>>>> NioProcessor-36, called closeInbound() >>>>> NioProcessor-36, fatal error: 80: Inbound closed before receiving >>>>> peer's close_notify: possible truncation attack? >>>>> >>>>> javax.net.ssl.SSLException: Inbound closed before receiving peer's >>>>> close_notify: possible truncation attack? >>>>> NioProcessor-36, SEND TLSv1 ALERT: fatal, description = >>>>> internal_errorNioProcessor-36, SEND TLSv1 ALERT: fatal, description = >>>>> internal_error >>>>> NioProcessor-36, Exception sending alert: java.io.IOException: writer >>>>> side was already closed. >>>>> NioProcessor-36, called closeOutbound() >>>>> NioProcessor-36, closeOutboundInternal() >>>>> >>>>> In OpenMeetings 2.0 reloease and last nightly build ( >>>>> https://builds.apache.org/view/M-R/view/OpenMeetings/job/OpenMeetings%202.0/) >>>>> it works good. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> WBR >>>>> Maxim aka solomax >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> >>>> >>>> >>>> -- >>>> Sebastian Wagner >>>> https://twitter.com/#!/dead_lock >>>> http://www.webbase-design.de >>>> http://www.wagner-sebastian.com >>>> [email protected] >>>> >>> >>> >>> >>> -- >>> Sebastian Wagner >>> https://twitter.com/#!/dead_lock >>> http://www.webbase-design.de >>> http://www.wagner-sebastian.com >>> [email protected] >>> >> > > > -- > WBR > Maxim aka solomax > -- WBR Maxim aka solomax
