The generation of a service class, port, and dispatch requires processing cost, so we recommend that you use the injection (only for the stub-based Web Service clients) or reuse the objects. For reusing the objects, see each of the following sections:

• For stub-based Web Service clients
  3.6.1(3) Generating service classes and acquiring ports
  
• For dispatch-based Web Service clients
  3.6.2(3) Reusing a service class and dispatch
  
• For API-based Web Service clients
  3.6.3(2) Reusing the javax.xml.ws.Service object and the port
  

As and when required, specify the settings for a proxy, SSL connection, and the basic authentication in the execution environment of Web Service clients. For details, see each of the following sections:

• Setting a proxy
  10.10 Connecting through a proxy server
  
• Setting an SSL connection
  10.11 Connection by SSL protocol
  
• Setting basic authentication
  10.12 Connection by basic authentication
  

In the environment in which you send a large number of requests from the Web Service client, the following exception might be recorded in some cases:

java.net.BindException: Address already in use: connect [errno=10048, syscall=select]

For example, an exception occurs when large number of requests reach the Web Service client that is implemented as a servlet.

In such a case, revise either one or both of the following values:

• Increase the range of port numbers that are available in the OS
• Decrease the duration of TIME_WAIT

For example, revise the settings of MaxUserPort and TcpTimedWaitDelay in the registry. However, the specifications differ depending on the OS version, edition, and the application status of the security update program, and therefore, see the documentation of each OS for details. Also, you must note that the settings affect the entire OS.