" in OM right above the whiteboard I got the same information" seems to be fixed
On 6 August 2014 18:54, Peter Dähn <[email protected]> wrote: > ok... :-( > > > Am 06.08.2014 um 13:30 schrieb Maxim Solodovnik: > > " in OM right above the whiteboard I got the same information" known > issue :( not sure since when > > > On 6 August 2014 18:25, Peter Dähn <[email protected]> wrote: > >> tried from W7 Chrome and FF also works... and I'm in the room with the >> "stopped one" I could give it moderation and start private chat... >> >> probably just a problem here... don't know.. >> >> but what also happened yesterday.. I couldn't stop recording... the >> recording itself stopped at the time i hit the button but the button said >> that I'm still recording and in OM right above the whiteboard I got the >> same information... I closed the screenrecord-window. The recording was >> produced as always... >> >> Greetings Peter >> >> Am 06.08.2014 um 13:16 schrieb Maxim Solodovnik: >> >> Ubuntu 14.04+Chrome also works ... >> weird >> >> >> On 6 August 2014 17:55, Vasiliy Degtyarev <[email protected]> wrote: >> >>> >>> Hello all, >>> >>> I enters to this room now without problem. >>> I have used Firefox on windows 7. >>> >>> Vasiliy >>> >>> >>> >>> On 06.08.2014 17:48, Peter Dähn wrote: >>> >>> right now I tried to enter the room >>> http://demo.dataved.ru:5080/openmeetings/#room/4 >>> I used public rooms list to get there... It stops with showing the blue >>> line... >>> >>> I let it as it is by now.. maybe you can have a look in the logs... >>> >>> This time I used Linux Mint 17 an Chrome with pepper flash... >>> >>> I try to test it with other browsers/os's >>> >>> Greetings Peter >>> >>> Am 06.08.2014 um 10:39 schrieb Maxim Solodovnik: >>> >>> never saw such behavior >>> what is the OS browser? >>> Is there anything in the developer console of the browser? >>> how are you entering the room? using direct URL: openmeetings/#room/2 of >>> using public/private/my rooms list? >>> >>> >>> On 6 August 2014 14:07, Peter Dähn <[email protected]> wrote: >>> >>>> it stops loading and just show the "blue line"... and in the logs that >>>> error... >>>> >>>> the second time everything is fine... >>>> >>>> as I made the record yesterday at dataved.ru i need to enter the room >>>> also twice... maybe the same problem??? This was also from a different >>>> maschine as I used at my testserver.... >>>> >>>> Greetinge Peter >>>> >>>> Am 05.08.2014 um 17:49 schrieb Maxim Solodovnik: >>>> >>>> >> "an i needed to enter a room twice till it woked" >>>> what was wrong after first room enter? >>>> >>>> >>>> On 5 August 2014 22:45, Guido Hornig <[email protected]> wrote: >>>> >>>>> >>>>> >>>>> Sent from SMail on Android >>>>> >>>>> On 05/08/14 16:53:53, >>>>> Maxim Solodovnik <[email protected]> wrote: >>>>> >definitely red5 synchronization error >>>>> >haven't seen this before :( >>>>> > >>>>> >is it latest build? >>>>> > >>>>> > >>>>> >On 5 August 2014 19:30, Peter Dähn <[email protected]> wrote: >>>>> > >>>>> >> Hallo together, >>>>> >> >>>>> >> I am going to test OM 3.0.3. >>>>> >> >>>>> >> I get the following error while enter a room... >>>>> >> >>>>> >> [WARN] [RTMPExecutor#DRSZB4JVU8LAR-1] >>>>> >> org.red5.server.net.rtmp.RTMPMinaConnection - Interrupted while >>>>> waiting for >>>>> >> write lock. State: connected >>>>> >> java.lang.InterruptedException: null >>>>> >> at >>>>> >> >>>>> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1325) >>>>> >> ~[na:1.7.0_55] >>>>> >> at java.util.concurrent.Semaphore.tryAcquire(Semaphore.java:414) >>>>> >> ~[na:1.7.0_55] >>>>> >> at >>>>> >> >>>>> org.red5.server.net.rtmp.RTMPMinaConnection.write(RTMPMinaConnection.java:366) >>>>> >> ~[red5-server.jar:na] >>>>> >> at org.red5.server.net.rtmp.Channel.write(Channel.java:136) >>>>> >> [red5-server.jar:na] >>>>> >> at org.red5.server.net.rtmp.Channel.write(Channel.java:106) >>>>> >> [red5-server.jar:na] >>>>> >> at >>>>> >> org.red5.server.net.rtmp.RTMPHandler.onCommand(RTMPHandler.java:485) >>>>> >> [red5-server.jar:na] >>>>> >> at >>>>> >> >>>>> org.red5.server.net.rtmp.BaseRTMPHandler.messageReceived(BaseRTMPHandler.java:89) >>>>> >> [red5-server.jar:na] >>>>> >> at >>>>> >> >>>>> org.red5.server.net.rtmp.ReceivedMessageTask.call(ReceivedMessageTask.java:55) >>>>> >> [red5-server.jar:na] >>>>> >> at >>>>> >> >>>>> org.red5.server.net.rtmp.ReceivedMessageTask.call(ReceivedMessageTask.java:11) >>>>> >> [red5-server.jar:na] >>>>> >> at java.util.concurrent.FutureTask.run(FutureTask.java:262) >>>>> >> [na:1.7.0_55] >>>>> >> at >>>>> >> >>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) >>>>> >> [na:1.7.0_55] >>>>> >> at java.util.concurrent.FutureTask.run(FutureTask.java:262) >>>>> >> [na:1.7.0_55] >>>>> >> at >>>>> >> >>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >>>>> >> [na:1.7.0_55] >>>>> >> at >>>>> >> >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >>>>> >> [na:1.7.0_55] >>>>> >> at java.lang.Thread.run(Thread.java:744) [na:1.7.0_55] >>>>> >> >>>>> >> The 2nd time everything works fine... Any ideas? >>>>> >> >>>>> >> Greetings Peter >>>>> >> >>>>> > >>>>> > >>>>> > >>>>> >-- >>>>> >WBR >>>>> >Maxim aka solomax >>>>> >>>> >>>> >>>> >>>> -- >>>> WBR >>>> Maxim aka solomax >>>> >>>> >>> >>> >>> -- >>> WBR >>> Maxim aka solomax >>> >>> >>> >> >> >> -- >> WBR >> Maxim aka solomax >> >> > > > -- > WBR > Maxim aka solomax > > -- WBR Maxim aka solomax
