That sounds like a problem I'm just having too, I've got quite a bit of 
XSP in my test cases, and Tomcat is just dieing without any errors 
displayed at all. In fact I've looked in every log I can think of (tomcat,
  cocoon, system) and I can't see any evidence of anything going wrong!

Stuart.

On Thursday, August 9, 2001, at 07:11  pm, Vadim Gritsenko wrote:

> I found a problem:
>
> Cocoon takes all available memory after ~ 500-600 accesses to 
> http://localhost:8080/cocoon/xsp/simple
> and Resin crashes:
> #
> # An EXCEPTION_ACCESS_VIOLATION exception has been detected in native 
> code outside the VM.
> # Program counter=0x50397707
> #
>
> Clearly, something is wrong with XSP... Some resources are not released.
> cocoon.log file does not have any errors.
>
> Berin,
> could you verify this behaviour?
>
> Vadim
>
>> -----Original Message-----
>> From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
>> Sent: Thursday, August 09, 2001 12:24 PM
>> To: [EMAIL PROTECTED]
>> Subject: Re: IT WON'T BREAK!!! (was Re: New Excalibur--Time to redo your 
>> Cocoon Load Tests)
>>
>>
>> Vadim Gritsenko wrote:
>>>
>>>> -----Original Message-----
>>>> From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
>>>> Sent: Thursday, August 09, 2001 11:23 AM
>>>> To: [EMAIL PROTECTED]
>>>> Subject: IT WON'T BREAK!!! (was Re: New Excalibur--Time to redo your 
>>>> Cocoon Load Tests)
>>>>
>>>>
>>>> Berin Loritsch wrote:
>>>>>
>>>>> My initial JMeter load tests show no error messages and plenty of 
>>>>> reason to smile.
>>>>> I simulated 20 users each hitting the server every 300ms.  When the 
>>>>> JVM was in
>>>>> a garbage collection cycle, the longest response time was 842ms.  
>>>>> During normal
>>>>> opperation, responses were between 0ms and 20ms (55% at 0, 40% at 10,
>>>>>  5% at 20)
>>>>> with occasional spikes around 100ms.
>>>>>
>>>>> I am going to up the JMeter load test to allow for 100 simultaneous 
>>>>> users just to
>>>>> try and break it.
>>>>
>>>> I ran it with 100 simultaneous users--and the longest processing 
>>>> times were still
>>>> less than 1.6 seconds (my magic "it takes too long on the server" 
>>>> time).
>>>>
>>>> I wasn't satisfied, so I went with 200 simultaneous users.  My 
>>>> longest processing
>>>> time was 3.135 seconds with one Resin Server through Apache, on a 750 
>>>> MHz Athlon
>>>> and 256 MB RAM.
>>>>
>>>
>>> I assume this results are for static resource (/welcome?), how about 
>>> dynamic resources?
>>> (simple sql or esql)?
>>
>> I'll let you know in a bit.  in the mean time, run some tests of your 
>> own and give some
>> feedback.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, email: [EMAIL PROTECTED]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>


-------------------------------------------------------------------------
Stuart Roebuck                                  [EMAIL PROTECTED]
Lead Developer                               Java, XML, MacOS X, XP, etc.
ADOLOS                                           <http://www.adolos.com/>

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

Reply via email to