Home Discussions Questions & Answers Concurrent Manager Stops Processing After Adsplicing New App

Concurrent Manager Stops Processing After Adsplicing New App

Avatar photoCustomer July 19, 2023 at 12:59 pm

We successfully created the XXEN application using adsplice and ran autoconfig, but the Concurrent Manager seems stalled and won’t process new requests.

Viewing 4 reply threads
  • Author
    Replies
    • Support July 21, 2023 at 12:43 am  

      This issue is common when a new application is created. The Concurrent Manager must be explicitly restarted after running autoconfig to ensure it picks up and processes requests for the newly created application.

    • Avatar photoCustomer July 21, 2023 at 6:19 pm  

      So autoconfig alone is not enough?

    • Support July 22, 2023 at 4:10 pm  

      That is correct. If you create a new application, you must plan for application tier downtime to stop and restart the Concurrent Manager to update its operational context.

    • Avatar photoCustomer July 24, 2023 at 10:58 am  

      We also noticed our older custom tops environment variables are now missing after splicing XXEN. Why would that happen?

    • Support July 24, 2023 at 7:04 pm  

      Missing environment variables for other custom tops often occur if those products were added manually instead of via adsplice. You will need to manually enter the custom top entries back into $APPL_TOP/admin/topfile.txt and rerun AutoConfig as a workaround.

Viewing 4 reply threads
  • You must be logged in to reply to this post.

Login with: