| Temporarily preventing a deployed application from starting |
| Categories: Audium Call Services 3.4.x and 3.5 |
| Article ID: | 5 |
| Last updated: | November 02, 2006 |
| User Opinions |
|
No users have voted.
|
|
Thank you for rating this answer.
|
SUMMARY
Instructions on how to prevent a deployed application from starting when the application server is started.
SYMPTOMS
There is a deployed application that the administrator would like to prevent from starting when the application server starts.
RESOLUTION
By temporarily renaming an application's directory, you can prevent it from being loaded by Audium Call Services when the application server is started. For example, if the application housed in the directory "myapp" needs to be prevented from starting, rename the directory to "myapp.donotload" and it will not start. The "donotload" portion could be any text that you wish, "no_load-myapp" would work just as well, for example. When the application server is started, you will notice a message in the logs:
*** Application - myapp.donotload *** is not permitted to be loaded in the current server.
This message can be disregarded, it is simply acknowledging that the application has not started. To once again allow the application to start when the application server starts, restore the directory to its original name. The application will start the next time the application server is started, or when the application's deployApp script is run.
Note that this is a workaround, and not an officially supported feature.
|
| Visitor Comments |
|
No visitor comments posted. Post a comment
|
| Attachments |
|
No attachments were found.
|
Search the Knowledgebase
Jump to ID
Browse by Category
Print this page
Post a comment