IC86756: STERLING B2B INTEGRATOR IS AN FTPS CLIENT. THE SSL HANDSHAKE GENERATES A FATAL ALERT FOR PROTOCOL VERSION MISMATCH.

APAR status

• Closed as program error.

Error description

• Using Sterling B2B Integrator 5.2 build 5020200.  Sterling B2B
  Integrator is acting as FTPS client.  Sporadically during the
  SSL handshake an SSL Alert is generated for protocol version
  mismatch. Also we see the same error for AS2 communicateion.
  
  
  The Perimeter Log shows error:
  [2010-05-07 16:24:50.853] ERROR <FTP-Client-Scheduler>
  000000000000 GLOBAL_SCOPE
  FtpClient99913843289com.sterlingcommerce.perimeter.api.conduit.S
  SLByteDataConduit@1dd735c:Got exception doing SSL
  com.certicom.net.ssl.b: FATAL Alert:PROTOCOL_VERSION - The
  protocol version requested is recognized but not supported.
   Description: ClientState: The Peer Protocol is not Supported.
      at
  com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(U
  nknown Source)
      at
  com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(U
  nknown Source)
      at com.certicom.tls.record.handshake.R.a(Unknown Source)
      at com.certicom.tls.record.handshake.f.a(Unknown Source)
      at com.certicom.tls.record.handshake.R.b(Unknown Source)
      at com.certicom.tls.record.handshake.R.a(Unknown Source)
      at com.certicom.tls.record.g.a(Unknown Source)
      at com.certicom.tls.record.g.a(Unknown Source)
      at com.certicom.tls.record.k.f(Unknown Source)
      at com.certicom.tls.record.k.c(Unknown Source)
      at com.certicom.tls.record.k.b(Unknown Source)
      at
  com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandsha
  ke(Unknown Source)
      at com.certicom.tls.record.k.read(Unknown Source)
      at
  com.sterlingcommerce.perimeter.api.conduit.SSLByteDataConduit.lo
  wLevelRead(SSLByteDataConduit.java:441)
      at
  com.sterlingcommerce.perimeter.api.conduit.SSLByteDataConduit.re
  ceive(SSLByteDataConduit.java:387)
      at
  com.sterlingcommerce.perimeter.api.conduit.SSLByteDataConduit.re
  ceive(SSLByteDataConduit.java:324)
      at
  com.sterlingcommerce.perimeter.api.conduit.SSLByteDataConduit.ca
  nReceive(SSLByteDataConduit.java:493)
      at
  com.sterlingcommerce.perimeter.api.conduit.SSLByteConduit.canRec
  eive(SSLByteConduit.java:268)
      at
  com.sterlingcommerce.perimeter.api.conduit.DataConduitApiImpl$3.
  body(DataConduitApiImpl.java:275)
      at
  com.sterlingcommerce.perimeter.api.ContextRunnable.run(ContextRu
  nnable.java:52)
      at
  com.sterlingcommerce.perimeter.api.scheduler.TaskNode.run(TaskNo
  de.java:70)
      at
  com.sterlingcommerce.perimeter.dispatcher.AbstractDispatcher.run
  Tasks(AbstractDispatcher.java:431)
      at
  com.sterlingcommerce.perimeter.dispatcher.AbstractDispatcher.doR
  un(AbstractDispatcher.java:397)
      at
  com.sterlingcommerce.perimeter.dispatcher.AbstractDispatcher$2.r
  un(AbstractDispatcher.java:172)
      at java.lang.Thread.run(Thread.java:595)
  [2010-05-07 16:24:50.853] DEBUG <FTP-Client-Scheduler>
  000000000000 GLOBAL_SCOPE
  FtpClient99913843289com.sterlingcommerce.perimeter.api.conduit.S
  SLByteDataConduit@1dd735c.close() - : Close
  CloseCode.CONNECTION_RESET
  

Local fix

• STTBIN - 310827
  
  TB / TB
  
  Circumvention: restart Sterling B2B Integrator or continue to
  retry the connection
  

Problem summary

• Users Affected:
  All users
  
  Problem Description:
  SI (is FTPS client ) during SSL handshake generates a fatal
  alert for protocol version mismatch.
  
  Platforms Affected:
  ALL
  

Problem conclusion

• Resolution Summary:
  Made the SSL session ID unique to differentiate the
  communications with different server and ports.
  
  Delivered in:
  5020401
  

Temporary fix

Comments

• Published on 10/11/12
  

APAR Information

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

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

Fix information

• Fixed component name

  STR FILE GATEWA

• Fixed component ID

  5725D0700

Applicable component levels

• R224 PSY

     UP