Hi Bill, As I mentioned earlier we have an apache http server and the tomcat container in place. In the previous implementation we were able to configure tomcat NIO channels to accept the requests(with mod_jk enabled). Our new implementation needs more enhanced support for comet as well as http on the tomcat server.
We were able to connect to the comet connector(HttpNioConnector) and ajp/http1.1 when we configured then independently on different port .On having a httserver in the front we need to configure connectors in such a way, to make that tomcat accept comet event request and http request. As ajp type is the only connector available for apache to connect to tomcat, we are not able to submit the request to the comat implementation directly with the standerd connectors configured (mentioned below) .Also the worker type doesn’t support HttpNioConnector types. 1) 2) 3) (Use only to test comet independently) Is there a way by which we can accept comet event request and http request by having an APR or NIO AJP connectors configured within tomcat? Can we have any of the below mentioned configuration enabled. 1) Configure connectors to accept the http request and convert it to an APR type which can allow the tomcat to access the comet implementation over HttpNioConnector 2) Configure connectors to accept the http request and convert it to NIO/AJP which can allow the tomcat to access the comet implementation over HttpNioConnector Saju K K Bill Barker-2 wrote: > > "Saju K K" wrote in message > news:[email protected]... >> >> On configuring nio/ajp I am getting and error org.apache.common.MsgApj >> p= >> rocessHeader " SEVER: BAD packet singnature 18245" >> >> We are using jdk 1.5.0_14/ apache-tomcat-6.0.18 / redhat linux 2.6.9 . >> I have tried configuring the following one at a time and it is working >> fine= >> . In order to have a high performance proxy we want to configure both >> nio/= >> ajp and http/ajp together in tomcat and make it listen to apache http >> serve= >> r on 8080. >> >> >> Tomcat server.xml >> >> mi= >> nProcessors=3D"5" maxProcessors=3D"100" protocol=3D"HTTP/1.1" >> redirectPort= >> =3D"8443" /> protocol=3D"org.apache.coyote.= http11.Http11NioProtocol" >> connectionTimeout=3D"20000" redirectPort=3D"8343= " /> >> redirectPort=3D"8943" /> redirectPort=3D"8643" channelNioSocket.soT= >> imeout=3D"600000" >> protocol=3D"AJP/1.3" port=3D"0" channelNioSocket.port=3D"= 8084" >> channelNioSocket.maxThreads=3D"150" channelNioSocket.maxSpareThreads= >> =3D"50" channelNioSocket.minSpareThreads=3D"25" >> channelNioSocket.bufferSize= >> =3D"16384"/> >> > > Going to have to agree with André here. You have extra spaces in both the > address and port attributes, which should prevent the NIO/AJP connector > from > starting at all. But it seems that it is starting. > > It looks like you are using mod_proxy_ajp instead of mod_jk. If this is > the > case, then the worker.properties file won't be read. > > Note that the NIO/AJP connector is currently considered "experimental" by > the TC developers, since it hasn't had the amount of testing that the > other > connectors have. That is why there is no offical documentation for it. > > If, despite the above warning, you want to continue using it, then set the > logging level for the category org.apache.jk to FINE, and post the results > here. I'll be more than happy to look into it if I have a test case. > >> worker.properties >> >> worker.list=3Dworker1,worker2,worker3 >> workers.tomcat_home=3D/opt/www/tomcat-6.0/apache-tomcat-6.0.18 >> workers.java_home=3D/root/softwares/jdk1.5.0_14 >> ps=3D/ >> # Define Node1 >> # modifies the host as your host IP or DNS name. >> >> worker.worker1.port=3D8083 >> worker.worker1.host=3Dserdev41 >> worker.worker1.type=3Dajp13 >> worker.worker1.lbfactor=3D1 >> worker.worker1.connection_pool_size=3D150 >> worker.worker1.connection_pool_timeout=3D600 >> worker.worker1.socket_keepalive=3D1 >> >> worker.worker2.port=3D8080 >> worker.worker2.host=3Dserdev41 >> worker.worker2.type=3Dajp13 >> worker.worker2.lbfactor=3D2 >> worker.worker2.connection_pool_size=3D150 >> worker.worker2.connection_pool_timeout=3D600 >> worker.worker2.socket_keepalive=3D1 >> >> worker.worker3.port=3D8084 >> worker.worker3.host=3Dserdev41 >> worker.worker3.type=3Dajp13 >> worker.worker3.lbfactor=3D3 >> worker.worker3.connection_pool_size=3D150 >> worker.worker3.connection_pool_timeout=3D600 >> worker.worker3.socket_keepalive=3D1 >> >> mod_jk.conf >> >> LoadModule jk_module modules/mod_jk.so >> JkWorkersFile conf/workers.properties >> JkLogFile logs/mod_jk.log >> JkLogLevel info >> JkLogStampFormat "[%a %b %d %H: %M: %S %Y]" >> JkRequestLogFormat "%w %V %T" >> JkMount /* worker3 >> >> >> Httpd.conf >> >> ProxyRequests off >> >> Order deny,allow >> Allow from all >> >> ProxyPreserveHost On >> ProxyPass /proxy ajp://serdev41:8084 >> ProxyPassReverse /proxy ajp://serdev41:8084 >> >> Include conf/mod_jk.conf >> LoadModule proxy_module modules/mod_proxy.so >> LoadModule proxy_http_module modules/mod_proxy_http.so >> >> >> On making a request I am getting we are getting the above mentioned >> error >> = >> ,what could be the problem for this >> >> Thanks in advance >> >> -- >> View this message in context: >> http://www.nabble.com/SEVERE%3A--BAD-packet-singnature-18245-tp22656151p22656151.html >> Sent from the Tomcat - User mailing list archive at Nabble.com. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://www.nabble.com/SEVERE%3A--BAD-packet-singnature-18245-tp22656151p22695544.html Sent from the Tomcat - User mailing list archive at Nabble.com.
