Troubleshooting
Problem
FATAL Alert:PROTOCOL_VERSION - The protocol version requested is recognized but not supported.
Symptom
Every since applying patch 5 to GIS4.3 they are getting a strange SSL error during one of their long existing FTP Bps. They have this BP scheduled to run the same time each day but whether they wait two minutes or twenty minutes later, they can resume the BP and it works each time with no SSL Protocol version not supported messages.
Error Message[2008-02-25 17:08:41.685] ERROR 000000000000 <a>GLOBAL_SCOPE
FtpClient20635176996com.sterlingcommerce.perimeter.api.conduit.SSLByteDataCon
duit@2fdddd:Doing reset3
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.M.a(Unknown Source)
at com.certicom.tls.record.handshake.e.a(Unknown Source)
at
com.certicom.tls.record.handshake.M.b(Unknown Source)
at
com.certicom.tls.record.handshake.M.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(SSLBy
teDataConduit.java:454)
at
com.sterlingcommerce.perimeter.api.conduit.SSLByteDataConduit.receive(SSLByteDat
aConduit.java:400)
at
com.sterlingcommerce.perimeter.api.conduit.SSLByteDataConduit.receive(SSLByteDat
aConduit.java:337)
at
com.sterlingcommerce.perimeter.api.conduit.SSLByteDataConduit.canReceive(SSLByte
DataConduit.java:502)
at
com.sterlingcommerce.perimeter.api.conduit.SSLByteConduit.canReceive(SSLByteCond
uit.java:258)
at
com.sterlingcommerce.perimeter.api.conduit.DataConduitApiImpl$3.body(DataConduit
ApiImpl.java:275)
at
com.sterlingcommerce.perimeter.api.ContextRunnable.run(ContextRunnable.java:52)<
br /> at
com.sterlingcommerce.perimeter.api.scheduler.TaskNode.run(TaskNode.java:70)
at
com.sterlingcommerce.perimeter.dispatcher.AbstractDispatcher.runTasks(AbstractDi
spatcher.java:431)
at
com.sterlingcommerce.perimeter.dispatcher.AbstractDispatcher.doRun(AbstractDispa
tcher.java:397)
at
com.sterlingcommerce.perimeter.dispatcher.AbstractDispatcher$2.run(AbstractDispa
tcher.java:172)
at java.lang.Thread.run(Thread.java:595)
To view more of this document
Historical Number
TRB2403
Was this topic helpful?
Document Information
Modified date:
18 May 2020
UID
swg21561419