Application change is not reflected in service

Symptoms

After modifying an application the changes do not seem to be taking effect when calling the service.

Resolution

When a change made to an application does not seem to have any effect when calling the corresponding service again, this might have different reasons that are listed below (sorted by probability).

• The service has not been redeployed after modifying the application. Each application change requires redeploying the service, otherwise the changes will not get effective.
  Does the Control Center show a yellow triangle icon next to the service? This indicates that a problem occurred when trying to redeploy the service. Check the tooltip of the icon and/or open the service info box to get more information about the occurred problem.
• The project or project version is wrong. If you have several project versions, you might work on a different version than the one that is currently deployed - or you might work on a different project. Only one project version can be deployed for a project. To find out which version this is, open the info box for the corresponding service in the Control Center. The name of the deployed project version is displayed here. To change the project version change the start object in the Service editor.
• The VSN has been changed for the number you dialed. In a test environment it may also happen that the media platform is connecting to a different service (VSN) than expected. Check the URL, which is used for the number you are calling; make sure the correct VSN is used.
• In case of a grammar change: The old version/file is still in the cache. Set Resource Fetching - Grammar Max Age (and Grammar Max Stale) in the Tuning section of the start object to 1 sec (not all platforms support Grammar Max Age.). Don't forget to set it back to a higher value later on. If this tuning property is not supported by your media platform clean the media platform cache manually.
• After changing a jar or JSP file: The old version/file is still in the cache/RAM. Restart the server.
  If there are frequent changes, set the component id="DynamicClassManager" to true (in the file WEB-INF/config/components.xml) and use "file://..." instead of "http://..." in the URI field of the Resource Locator object which is linked with the Connector object executing the jar or JSP file.