App Connect

 View Only

  • 1.  ACE v12 Integration Server Hanged

    Posted Fri March 25, 2022 10:26 AM
    Hi, 
    Integration Server / Execution group running as part of Integration Node has hanged after a deployment failed. ACE v12 is running on AIX platform.
    Even after restarting the integration node, one of the integration servers is not starting. Commands are also not helping. 

    Please help to resolve this issue. 

    Many Thanks in advance. 



    ------------------------------
    Thanks & Regards,
    Nithin K S
    ------------------------------


  • 2.  RE: ACE v12 Integration Server Hanged

    Posted Wed April 06, 2022 12:11 PM
    Hi Nithin,

    This is not a problem that can be resolved on the forum.  We would need to look at data and logs.  Most likely your deploy contains a resource that could not start properly.  Finding what resource would require a trace.  If you are still having this problem, please open a support case and provide a backup of the integration server, a service trace of the startup attempt, and the latest deployed artifacts (BAR and associated PI).

    ------------------------------
    MATTHEW SEGALL
    ------------------------------

    Original Message


  • 3.  RE: ACE v12 Integration Server Hanged

    IBM Champion
    Posted Sat April 09, 2022 02:16 AM

    Nithin,

     

    There are many reasons why an integration server would not start.  The most common is something amiss in the server.conf.yaml file.  It could be a typo, etc.  Make sure you look for any spelling issues, etc.  Download the file and use notepad ++ with a Yaml editor to check for any errors.  Remember v12 is a migration so check in the documentation for differences in the yaml file between the two versions.

     

    Here is a checklist to start:

    1. Check the stderr file for the integration server to see if there are any errors logged
    2. Check that there is enough memory/Ram on the server to start all integration servers
    3. Check space in /var and /var/mqsi
    4. Check  to see if any large heapdumps, core dumps, etc. have been created
    5. Check in /var/mqsi/common/errors for that integration server – do you see anything?
    6. Check in /var/log/messages and see if you see anything

     

    Are you using a node to manage the integration server?  Is the server in a container?   Was this working before in v11?  Have you made any changes? 

     

    If the yaml file is fine then do this:

    1. Check what is in the overrides directory – this is always the "gotcha"
    2. Remove all deployed flows/applications/subflows in the run directory and just try starting the integration server then try starting the integration server alone.  Once it starts then stop the integration server and move the applications back to the ...../run folder one at a time.  Start the integration server and see if it starts successfully.  This way you can find which flow or application is causing a problem.
    3. If you're using a node check that you have added in the security parameters in the node.conf.yaml file to manage the server.

     

    You can also run the Transformation Advisor.  This is a great tool to tell you what needs to be modified. https://www.ibm.com/docs/en/app-connect/12.0?topic=tasks-running-transformation-advisor-tool

     

    I hope this helps. 

     

    Susan Barker

    Lead MQ, ACE, ITX, Kafka, WAS Architect

    Victory is nothing without humility, respect and charity...unknown

    Let no one ever come to you without leaving happier...Mother Theresa

    Logo, company name Description automatically generated

    IBM WAS Advisory Board

    IBM ACEvNext Beta Program

    IBM MQvNext Beta Program

     

     

     




    Original Message