IC SunsetThe developerWorks Connections platform will be sunset on December 31, 2019. On January 1, 2020, this forum will no longer be available. More details available on our FAQ.
Topic
  • 1 reply
  • Latest Post - ‏2015-06-04T12:02:55Z by philcoxhead
RANEEE
RANEEE
1 Post

Pinned topic MQFTE FTPS Bridge - BFGBR0150E error

‏2015-05-28T11:57:43Z | fte mq-mft mqfte transfer

I am trying to implement MQFTE FTPS Bridge. The problem is that is doesn't connect to the FTPS Server. The network is opened - I have managed to connect with some other FTPS Client software.

There is nothing in the log files, but in the trace I get the following messages:

[PB-ADM-CONNECT - failed [IOException=Read timed out]]

connect, BFGBR0150E: Protocol IO exception has occurred. Exception: Read timed out [com.ibm.wmqfte.bridge.protocol.ProtocolException]

<init>, BFGBR0150E: Protocol IO exception has occurred. Exception: Read timed out [com.ibm.wmqfte.io.FTETransferIOException]

If it helps, attached a few configuration settings I used in this implementation.

I will appreciate any help.

Thanks,

Ran

 

my ProtocolBridgeProperties:

<tns:defaultServer name="name" />
<tns:ftpsServer name="name" host="host" port="990" platform="Windows"
     timeZone="Europe/London" locale="en_GB" fileEncoding="UTF8"
     listFormat="unix" limitedWrite="false" ftpsType="explicit" connectTimeout="5"
     trustStore="C:\ProgramData\IBM\MQ\mqft\config\QM1\agents\BRITEST1\KEY.jks" />

 

my ProtocolBridgeCredentials:

          <tns:agent name="agent">                                        
            <tns:serverHost name="host" 
                            keyStorePassword="password" 
                            trustStorePassword="password">
              <tns:user name="user" serverUserId="ftpsuser" serverPassword="password" hostKey="fingerprint" />
            </tns:serverHost>
          </tns:agent>

 

 

 

 

  • philcoxhead
    philcoxhead
    1 Post

    Re: MQFTE FTPS Bridge - BFGBR0150E error

    ‏2015-06-04T12:02:55Z  

    Hi Raneee, I would be tempted to change the connect timeout to a much large value and see if this is the cause. The trace is indicating this is during connect processing, even though the exception implies a "read".

    Phil