You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Maurizio Calcara <m....@cgsgroup.it> on 2000/07/03 11:32:47 UTC
Re: HANDLER THREAD PROBLEM
Hi Rob,
thank's for your help.
Unfortunately I'm trying to use ajpv12 as communication protocol
(ajpv12://localhost:8007), but Netscape says "Netscape is unable to
locate the server ajpv12:.".
Are there other configurations that have to be made on the server ??
Thank you again,
Maurizio
"Rob S." wrote:
> 'allo,We did the same thing when we were installing Tomcat =) The
> protocol used to communicate with Tomcat on port 8007 is ajpv12.
> You're trying to use HTTP. By default, that port is meant for
> webserver-Tomcat communication.Hope it helps!- r
>
> -----Original Message-----
> From: maurizio@cgsgroup.it [mailto:maurizio@cgsgroup.it]On
> Behalf Of Maurizio Calcara
> Sent: June 30, 2000 9:14 AM
> To: tomcat-user@jakarta.apache.org
> Subject: HANDLER THREAD PROBLEM
> Hi,
> I'm installing "Tomcat 3.1" on a Linux RedHat 6.1 system
> running a 2.2.15 kernel and the "jdk1.2.2" Java version.
> By using Tomcat in stand-alone mode it works fine.
>
> When I try to use Tomcat with Apache (both 1.3.9 and 1.3.12)
> by means the "mod_jserv.so" (I try to connect to
> "http://localhost:8007", the default settings) the console
> produces the following error:
>
> HANDLER THREAD PROBLEM: java.io.IOException:
> Stream brokenjava.io.IOException: Stream broken
> at
> org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Ajp12ConnectionHandler.java:386)
>
> at
> org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection(Ajp12ConnectionHandler.java:134)
>
> at
> org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.java:338)
>
> at java.lang.Thread.run(Thread.java:475)
>
>
> Please, Is there anybody that solved this problem???
> Any idea??
> Thanks,
> Maurizio Calcara
>
> --
>
> dr. Maurizio Calcara
> m.calcara@cgsgroup.it
>
>
>
--
dr. Maurizio Calcara
m.calcara@cgsgroup.it
Re: HANDLER THREAD PROBLEM
Posted by Maurizio Calcara <m....@cgsgroup.it>.
Hi Ed, hi Rob,
Thank's for your support. Now it is clear how I have to use the
mod_jeserv.so and, finally, it is *WORKING* fine. I think it was
working before too, but I didin't use it correclty. :-)
Thank you again.
Ed wrote:
> The mistake is the http://localhost:8007 bit. You don't talk to the
> tomcat servlet engine directly, you must go through a web server. In
> stand alone mode, Tomcat creates it's own web-server which you must go
> through (by default it is 8080), however when you combine it with
> apache, you MUST go through the apache webserver process - you have no
> choice (unless of course you grab the ajpv12 protocol code and write
> your own client...) I apologise if the following is a little
> patronising, but here goes :)Example of calling the SnoopServletThe
> URL would be http://your.host.name/servlet/SnoopServlet The tomcat
> apache config file instructs apache that any request to the servlet
> directory is to be passed to tomcat via the ajpv12 protocol so it can
> process the request instead - this is completely transparent to the
> calling client browser - as apache itself cannot serve Servlets
> directly. A similar case is for the jsp files.A url to a jsp page
> could behttp://your.host.name/test/realPath.jsp The tomcat apache conf
> file instructs apache that any url with file extension .jsp is to be
> sent to tomcat for serving, again using the ajpv12 protocol. So, what
> I'm saying here is that tomcat, when combined with another web server,
> is a little server for use purely for the web-server to handle
> requests that the web-server can't deal with personally. I hope this
> helps :)
--
dr. Maurizio Calcara
m.calcara@cgsgroup.it
RE: HANDLER THREAD PROBLEM
Posted by "Rob S." <rs...@home.com>.
Maurizio,
As a supplement to Ed's very-well-put replies on this thread...
The form of a URL is: protocol://hostname:portnumber/path
When you talk to a webserver, like Apache, with your browser, you are using
the HTTP protocol, which is why you type in:
http://www.RobSlifka.com/GodFatherOfSoul/
Here, protocol = http, hostname = www.RobSlifka.com, port = 80 ("well-known"
/ default for the HTTP protocol), and path = /GodFatherOfSoul/
What you're telling your browser to do is to use the HTTP protocol to carry
out communications with the host www.RobSlifka.com on port 80, and you are
requesting the contents of the path /GodFatherOfSoul.
Now, think about what you're attemping with Netscape. From your web
browser, you're trying to talk to Tomcat on port 8007 by using the AJPV12
protocol. ***This protocol is not used for communication from a web browser
to a web server***. This is a protocol used by Tomcat/JServ/Apache for
internal communication ***ONLY***. The *only only only* time you need deal
with AJP is making sure that Tomcat has an AJP listen port (8007 by default,
and is obviously working with your setup or else Tomcat wouldn't be giving
you the HANDLER THREAD exceptions) and that Apache is set to communicate
with it. Other than that, you never ever ever need to even think about
AJPV12, let alone type it in anywhere.
Hope this helps!
- r
-----Original Message-----
From: Ed [mailto:ed@jsq.co.uk]
Sent: July 3, 2000 9:38 AM
To: tomcat-user@jakarta.apache.org
Subject: Re: HANDLER THREAD PROBLEM
The mistake is the http://localhost:8007 bit. You don't talk to the
tomcat servlet engine directly, you must go through a web server. In stand
alone mode, Tomcat creates it's own web-server which you must go through (by
default it is 8080), however when you combine it with apache, you MUST go
through the apache webserver process - you have no choice (unless of course
you grab the ajpv12 protocol code and write your own client...)
I apologise if the following is a little patronising, but here goes :)
Example of calling the SnoopServlet
The URL would be http://your.host.name/servlet/SnoopServlet
The tomcat apache config file instructs apache that any request to the
servlet directory is to be passed to tomcat via the ajpv12 protocol so it
can process the request instead - this is completely transparent to the
calling client browser - as apache itself cannot serve Servlets directly.
A similar case is for the jsp files.
A url to a jsp page could be
http://your.host.name/test/realPath.jsp
The tomcat apache conf file instructs apache that any url with file
extension .jsp is to be sent to tomcat for serving, again using the ajpv12
protocol.
So, what I'm saying here is that tomcat, when combined with another web
server, is a little server for use purely for the web-server to handle
requests that the web-server can't deal with personally.
I hope this helps :)
----- Original Message -----
From: Maurizio Calcara
To: tomcat-user@jakarta.apache.org
Sent: Monday, July 03, 2000 4:32 PM
Subject: Re: HANDLER THREAD PROBLEM
Hi Ed,
thank's for your help.
Yes, I use "ajp12" inside the "tomcat-apache.conf" file, that I have
copied into the /etc/http/conf dir. I have modified inside this
configuration file only the path to the mod_jserv.so (in the file
generated by tomcat there was "libexec/mod_jserv.so", I have the modules
inside the "modules" dir. "/etc/httpd/modules", as a standard RedHat 6.1
installation), by writing "modules/mod_jserv.so" instead
"libexec/mod_jserv.so".
No errors appear during the startup phase. When I type into the Netscape
location box "http://localhost:8007" the error "HANDLER THREAD PROBLEM: ..."
appears on the console.
Where is the mistake?
Have you copied the mod_jserv.so into the /etc/httpd/modules (that is a
link /usr/lib/apache/) dir ?
Maurizio
Ed wrote:
Ok, I've read your original problem again and I need a bit more
clarification.Where exactly are you typing in this URL to the ajpv12? If
you are in fact typing the ajpv12://localhost directly into the netscape URL
thingy then it will completely fail as it is not a standard internet
protocol like http, ftp or gopher. This ajpv12 thing should only appear
inside your configuration script(s). The tomcat-apache.conf file *can*
contain this protocol specifier if you are attempting to connect to a tomcat
server other than the one that is on the local host (or using a different
port). Normally the default tomcat-apache.conf file that should be included
in the main http.conf will work (apart from checking the that the location
to the mod_jserv library is correct). Personally, I installed apache 3.1.12,
tomcat, tomcat source and apache development packages onto my RedHat 6.2
box. After compiling the mod_jserv.so with apxs (instructions in the user
guide), copying the tomcat-apache.conf into /etc/httpd/conf directory,
including it in the http.conf file, altering tomcat-apache.conf so that it
had the correct path to mod_jserv.so and finally starting up the servers it
just ran fine. I modified nothing else.
--
dr. Maurizio Calcara
m.calcara@cgsgroup.it
Re: HANDLER THREAD PROBLEM
Posted by Ed <ed...@jsq.co.uk>.
The mistake is the http://localhost:8007 bit. You don't talk to the tomcat servlet engine directly, you must go through a web server. In stand alone mode, Tomcat creates it's own web-server which you must go through (by default it is 8080), however when you combine it with apache, you MUST go through the apache webserver process - you have no choice (unless of course you grab the ajpv12 protocol code and write your own client...)
I apologise if the following is a little patronising, but here goes :)
Example of calling the SnoopServlet
The URL would be http://your.host.name/servlet/SnoopServlet
The tomcat apache config file instructs apache that any request to the servlet directory is to be passed to tomcat via the ajpv12 protocol so it can process the request instead - this is completely transparent to the calling client browser - as apache itself cannot serve Servlets directly.
A similar case is for the jsp files.
A url to a jsp page could be
http://your.host.name/test/realPath.jsp
The tomcat apache conf file instructs apache that any url with file extension .jsp is to be sent to tomcat for serving, again using the ajpv12 protocol.
So, what I'm saying here is that tomcat, when combined with another web server, is a little server for use purely for the web-server to handle requests that the web-server can't deal with personally.
I hope this helps :)
----- Original Message -----
From: Maurizio Calcara
To: tomcat-user@jakarta.apache.org
Sent: Monday, July 03, 2000 4:32 PM
Subject: Re: HANDLER THREAD PROBLEM
Hi Ed,
thank's for your help.
Yes, I use "ajp12" inside the "tomcat-apache.conf" file, that I have copied into the /etc/http/conf dir. I have modified inside this configuration file only the path to the mod_jserv.so (in the file generated by tomcat there was "libexec/mod_jserv.so", I have the modules inside the "modules" dir. "/etc/httpd/modules", as a standard RedHat 6.1 installation), by writing "modules/mod_jserv.so" instead "libexec/mod_jserv.so".
No errors appear during the startup phase. When I type into the Netscape location box "http://localhost:8007" the error "HANDLER THREAD PROBLEM: ..." appears on the console.
Where is the mistake?
Have you copied the mod_jserv.so into the /etc/httpd/modules (that is a link /usr/lib/apache/) dir ?
Maurizio
Ed wrote:
Ok, I've read your original problem again and I need a bit more clarification.Where exactly are you typing in this URL to the ajpv12? If you are in fact typing the ajpv12://localhost directly into the netscape URL thingy then it will completely fail as it is not a standard internet protocol like http, ftp or gopher. This ajpv12 thing should only appear inside your configuration script(s). The tomcat-apache.conf file *can* contain this protocol specifier if you are attempting to connect to a tomcat server other than the one that is on the local host (or using a different port). Normally the default tomcat-apache.conf file that should be included in the main http.conf will work (apart from checking the that the location to the mod_jserv library is correct). Personally, I installed apache 3.1.12, tomcat, tomcat source and apache development packages onto my RedHat 6.2 box. After compiling the mod_jserv.so with apxs (instructions in the user guide), copying the tomcat-apache.conf into /etc/httpd/conf directory, including it in the http.conf file, altering tomcat-apache.conf so that it had the correct path to mod_jserv.so and finally starting up the servers it just ran fine. I modified nothing else.
--
dr. Maurizio Calcara
m.calcara@cgsgroup.it
Re: HANDLER THREAD PROBLEM
Posted by Maurizio Calcara <m....@cgsgroup.it>.
Hi Ed,
thank's for your help.
Yes, I use "ajp12" inside the "tomcat-apache.conf" file, that I have
copied into the /etc/http/conf dir. I have modified inside this
configuration file only the path to the mod_jserv.so (in the file
generated by tomcat there was "libexec/mod_jserv.so", I have the modules
inside the "modules" dir. "/etc/httpd/modules", as a standard RedHat
6.1 installation), by writing "modules/mod_jserv.so" instead
"libexec/mod_jserv.so".
No errors appear during the startup phase. When I type into the Netscape
location box "http://localhost:8007" the error "HANDLER THREAD PROBLEM:
..." appears on the console.
Where is the mistake?
Have you copied the mod_jserv.so into the /etc/httpd/modules (that is a
link /usr/lib/apache/) dir ?
Maurizio
Ed wrote:
> Ok, I've read your original problem again and I need a bit more
> clarification.Where exactly are you typing in this URL to the ajpv12?
> If you are in fact typing the ajpv12://localhost directly into the
> netscape URL thingy then it will completely fail as it is not a
> standard internet protocol like http, ftp or gopher. This ajpv12
> thing should only appear inside your configuration script(s). The
> tomcat-apache.conf file *can* contain this protocol specifier if you
> are attempting to connect to a tomcat server other than the one that
> is on the local host (or using a different port). Normally the
> default tomcat-apache.conf file that should be included in the main
> http.conf will work (apart from checking the that the location to the
> mod_jserv library is correct). Personally, I installed apache 3.1.12,
> tomcat, tomcat source and apache development packages onto my RedHat
> 6.2 box. After compiling the mod_jserv.so with apxs (instructions in
> the user guide), copying the tomcat-apache.conf into /etc/httpd/conf
> directory, including it in the http.conf file, altering
> tomcat-apache.conf so that it had the correct path to mod_jserv.so and
> finally starting up the servers it just ran fine. I modified nothing
> else.
--
dr. Maurizio Calcara
m.calcara@cgsgroup.it
Re: HANDLER THREAD PROBLEM
Posted by Ed <ed...@jsq.co.uk>.
Ok, I've read your original problem again and I need a bit more clarification.
Where exactly are you typing in this URL to the ajpv12? If you are in fact typing the ajpv12://localhost directly into the netscape URL thingy then it will completely fail as it is not a standard internet protocol like http, ftp or gopher. This ajpv12 thing should only appear inside your configuration script(s). The tomcat-apache.conf file *can* contain this protocol specifier if you are attempting to connect to a tomcat server other than the one that is on the local host (or using a different port). Normally the default tomcat-apache.conf file that should be included in the main http.conf will work (apart from checking the that the location to the mod_jserv library is correct).
Personally, I installed apache 3.1.12, tomcat, tomcat source and apache development packages onto my RedHat 6.2 box. After compiling the mod_jserv.so with apxs (instructions in the user guide), copying the tomcat-apache.conf into /etc/httpd/conf directory, including it in the http.conf file, altering tomcat-apache.conf so that it had the correct path to mod_jserv.so and finally starting up the servers it just ran fine. I modified nothing else.
----- Original Message -----
From: Maurizio Calcara
To: tomcat-user@jakarta.apache.org
Sent: Monday, July 03, 2000 11:23 AM
Subject: Re: HANDLER THREAD PROBLEM
Unfortunately I try to talk *only* with the server (by using ajpv12://localhost) but Netscape seems to try to use the http protocol to locate the server and it says again: "Netscape is unable to locate the server ajpv12:.".
Is there any setting has to be made into the "http.conf" file (apart the "include tomcat-apache.conf") .
Thanks.
Ed wrote:
You should not be trying to directly communicate to the 8007 port at all. Stop it. You talk to the web-server then *it* talks to the 8007 port. It is supposed to be transaparent.
----- Original Message -----
From:Maurizio Calcara
To: tomcat-user@jakarta.apache.org
Sent: Monday, July 03, 2000 10:32 AM
Subject: Re: HANDLER THREAD PROBLEM
Hi Rob,
thank's for your help.
Unfortunately I'm trying to use ajpv12as communication protocol (ajpv12://localhost:8007), but Netscape says "Netscape is unable to locate the server ajpv12:.".
Are there other configurations that have to be made on the server ??
Thank you again,
Maurizio
"Rob S." wrote:
'allo,We did the same thing when we were installing Tomcat =) The protocol used to communicate with Tomcat on port 8007 is ajpv12. You're trying to use HTTP. By default, that port is meant for webserver-Tomcat communication.Hope it helps!- r
-----Original Message-----
From: maurizio@cgsgroup.it [mailto:maurizio@cgsgroup.it]On Behalf Of Maurizio Calcara
Sent: June 30, 2000 9:14 AM
To: tomcat-user@jakarta.apache.org
Subject: HANDLER THREAD PROBLEM
Hi,
I'm installing "Tomcat 3.1" on a Linux RedHat 6.1 system running a 2.2.15 kernel and the "jdk1.2.2" Java version.
By using Tomcat in stand-alone mode it works fine.
When I try to use Tomcat with Apache (both 1.3.9 and 1.3.12) by means the "mod_jserv.so" (I try to connect to "http://localhost:8007", the default settings) the console produces the following error:
HANDLER THREAD PROBLEM: java.io.IOException: Stream brokenjava.io.IOException: Stream broken
at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Ajp12ConnectionHandler.java:386)
at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection(Ajp12ConnectionHandler.java:134)
at org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.java:338)
at java.lang.Thread.run(Thread.java:475)
Please, Is there anybody that solved this problem???
Any idea??
Thanks,
Maurizio Calcara
--
dr. Maurizio Calcara
m.calcara@cgsgroup.it
--
dr. Maurizio Calcara
m.calcara@cgsgroup.it
--
dr. Maurizio Calcara
IT Manager - CGS sas
via S.Cecilia, 16
56124 - Pisa (Italy)
Fax: +39 050 573854
Tel: +39 050 573205
m.calcara@cgsgroup.it
Re: HANDLER THREAD PROBLEM
Posted by Maurizio Calcara <m....@cgsgroup.it>.
Unfortunately I try to talk *only* with the server (by using
ajpv12://localhost) but Netscape seems to try to use the http protocol
to locate the server and it says again: "Netscape is unable to locate
the server ajpv12:.".
Is there any setting has to be made into the "http.conf" file (apart the
"include tomcat-apache.conf") .
Thanks.
Ed wrote:
> You should not be trying to directly communicate to the 8007 port at
> all. Stop it. You talk to the web-server then *it* talks to the 8007
> port. It is supposed to be transaparent.
>
> ----- Original Message -----
> From:Maurizio Calcara
> To: tomcat-user@jakarta.apache.org
> Sent: Monday, July 03, 2000 10:32 AM
> Subject: Re: HANDLER THREAD PROBLEM
> Hi Rob,
> thank's for your help.
> Unfortunately I'm trying to use ajpv12as communication
> protocol (ajpv12://localhost:8007), but Netscape says
> "Netscape is unable to locate the server ajpv12:.".
> Are there other configurations that have to be made on the
> server ??
>
> Thank you again,
> Maurizio
>
> "Rob S." wrote:
>
> > 'allo,We did the same thing when we were installing Tomcat
> > =) The protocol used to communicate with Tomcat on port
> > 8007 is ajpv12. You're trying to use HTTP. By default,
> > that port is meant for webserver-Tomcat communication.Hope
> > it helps!- r
> >
> > -----Original Message-----
> > From: maurizio@cgsgroup.it
> > [mailto:maurizio@cgsgroup.it]On Behalf Of
> > Maurizio Calcara
> > Sent: June 30, 2000 9:14 AM
> > To: tomcat-user@jakarta.apache.org
> > Subject: HANDLER THREAD PROBLEM
> > Hi,
> > I'm installing "Tomcat 3.1" on a Linux RedHat
> > 6.1 system running a 2.2.15 kernel and the
> > "jdk1.2.2" Java version.
> > By using Tomcat in stand-alone mode it works
> > fine.
> >
> > When I try to use Tomcat with Apache (both 1.3.9
> > and 1.3.12) by means the "mod_jserv.so" (I try
> > to connect to "http://localhost:8007", the
> > default settings) the console produces the
> > following error:
> >
> > HANDLER THREAD PROBLEM:
> > java.io.IOException: Stream
> > brokenjava.io.IOException: Stream
> > broken
> > at
> > org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Ajp12ConnectionHandler.java:386)
> >
> > at
> > org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection(Ajp12ConnectionHandler.java:134)
> >
> > at
> > org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.java:338)
> >
> > at
> > java.lang.Thread.run(Thread.java:475)
> >
> >
> > Please, Is there anybody that solved this
> > problem???
> > Any idea??
> > Thanks,
> > Maurizio Calcara
> >
> > --
> >
> > dr. Maurizio Calcara
> > m.calcara@cgsgroup.it
> >
> >
> >
> --
>
> dr. Maurizio Calcara
> m.calcara@cgsgroup.it
>
>
>
--
dr. Maurizio Calcara
IT Manager - CGS sas
via S.Cecilia, 16
56124 - Pisa (Italy)
Fax: +39 050 573854
Tel: +39 050 573205
m.calcara@cgsgroup.it
Re: HANDLER THREAD PROBLEM
Posted by Ed <ed...@jsq.co.uk>.
You should not be trying to directly communicate to the 8007 port at all. Stop it. You talk to the web-server then *it* talks to the 8007 port. It is supposed to be transaparent.
----- Original Message -----
From: Maurizio Calcara
To: tomcat-user@jakarta.apache.org
Sent: Monday, July 03, 2000 10:32 AM
Subject: Re: HANDLER THREAD PROBLEM
Hi Rob,
thank's for your help.
Unfortunately I'm trying to use ajpv12 as communication protocol (ajpv12://localhost:8007), but Netscape says "Netscape is unable to locate the server ajpv12:.".
Are there other configurations that have to be made on the server ??
Thank you again,
Maurizio
"Rob S." wrote:
'allo,We did the same thing when we were installing Tomcat =) The protocol used to communicate with Tomcat on port 8007 is ajpv12. You're trying to use HTTP. By default, that port is meant for webserver-Tomcat communication.Hope it helps!- r
-----Original Message-----
From: maurizio@cgsgroup.it [mailto:maurizio@cgsgroup.it]On Behalf Of Maurizio Calcara
Sent: June 30, 2000 9:14 AM
To: tomcat-user@jakarta.apache.org
Subject: HANDLER THREAD PROBLEM
Hi,
I'm installing "Tomcat 3.1" on a Linux RedHat 6.1 system running a 2.2.15 kernel and the "jdk1.2.2" Java version.
By using Tomcat in stand-alone mode it works fine.
When I try to use Tomcat with Apache (both 1.3.9 and 1.3.12) by means the "mod_jserv.so" (I try to connect to "http://localhost:8007", the default settings) the console produces the following error:
HANDLER THREAD PROBLEM: java.io.IOException: Stream brokenjava.io.IOException: Stream broken
at org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Ajp12ConnectionHandler.java:386)
at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection(Ajp12ConnectionHandler.java:134)
at org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.java:338)
at java.lang.Thread.run(Thread.java:475)
Please, Is there anybody that solved this problem???
Any idea??
Thanks,
Maurizio Calcara
--
dr. Maurizio Calcara
m.calcara@cgsgroup.it
--
dr. Maurizio Calcara
m.calcara@cgsgroup.it