[
https://issues.apache.org/jira/browse/OPENMEETINGS-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Ghenov updated OPENMEETINGS-576:
---------------------------------------
Attachment: OPENMEETINGS-576
Hello,
This tunneling patch working for om 3.00 via port 80,
but in 2.1 Revision 1496470 i getting an a issue.
I can login to OM, but if i try to enter any room i getting:
DEBUG 06-25 14:46:38.199 UploadController.java 532933 143
org.apache.openmeetings.servlet.outputhandler.UploadController
[http-bio-0.0.0.0-80-exec-6] - [CLIENT MESSAGE] error
NetConnection.Connect.Closed undefined undefined name: getServerForSession false
Looks like sometging wrong with testSetup.lzx.
Tunneling working in 3.0 (port 80) with followning configuration:
dist/red5/conf/jee-container.xml - disable tomcat <!-- RTMPT (dedicated server)
--> bean by deleting or comenting.
dist/red5/conf/red5.proporties - set this settings:
http.port=80
dist/red5/webapps/openmeetings/web-inf/web.xml - uncomment <!-- Rtmpt red5
servlet -->.
dist/red5/webapps/openmeetings/public/config.xml - set this settings:
<red5httpport>80</red5httpport>
enable red 5 servlet
<usered5RTMPT>yes</usered5RTMPT>.
I used apache derby db,
Red5 running under root debian account (For development, it can be fixed with
port remapping, becouse linux not allow to use port 80 to no-root processes).
To get tunneling working in 2.1 Revision 1496470 (And reproduse issue) need
make following changes in configuration:
dist/red5/conf/jee-container.xml - disable tomcat "RTMPT (dedicated server)"
bean by deleting or comenting.
dist/red5/conf/red5.proporties - set this settings:
http.port=80
rtmpt.target_reponse_size=8192
dist/red5/conf/red5.core - set this settings:
Delete this bean defination (Labeled with <!-- RTMPT -->) -<bean
id="rtmptConnManager" class="org.red5.server.net.rtmp.RTMPConnManager" />-
Replace property in bean id="rtmptServlet" -<property
name="rtmpConnManager" ref="rtmptConnManager" />-
+<property
name="rtmpConnManager" ref="rtmpMinaConnManager" />+
dist/red5/webapps/openmeetings/config.xml - set this settings:
<red5httpport>80</red5httpport>
enable RTMPT servlet
<usered5RTMPT>yes</usered5RTMPT>.
dist/red5/webapps/openmeetings/web-inf/web.xml - enable RTMPT servlet invoke
(added in patch, but commented).
I used apache derby db,
Red5 running under root debian account (For development, it can be fixed with
port remapping, becouse linux not allow to use port 80 to no-root processes).
> Suggestion about the tunnelling implementation.
> -----------------------------------------------
>
> Key: OPENMEETINGS-576
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-576
> Project: Openmeetings
> Issue Type: New Feature
> Environment: Unix
> Reporter: Alexey Ghenov
> Priority: Minor
> Labels: newbie
> Attachments: build.properties, build.xml, OPENMEETINGS-576
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> - proper traffic tunnelling (images and screensharing now use 5080 port, SIP
> applet likely uses different ports as well, while anything should be happy
> with 80 port);
> - performance: getting rid of Apache httpd to improve openmeetings hosting
> performance (Apache eats tons os megabytes - proper jetty configuration can
> be done as a part of tunelling task);
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
