You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Alexandre Chapellon <al...@mana.pf> on 2010/09/01 00:35:47 UTC

Re: pick load

Le mardi 31 août 2010 à 14:39 -0400, Christopher Schultz a écrit :

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Alexandre,
> 
> On 8/30/2010 10:49 PM, Alexandre Chapellon wrote:
> > [Considering] the fair analysis of Charles, we decided to move applications
> > to Poolable connection factory
> 
> Excellent.
> 
> > To do so I created a factory iun server.xml as follow:
> > 
> > <Resource name="jdbc/crm" auth="Container" type="javax.sql.DataSource"/>
> 
> I just realized that you're using Tomcat 4.1. Any possibility of moving
> up to Tomcat 6.0? I've recently moved several webapps from 4.1 up to 6.0
> with very little headache. You'll get the benefit of security and
> stability updates, as well as performance improvements in the new version.
> 

We're using an old version of highdeal billing system which apparently
(tat's what the support says) doens't support java6.
Migration is planned for next year.


> >         <ResourceParams name="jdbc/crm">
> >                 <parameter>
> >                         <name>url</name>
> >          <value>jdbc:oracle:thin:@1.2.3.4:1521:SID</value>
> 
> Double-check that this driver URL is correct. If you copied it from your
> old configuration, it's probably fine.
> 

Indeed the url what good for one of the pool (oracle9i) but not for the
other (Oracle10g)
I Changed it, and so get rid of error messages.
4

> >                 <parameter>
> >                         <name>factory</name>
> > 
> > <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
> >                 </parameter>
> 
> This parameter should not be necessary. Once you have things working,
> try removing this parameter. If things are still working fine, then
> leave this out of your configuration.
> 
> > When trying to connect to the application. Login succeed but I get the
> > following errors in catalina.out:
> > 
> > org.apache.commons.dbcp.SQLNestedException: Cannot create
> > PoolableConnectionFactory (invalid argument in call)
> 
> Can you post the code that fetches a connection from the pool?
> 
> > Did i miss something in xml definitions or is it a problem with the way
> > the app uses the connection Pool?
> 
> My guess is the location of the driver .jar file. The file oracle.jar
> (or whatever it is called) should /only/ be in the server's server/lib
> directory, and /not/ in the webapp's WEB-INF/lib directory. If you have
> the driver .jar in both places (or only in WEB-INF/lib), you'll get
> errors like this.
> 

I removed the factory param and redundant oracle jar files.

Thanks for your help


> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> 
> iEYEARECAAYFAkx9TEwACgkQ9CaO5/Lv0PCgHQCfcGRWdjQ8UHYpUizRn49GbD4p
> D/kAn0V5rZ2rjtOjyfBZcQH0UcmZsXdq
> =7a6L
> -----END PGP SIGNATURE-----
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 



Re: pick load

Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alexandre,

On 9/2/2010 1:49 PM, Alexandre Chapellon wrote:
> Yes to me too, but what's weired is that thoose errors enver appears
> under normal load... this really drives me crazy!

I would bet that there's an exception being caught and re-thrown without
the original exception being logged. Check the code around where that
exception is being thrown (Client.java:676) and see if it's in a catch
block. If so, try logging the original exception, or chaining the root
cause to the new exception like this:

throw new Exception("Erreur: impossible de recuperer la partie CHAP0712A
: " + whatever, originalException);

This will help you figure out what's really happening.

- -chris

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

iEYEARECAAYFAkyAGMcACgkQ9CaO5/Lv0PBMqgCgove+TKLYTcsd9JWQy3gTff4b
qgMAn0F7jknSIJ1+xrtseRkRZtpMmKKp
=9CDH
-----END PGP SIGNATURE-----

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


Re: pick load

Posted by Alexandre Chapellon <al...@mana.pf>.
Le jeudi 02 septembre 2010 à 11:22 -0400, Christopher Schultz a écrit :

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Alexandre,
> 
> On 9/2/2010 12:08 AM, Alexandre Chapellon wrote:
> > Forget about it this doesn't seems to be related to the jk connector.
> 
> Right: the jk connector can be tweaked separately. You appear to have
> other problems.
> 
> > I have the same problems when direct sending requests to tomcat (errors
> > which do not appear under nomal load):
> > 
> > 2010-09-01 18:06:53.459 - FAILURE - [tracing] - MANA - Exception dans
> > [Authentification::doAuthentification(String,String)] :
> > [Search::searchPartyByAddInfo(String,object)] Erreur : impossible de
> > recuperer les parties avec l'info additionnel accessCode = CHAP0712A : 
> > null
> > 2010-09-01 18:06:53.459 - FAILURE - [tracing] - MANA -
> > [Authentification::performTask(HttpServletRequest,HttpServletResponse)]
> > Exception rencontr?e pendant l'authentification de CHAP0712A.
> > 2010-09-01 18:06:53.467 - FAILURE - [tracing] - MANA - Exception dans
> > [Search::searchParty(String)] : null
> > 2010-09-01 18:06:53.471 - FAILURE - [tracing] - MANA - Exception dans
> > [Client.fetchInformation(String)] :[Search::searchParty(String)]
> > Erreur : impossible de recuperer la partie CHAP0712A : null
> > java.lang.Exception: [Search::searchParty(String)] Erreur : impossible
> > de recuperer la partie CHAP0712A : null
> > 	at com.mana.om.Client.fetchInformation(Client.java:676)
> > 	at com.mana.selfcare.Authenticate.performTask(Authenticate.java:207)
> > 	at com.mana.selfcare.Authenticate.doPost(Authenticate.java:84)
> 
> That looks like an application error to me.


Yes to me too, but what's weired is that thoose errors enver appears
under normal load... this really drives me crazy!


> 
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> 
> iEYEARECAAYFAkx/wTMACgkQ9CaO5/Lv0PDXFgCgrMYix3jPszsSdOotB2qyZ9+i
> DBIAnjm44KkSTGLwRtl6GswN/njUC5bD
> =ZDt3
> -----END PGP SIGNATURE-----
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 



Re: pick load

Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alexandre,

On 9/2/2010 12:08 AM, Alexandre Chapellon wrote:
> Forget about it this doesn't seems to be related to the jk connector.

Right: the jk connector can be tweaked separately. You appear to have
other problems.

> I have the same problems when direct sending requests to tomcat (errors
> which do not appear under nomal load):
> 
> 2010-09-01 18:06:53.459 - FAILURE - [tracing] - MANA - Exception dans
> [Authentification::doAuthentification(String,String)] :
> [Search::searchPartyByAddInfo(String,object)] Erreur : impossible de
> recuperer les parties avec l'info additionnel accessCode = CHAP0712A : 
> null
> 2010-09-01 18:06:53.459 - FAILURE - [tracing] - MANA -
> [Authentification::performTask(HttpServletRequest,HttpServletResponse)]
> Exception rencontr?e pendant l'authentification de CHAP0712A.
> 2010-09-01 18:06:53.467 - FAILURE - [tracing] - MANA - Exception dans
> [Search::searchParty(String)] : null
> 2010-09-01 18:06:53.471 - FAILURE - [tracing] - MANA - Exception dans
> [Client.fetchInformation(String)] :[Search::searchParty(String)]
> Erreur : impossible de recuperer la partie CHAP0712A : null
> java.lang.Exception: [Search::searchParty(String)] Erreur : impossible
> de recuperer la partie CHAP0712A : null
> 	at com.mana.om.Client.fetchInformation(Client.java:676)
> 	at com.mana.selfcare.Authenticate.performTask(Authenticate.java:207)
> 	at com.mana.selfcare.Authenticate.doPost(Authenticate.java:84)

That looks like an application error to me.

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

iEYEARECAAYFAkx/wTMACgkQ9CaO5/Lv0PDXFgCgrMYix3jPszsSdOotB2qyZ9+i
DBIAnjm44KkSTGLwRtl6GswN/njUC5bD
=ZDt3
-----END PGP SIGNATURE-----

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


RE: pick load

Posted by Alexandre Chapellon <al...@mana.pf>.
Forget about it this doesn't seems to be related to the jk connector.
I have the same problems when direct sending requests to tomcat (errors
which do not appear under nomal load):

2010-09-01 18:06:53.459 - FAILURE - [tracing] - MANA - Exception dans
[Authentification::doAuthentification(String,String)] :
[Search::searchPartyByAddInfo(String,object)] Erreur : impossible de
recuperer les parties avec l'info additionnel accessCode = CHAP0712A : 
null
2010-09-01 18:06:53.459 - FAILURE - [tracing] - MANA -
[Authentification::performTask(HttpServletRequest,HttpServletResponse)]
Exception rencontr?e pendant l'authentification de CHAP0712A.
2010-09-01 18:06:53.467 - FAILURE - [tracing] - MANA - Exception dans
[Search::searchParty(String)] : null
2010-09-01 18:06:53.471 - FAILURE - [tracing] - MANA - Exception dans
[Client.fetchInformation(String)] :[Search::searchParty(String)]
Erreur : impossible de recuperer la partie CHAP0712A : null
java.lang.Exception: [Search::searchParty(String)] Erreur : impossible
de recuperer la partie CHAP0712A : null
	at com.mana.om.Client.fetchInformation(Client.java:676)
	at com.mana.selfcare.Authenticate.performTask(Authenticate.java:207)
	at com.mana.selfcare.Authenticate.doPost(Authenticate.java:84)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:638)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:720)
	at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:199)
	at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:145)
	at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
	at org.apache.catalina.core.StandardPipeline
$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
	at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
	at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955)
	at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:139)
	at org.apache.catalina.core.StandardPipeline
$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
	at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:446)
	at org.apache.catalina.core.StandardPipeline
$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
	at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:545)
	at org.apache.catalina.core.StandardPipeline
$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
	at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
	at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955)
	at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2460)
	at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:133)
	at org.apache.catalina.core.StandardPipeline
$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
	at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:119)
	at org.apache.catalina.core.StandardPipeline
$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
	at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:116)
	at org.apache.catalina.core.StandardPipeline
$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
	at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
	at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955)
	at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:127)
	at org.apache.catalina.core.StandardPipeline
$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
	at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
	at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955)
	at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:157)
	at
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:200)
	at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
	at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:775)
	at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:704)
	at org.apache.jk.common.ChannelSocket
$SocketConnection.runIt(ChannelSocket.java:897)
	at org.apache.tomcat.util.threads.ThreadPool
$ControlRunnable.run(ThreadPool.java:689)
	at java.lang.Thread.run(Thread.java:534)

Le mercredi 01 septembre 2010 à 17:28 -1000, Alexandre Chapellon a
écrit :

> With load growing I have thoose errors that appear in mod_jk logs:
> 
> [Sun Aug 29 08:28:27.976 2010] [26242:4106161040] [info]
> jk_handler::mod_jk.c (2611): Aborting connection for worker=selfcare
> [Sun Aug 29 12:15:45.829 2010] [27162:4097772432] [info]
> ajp_service::jk_ajp_common.c (2540): (selfcare) sending request to
> tomcat failed (recoverable), because of server error (attempt=1)
> [Sun Aug 29 12:15:45.929 2010] [27162:4097772432] [info]
> ajp_send_request::jk_ajp_common.c (1490): (selfcare) did not receive
> END_RESPONSE, closing socket -1
> [Sun Aug 29 12:15:45.933 2010] [27162:4097772432] [info]
> ajp_service::jk_ajp_common.c (2540): (selfcare) sending request to
> tomcat failed (recoverable), because of server error (attempt=2)
> [Sun Aug 29 12:15:45.933 2010] [27162:4097772432] [error]
> ajp_service::jk_ajp_common.c (2559): (selfcare) connecting to tomcat
> failed.
> [Sun Aug 29 12:15:45.933 2010] [27162:4097772432] [info]
> jk_handler::mod_jk.c (2618): Service error=-3 for worker=selfcare
> [Sun Aug 29 15:04:46.507 2010] [27104:4039052176] [info]
> ajp_process_callback::jk_ajp_common.c (1882): Writing to client aborted
> or client network problems
> ...skipping...
> 
> I really don't know what to tune....
> 
> Le mardi 31 août 2010 à 17:49 -0500, Caldarale, Charles R a écrit :
> 
> > > From: Alexandre Chapellon [mailto:alexandre.chapellon@mana.pf] 
> > > Subject: Re: pick load
> > 
> > > We're using an old version of highdeal billing system which 
> > > apparently (tat's what the support says) doens't support java6.
> > 
> > Chris suggested *Tomcat* 6, not Java 6.  You can run Tomcat 6 on JRE 5.
> > 
> >  - Chuck
> > 
> > 
> > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
> > 
> 
> 



RE: pick load

Posted by Alexandre Chapellon <al...@mana.pf>.
With load growing I have thoose errors that appear in mod_jk logs:

[Sun Aug 29 08:28:27.976 2010] [26242:4106161040] [info]
jk_handler::mod_jk.c (2611): Aborting connection for worker=selfcare
[Sun Aug 29 12:15:45.829 2010] [27162:4097772432] [info]
ajp_service::jk_ajp_common.c (2540): (selfcare) sending request to
tomcat failed (recoverable), because of server error (attempt=1)
[Sun Aug 29 12:15:45.929 2010] [27162:4097772432] [info]
ajp_send_request::jk_ajp_common.c (1490): (selfcare) did not receive
END_RESPONSE, closing socket -1
[Sun Aug 29 12:15:45.933 2010] [27162:4097772432] [info]
ajp_service::jk_ajp_common.c (2540): (selfcare) sending request to
tomcat failed (recoverable), because of server error (attempt=2)
[Sun Aug 29 12:15:45.933 2010] [27162:4097772432] [error]
ajp_service::jk_ajp_common.c (2559): (selfcare) connecting to tomcat
failed.
[Sun Aug 29 12:15:45.933 2010] [27162:4097772432] [info]
jk_handler::mod_jk.c (2618): Service error=-3 for worker=selfcare
[Sun Aug 29 15:04:46.507 2010] [27104:4039052176] [info]
ajp_process_callback::jk_ajp_common.c (1882): Writing to client aborted
or client network problems
...skipping...

I really don't know what to tune....

Le mardi 31 août 2010 à 17:49 -0500, Caldarale, Charles R a écrit :

> > From: Alexandre Chapellon [mailto:alexandre.chapellon@mana.pf] 
> > Subject: Re: pick load
> 
> > We're using an old version of highdeal billing system which 
> > apparently (tat's what the support says) doens't support java6.
> 
> Chris suggested *Tomcat* 6, not Java 6.  You can run Tomcat 6 on JRE 5.
> 
>  - Chuck
> 
> 
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
> 



RE: pick load

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Alexandre Chapellon [mailto:alexandre.chapellon@mana.pf] 
> Subject: Re: pick load

> We're using an old version of highdeal billing system which 
> apparently (tat's what the support says) doens't support java6.

Chris suggested *Tomcat* 6, not Java 6.  You can run Tomcat 6 on JRE 5.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.