Error [10048] Address already in use

351 views
Skip to first unread message

karim ibrahim

unread,
Jun 27, 2011, 6:54:08 AM6/27/11
to lr-loa...@googlegroups.com
Hello all , 

I am facing the below error during running the performance scripts using have load of 300 user (This error is not appearing with normal load of 50 users ) , i have changed the  registry value and restarted the machine and the issue is not solved , could you please advice about his issue 


Failed to connect to server "10.122.122.12:443":


[10048] Address already in use

Try changing the registry value

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\tcpip\Parameters\TcpTimedWaitDelay to 30

and HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\tcpip\Parameters\MaxUserPort to 65534

and rebooting the machine


Accept My Regards,
Karim  

James Pulley

unread,
Jun 27, 2011, 9:31:00 AM6/27/11
to lr-loa...@googlegroups.com

I am uncertain how changing the values you note in the registry would have any impact on a address conflict.   You have two possibilities here.  (1) You have a re-use of a local port already in use for the transient client side port connection to the server or (2) you have a server side conflict.   Let’s take a divide and conquer approach.   

 

I am assuming you are following best practices and have at least three load generators involved, not including your controller (2 primary plus 1 control).   Do the errors follow to all load generators?  Is your lightly loaded control generator impacted at the same rate as the two primary load generators?   If only a single load generator is impacted and not the others, then you have your answer.  It is a local issue that needs resolution.   Find what is happening on the problematic load generator which is different and fix that.    Goes back to testing 101 stuff regarding documented initial conditions for both the app and the environment.

 

Now, if you have errors which are crossing all load generators, both primary load and the lightly loaded control generator, then you most likely have a server side issue to address where you may have a restriction on the number of concurrent ports on the server side so it is attempting to re-use an already open transient client connection, hence the conflict.

 

This is a prime opportunity to leverage those foundation skills in testing!   You need to be able to easily troubleshoot items such as this before you are able to look inside complex application architectures for issues.

 

James Pulley, http://www.loadrunnerbythehour.com/PricingMatrix

--
You received this message because you are subscribed to the Google "LoadRunner" group.
To post to this group, send email to LR-Loa...@googlegroups.com
To unsubscribe from this group, send email to
LR-LoadRunne...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/LR-LoadRunner?hl=en

Jerry Yin

unread,
Aug 20, 2012, 11:25:27 PM8/20/12
to lr-loa...@googlegroups.com
Did you tried to change the value in the registry of the LG?

On Fri, Aug 17, 2012 at 10:09 PM, SRK <suryakant...@gmail.com> wrote:
Hi Karim and others, have you got this issue resolved, if yes please send me the solution as I am facing the same issue..

Thanks in advance..
SRK
Reply all
Reply to author
Forward
0 new messages