The connector you show above is for AJP / JK connections; those that are between Apache HTTP server and Tomcat. It has nothing to do with Red5.
Paul On 9/5/07, David Engelmaier <[EMAIL PROTECTED]> wrote: > > Hello Lenny, thanks a lot for the guide, Hi Paul, thanks for the info > about the differences between standalone and war versions. > I tried both ways and got errors. Now i'm taking the way of changing the > RTMPT port in the red5.properties file and after > restarting tomcat everything seems to be ok in the logs, however when I > run the port tester application I get the following error > in the tomcat log: > Sep 6, 2007 1:52:28 AM org.apache.catalina.connector.CoyoteAdapter service > SEVERE: An exception or error occurred in the container during the > request processing > java.lang.ArrayIndexOutOfBoundsException: 0 > at > org.apache.catalina.connector.CoyoteAdapter.normalize(CoyoteAdapter.java > :524) > at > org.apache.catalina.connector.CoyoteAdapter.postParseRequest( > CoyoteAdapter.java:232) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java > :146) > at > org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199) > at > org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282) > at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java > :767) > at > org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java > :697) > at > org.apache.jk.common.ChannelSocket$SocketConnection.runIt( > ChannelSocket.java:889) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run( > ThreadPool.java:684) > at java.lang.Thread.run(Thread.java:619) > > my server.xml connector init looks like this: > <Connector port="8009" > enableLookups="false" redirectPort="8443" > protocol="AJP/1.3" /> > > my apache2 workers.properties look like this: > # Define 1 ajp13 worker > worker.list=worker1 > # Set properties for worker1 (ajp13) > worker.worker1.type=ajp13 > worker.worker1.host=localhost > worker.worker1.port=8009 > worker.worker1.lbfactor=50 > worker.worker1.socket_keepalive=1 > > my apache virtual host setting looks like this: > <VirtualHost *:80> > ServerName red5-0.6.2-java6 > DocumentRoot /var/lib/tomcat5.5/webapps/red5-0.6.2-java6 > ServerAdmin [EMAIL PROTECTED] > ErrorLog /var/log/apache2/error.log > CustomLog /var/log/apache2/red5.log combined > > Alias / "/var/lib/tomcat5.5/webapps/red5-0.6.2-java6" > <Directory "/var/lib/tomcat5.5/webapps/red5-0.6.2-java6"> > Options Indexes +FollowSymLinks > </Directory> > > JkMount /* worker1 > > <Location "/red5-0.6.2-java6/WEB-INF/"> > #AllowOverride None > deny from all > </Location> > </VirtualHost> > > Do you have any clues what the error might be related to? > Thanks > David > > Lenny Sorey wrote: > > Hi David, > > > > RTMPT works fine. > > > > I also run the same setup > > Java 1.6_2, Tomcat 6.0.13 / Apache 2.2.4 / Mod_jk, etc. > > > > You have to reference port 8080 for rtmpt instead of port 8080 > > in order for Tomcat to reroute rtmpt via 8009 to port 80. > > > > The only other alternative is to make changes to accommodate > > port 8088 in Tomcat's server.xml file. > > > > Make this change and try it again. > > > > Regards, > > > > Lenny > > > > > > On 9/5/07, *David Engelmaier* <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > I think to solve this issue we should analyse the case. I have the > > following configuration: > > Linux Debian Etch 2.6.18-4-amd64 > > Java Sun 1.6.0-b105 > > Apache Tomcat/5.5 > > Apache 2.2.4 > > Mod_Jk > > Red5 0.6.2 stable WAR > > > > The thing is the RTMPT service doesn't listen on the 8088 port as > it's > > set up in the red.properties and classes/red5.properties > > I don't think it's a problem of the Tomcat container as I saw > someone > > saying here in the discussion since if I run a standalone > > version a use nmap to scan the ports I get the following: > > > > Port 1935 - open/rtmp > > Port 8088 - open/unknown > > > > This shows in the standalone version the RTMPT service is listening > on > > port 8088 and using the port tester I can connect to it > localhost:8088 > > > > If I run the nmap on a WAR version I get the following: > > > > Port 1935 - open/rtmp > > Port 8088 - closed/unknown > > > > > > This shows the RTMP service is listening on the 1935 port > > regardless the > > Tomcat container in which it runs listens on port 8080 and > > 8009(jk_mod), > > so I guess it should be the same for the RTMPT service listening on > > 8088, then when we solve why it's not working on this port we can > > go on with > > the Mod_jk redirection(I've got this working for Apache2/Tomcat). > > > > I see Lenny and Joachim are the only people that got the RTMPT > working > > in the WAR version. I've read this mailing list and tutorials on > > the net and > > Red5 wiki, done test, but this is the point where I got, I can > > redirect > > trafic to port 80 to the Tomcat, but since the RTMPT service is > > just not > > listening > > on its port I'm not getting any further with setting up the RTMPT > :(. > > > > Any help largely appreciated > > Thanks > > David Engelmaier > > > > _______________________________________________ > > Red5 mailing list > > [email protected] <mailto:[email protected]> > > http://osflash.org/mailman/listinfo/red5_osflash.org > > <http://osflash.org/mailman/listinfo/red5_osflash.org> > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Red5 mailing list > > [email protected] > > http://osflash.org/mailman/listinfo/red5_osflash.org > > > > > -- > > David Engelmaier > > Software development consultant > > http://www.ixperience.net > > > _______________________________________________ > Red5 mailing list > [email protected] > http://osflash.org/mailman/listinfo/red5_osflash.org > -- It is difficult to free fools from the chains they revere. - Voltaire
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
