webMethods

 View Only
Expand all | Collapse all

Apigateway unable to connect to Terracotta cluster (SSL)

  • 1.  Apigateway unable to connect to Terracotta cluster (SSL)

    Posted Fri September 24, 2021 03:36 AM

    Hi,
    We have configured SSL communication for APIGATEWAY and TERRACOTTA , Terracotta two nodes were able to start and joined the cluster in active passive mode.but API gateway on startup throwing error in server log.
    Actions perfomed before startup:
    1)cleared Terracotta data folders
    2)added certificates at Java cacerts on all the nodes
    3)wild card certificates used across all components
    Error:PFAError.txt (31.8 KB)


    #webMethods
    #ssl
    #Integration-Server-and-ESB
    #cluster
    #Terracotta
    #API-Gateway


  • 2.  RE: Apigateway unable to connect to Terracotta cluster (SSL)

    Posted Fri September 24, 2021 08:18 AM

    Hi Rakesh,

    please specify your version and check if you have the latest Fixes applied.

    According to the error message this looks like either Classloading issue or incorrect config.
    Please check for the SoftwareAG-IS-Core.xml mentioned in your log snippet.

    Regards,
    Holger


    #webMethods
    #ssl
    #Terracotta
    #API-Gateway
    #cluster
    #Integration-Server-and-ESB


  • 3.  RE: Apigateway unable to connect to Terracotta cluster (SSL)

    Posted Sat September 25, 2021 09:46 PM

    Hi Holger, Thank you for your quick response, We are running on 10.7, and with the latest fixes,here I’ve attached config filesSoftwareAG-IS-Core.xml (7.3 KB)
    tc-config.xml (3.0 KB)
    Do we need to change anything as part of cluster configurations in SoftwareAG-IS-Core.xml ? I don’t see anything in the documentation.
    Thanks.


    #Terracotta
    #cluster
    #Integration-Server-and-ESB
    #API-Gateway
    #ssl
    #webMethods


  • 4.  RE: Apigateway unable to connect to Terracotta cluster (SSL)

    Posted Sun September 26, 2021 06:06 AM

    Note that your config files vs error message have different IPs - 10.190.0.* vs 172.25.20.*

    Could not fetch configuration data from 2 different configuration sources” implies that the IS is not able to reach either/both the TC nodes.

    KM


    #ssl
    #cluster
    #API-Gateway
    #Terracotta
    #Integration-Server-and-ESB
    #webMethods


  • 5.  RE: Apigateway unable to connect to Terracotta cluster (SSL)

    Posted Sun September 26, 2021 06:12 AM

    Sorry for the confusion,The error message is from actual environment,since I couldn’t able to get config files from that environment I replicated same in my local environment and shared the config files,Thanks


    #API-Gateway
    #Terracotta
    #Integration-Server-and-ESB
    #webMethods
    #cluster
    #ssl


  • 6.  RE: Apigateway unable to connect to Terracotta cluster (SSL)

    Posted Sun September 26, 2021 07:01 AM

    Well, the fundamental point still applies that your actual environment’s IS instance is unable to reach either/both the TC nodes, which is what the error message explains. Can you check the connectivity from the remote IS to the target TC IPs and ports?

    KM


    #API-Gateway
    #webMethods
    #ssl
    #cluster
    #Terracotta
    #Integration-Server-and-ESB


  • 7.  RE: Apigateway unable to connect to Terracotta cluster (SSL)

    Posted Mon September 27, 2021 12:23 AM

    Hello Kasi,
    I have verified with telnet I was able to connect. Since we have replicated the same in another environment, the issue remains the same.


    #Integration-Server-and-ESB
    #cluster
    #webMethods
    #API-Gateway
    #Terracotta
    #ssl