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

Reply via email to