-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Renuka,

On 10/12/2009 1:45 AM, Renuka Slalagi wrote:
> I am running tomcat jakarta-tomcat-4.1.31 on Solaris.As my server gets 
> down I get the below errors logged in catalina.

Tomcat 4.x is no longer supported, so you should upgrade to a more
recent version (they're on 6.0 these days).

> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run
> SEVERE: Caught exception (java.lang.NullPointerException) executing 
> org.apache.jk.common.socketconnect...@1cb0cb7, terminating thread Oct 10, 
> 2009 9:27:13 PM org.apache.jk.common.MsgAjp processHeader
> SEVERE: BAD packet signature 200
> 00 c8 00 00                                      | .?..

Hmm...

> Oct 10, 2009 9:27:13 PM org.apache.jk.common.MsgAjp processHeader
> SEVERE: BAD packet signature 18245
> 47 45 54 20 00 00 00 00 00 00 00 00 00 00 00 00  | GET ............


This looks like you have an AJP (or "JK") connector configured on a
port, but you're trying to speak HTTP to it.

Please post your server.xml configuration for all enabled <Connector>
elements, and provide an example URL that will cause this error to occur.

I suspect you have inadvertently configured an AJP connector on port 80
(or 8080, or whatever you expected to be an HTTP connector).

These log lines appear to be from a subsequent Tomcat startup:

> org.apache.coyote.http11.Http11Protocol init
> INFO: Initializing Coyote HTTP/1.1 on http-8080 Starting service 
> Tomcat-Standalone Apache Tomcat/4.1.31 Oct 11, 2009 4:20:04 PM 

The HTTP connector appears to be running on port 8080.

> org.apache.coyote.http11.Http11Protocol start
> INFO: Starting Coyote HTTP/1.1 on http-8080 Oct 11, 2009 4:20:18 PM 
> org.apache.jk.common.ChannelSocket init
> INFO: JK2: ajp13 listening on /0.0.0.0:8009 Oct 11, 2009 4:20:18 PM 
> org.apache.jk.server.JkMain start

The AJP connector appears to be running on port 8009.

Are you running Tomcat behind Apache httpd or some other web server? If
so, it's possible that you are trying to access port 8009 directly using
HTTP protocol instead of AJP.

> INFO: Jk running ID=0 time=1/52 
> config=/appl/apache/jakarta-tomcat-4.1.31/conf/jk2.properties

Yikes! You should get rid of jk2. mod_jk has incorporated everything
useful from the attempt at jk2 and jk2 is a completely dead project.

You should post the configuration from
/appl/apache/jakarta-tomcat-4.1.31/conf/jk2.properties as well.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrTcL8ACgkQ9CaO5/Lv0PD/qgCgkCX6yHCns41J3qHjk1IrU7BA
T7QAn2e6eYmS4QE8ZKIjJGHYh2iNfrjb
=woZ+
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to