PASOE doesn't publish new version of compiled code

Progress Application Server for OpenEdge doesn't publish new version of the code compiled in Progress Developer Studio. After updating a file and recompiling it PASOE loads changes only when it is restarted.

Once a Class or Procedure is updated and compiled, PASOE shows that the REST or Mobile Service is being republished and synchronized 

After the  REST/Mobile Service is republished and synchronized, changes made in the code do not take effect when the code is run; PASOE keeps running the previous version of the code. 

R-code is published physically in PASOE directory

Code is developed in Progress Developer Studio in an ABL Web App project.

The ABL Web App project type is used to develop code that will be published to PASOE.

ABL Web App projects publish r-code incrementally to the PASOE server. However, the server is unable to load the updated r-code for singleton classes and procedures into memory. To do so requires trimming of the agents after performing the incremental publish operation. This trimming is not taking place as required.

Upgrade to OpenEdge 11.6.1.

Restart the PASOE server after publishing r-code.

References to Other Documentation:
Progress Article(s):

000015214: Cannot see changes to WebSpeed application unless WebSpeed broker is restarted