Hi, I've been checking the logs again and here's what I get from red5:
2013-08-09 13:58:56,293 [main] INFO o.r.s.net.rtmp.RTMPMinaTransport - RTMP Mina Transport bound to /0.0.0.0:1935 2013-08-09 13:58:56,387 [main] INFO o.r.s.net.rtmp.RTMPMinaTransport - RTMP Mina Transport bound to /0.0.0.0:8443 2013-08-09 13:58:56,897 [main] INFO o.a.coyote.http11.Http11Protocol - Initializing ProtocolHandler ["http-bio-0.0.0.0-7443"] 2013-08-09 13:59:07,223 [main] INFO o.a.coyote.http11.Http11Protocol - Starting ProtocolHandler ["http-bio-0.0.0.0-7443"] 2013-08-09 13:59:09,697 [main] INFO o.a.coyote.http11.Http11NioProtocol - Initializing ProtocolHandler ["http-nio-8088"] 2013-08-09 13:59:09,704 [main] INFO o.a.coyote.http11.Http11NioProtocol - Starting ProtocolHandler ["http-nio-8088"] 2013-08-09 13:59:11,998 [main] INFO o.a.coyote.http11.Http11NioProtocol - Initializing ProtocolHandler ["http-nio-8443"] 2013-08-09 13:59:12,004 [main] INFO o.a.coyote.http11.Http11NioProtocol - Stopping ProtocolHandler ["http-nio-8443"] 2013-08-09 13:59:12,004 [main] INFO o.a.coyote.http11.Http11NioProtocol - Starting ProtocolHandler ["http-nio-8443"] So it actually does sound like for some reason we do use 8443 for both. We've been through the configuration now a few times. One part I don't understand is this: Edit red5/conf/jee-container.xml file: Comment Tomcat without SSL enabled section UNComment Tomcat with SSL enabled section I didn't actually do the setup but a colleague did that and he said: "After certain version of Openmeetings, jee-container.xml doesn't have the tomcat commented sections anymore. Instead, there are 2 xml files - jee-container.xml and jee-container-ssl.xml. To enable SSL, I think I only had to rename the jee-container to another name. And the one with the ssl to jee-container.xml." So reading the above I'm thinking there's an issue in our jee-container.xml. But which section exactly would I have to comment? Would it be the whole section of <bean id="tomcat.server" class="org.red5.server.tomcat.TomcatLoader" init-method="init" destroy-method="shutdown" depends-on="context.loader"> or just some part of it? There's also a section for RTMPT, should that be active? Thanks, Daniela On 2013-08-01, at 9:51 AM, Maxim Solodovnik wrote: > Is it possible you have chosed 8443 for both RTMPS and HTTPS? OM 2.1 requires > 2-3 _different_ ports > > > On Thu, Aug 1, 2013 at 10:14 PM, Daniela Kirsch <[email protected]> > wrote: > Hi, > > netstat only shows one line for port 8443 when OpenMeetings is started, it > doesn't list anything when ended: > tcp 0 0 0.0.0.0:8443 0.0.0.0:* > LISTEN > > However I did search a bit and found that it could be caused when red5 isn't > shut down properly, meaning when you kill the process it might not release > the ports. So the suggestion was to use red5-shutdown.sh > That script is a little confusing, do we have to change it? It's the > following right now: > > # port, username, password > export RED5_OPTS="9999 red5user changeme" > export RED5_MAINCLASS=org.red5.server.Shutdown > exec $RED5_HOME/red5.sh > > But if we were to change that line with port, username, password, what would > it be? > > Thanks, > Daniela > > On 2013-07-31, at 4:19 PM, Maxim Solodovnik wrote: > >> Hello Daniela, >> >> http://openmeetings.apache.org/RTMPSAndHTTPS.html is the most recent >> document. According to my observations all need to be done is to follow this >> instruction step by step :) >> >> "Address already in use" usually means some other application is using same >> port (can be checked with netstat) >> >> >> On Thu, Aug 1, 2013 at 5:32 AM, Daniela Kirsch <[email protected]> >> wrote: >> Hi, >> >> we are trying to set up RTMPS with Open Meetings 2.1. >> >> There are 2 documents that we found: >> https://code.google.com/p/openmeetings/wiki/RTMPSandHTTPS >> http://openmeetings.apache.org/RTMPSAndHTTPS.html >> >> They are almost identical, however both say Open Meetings 1.9 is required. >> So are the settings the same for 2.1? If not, is there some other >> documentation? >> >> In the red5.log we get a few error messages on server startup (8443 is the >> port we want to use): >> 2013-07-31 14:14:20,424 [main] ERROR o.a.coyote.http11.Http11NioProtocol - >> Failed to initialize end point associated with ProtocolHandler >> ["http-nio-8443"] >> java.net.BindException: Address already in use >> >> 2013-07-31 14:14:20,425 [main] ERROR o.a.catalina.core.StandardService - >> Failed to start connector >> [Connector[org.apache.coyote.http11.Http11NioProtocol-8443]] >> org.apache.catalina.LifecycleException: Failed to initialize component >> [Connector[org.apache.coyote.http11.Http11NioProtocol-8443]] >> >> 2013-07-31 14:14:20,427 [main] ERROR o.a.coyote.http11.Http11NioProtocol - >> Failed to start end point associated with ProtocolHandler ["http-nio-8443"] >> java.net.BindException: Address already in use >> >> 2013-07-31 14:14:20,428 [main] ERROR o.r.server.tomcat.rtmps.RTMPSLoader - >> Error initializing RTMPS server instance >> org.apache.catalina.LifecycleException: Failed to start component >> [Connector[org.apache.coyote.http11.Http11NioProtocol-8443]] >> >> When we disable port 1935 lots of problems occur and we can't use the >> application. >> >> Thanks, >> Daniela >> >> >> >> -- >> WBR >> Maxim aka solomax > > > > > -- > WBR > Maxim aka solomax
