[
https://issues.apache.org/jira/browse/OPENMEETINGS-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SebastianWagner updated OPENMEETINGS-295:
-----------------------------------------
Description:
You can test by:
Modifying the config.xml, change "rtmpport" to a invalid setting.
It will try rtmpt then.
rtmpt loads the first 1500 labels but then stops.
I've test with windows and OSX acting as server as well as acting as client.
Same results.
There is a warning in the red5 log:
2012-05-27 10:48:33,117 [Red5_Scheduler_Worker-3] WARN
o.r.server.net.rtmp.RTMPConnection - This often happens if YOUR Red5
application generated an exception on start-up. Check earlier in the log for
that exception first!
2012-05-27 10:48:33,118 [Red5_Scheduler_Worker-3] INFO
o.o.a.r.r.ScopeApplicationAdapter - W3C x-category:session x-event:disconnect
c-ip:192.168.1.3 c-client-id:14
2012-05-27 10:48:33,126 [Red5_Scheduler_Worker-3] INFO
o.o.a.r.r.ScopeApplicationAdapter - W3C x-category:session x-event:disconnect
c-ip:192.168.1.3 c-client-id:14
2012-05-27 10:48:33,164 [http-0.0.0.0-8088-exec-2] WARN
o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
2012-05-27 10:48:34,399 [http-0.0.0.0-8088-exec-4] WARN
o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
2012-05-27 10:48:35,612 [http-0.0.0.0-8088-exec-5] WARN
o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
2012-05-27 10:48:36,849 [http-0.0.0.0-8088-exec-1] WARN
o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
2012-05-27 10:48:38,084 [http-0.0.0.0-8088-exec-3] WARN
o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
2012-05-27 10:48:39,323 [http-0.0.0.0-8088-exec-2] WARN
o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
2012-05-27 10:48:40,557 [http-0.0.0.0-8088-exec-4] WARN
o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
2012-05-27 10:48:41,788 [http-0.0.0.0-8088-exec-5] WARN
o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
2012-05-27 10:48:43,024 [http-0.0.0.0-8088-exec-1] WARN
o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
2012-05-27 10:48:44,258 [http-0.0.0.0-8088-exec-3] WARN
o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
2012-05-27 10:48:45,494 [http-0.0.0.0-8088-exec-2] WARN
o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
was:
You can test by:
Modifying the config.xml, change "rtmpport" to a invalid setting.
It will try rtmpt then.
rtmpt loads the first 1500 labels but then stops (without any error message or
exception)
I've test with windows and OSX acting as server as well as acting as client.
Same results.
Affects Version/s: 2.0 Apache Incubator Release
Fix Version/s: 2.0 Apache Incubator Release
> OpenMeetings with rtmp over HTTP Tunneling does not work anymore with Red5
> r4374
> --------------------------------------------------------------------------------
>
> Key: OPENMEETINGS-295
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-295
> Project: Openmeetings
> Issue Type: Bug
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: SebastianWagner
> Fix For: 2.0 Apache Incubator Release
>
>
> You can test by:
> Modifying the config.xml, change "rtmpport" to a invalid setting.
> It will try rtmpt then.
> rtmpt loads the first 1500 labels but then stops.
> I've test with windows and OSX acting as server as well as acting as client.
> Same results.
> There is a warning in the red5 log:
> 2012-05-27 10:48:33,117 [Red5_Scheduler_Worker-3] WARN
> o.r.server.net.rtmp.RTMPConnection - This often happens if YOUR Red5
> application generated an exception on start-up. Check earlier in the log for
> that exception first!
> 2012-05-27 10:48:33,118 [Red5_Scheduler_Worker-3] INFO
> o.o.a.r.r.ScopeApplicationAdapter - W3C x-category:session x-event:disconnect
> c-ip:192.168.1.3 c-client-id:14
> 2012-05-27 10:48:33,126 [Red5_Scheduler_Worker-3] INFO
> o.o.a.r.r.ScopeApplicationAdapter - W3C x-category:session x-event:disconnect
> c-ip:192.168.1.3 c-client-id:14
> 2012-05-27 10:48:33,164 [http-0.0.0.0-8088-exec-2] WARN
> o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
> 2012-05-27 10:48:34,399 [http-0.0.0.0-8088-exec-4] WARN
> o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
> 2012-05-27 10:48:35,612 [http-0.0.0.0-8088-exec-5] WARN
> o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
> 2012-05-27 10:48:36,849 [http-0.0.0.0-8088-exec-1] WARN
> o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
> 2012-05-27 10:48:38,084 [http-0.0.0.0-8088-exec-3] WARN
> o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
> 2012-05-27 10:48:39,323 [http-0.0.0.0-8088-exec-2] WARN
> o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
> 2012-05-27 10:48:40,557 [http-0.0.0.0-8088-exec-4] WARN
> o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
> 2012-05-27 10:48:41,788 [http-0.0.0.0-8088-exec-5] WARN
> o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
> 2012-05-27 10:48:43,024 [http-0.0.0.0-8088-exec-1] WARN
> o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
> 2012-05-27 10:48:44,258 [http-0.0.0.0-8088-exec-3] WARN
> o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
> 2012-05-27 10:48:45,494 [http-0.0.0.0-8088-exec-2] WARN
> o.r.server.net.rtmpt.RTMPTServlet - Null connection for clientId: 23
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
