Home Discussions Questions & Answers Concurrent Manager Stalls After New Application Creation

Concurrent Manager Stalls After New Application Creation

Avatar photoCustomer April 9, 2020 at 3:01 am

We created the new XXEN application using `adsplice`, ran `autoconfig`, and application services are up, but the Concurrent Manager is not processing any new requests. Is a full restart necessary?

Viewing 2 reply threads
  • Author
    Replies
    • Support April 10, 2020 at 8:32 am  

      Yes, this is a known consequence. Creating a new application via `adsplice` requires running `autoconfig` and then a definitive Concurrent Manager restart (bouncing the application tier services). The restart is essential to enable the manager to pick up and process concurrent requests for the newly created application.

    • Avatar photoCustomer April 11, 2020 at 3:45 pm  

      So, `autoconfig` itself doesn’t notify the manager of the new application context?

    • Support April 12, 2020 at 9:16 pm  

      That is correct. The manager’s operational context must be re-initialized. If you choose to create a new application, you must plan downtime for this specific step.

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

Login with: