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

Technote (troubleshooting)


Problem(Abstract)

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

Symptom

The control connection closes unexpectedly. Usually on the 2nd retry the connection will be established, but it may not, or it could take up to more retries.


Cause

This has been identified as a product defect under APAR IC86756

Environment

All

Diagnosing the problem

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.


The Perimeter Log shows error:

[2010-05-07 16:24:50.853] ERROR <FTP-Client-Scheduler>
000000000000 GLOBAL_SCOPE FtpClient99913843289com.sterlingcommerce.perimeter.api.conduit.SSLByteDataConduit@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(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown 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.completeHandshake(Unknown Source)
at com.certicom.tls.record.k.read(Unknown Source)
at com.sterlingcommerce.perimeter.api.conduit.SSLByteDataConduit.lowLevelRead(SSLByteDataConduit.java:441)
at com.sterlingcommerce.perimeter.api.conduit.SSLByteDataConduit.receive(SSLByteDataConduit.java:387)
at com.sterlingcommerce.perimeter.api.conduit.SSLByteDataConduit.receive(SSLByteDataConduit.java:324)
at com.sterlingcommerce.perimeter.api.conduit.SSLByteDataConduit.canReceive(SSLByteDataConduit.java:493)
at com.sterlingcommerce.perimeter.api.conduit.SSLByteConduit.canReceive(SSLByteConduit.java:268)
at com.sterlingcommerce.perimeter.api.conduit.DataConduitApiImpl$3.body(DataConduitApiImpl.java:275)
at com.sterlingcommerce.perimeter.api.ContextRunnable.run(ContextRunnable.java:52)
at com.sterlingcommerce.perimeter.api.scheduler.TaskNode.run(TaskNode.java:70)
at com.sterlingcommerce.perimeter.dispatcher.AbstractDispatcher.runTasks(AbstractDispatcher.java:431)
at com.sterlingcommerce.perimeter.dispatcher.AbstractDispatcher.doRun(AbstractDispatcher.java:397)
at com.sterlingcommerce.perimeter.dispatcher.AbstractDispatcher$2.run(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.SSLByteDataConduit@1dd735c.close() - : Close CloseCode.CONNECTION_RESET


Resolving the problem

APAR IC86756 is now included in Sterling B2B Integrator 5.2 build 5020401 which was ega on Oct 22, 2012.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Sterling B2B Integrator

Software version:

5.2.2

Operating system(s):

All

Reference #:

1616006

Modified date:

2013-01-09

Translate my page

Machine Translation

Content navigation