Re: SEVERE: BAD packet singnature 18245

2009-03-25 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Saju, On 3/24/2009 12:05 AM, Saju K K wrote: > I am using only one connector with tomcat( NIO connector) , In that case > also i get the same error . No, you're not: > minProcessors="5" maxProcessors="100" protocol="HTTP/1.1" > redirectPort="844

Re: SEVERE: BAD packet singnature 18245

2009-03-24 Thread Saju K K
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

Re: SEVERE: BAD packet singnature 18245

2009-03-24 Thread Saju K K
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 htt

Re: SEVERE: BAD packet singnature 18245

2009-03-24 Thread Saju K K
Hi, Thanks The issue was due to having the proxy module in the configuration . There were no space in the file .It all came when i copied and pasted the content in while submitting the query . Thanks a lot Saju Bill Barker-2 wrote: > > "Saju K K" wrote in message > news:22656151.p...@tal

Re: SEVERE: BAD packet singnature 18245

2009-03-23 Thread Bill Barker
"Saju K K" wrote in message news:22656151.p...@talk.nabble.com... > > 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 conf

Re: SEVERE: BAD packet singnature 18245

2009-03-23 Thread Saju K K
Hi, Thanks for you comments , I am using only one connector with tomcat( NIO connector) , In that case also i get the same error . Saju awarnier wrote: > > Saju K K wrote: > ... > Hi. > You probably see this yourself looking at your message in the list, but > somehow when you posted, yo

Re: SEVERE: BAD packet singnature 18245

2009-03-23 Thread André Warnier
Saju K K wrote: ... Hi. You probably see this yourself looking at your message in the list, but somehow when you posted, your sample configuration files got coded in a funny way, which makes it difficult to read them. I am not a specialist of the matter, but the "bad packet signature" makes m

SEVERE: BAD packet singnature 18245

2009-03-23 Thread Saju K K
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