RE: Load test with ab

2002-04-08 Thread Stefan Seifert

We are using MS SQL 2000 and Cocoon 2 very sucessful in two big
projects.
We bought a JDBC Driver (SPRINTA and OPTA) from inet-software
(http://www.inetsoftware.de).
They are not cheap, but worth the money.

Stefan

 -Original Message-
 From: Horst Rutter [mailto:[EMAIL PROTECTED]]
 Sent: Saturday, April 06, 2002 12:15 AM
 To: [EMAIL PROTECTED]; Nicola Ken Barozzi
 Subject: Re: Load test with ab
 
 
 Frustrating, I also have to communicate with a MS SQL 2000 db server.
 Not having started on the JDBC work I would be interested to know:
 a) what kind of experiences people have made using JDBC in a 
 Cocoon 2.x
 environment talking to MS SQL 2000
 b) any pointers to alternative (other than MS) JDBC drivers, 
 if that's the
 bottleneck.
 
 Thanks,
 Horst
 
 - Original Message -
 From: Nicola Ken Barozzi [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Thursday, April 04, 2002 11:57 PM
 Subject: Re: Load test with ab
  
  Out of all the drivers we used, Microsoft's new JDBC driver 
 had the most
  problems. It's still a beta driver in the form distributed 
 on Microsoft's
  Web site, but it's not a new product per se, because it's 
 based on code
  licensed from DataDirect Technologies Inc., which has had 
 the leading
  third-party SQL Server JDBC driver for some years now.
  Providing and supporting its own JDBC driver is a very 
 welcome move, and
  Microsoft officials informed us last month that they had 
 70,000 downloads
 of
  the driver so far, so there is considerable customer interest in it.
  However, the driver, in both Beta 1 and Beta 2 forms (we 
 tested both), has
  serious performance and stability problems.
  Using the driver, we were unable to get more than about
 200-page-per-second
  throughput, and the problem was clearly the driver-the 
 database was only
 at
  about 15 percent to 20 percent CPU utilization at this 
 load. The driver
 also
  has memory leaks: We could see on WebLogic's administration 
 console that
  less memory was freed each time the Java virtual machine 
 did a garbage
  collection. Because of these leaks, the Microsoft JDBC 
 driver was unable
 to
  run for 8 hours straight.
  
 
  You should change driver (see 3rd party) od DB ;-)
 
  --
  Nicola Ken Barozzi   [EMAIL PROTECTED]
  - verba volant, scripta manent -
 (discussions get forgotten, just code remains)
  
 -
 
 
  
 -
  Please check that your question has not already been answered in the
  FAQ before posting. http://xml.apache.org/cocoon/faqs.html
 
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 
 -
 Please check that your question has not already been answered in the
 FAQ before posting. http://xml.apache.org/cocoon/faqs.html
 
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 

-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: Load test with ab

2002-04-07 Thread Liam Morley

Yep, I'm pretty sure sitemap_xmap.java ends up in the work directory,
and it'll show up there each time you restart Tomcat. It's a dynamically
generated java representation of the sitemap in WEB-INF, so it's not for
editing (for those new to C2).

Liam Morley

On Fri, 5 Apr 2002, Michael Wechner wrote:

 Where do I find sitemap_xmap.java? Within the work directory of Tomcat?
 If so, then I can't tell, because I deleted it unfortunately.
 But I can do another load test!

 Thanks for your help

 Michael



 Vadim Gritsenko wrote:

  What is in these lines?
 
  org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2099)
  org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2071)
 
  Vadim
 
 
 -Original Message-
 From: Michael Wechner [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, April 04, 2002 9:37 AM
 To: [EMAIL PROTECTED]
 Subject: Load test with ab
 
 Hi
 
 We did a load test of Cocoon 2.0.1 with ab from Apache.
 
 Everything is fine when we do Concurrency 1 or 3
 (ab -n 10 -c 3)
 and performance looks good (pretty much the same as Zope).
 
 But when we set Concurrency 10 we run into trouble.
 Cocoon seems to stop running after a certain time and is throwing
 various Exceptions. And it doesn't recover (to recover we have to
 restart Tomcat).
 
 But Tomcat is still running perfectly althought Cocoon doesn't work
 anymore.
 
 So I guess it must have something to do with Caching in the memory!
 
 Any help is very much appreciated.
 
 Thanks
 
 Michael
 
 
 
 
 
 
 == error.log.03 ==
 ERROR   (2002-04-04) 16:33.01:693   [access] (/wyona-cms/)
 HttpProcessor[8080][2]/CocoonServlet: Problem with servlet
 java.lang.NullPointerException
  at
 org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2099)
  at
 org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2071)
  at
 
  org.apache.cocoon.sitemap.Handler.process(Handler.java:173)
 
  at org.apache.cocoon.sitemap.Manager.invoke(Manager.java:115)
  at
 
 
  org.apache.cocoon.sitemap.SitemapManager.process(SitemapManager.java:144
  )
 
  at org.apache.cocoon.Cocoon.process(Cocoon.java:605)
  at
 
 
  org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:795)
 
  at
 
  javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 
  at
 
 
  org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Unknown
 
 Source)
  at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(Unknown
 
  Source)
 
  at
 
  org.apache.catalina.core.StandardWrapperValve.invoke(Unknown
 
 Source)
  at
 
  org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
 Source)
  at org.apache.catalina.core.StandardPipeline.invoke(Unknown
 
  Source)
 
  at org.apache.catalina.core.ContainerBase.invoke(Unknown
 
  Source)
 
  at
 
  org.apache.catalina.core.StandardContextValve.invoke(Unknown
 
 Source)
  at
 
  org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
 Source)
  at org.apache.catalina.core.StandardPipeline.invoke(Unknown
 
  Source)
 
  at org.apache.catalina.core.ContainerBase.invoke(Unknown
 
  Source)
 
  at org.apache.catalina.core.StandardContext.invoke(Unknown
 
  Source)
 
  at org.apache.catalina.core.StandardHostValve.invoke(Unknown
 Source)
  at
 
  org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
 Source)
  at
 org.apache.catalina.valves.ErrorDispatcherValve.invoke(Unknown Source)
  at
 
  org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
 Source)
  at org.apache.catalina.valves.ErrorReportValve.invoke(Unknown
 Source)
  at
 
  org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
 Source)
  at org.apache.catalina.valves.AccessLogValve.invoke(Unknown
 
  Source)
 
  at
 
  org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
 Source)
  at org.apache.catalina.core.StandardPipeline.invoke(Unknown
 
  Source)
 
  at org.apache.catalina.core.ContainerBase.invoke(Unknown
 
  Source)
 
  at
 
  org.apache.catalina.core.StandardEngineValve.invoke(Unknown
 
 Source)
  at
 
  org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
 Source)
  at org.apache.catalina.core.StandardPipeline.invoke(Unknown
 
  Source)
 
  at org.apache.catalina.core.ContainerBase.invoke(Unknown
 
  Source)
 
  at
 org.apache.catalina.connector.http.HttpProcessor.process(Unknown
 
  Source)
 
  at
 
  org.apache.catalina.connector.http.HttpProcessor.run(Unknown
 
 Source)
  at java.lang.Thread.run(Thread.java:484)
 
 
 
 
 
 -
 Please check that your question has not already been answered in the
 FAQ before posting. http://xml.apache.org/cocoon/faqs.html
 
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional 

Re: Load test with ab

2002-04-05 Thread Michael Wechner

Where do I find sitemap_xmap.java? Within the work directory of Tomcat?
If so, then I can't tell, because I deleted it unfortunately.
But I can do another load test!

Thanks for your help

Michael



Vadim Gritsenko wrote:

 What is in these lines?
 
 org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2099)
 org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2071)
 
 Vadim
 
 
-Original Message-
From: Michael Wechner [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 04, 2002 9:37 AM
To: [EMAIL PROTECTED]
Subject: Load test with ab

Hi

We did a load test of Cocoon 2.0.1 with ab from Apache.

Everything is fine when we do Concurrency 1 or 3
(ab -n 10 -c 3)
and performance looks good (pretty much the same as Zope).

But when we set Concurrency 10 we run into trouble.
Cocoon seems to stop running after a certain time and is throwing
various Exceptions. And it doesn't recover (to recover we have to
restart Tomcat).

But Tomcat is still running perfectly althought Cocoon doesn't work
anymore.

So I guess it must have something to do with Caching in the memory!

Any help is very much appreciated.

Thanks

Michael






== error.log.03 ==
ERROR   (2002-04-04) 16:33.01:693   [access] (/wyona-cms/)
HttpProcessor[8080][2]/CocoonServlet: Problem with servlet
java.lang.NullPointerException
 at
org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2099)
 at
org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2071)
 at

 org.apache.cocoon.sitemap.Handler.process(Handler.java:173)
 
 at org.apache.cocoon.sitemap.Manager.invoke(Manager.java:115)
 at


 org.apache.cocoon.sitemap.SitemapManager.process(SitemapManager.java:144
 )
 
 at org.apache.cocoon.Cocoon.process(Cocoon.java:605)
 at


 org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:795)
 
 at

 javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 
 at


 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Unknown
 
Source)
 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(Unknown

 Source)
 
 at

 org.apache.catalina.core.StandardWrapperValve.invoke(Unknown
 
Source)
 at

 org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
Source)
 at org.apache.catalina.core.StandardPipeline.invoke(Unknown

 Source)
 
 at org.apache.catalina.core.ContainerBase.invoke(Unknown

 Source)
 
 at

 org.apache.catalina.core.StandardContextValve.invoke(Unknown
 
Source)
 at

 org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
Source)
 at org.apache.catalina.core.StandardPipeline.invoke(Unknown

 Source)
 
 at org.apache.catalina.core.ContainerBase.invoke(Unknown

 Source)
 
 at org.apache.catalina.core.StandardContext.invoke(Unknown

 Source)
 
 at org.apache.catalina.core.StandardHostValve.invoke(Unknown
Source)
 at

 org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
Source)
 at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(Unknown Source)
 at

 org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
Source)
 at org.apache.catalina.valves.ErrorReportValve.invoke(Unknown
Source)
 at

 org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
Source)
 at org.apache.catalina.valves.AccessLogValve.invoke(Unknown

 Source)
 
 at

 org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
Source)
 at org.apache.catalina.core.StandardPipeline.invoke(Unknown

 Source)
 
 at org.apache.catalina.core.ContainerBase.invoke(Unknown

 Source)
 
 at

 org.apache.catalina.core.StandardEngineValve.invoke(Unknown
 
Source)
 at

 org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
Source)
 at org.apache.catalina.core.StandardPipeline.invoke(Unknown

 Source)
 
 at org.apache.catalina.core.ContainerBase.invoke(Unknown

 Source)
 
 at
org.apache.catalina.connector.http.HttpProcessor.process(Unknown

 Source)
 
 at

 org.apache.catalina.connector.http.HttpProcessor.run(Unknown
 
Source)
 at java.lang.Thread.run(Thread.java:484)





-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

 
 
 -
 Please check that your question has not already been answered in the
 FAQ before posting. http://xml.apache.org/cocoon/faqs.html
 
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 



-
Please check that your question has not already been answered 

RE: Load test with ab

2002-04-05 Thread Carsten Ziegeler

We had the same problem, and it had to do with the MRUStore which is
not thread safe in 2.0.1 and 2.0.2.

I suggest you try the latest cvs version which is (paranoid) synchronized.
This solved our problem with a hanging (dead) Cocoon.

Carsten

 -Original Message-
 From: Michael Wechner [mailto:[EMAIL PROTECTED]]
 Sent: Friday, April 05, 2002 2:08 PM
 To: [EMAIL PROTECTED]
 Subject: Re: Load test with ab


 Where do I find sitemap_xmap.java? Within the work directory of Tomcat?
 If so, then I can't tell, because I deleted it unfortunately.
 But I can do another load test!

 Thanks for your help

 Michael



 Vadim Gritsenko wrote:

  What is in these lines?
 
  org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2099)
  org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2071)
 
  Vadim
 
 
 -Original Message-
 From: Michael Wechner [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, April 04, 2002 9:37 AM
 To: [EMAIL PROTECTED]
 Subject: Load test with ab
 
 Hi
 
 We did a load test of Cocoon 2.0.1 with ab from Apache.
 
 Everything is fine when we do Concurrency 1 or 3
 (ab -n 10 -c 3)
 and performance looks good (pretty much the same as Zope).
 
 But when we set Concurrency 10 we run into trouble.
 Cocoon seems to stop running after a certain time and is throwing
 various Exceptions. And it doesn't recover (to recover we have to
 restart Tomcat).
 
 But Tomcat is still running perfectly althought Cocoon doesn't work
 anymore.
 
 So I guess it must have something to do with Caching in the memory!
 
 Any help is very much appreciated.
 
 Thanks
 
 Michael
 
 
 
 
 
 
 == error.log.03 ==
 ERROR   (2002-04-04) 16:33.01:693   [access] (/wyona-cms/)
 HttpProcessor[8080][2]/CocoonServlet: Problem with servlet
 java.lang.NullPointerException
  at
 org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2099)
  at
 org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2071)
  at
 
  org.apache.cocoon.sitemap.Handler.process(Handler.java:173)
 
  at org.apache.cocoon.sitemap.Manager.invoke(Manager.java:115)
  at
 
 
  org.apache.cocoon.sitemap.SitemapManager.process(SitemapManager.java:144
  )
 
  at org.apache.cocoon.Cocoon.process(Cocoon.java:605)
  at
 
 
  org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:795)
 
  at
 
  javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 
  at
 
 
  org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Unknown
 
 Source)
  at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(Unknown
 
  Source)
 
  at
 
  org.apache.catalina.core.StandardWrapperValve.invoke(Unknown
 
 Source)
  at
 
  org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
 Source)
  at org.apache.catalina.core.StandardPipeline.invoke(Unknown
 
  Source)
 
  at org.apache.catalina.core.ContainerBase.invoke(Unknown
 
  Source)
 
  at
 
  org.apache.catalina.core.StandardContextValve.invoke(Unknown
 
 Source)
  at
 
  org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
 Source)
  at org.apache.catalina.core.StandardPipeline.invoke(Unknown
 
  Source)
 
  at org.apache.catalina.core.ContainerBase.invoke(Unknown
 
  Source)
 
  at org.apache.catalina.core.StandardContext.invoke(Unknown
 
  Source)
 
  at org.apache.catalina.core.StandardHostValve.invoke(Unknown
 Source)
  at
 
  org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
 Source)
  at
 org.apache.catalina.valves.ErrorDispatcherValve.invoke(Unknown Source)
  at
 
  org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
 Source)
  at org.apache.catalina.valves.ErrorReportValve.invoke(Unknown
 Source)
  at
 
  org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
 Source)
  at org.apache.catalina.valves.AccessLogValve.invoke(Unknown
 
  Source)
 
  at
 
  org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
 Source)
  at org.apache.catalina.core.StandardPipeline.invoke(Unknown
 
  Source)
 
  at org.apache.catalina.core.ContainerBase.invoke(Unknown
 
  Source)
 
  at
 
  org.apache.catalina.core.StandardEngineValve.invoke(Unknown
 
 Source)
  at
 
  org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 
 Source)
  at org.apache.catalina.core.StandardPipeline.invoke(Unknown
 
  Source)
 
  at org.apache.catalina.core.ContainerBase.invoke(Unknown
 
  Source)
 
  at
 org.apache.catalina.connector.http.HttpProcessor.process(Unknown
 
  Source)
 
  at
 
  org.apache.catalina.connector.http.HttpProcessor.run(Unknown
 
 Source)
  at java.lang.Thread.run(Thread.java:484)
 
 
 
 
 
 -
 Please check that your question has not already been answered in the
 FAQ

Re: Load test with ab

2002-04-05 Thread Michael Wechner

There must be another reason in our case. We don't use Microsoft
and we don't use a database. In the case of our load test, everything 
was retrieved from the filesystem.

I will try Cocoon 2.0.2 over the weekend. Maybe that helps.

Michael



Nicola Ken Barozzi wrote:

 From: Chris Warr [EMAIL PROTECTED]
 
Hi, I'm a bit of a newbie so go easy on me if I get things wrong.

We're also having trouble with with cocoon under load.  We're running

 under
 
NT4 SP6a, Tomcat 4.0.3, Cocoon 2.0.2, and JDK 1.3.1.  We've got a webapp
that connects to an MSSQL Server 2000 db using Microsoft's jdbc driver, it
reads some XML from the db then uses FOP to generate a PDF.  The app works
fine under low load however once we beef it up to say 20 processes

 querying
 
concurrently  bad things happen.  Firstly we were using cocoon 2.0.1 as

 you
 
are and found after about 1500 hits cocoon would hang, as you found,

 Tomcat
 
was still okay, and even the sample webapps still run.  So it's our webapp
only that hangs.  THe last few days I've upgraded to Cocoon 2.0.2 and
haven't encountered the hang-up problem.  However I have a new problem,
after a random amount of time (the furthest I've got is 2500 hits, the
quickest was 100 hits) the jvm crashes.  I'm running Tomcat standalone in

 a
 
command prompt.  The error comes in a message box, something about a
reference to a null pointer (0x00), sorry I don't have the exact

 message
 
handy, trying to replicate but it takes a while to get to the problem
numbers.  Anyone else seen this, would upgrading to Tomcat 4.0.4b2 or JVM
1.4 help at all.  To use 1.4 do I need to rebuild cocoon, or just run it

 all
 
with jvm 1.4?

 
 I've had the same problems with many versions of Tomcat, Cocoon, and JDK.
 The problem is the Microsoft drivers and (in the case of Access) the
 JDBC-ODBC bridge driver.
 
 Never use the bridge in a production environment; we had crashes when simply
 closing connections!
 
 Also, Microsofts driver limits in some way the performance:
 http://www.eweek.com/article/0,3658,s=708a=23115,00.asp
 
 
 Out of all the drivers we used, Microsoft's new JDBC driver had the most
 problems. It's still a beta driver in the form distributed on Microsoft's
 Web site, but it's not a new product per se, because it's based on code
 licensed from DataDirect Technologies Inc., which has had the leading
 third-party SQL Server JDBC driver for some years now.
 Providing and supporting its own JDBC driver is a very welcome move, and
 Microsoft officials informed us last month that they had 70,000 downloads of
 the driver so far, so there is considerable customer interest in it.
 However, the driver, in both Beta 1 and Beta 2 forms (we tested both), has
 serious performance and stability problems.
 Using the driver, we were unable to get more than about 200-page-per-second
 throughput, and the problem was clearly the driver-the database was only at
 about 15 percent to 20 percent CPU utilization at this load. The driver also
 has memory leaks: We could see on WebLogic's administration console that
 less memory was freed each time the Java virtual machine did a garbage
 collection. Because of these leaks, the Microsoft JDBC driver was unable to
 run for 8 hours straight.
 
 
 You should change driver (see 3rd party) od DB ;-)
 
 --
 Nicola Ken Barozzi   [EMAIL PROTECTED]
 - verba volant, scripta manent -
(discussions get forgotten, just code remains)
 -
 
 
 -
 Please check that your question has not already been answered in the
 FAQ before posting. http://xml.apache.org/cocoon/faqs.html
 
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 



-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: Load test with ab

2002-04-05 Thread Michael Wechner

Sorry, didn't see your email. Ok, then I won't try 2.0.2 but rather
try the latest CVS version.

Thanks a lot for your help

Michael



Carsten Ziegeler wrote:

 We had the same problem, and it had to do with the MRUStore which is
 not thread safe in 2.0.1 and 2.0.2.
 
 I suggest you try the latest cvs version which is (paranoid) synchronized.
 This solved our problem with a hanging (dead) Cocoon.
 
 Carsten
 
 
-Original Message-
From: Michael Wechner [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 05, 2002 2:08 PM
To: [EMAIL PROTECTED]
Subject: Re: Load test with ab


Where do I find sitemap_xmap.java? Within the work directory of Tomcat?
If so, then I can't tell, because I deleted it unfortunately.
But I can do another load test!

Thanks for your help

Michael



Vadim Gritsenko wrote:


What is in these lines?

org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2099)
org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2071)

Vadim



-Original Message-
From: Michael Wechner [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 04, 2002 9:37 AM
To: [EMAIL PROTECTED]
Subject: Load test with ab

Hi

We did a load test of Cocoon 2.0.1 with ab from Apache.

Everything is fine when we do Concurrency 1 or 3
(ab -n 10 -c 3)
and performance looks good (pretty much the same as Zope).

But when we set Concurrency 10 we run into trouble.
Cocoon seems to stop running after a certain time and is throwing
various Exceptions. And it doesn't recover (to recover we have to
restart Tomcat).

But Tomcat is still running perfectly althought Cocoon doesn't work
anymore.

So I guess it must have something to do with Caching in the memory!

Any help is very much appreciated.

Thanks

Michael






== error.log.03 ==
ERROR   (2002-04-04) 16:33.01:693   [access] (/wyona-cms/)
HttpProcessor[8080][2]/CocoonServlet: Problem with servlet
java.lang.NullPointerException
at
org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2099)
at
org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2071)
at


org.apache.cocoon.sitemap.Handler.process(Handler.java:173)


at org.apache.cocoon.sitemap.Manager.invoke(Manager.java:115)
at



org.apache.cocoon.sitemap.SitemapManager.process(SitemapManager.java:144
)


at org.apache.cocoon.Cocoon.process(Cocoon.java:605)
at



org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:795)


at


javax.servlet.http.HttpServlet.service(HttpServlet.java:853)


at



org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Unknown


Source)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(Unknown


Source)


at


org.apache.catalina.core.StandardWrapperValve.invoke(Unknown


Source)
at


org.apache.catalina.core.StandardPipeline.invokeNext(Unknown


Source)
at org.apache.catalina.core.StandardPipeline.invoke(Unknown


Source)


at org.apache.catalina.core.ContainerBase.invoke(Unknown


Source)


at


org.apache.catalina.core.StandardContextValve.invoke(Unknown


Source)
at


org.apache.catalina.core.StandardPipeline.invokeNext(Unknown


Source)
at org.apache.catalina.core.StandardPipeline.invoke(Unknown


Source)


at org.apache.catalina.core.ContainerBase.invoke(Unknown


Source)


at org.apache.catalina.core.StandardContext.invoke(Unknown


Source)


at org.apache.catalina.core.StandardHostValve.invoke(Unknown
Source)
at


org.apache.catalina.core.StandardPipeline.invokeNext(Unknown


Source)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(Unknown Source)
at


org.apache.catalina.core.StandardPipeline.invokeNext(Unknown


Source)
at org.apache.catalina.valves.ErrorReportValve.invoke(Unknown
Source)
at


org.apache.catalina.core.StandardPipeline.invokeNext(Unknown


Source)
at org.apache.catalina.valves.AccessLogValve.invoke(Unknown


Source)


at


org.apache.catalina.core.StandardPipeline.invokeNext(Unknown


Source)
at org.apache.catalina.core.StandardPipeline.invoke(Unknown


Source)


at org.apache.catalina.core.ContainerBase.invoke(Unknown


Source)


at


org.apache.catalina.core.StandardEngineValve.invoke(Unknown


Source)
at


org.apache.catalina.core.StandardPipeline.invokeNext(Unknown


Source)
at org.apache.catalina.core.StandardPipeline.invoke(Unknown


Source)


at org.apache.catalina.core.ContainerBase.invoke(Unknown


Source)


at
org.apache.catalina.connector.http.HttpProcessor.process(Unknown


Source)


at


org.apache.catalina.connector.http.HttpProcessor.run(Unknown


Source)
at java.lang.Thread.run(Thread.java:484)





-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon

RE: Load test with ab

2002-04-05 Thread Bert Van Kets

Carsten,
does this mean that the latest CVS build can be trusted under heavy loads, 
say 50 to 100 concurrent users?
Bert

At 14:12 5/04/2002 +0200, you wrote:
We had the same problem, and it had to do with the MRUStore which is
not thread safe in 2.0.1 and 2.0.2.

I suggest you try the latest cvs version which is (paranoid) synchronized.
This solved our problem with a hanging (dead) Cocoon.

Carsten


-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




RE: Load test with ab

2002-04-05 Thread Carsten Ziegeler

 -Original Message-
 From: Bert Van Kets [mailto:[EMAIL PROTECTED]]
 Sent: Friday, April 05, 2002 2:51 PM
 To: [EMAIL PROTECTED]
 Subject: RE: Load test with ab
 
 
 Carsten,
 does this mean that the latest CVS build can be trusted under 
 heavy loads, 
 say 50 to 100 concurrent users?
 Bert
 
We had no problems with the average of 80 (and more) simulated 
concurrent users.

Carsten

-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: Load test with ab

2002-04-05 Thread Horst Rutter

Frustrating, I also have to communicate with a MS SQL 2000 db server.
Not having started on the JDBC work I would be interested to know:
a) what kind of experiences people have made using JDBC in a Cocoon 2.x
environment talking to MS SQL 2000
b) any pointers to alternative (other than MS) JDBC drivers, if that's the
bottleneck.

Thanks,
Horst

- Original Message -
From: Nicola Ken Barozzi [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, April 04, 2002 11:57 PM
Subject: Re: Load test with ab
 
 Out of all the drivers we used, Microsoft's new JDBC driver had the most
 problems. It's still a beta driver in the form distributed on Microsoft's
 Web site, but it's not a new product per se, because it's based on code
 licensed from DataDirect Technologies Inc., which has had the leading
 third-party SQL Server JDBC driver for some years now.
 Providing and supporting its own JDBC driver is a very welcome move, and
 Microsoft officials informed us last month that they had 70,000 downloads
of
 the driver so far, so there is considerable customer interest in it.
 However, the driver, in both Beta 1 and Beta 2 forms (we tested both), has
 serious performance and stability problems.
 Using the driver, we were unable to get more than about
200-page-per-second
 throughput, and the problem was clearly the driver-the database was only
at
 about 15 percent to 20 percent CPU utilization at this load. The driver
also
 has memory leaks: We could see on WebLogic's administration console that
 less memory was freed each time the Java virtual machine did a garbage
 collection. Because of these leaks, the Microsoft JDBC driver was unable
to
 run for 8 hours straight.
 

 You should change driver (see 3rd party) od DB ;-)

 --
 Nicola Ken Barozzi   [EMAIL PROTECTED]
 - verba volant, scripta manent -
(discussions get forgotten, just code remains)
 -


 -
 Please check that your question has not already been answered in the
 FAQ before posting. http://xml.apache.org/cocoon/faqs.html

 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]





-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




RE: Load test with ab

2002-04-04 Thread Vadim Gritsenko

What is in these lines?

org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2099)
org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2071)

Vadim

 -Original Message-
 From: Michael Wechner [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, April 04, 2002 9:37 AM
 To: [EMAIL PROTECTED]
 Subject: Load test with ab
 
 Hi
 
 We did a load test of Cocoon 2.0.1 with ab from Apache.
 
 Everything is fine when we do Concurrency 1 or 3
 (ab -n 10 -c 3)
 and performance looks good (pretty much the same as Zope).
 
 But when we set Concurrency 10 we run into trouble.
 Cocoon seems to stop running after a certain time and is throwing
 various Exceptions. And it doesn't recover (to recover we have to
 restart Tomcat).
 
 But Tomcat is still running perfectly althought Cocoon doesn't work
 anymore.
 
 So I guess it must have something to do with Caching in the memory!
 
 Any help is very much appreciated.
 
 Thanks
 
 Michael
 
 
 
 
 
 
 == error.log.03 ==
 ERROR   (2002-04-04) 16:33.01:693   [access] (/wyona-cms/)
 HttpProcessor[8080][2]/CocoonServlet: Problem with servlet
 java.lang.NullPointerException
  at
 org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2099)
  at
 org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2071)
  at
org.apache.cocoon.sitemap.Handler.process(Handler.java:173)
  at org.apache.cocoon.sitemap.Manager.invoke(Manager.java:115)
  at

org.apache.cocoon.sitemap.SitemapManager.process(SitemapManager.java:144
)
  at org.apache.cocoon.Cocoon.process(Cocoon.java:605)
  at

org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:795)
  at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
  at

org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Unknown
 Source)
  at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(Unknown
Source)
  at
org.apache.catalina.core.StandardWrapperValve.invoke(Unknown
 Source)
  at
org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 Source)
  at org.apache.catalina.core.StandardPipeline.invoke(Unknown
Source)
  at org.apache.catalina.core.ContainerBase.invoke(Unknown
Source)
  at
org.apache.catalina.core.StandardContextValve.invoke(Unknown
 Source)
  at
org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 Source)
  at org.apache.catalina.core.StandardPipeline.invoke(Unknown
Source)
  at org.apache.catalina.core.ContainerBase.invoke(Unknown
Source)
  at org.apache.catalina.core.StandardContext.invoke(Unknown
Source)
  at org.apache.catalina.core.StandardHostValve.invoke(Unknown
 Source)
  at
org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 Source)
  at
 org.apache.catalina.valves.ErrorDispatcherValve.invoke(Unknown Source)
  at
org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 Source)
  at org.apache.catalina.valves.ErrorReportValve.invoke(Unknown
 Source)
  at
org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 Source)
  at org.apache.catalina.valves.AccessLogValve.invoke(Unknown
Source)
  at
org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 Source)
  at org.apache.catalina.core.StandardPipeline.invoke(Unknown
Source)
  at org.apache.catalina.core.ContainerBase.invoke(Unknown
Source)
  at
org.apache.catalina.core.StandardEngineValve.invoke(Unknown
 Source)
  at
org.apache.catalina.core.StandardPipeline.invokeNext(Unknown
 Source)
  at org.apache.catalina.core.StandardPipeline.invoke(Unknown
Source)
  at org.apache.catalina.core.ContainerBase.invoke(Unknown
Source)
  at
 org.apache.catalina.connector.http.HttpProcessor.process(Unknown
Source)
  at
org.apache.catalina.connector.http.HttpProcessor.run(Unknown
 Source)
  at java.lang.Thread.run(Thread.java:484)
 
 
 
 
 
 -
 Please check that your question has not already been answered in the
 FAQ before posting. http://xml.apache.org/cocoon/faqs.html
 
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




RE: Load test with ab

2002-04-04 Thread Chris Warr


Hi, I'm a bit of a newbie so go easy on me if I get things wrong.

We're also having trouble with with cocoon under load.  We're running under
NT4 SP6a, Tomcat 4.0.3, Cocoon 2.0.2, and JDK 1.3.1.  We've got a webapp
that connects to an MSSQL Server 2000 db using Microsoft's jdbc driver, it
reads some XML from the db then uses FOP to generate a PDF.  The app works
fine under low load however once we beef it up to say 20 processes querying
concurrently  bad things happen.  Firstly we were using cocoon 2.0.1 as you
are and found after about 1500 hits cocoon would hang, as you found, Tomcat
was still okay, and even the sample webapps still run.  So it's our webapp
only that hangs.  THe last few days I've upgraded to Cocoon 2.0.2 and
haven't encountered the hang-up problem.  However I have a new problem,
after a random amount of time (the furthest I've got is 2500 hits, the
quickest was 100 hits) the jvm crashes.  I'm running Tomcat standalone in a
command prompt.  The error comes in a message box, something about a
reference to a null pointer (0x00), sorry I don't have the exact message
handy, trying to replicate but it takes a while to get to the problem
numbers.  Anyone else seen this, would upgrading to Tomcat 4.0.4b2 or JVM
1.4 help at all.  To use 1.4 do I need to rebuild cocoon, or just run it all
with jvm 1.4?

Chris.


-Original Message-
From: Michael Wechner [mailto:[EMAIL PROTECTED]]
Sent: Friday, 5 April 2002 0:37
To: [EMAIL PROTECTED]
Subject: Load test with ab


Hi

We did a load test of Cocoon 2.0.1 with ab from Apache.

Everything is fine when we do Concurrency 1 or 3
(ab -n 10 -c 3)
and performance looks good (pretty much the same as Zope).

But when we set Concurrency 10 we run into trouble.
Cocoon seems to stop running after a certain time and is throwing 
various Exceptions. And it doesn't recover (to recover we have to 
restart Tomcat).

But Tomcat is still running perfectly althought Cocoon doesn't work
anymore.

So I guess it must have something to do with Caching in the memory!

Any help is very much appreciated.

Thanks

Michael






== error.log.03 ==
ERROR   (2002-04-04) 16:33.01:693   [access] (/wyona-cms/) 
HttpProcessor[8080][2]/CocoonServlet: Problem with servlet
java.lang.NullPointerException
 at 
org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2099)
 at 
org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2071)
 at org.apache.cocoon.sitemap.Handler.process(Handler.java:173)
 at org.apache.cocoon.sitemap.Manager.invoke(Manager.java:115)
 at 
org.apache.cocoon.sitemap.SitemapManager.process(SitemapManager.java:144)
 at org.apache.cocoon.Cocoon.process(Cocoon.java:605)
 at 
org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:795)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Unknown 
Source)
 at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(Unknown Source)
 at org.apache.catalina.core.StandardWrapperValve.invoke(Unknown 
Source)
 at org.apache.catalina.core.StandardPipeline.invokeNext(Unknown 
Source)
 at org.apache.catalina.core.StandardPipeline.invoke(Unknown Source)
 at org.apache.catalina.core.ContainerBase.invoke(Unknown Source)
 at org.apache.catalina.core.StandardContextValve.invoke(Unknown 
Source)
 at org.apache.catalina.core.StandardPipeline.invokeNext(Unknown 
Source)
 at org.apache.catalina.core.StandardPipeline.invoke(Unknown Source)
 at org.apache.catalina.core.ContainerBase.invoke(Unknown Source)
 at org.apache.catalina.core.StandardContext.invoke(Unknown Source)
 at org.apache.catalina.core.StandardHostValve.invoke(Unknown 
Source)
 at org.apache.catalina.core.StandardPipeline.invokeNext(Unknown 
Source)
 at 
org.apache.catalina.valves.ErrorDispatcherValve.invoke(Unknown Source)
 at org.apache.catalina.core.StandardPipeline.invokeNext(Unknown 
Source)
 at org.apache.catalina.valves.ErrorReportValve.invoke(Unknown 
Source)
 at org.apache.catalina.core.StandardPipeline.invokeNext(Unknown 
Source)
 at org.apache.catalina.valves.AccessLogValve.invoke(Unknown Source)
 at org.apache.catalina.core.StandardPipeline.invokeNext(Unknown 
Source)
 at org.apache.catalina.core.StandardPipeline.invoke(Unknown Source)
 at org.apache.catalina.core.ContainerBase.invoke(Unknown Source)
 at org.apache.catalina.core.StandardEngineValve.invoke(Unknown 
Source)
 at org.apache.catalina.core.StandardPipeline.invokeNext(Unknown 
Source)
 at org.apache.catalina.core.StandardPipeline.invoke(Unknown Source)
 at org.apache.catalina.core.ContainerBase.invoke(Unknown Source)
 at 
org.apache.catalina.connector.http.HttpProcessor.process(Unknown Source)
 at 

Re: Load test with ab

2002-04-04 Thread Nicola Ken Barozzi

From: Chris Warr [EMAIL PROTECTED]


 Hi, I'm a bit of a newbie so go easy on me if I get things wrong.

 We're also having trouble with with cocoon under load.  We're running
under
 NT4 SP6a, Tomcat 4.0.3, Cocoon 2.0.2, and JDK 1.3.1.  We've got a webapp
 that connects to an MSSQL Server 2000 db using Microsoft's jdbc driver, it
 reads some XML from the db then uses FOP to generate a PDF.  The app works
 fine under low load however once we beef it up to say 20 processes
querying
 concurrently  bad things happen.  Firstly we were using cocoon 2.0.1 as
you
 are and found after about 1500 hits cocoon would hang, as you found,
Tomcat
 was still okay, and even the sample webapps still run.  So it's our webapp
 only that hangs.  THe last few days I've upgraded to Cocoon 2.0.2 and
 haven't encountered the hang-up problem.  However I have a new problem,
 after a random amount of time (the furthest I've got is 2500 hits, the
 quickest was 100 hits) the jvm crashes.  I'm running Tomcat standalone in
a
 command prompt.  The error comes in a message box, something about a
 reference to a null pointer (0x00), sorry I don't have the exact
message
 handy, trying to replicate but it takes a while to get to the problem
 numbers.  Anyone else seen this, would upgrading to Tomcat 4.0.4b2 or JVM
 1.4 help at all.  To use 1.4 do I need to rebuild cocoon, or just run it
all
 with jvm 1.4?

I've had the same problems with many versions of Tomcat, Cocoon, and JDK.
The problem is the Microsoft drivers and (in the case of Access) the
JDBC-ODBC bridge driver.

Never use the bridge in a production environment; we had crashes when simply
closing connections!

Also, Microsofts driver limits in some way the performance:
http://www.eweek.com/article/0,3658,s=708a=23115,00.asp


Out of all the drivers we used, Microsoft's new JDBC driver had the most
problems. It's still a beta driver in the form distributed on Microsoft's
Web site, but it's not a new product per se, because it's based on code
licensed from DataDirect Technologies Inc., which has had the leading
third-party SQL Server JDBC driver for some years now.
Providing and supporting its own JDBC driver is a very welcome move, and
Microsoft officials informed us last month that they had 70,000 downloads of
the driver so far, so there is considerable customer interest in it.
However, the driver, in both Beta 1 and Beta 2 forms (we tested both), has
serious performance and stability problems.
Using the driver, we were unable to get more than about 200-page-per-second
throughput, and the problem was clearly the driver-the database was only at
about 15 percent to 20 percent CPU utilization at this load. The driver also
has memory leaks: We could see on WebLogic's administration console that
less memory was freed each time the Java virtual machine did a garbage
collection. Because of these leaks, the Microsoft JDBC driver was unable to
run for 8 hours straight.


You should change driver (see 3rd party) od DB ;-)

--
Nicola Ken Barozzi   [EMAIL PROTECTED]
- verba volant, scripta manent -
   (discussions get forgotten, just code remains)
-


-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]