Hi, If it's any consolation we see these informational messages too sometimes under almost non-existant load.
I have heard that in earlier versions of apache (1.x) it reset itself under certain conditions and it was a normal thing to see this message. I also heard a _rumor_ that the apache developers were going to change this message to DEBUG. But that was a long time ago. I'm not sure about what's going on with apache 2.x. I think there is something else going on here. -e On Wed, 9 Jul 2003, Fletcher Cocquyt wrote: > Hi Fellow Tomcat users, > I am seeing the following errors in my catalina.out logfile when running > any kind of load against the server using apache bench: > Jul 9, 2003 5:36:42 PM org.apache.jk.server.JkCoyoteHandler action > INFO: RESET > Jul 9, 2003 5:36:42 PM org.apache.jk.server.JkCoyoteHandler action > INFO: RESET > > These correspond to in a 1:1 ratio with the number of Server Error 500 > org.apache.jasper.JasperException: ORA-00933: SQL command not properly > ended error messages returned from the apache bench test. > Eg when I run: > /opt/http-2.0.45/bin/ab -c 5 -n 100 http:// > <http://%3cservername%3e/main.jsp> <servername>/main.jsp > > I get roughly 40-50% error rates: > > Benchmarking <servername> (be patient).....done > Server Software: Apache/2.0.45 > > Server Hostname: <servername> > Server Port: 80 > Document Path: /main.jsp > Document Length: 30399 bytes > Concurrency Level: 5 > Time taken for tests: 1.548 seconds > Complete requests: 100 > Failed requests: 42 > (Connect: 0, Length: 42, Exceptions: 0) > Broken pipe errors: 0 > Non-2xx responses: 42 > > > The configuration is: > Test client: Solaris 9 server running apache bench hitting: > > Test Web Server: Solaris 9 Sunfire 280R running Apache 2.0.45: > Worker.properties: > # All the workers that we know about > worker.list=app-01 > # Set properties for app-01 (ajp13) > worker.app-01.type=ajp13 > worker.app-01.host=<appserverIP> # first instance on app-01 > worker.app-01.port=8009 > worker.app-01.cachesize=10 > worker.app-01.cache_timeout=600 > worker.app-01.socket_keepalive=1 > worker.app-01.socket_timeout=300 > Solaris 9 Sunfire 280R running tomcat 4.1.24 > From server.xml: > <name>url</name> > <value>jdbc:oracle:thin:@<database > server>:1521:dev</value> > <parameter> > <name>maxActive</name> > <value>20</value> > </parameter> > <parameter> > <name>maxIdle</name> > <value>10</value> > </parameter> > <parameter> > <name>maxWait</name> > <value>10000</value> > </parameter> > <parameter> > <name>removeAbadoned</name> > <value>true</value> > </parameter> > <parameter> > <name>logAdandoned</name> > <value>true</value> > </parameter> > > Anyone know what causes these errors under relatively light load? > The same test against a Linux development web/apache tomcat server does > this error free with many more users (hitting the same oracle database > instance with the same URL connect string) > Throughput on sftp between these servers is error free 11000kB/s > What extra logging can I do to see what's causing the errors? > What tuning parameters might help this configuration? > > Thanks in advance, > > Fletcher Cocquyt > Senior Systems Administrator > [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
