You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Simon Chatfield <si...@thechatfieldgroup.com> on 2002/12/18 19:55:26 UTC
mod_jk connection issues, more information.
The number of open connections....
# netstat -a |grep 8009 |wc -l
175
#
actually, I think that shows both sides of the connection between apache
and tomcat + the listener, so that's 87 connections...
Now streaming in the apache errors_log
er
[Wed Dec 18 11:50:48 2002] [warn] (128)Network is unreachable: connect
to listener
[Wed Dec 18 11:50:49 2002] [warn] (128)Network is unreachable: connect
to listener
[Wed Dec 18 11:50:50 2002] [warn] (128)Network is unreachable: connect
to listener
[Wed Dec 18 11:50:51 2002] [warn] (128)Network is unreachable: connect
to listener
Any ideas?
--
Simon Chatfield
The Chatfield Group
email: simon@thechatfieldgroup.com
phone: 602-971-9598
web: http://www.thechatfieldgroup.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Forwarding to an
Posted by Dodd Gatsos <dg...@slb.com>.
Trying to forward a request to a certain location in a JSP page. Ie an <a
name=> section. It doesn't seem to work.
I've tried both:
getServletContext().getRequestDispatcher("/admin/AgentReport.jsp#section2").
forward(req,res);
and:
response.sendRedirect("/admin/AgentReport.jsp#section2");
But neither seem to work. I've also tried replacing the # with the Encoded
URL character without success.
I don't know if this is an HTML/Browser issue or an issue with the Servlet
spec.
Any Comments, Ideas, Suggestions, Work Arounds?
Thanks,
Dodd
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: "Naive question" thread
Posted by jon wingfield <jo...@mkodo.com>.
i use pstree -aup.
Very useful with multiple java apps running on one server :)
-----Original Message-----
From: Milt Epstein [mailto:mepstein@uiuc.edu]
Sent: 18 December 2002 20:15
To: Tomcat Users List
Subject: "Naive question" thread
Saw a post in the "naive question" thread earlier today that I wanted
to respond to, but my quick "delete" finger got to it before I got
around to it. This was a thread in which John Turner, Denise Mangano,
and some others had been participating.
Anyway, Denise posted the output of ps that had a whole bunch of java
processes listed. I'd be concerned about the number of such
processes, because normally there shouldn't be so many -- in fact,
most typically (i.e. one tomcat instance), there should be just one.
Now, Denise said she's using linux, and it's my understanding that ps
under linux will list threads, not just processes. So it's possible
all those java listings were all the threads running in one java
process. And I think there's an option to ps to cause it list actual
processes, not threads. So you might try that and see what the output
looks like.
Milt Epstein
Research Programmer
Integration and Software Engineering (ISE)
Campus Information Technologies and Educational Services (CITES)
University of Illinois at Urbana-Champaign (UIUC)
mepstein@uiuc.edu
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: "Naive question" thread
Posted by jon wingfield <jo...@mkodo.com>.
i use pstree -aup.
Very useful with multiple java apps running on one server :)
-----Original Message-----
From: Milt Epstein [mailto:mepstein@uiuc.edu]
Sent: 18 December 2002 20:15
To: Tomcat Users List
Subject: "Naive question" thread
Saw a post in the "naive question" thread earlier today that I wanted
to respond to, but my quick "delete" finger got to it before I got
around to it. This was a thread in which John Turner, Denise Mangano,
and some others had been participating.
Anyway, Denise posted the output of ps that had a whole bunch of java
processes listed. I'd be concerned about the number of such
processes, because normally there shouldn't be so many -- in fact,
most typically (i.e. one tomcat instance), there should be just one.
Now, Denise said she's using linux, and it's my understanding that ps
under linux will list threads, not just processes. So it's possible
all those java listings were all the threads running in one java
process. And I think there's an option to ps to cause it list actual
processes, not threads. So you might try that and see what the output
looks like.
Milt Epstein
Research Programmer
Integration and Software Engineering (ISE)
Campus Information Technologies and Educational Services (CITES)
University of Illinois at Urbana-Champaign (UIUC)
mepstein@uiuc.edu
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
"Naive question" thread
Posted by Milt Epstein <me...@uiuc.edu>.
Saw a post in the "naive question" thread earlier today that I wanted
to respond to, but my quick "delete" finger got to it before I got
around to it. This was a thread in which John Turner, Denise Mangano,
and some others had been participating.
Anyway, Denise posted the output of ps that had a whole bunch of java
processes listed. I'd be concerned about the number of such
processes, because normally there shouldn't be so many -- in fact,
most typically (i.e. one tomcat instance), there should be just one.
Now, Denise said she's using linux, and it's my understanding that ps
under linux will list threads, not just processes. So it's possible
all those java listings were all the threads running in one java
process. And I think there's an option to ps to cause it list actual
processes, not threads. So you might try that and see what the output
looks like.
Milt Epstein
Research Programmer
Integration and Software Engineering (ISE)
Campus Information Technologies and Educational Services (CITES)
University of Illinois at Urbana-Champaign (UIUC)
mepstein@uiuc.edu
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: mod_jk connection issues, more information.
Posted by Simon Chatfield <si...@thechatfieldgroup.com>.
The connectionTimeout was the solution, increasing the value of the
other attributes simply delayed the problem.
I had been using the Ajp13Connector earlier, then noticed this new
attribute on they CoyoteConnector so tried that as a work around. So far
so good in my testing.
-Simon
Milt Epstein wrote:
> On Wed, 18 Dec 2002, Simon Chatfield wrote:
>
>
>>I made the following change
>>
>><Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
>> port="8009" minProcessors="5" maxProcessors="100"
>> enableLookups="true" redirectPort="8443"
>> acceptCount="100" debug="0" connectionTimeout="20000"
>> useURIValidationHack="false"
>>
>>protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>
>
>
> Could you indicate what you changed? maxProcessors? acceptCount?
> connectionTimeout? (Perhaps you posted what it was earlier in the
> thread, but if so I missed it.) Thanks.
>
> FWIW, my comment below was about Ajp13Connector, I didn't realize you
> were using CoyoteConnector. And looks like Ajp13Connector has the
> maxProcessors and acceptCount attributes, but not connectionTimeout.
>
>
>>And it appears to have fixed the lock-up problem at least. The problem
>>wasn't in tomcat in my estimation, the apache/mod_jk side was holding
>>onto the connection and not allowing the next request to use it. The
>>timeout kills off the connections that are being held onto by apache and
>>so no lockups. I think this is only a temporary kludge/fix, but for the
>>other people who were having the same problem, try this for now. Thanks
>>for everyone's help.
>>
>>-Simon
>>
>>ps.
>>
>>I also upgraded from 4.1.12 to 4.1.17 in my debugging process though
>>that didn't solve the problem in and of itself.
>>
>>Milt Epstein wrote:
>>
>>>On Wed, 18 Dec 2002, Simon Chatfield wrote:
>>>
>>>
>>>
>>>>The number of open connections....
>>>>
>>>># netstat -a |grep 8009 |wc -l
>>>> 175
>>>>#
>>>>
>>>>actually, I think that shows both sides of the connection between apache
>>>>and tomcat + the listener, so that's 87 connections...
>>>
>>>[ ... ]
>>>
>>>I think how many of these can exist is controlled by the maxProcessors
>>>attribute setting in the Ajp13Connector Connector tag in server.xml.
>>>Also, you can see messsages about their starting up in
>>>cataling_log.YYYY-MM-DD.txt (where YYYY-MM-DD is the date). And it
>>>may be correct that they are not closed/stopped once they're started.
>>>
>>>Milt Epstein
>>>Research Programmer
>>>Integration and Software Engineering (ISE)
>>>Campus Information Technologies and Educational Services (CITES)
>>>University of Illinois at Urbana-Champaign (UIUC)
>>>mepstein@uiuc.edu
>>>
>>>
>>>--
>>>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>>>For additional commands, e-mail: <ma...@jakarta.apache.org>
>>
>>
>>--
>>Simon Chatfield
>>The Chatfield Group
>>email: simon@thechatfieldgroup.com
>>phone: 602-971-9598
>>web: http://www.thechatfieldgroup.com
>>
>>
>>--
>>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>>For additional commands, e-mail: <ma...@jakarta.apache.org>
>>
>
> Milt Epstein
> Research Programmer
> Integration and Software Engineering (ISE)
> Campus Information Technologies and Educational Services (CITES)
> University of Illinois at Urbana-Champaign (UIUC)
> mepstein@uiuc.edu
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
Simon Chatfield
The Chatfield Group
email: simon@thechatfieldgroup.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: mod_jk connection issues, more information.
Posted by Milt Epstein <me...@uiuc.edu>.
On Wed, 18 Dec 2002, Simon Chatfield wrote:
> I made the following change
>
> <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
> port="8009" minProcessors="5" maxProcessors="100"
> enableLookups="true" redirectPort="8443"
> acceptCount="100" debug="0" connectionTimeout="20000"
> useURIValidationHack="false"
>
> protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>
Could you indicate what you changed? maxProcessors? acceptCount?
connectionTimeout? (Perhaps you posted what it was earlier in the
thread, but if so I missed it.) Thanks.
FWIW, my comment below was about Ajp13Connector, I didn't realize you
were using CoyoteConnector. And looks like Ajp13Connector has the
maxProcessors and acceptCount attributes, but not connectionTimeout.
> And it appears to have fixed the lock-up problem at least. The problem
> wasn't in tomcat in my estimation, the apache/mod_jk side was holding
> onto the connection and not allowing the next request to use it. The
> timeout kills off the connections that are being held onto by apache and
> so no lockups. I think this is only a temporary kludge/fix, but for the
> other people who were having the same problem, try this for now. Thanks
> for everyone's help.
>
> -Simon
>
> ps.
>
> I also upgraded from 4.1.12 to 4.1.17 in my debugging process though
> that didn't solve the problem in and of itself.
>
> Milt Epstein wrote:
> > On Wed, 18 Dec 2002, Simon Chatfield wrote:
> >
> >
> >>The number of open connections....
> >>
> >># netstat -a |grep 8009 |wc -l
> >> 175
> >>#
> >>
> >>actually, I think that shows both sides of the connection between apache
> >>and tomcat + the listener, so that's 87 connections...
> >
> > [ ... ]
> >
> > I think how many of these can exist is controlled by the maxProcessors
> > attribute setting in the Ajp13Connector Connector tag in server.xml.
> > Also, you can see messsages about their starting up in
> > cataling_log.YYYY-MM-DD.txt (where YYYY-MM-DD is the date). And it
> > may be correct that they are not closed/stopped once they're started.
> >
> > Milt Epstein
> > Research Programmer
> > Integration and Software Engineering (ISE)
> > Campus Information Technologies and Educational Services (CITES)
> > University of Illinois at Urbana-Champaign (UIUC)
> > mepstein@uiuc.edu
> >
> >
> > --
> > To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> > For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
> --
> Simon Chatfield
> The Chatfield Group
> email: simon@thechatfieldgroup.com
> phone: 602-971-9598
> web: http://www.thechatfieldgroup.com
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
Milt Epstein
Research Programmer
Integration and Software Engineering (ISE)
Campus Information Technologies and Educational Services (CITES)
University of Illinois at Urbana-Champaign (UIUC)
mepstein@uiuc.edu
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: mod_jk connection issues, more information.
Posted by Simon Chatfield <si...@thechatfieldgroup.com>.
I made the following change
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8009" minProcessors="5" maxProcessors="100"
enableLookups="true" redirectPort="8443"
acceptCount="100" debug="0" connectionTimeout="20000"
useURIValidationHack="false"
protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>
And it appears to have fixed the lock-up problem at least. The problem
wasn't in tomcat in my estimation, the apache/mod_jk side was holding
onto the connection and not allowing the next request to use it. The
timeout kills off the connections that are being held onto by apache and
so no lockups. I think this is only a temporary kludge/fix, but for the
other people who were having the same problem, try this for now. Thanks
for everyone's help.
-Simon
ps.
I also upgraded from 4.1.12 to 4.1.17 in my debugging process though
that didn't solve the problem in and of itself.
Milt Epstein wrote:
> On Wed, 18 Dec 2002, Simon Chatfield wrote:
>
>
>>The number of open connections....
>>
>># netstat -a |grep 8009 |wc -l
>> 175
>>#
>>
>>actually, I think that shows both sides of the connection between apache
>>and tomcat + the listener, so that's 87 connections...
>
> [ ... ]
>
> I think how many of these can exist is controlled by the maxProcessors
> attribute setting in the Ajp13Connector Connector tag in server.xml.
> Also, you can see messsages about their starting up in
> cataling_log.YYYY-MM-DD.txt (where YYYY-MM-DD is the date). And it
> may be correct that they are not closed/stopped once they're started.
>
> Milt Epstein
> Research Programmer
> Integration and Software Engineering (ISE)
> Campus Information Technologies and Educational Services (CITES)
> University of Illinois at Urbana-Champaign (UIUC)
> mepstein@uiuc.edu
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
Simon Chatfield
The Chatfield Group
email: simon@thechatfieldgroup.com
phone: 602-971-9598
web: http://www.thechatfieldgroup.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: mod_jk connection issues, more information.
Posted by Milt Epstein <me...@uiuc.edu>.
On Wed, 18 Dec 2002, Simon Chatfield wrote:
> The number of open connections....
>
> # netstat -a |grep 8009 |wc -l
> 175
> #
>
> actually, I think that shows both sides of the connection between apache
> and tomcat + the listener, so that's 87 connections...
[ ... ]
I think how many of these can exist is controlled by the maxProcessors
attribute setting in the Ajp13Connector Connector tag in server.xml.
Also, you can see messsages about their starting up in
cataling_log.YYYY-MM-DD.txt (where YYYY-MM-DD is the date). And it
may be correct that they are not closed/stopped once they're started.
Milt Epstein
Research Programmer
Integration and Software Engineering (ISE)
Campus Information Technologies and Educational Services (CITES)
University of Illinois at Urbana-Champaign (UIUC)
mepstein@uiuc.edu
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>