Was this article helpful?
Was this article helpful?
Related Articles
Pro2 - Does Pro2 need to be restarted after loss of Target or Source db connection is restored? 609Number of Views Catching a STOP condition after loss of db connection causes ABL session to hang 253Number of Views Pro2 retention rules are not correctly synchronized to the appserver side in WAN configuration 287Number of Views Pro2 - Threads hang after AppServer connection loss 2.86KNumber of Views PASOE appserver doesn't trap STOP condition when database has been restarted 2.86KNumber of Views
Disclaimer
The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.
Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.