On 08/02/2010 15:05, Munirathinavel wrote:
Our application is Online Vehicle Booking for Rental.
I'm doing Load Testing using HP Load Runner and I've recorded a script that
contains booking a vehicle (submitting data to MSSQL Server 2008) then did a
load testing with 20 concurrent users.Meanwhile I'm trying to do booking
manually from the browser.
But booking window is loading for long time and only one message i'm getting
is 200 Aborted.(In Firebug from Mozilla Firefox).but Internet explorer not
showing anything.
In log I'm getting this message..
org.hibernate.LazyInitializationException: could not initialize proxy - the
owning Session was closed
Seems clear where the problem is.
Hibernate is not able to acquire a resource that it needs, I'd suggest
that you look to your Hibernate / database configuration for answers.
p
Pid Ster wrote:
On 08/02/2010 06:37, munirathina...@gmail.com wrote:
I'm having the following configuration.....
Please reply to the list only.
Leaving the whole/majority of the previous message intact helps other
readers follow the thread.
Again, no need for all the extra spacing.
OS- Windows Server 2008
RAM- 4 GB
Processor-Intel Xeon(R)
Tomcat version-6.0.18
>This is my server.xml configuration......
<Executor name="tomcatThreadPool"
namePrefix="catalina-exec-"
maxThreads="400" minSpareThreads="4"
maxSpareThreads="100" />
What, all of it?
JVM memory settings:
Path -C:\Program Files\Java\jdk1.6.0_16\jre\bin\server\jvm.dll
Initial memory pool - 1024 MB
Maximum memory pool - 2560 MB
Thread stack size - 1024 KB
I'm not a Windows expert, but that doesn't look
Last few days I'm doing load testing in my application.Two
days back i did a load testing with 20 concurrent users and the
application responding very slowly.Some pages are not getting loaded. In
Mozilla (Firebug) I'm getting Page Aborted as the status.
Can you please tell me what is the problem and how can i
proceed with more than 20 concurrent users.
Thanks.
Based on the information you've provided I'd have to guess that your
application is the problem. You can proceed with more than 20
concurrent users by fixing your application.
Tomcat is known to support very high loads in production, some regulars
on the list here will attest to that.
Read the following:
http://catb.org/~esr/faqs/smart-questions.html
What does your application do?
How are you load testing your application, exactly?
What do your application logs say during the slow down?
p
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
