Resolving the “Bind Exception” stumble block for JMeter

Resolving the “Bind Exception” stumble block for JMeter

Using JMeter to test performance provides an unusual stumble block in the form of Windows limitations. When 1000 to 1200 threads are in process, you may hit the block in the form of “Bind Exception“. This is attributed to the limitation of Windows to process concurrent threads. We can enhance the limit by the following workaround.

1. Type “regedit” and invoke Registry Editor in the RUN menu
2. Locate the following subkey in the registry.
3. Go to Parameters:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. On the Edit menu, click New, and then add the following registry entry

Value Name: MaxUserPort

Value Type: DWORD

Value data: 65534

Default: 0x1388 (5000 decimal)

How this setting helps?

The setting for the parameter controls the maximum allowable port number that could be used when any program requests available user port from the system. Typical usage of ports are managed within the range 1024 and 5000. When the number of VUs (threads) increases, then it needs more open ports since the refresh of the available ports take a while.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s