App Connect

 View Only

  • 1.  ACE SaaS

    Posted Thu August 22, 2024 06:28 AM
    Reply

    Hello

    Can anyone help me understand what the issue might be for this error:

    2117E: IBM App Connect Enterprise internal error: diagnostic information 'Fatal Error; exception thrown before initialisation completed', 'Creating credentials manager', '', '63', '63', '9', '8'.

    I am deploying a BAR created in toolkit that is referencing a vault with KAFKA and S3 credentials.

    Thanks



    ------------------------------
    Amanda Erlank
    Architect
    Woolworths
    Cape Town
    27214072560
    ------------------------------


  • 2.  RE: ACE SaaS

    Posted Thu August 22, 2024 08:52 AM
    Reply

    I recreated the vault and seemed to have gone past the above error.  The new error is:

    4362E: Java node error: [BIPmsgs:3891]BIP3891E: The Kafka input connector was unable to subscribe to topic 'IND.XXXXXXXXXXXX.IN' on Kafka server at address 'pkc-e8mp5.eu-west-1.aws.confluent.cloud:9092'. Explanation 'Timeout expired while fetching topic metadata'.



    ------------------------------
    Amanda Erlank
    Architect
    Woolworths
    Cape Town
    27214072560
    ------------------------------

    Original Message


  • 3.  RE: ACE SaaS

    Posted Fri August 23, 2024 05:44 AM
    Reply

    Hi Amanda
    Have you tried running it on a local test server? If so, does the same problem occur?

    Regards



    ------------------------------
    SRECKO JANJIC
    ------------------------------

    Original Message


  • 4.  RE: ACE SaaS

    Posted Fri August 23, 2024 06:05 AM
    Reply

    Hi Srecko

    As a matter of fact, I did that and fixed a couple of things.  The problem I am left with a mapping one.  I am reading a JSON message of a Kafka topic and then writing that to S3.  When I use the S3 option of using input as is I get an error: 

    • Text:CHARACTER:Object has an additional member 'ntfEvent' that is not allowed by the schema.
    • Text:CHARACTER:Object is missing the following members required by the schema: 'Key'.

    How to use the alternative option of mapping the Kafka payload into the S3 body I have not figured out.
    Thanks for your suggestion.

    Regards



    ------------------------------
    Amanda Erlank
    Architect
    Woolworths
    Cape Town
    27214072560
    ------------------------------

    Original Message


  • 5.  RE: ACE SaaS

    Posted Tue August 27, 2024 11:51 PM
    Reply

    Hi Amanda,

    Check , if the input fields are matching with the S3 Request JSON Schema supported by S3Request Connector. The schema will be automatically added to the JSON Schemas under the Application. 'Key' is the mandatory field for S3 action "Create or Update Object". There is no 'ntfEvent' field in the schema, you have to map with the equivalent field from the Schema



    ------------------------------
    Thanks,
    Santhosh Ramanathan
    ------------------------------

    Original Message


  • 6.  RE: ACE SaaS

    Posted Fri August 23, 2024 02:12 PM
    Reply

    Hello Amanda,

    Are you still facing this issue? Some possible reasons for this failure might be if there is a firewall in place or security mechanisms (such as IP allow lists) preventing appropriate connections - are you able to check / confirm? Another that is mentioned here (https://stackoverflow.com/questions/54254686/timeoutexception-timeout-expired-while-fetching-topic-metadata-kafka) indicates this error may be caused if the broker is expecting a secure connection but that hasn't been configured in client connection details.

    If related to IP address allow lists then the list of outbound IP addresses for ACEaaS can be found at https://www.ibm.com/docs/en/app-connect/saas?topic=information-ip-addresses.



    ------------------------------
    Martin Ross
    IBM
    ------------------------------

    Original Message


Related Content