Difference between revisions of "RPC HELP DEBUG RPC Error Trapping"
(Created page with " RPC Broker Help Home <h2>RPC Error Trapping</h2> M errors on the VistA M Server that occur during RPC execution are trapped by the use o...") |
|||
| Line 3: | Line 3: | ||
M errors on the VistA M Server that occur during [[RPC_HELP_RPCs|RPC]] execution are trapped by the use of M and Kernel error handling. In addition, the M error message is sent back to the Delphi client. Delphi will raise an exception [[RPC_HELP_TRPCB_EBrokerError|EBrokerError]] and a popup box displaying the error. At this point [[RPC_HELP_RPCs|RPC]] execution terminates and the channel is closed. | M errors on the VistA M Server that occur during [[RPC_HELP_RPCs|RPC]] execution are trapped by the use of M and Kernel error handling. In addition, the M error message is sent back to the Delphi client. Delphi will raise an exception [[RPC_HELP_TRPCB_EBrokerError|EBrokerError]] and a popup box displaying the error. At this point [[RPC_HELP_RPCs|RPC]] execution terminates and the channel is closed. | ||
| − | In some instances, an application's RPC could get a memory allocation error on the VistA M Server (in DSM an "allocation failure"). Kernel does not trap these errors. However, these errors are trapped in the operating system's error trap. For example, if an RPC receives or generates an abundance of data in local memory, the symbol table could be depleted resulting in a memory allocation error. To diagnose this problem, users should check the operating system's error trap. | + | In some instances, an application's [[RPC_HELP_RPCs|RPC]] could get a memory allocation error on the VistA M Server (in DSM an "allocation failure"). Kernel does not trap these errors. However, these errors are trapped in the operating system's error trap. For example, if an RPC receives or generates an abundance of data in local memory, the symbol table could be depleted resulting in a memory allocation error. To diagnose this problem, users should check the operating system's error trap. |
Latest revision as of 11:24, 7 July 2015
RPC Error Trapping
M errors on the VistA M Server that occur during RPC execution are trapped by the use of M and Kernel error handling. In addition, the M error message is sent back to the Delphi client. Delphi will raise an exception EBrokerError and a popup box displaying the error. At this point RPC execution terminates and the channel is closed.
In some instances, an application's RPC could get a memory allocation error on the VistA M Server (in DSM an "allocation failure"). Kernel does not trap these errors. However, these errors are trapped in the operating system's error trap. For example, if an RPC receives or generates an abundance of data in local memory, the symbol table could be depleted resulting in a memory allocation error. To diagnose this problem, users should check the operating system's error trap.
