You should listen to SuperKevy and investigate hard limits in the
number of connections allowed on the server.
Try browsing manually while the virtual users are failing. If you see
errors then this proves that LoadRunner is not at fault.
Look at the graphs of TCP connections, CPU and RAM on the server side.
Their shapes will give you clues to what is happening.
Try to understand what the server is doing when it fails, find the
error logs and read them. Learn about the technologies that you're
testing, find the experts and ask them for advice, get the developers
to draw you diagrams until you understand each component in the
system.
Use smaller scripts to pinpoint the failing component in a scientific
manor: Could it be connections to the web server? Could it be web
services called within the pages? Could it be connections to the
database?
Once you have found the problematic component, examine and adjust the
configuration, repeating the test each time you change something. If
you have exhausted all available options, ask the developers to add
additional error logging and start again.
> > On Sat, Mar 21, 2009 at 10:11 AM, prasenjit dutta <
prasenjit...@gmail.com>wrote:
>
> >> hi abdul,
>
> >> can u plz tell me actually where we need to add those code???/starting of
> >> the script/end, init, action or in the end section.
> >> pls let me know all these......
>
> >> thanks,
> >> prasenjit
>