Consultor Eletrônico



Kbase 20352: ADM2 - SDO Gets Errors 5639 or 6456 Against AppServer
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   1/23/2001
SUMMARY:

If you are using SmartDataObjects (SDO) that are split across an AppServer and the AppServer is running in stateless mode, it is possible that you could erroneously receive either of the following errors when you invoke code in the server side of the SDO:

- User-defined function '<function>' invoked
dynamically but could not be found. (5639)

- Procedure <procedure> has no entry point for
<internal-procedure>. (6456)

EXPLANATION:

These error messages are caused by a bug in the getASHandle function where it does not properly handle the possibility that the handle it has cached for the server side of the SDO has been reused by another persistent procedure on the AppServer.

Note that when running stateless, the server side of the SDO is constantly instantiated, used, and then destroyed.

This problem has been seen most often with Windows 2000. It appears that Windows 2000 will reuse handles much more quickly than do other versions of Windows.

A bug report has been submitted to Progress Development to have the getASHandle function fixed. The bug number is 20001117-003, which is a DUP of 20000822-001.