tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anthony Milbourne <anthony.milbou...@becta.org.uk>
Subject RE: mod_jk error under load (errno codes)
Date Tue, 01 Oct 2002 09:00:13 GMT
Hi

I just searched through google.  I didn't find any lists of error codes -
which is something that I would find quite useful as well.  All I found was
someone elses post to another forum.

Question for developers & people in the know:

I realise that I could read the source to find this out but I would rather
not have to (I use Tomcat at work and my boss would not appreciate me
spending the time to do this)...
Is there any way of obtaining a list of what these errno's mean?
It might be a handy appendix to future documentation - it would certainly
give competent sys-admins/users more of a clue where to look for the
problem.

Thanks,

	Anthony.

> -----Original Message-----
> From:	Marc [SMTP:mvila@telemako.com]
> Sent:	30 September 2002 14:23
> To:	Tomcat Users List
> Subject:	Re: mod_jk error under load
> 
> Hi, where can I find a description for each 'errno'?
> I receive errno = 110 when I try to access tomcat connecting to a *.jsp
> page
> through apache.
> 
> Thank you!!!
> 
> Marc
> 
> Anthony Milbourne wrote:
> 
> > Hi
> >
> > 146 is a socket connection error.
> > Try checking your workers.properties file (or the JBoss file that
> generates
> > it ?) and making sure that the only connectors mentioned in workers.list
> > also have connectors defined in server.xml.  Specifically - check there
> > isn't an ajp12 in workers.properties and not in server.xml.
> >
> > Hope that helps.
> >
> >                 Anthony.
> >
> > > -----Original Message-----
> > > From: David Ward [SMTP:david.ward@dotech.com]
> > > Sent: 27 September 2002 17:57
> > > To:   tomcat-user@jakarta.apache.org
> > > Subject:      mod_jk error under load
> > >
> > > In running an automated load test against our app, we get the
> following
> > > errors in or jk.log file:
> > >
> > > [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> > > [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> > > [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> > > [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> > > [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> > > [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> > > [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> > > [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> > > [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> > > [jk_ajp12_worker.c (152)]: In jk_endpoint_t::service, Error sd = -1
> > > [jk_connect.c (143)]: jk_open_socket, connect() failed errno = 146
> > >
> > > Anyone know what these errors are? I can't find anything conclusive
> > > about them searching various lists/forums.
> > >
> > > We are running Apache 1.3.12 on a Solaris 7 Ultra 10 using
> mod_jk/ajp12
> > > to talk to JBoss-2.4.7_Tomcat-3.2.3 on a Solaris 7 E250, JDK 1.3.1_02.
> > >
> > > The symptoms we see are that the number of httpd processes maxes out
> on
> > > the web server box, though the CPU is almost completely idle. The
> weird
> > > thing is that the app server is mostly idle too, and doing a thread
> dump
> > > on the java (jboss+tomcat in same vm) process shows that there are
> lots
> > > of threads waiting for work to do. Once we stop the load test, things
> > > are still messed up until I restart apache, then we can access the app
> > > again. Note that I didn't have to touch the app server at all.
> Accessing
> > > URLs that aren't configured to go through mod_jk have no problem,
> until
> > > the max http children process gets reached, of course...
> > >
> > > I haven't gotten a response from the Tomcat forum at JGuru.
> > >
> > > Thanks all,
> > > David
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> > > <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
> > > For additional commands, e-mail:
> > > <mailto:tomcat-user-help@jakarta.apache.org>
> >
> > **********************************************************************
> > This email and any files transmitted with it are confidential and
> > intended solely for the use of the individual or entity to whom they
> > are addressed. If you have received this email in error please notify
> > the system manager.
> > This footnote also confirms that this email message has been swept by
> > MIMEsweeper for the presence of computer viruses.
> > www.mimesweeper.com
> > **********************************************************************
> >
> > --
> > To unsubscribe, e-mail:
> <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail:
> <mailto:tomcat-user-help@jakarta.apache.org>
> 
> 
> --
> To unsubscribe, e-mail:
> <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
> <mailto:tomcat-user-help@jakarta.apache.org>


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************


--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@jakarta.apache.org>


Mime
View raw message