IC39910: HOD: USING WINDOWS 98 VIA DIAL-UP CONNECTION WITH SSL ENABLED, HOST ON-DEMAND GIVES COMM657 AND WILL NOT CONNECT TO THE HOST.

APAR status

• Closed as program error.

Error description

• Host On-Demand 8.00
  ___________________
  Using a Windows 98 machine connecting with narrowband,
  specifically a modem connection, with an SSL-enabled session
  through the redirector, the connection will never be establish-
  ed. A COMM657 will continue to be seen in the OIA.
  The redirector trace shows a
  00:00:00:000@Redirector@RedirectorService@RDR@SSLServerProxyThre
  ad:run:caught IOException java.io.IOException:
  javaskitSecureSocket.init(...) call failed : rc = 420.
  The sm.zip file has been edited to take into account the
  slower timing requirements.
  ___________________
  Keywords:  Windows 98, SSL, COMM657, dial-up, narrowband
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users making a Host On-Demand SSL            *
  *                 connection over dial-up or slow              *
  *                 connection                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Client-side SSL via Host On-Demand      *
  *                      redirector over a slow or dial-up       *
  *                      connection does not work as the         *
  *                      underlying socket times out.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Using a Microsoft Windows 98 machine connecting with
  narrowband, specifically a modem connection, with an
  SSL-enablesd session through the redirector, the
  connection will never be established.
  A COMM657 will be seen in the OIA.
  
  The redirector trace shows a
  
  00:00:00:000@Redirector@RedirectorService@RDR@SSLServerProxyThre
  
  ad:run:caught IOException java.io.IOException:
  
  javaskitSecureSocket.init(...) call failed : rc = 420.
  

Problem conclusion

• The socket timeout of 20 ms was getting set in the
  SecureSocketAccept call. The socket timeout should be set
  much later after the ssl connection has been established.
  Removed the Socket timeout setting as a parameter to the
  secureSocketAccept call.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• SSLSERVE
  

Fix information

Applicable component levels

• R800 PSY

     UP