Kbase P102471: What errors should the Sonic 4GL Adapter client be capturing?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
17/02/2009 |
|
Status: Verified
GOAL:
What errors should the Sonic 4GL Adapter client be capturing?
GOAL:
Should the Sonic Adapter client be trapping more than just error -5, which means the Sonic broker disconnected?
GOAL:
What errors could be reported to the SonicMQ 4GL Adapter from the SonicMQ Client?
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
FIX:
The asynchronous error handler in the SonicMQ Adapter is used to report exceptions that are generated by the SonicMQ client onException handler. All the adapter does is report the exception text, and if present, the exception number. Messages other than -5 can be received by the exception handler, and not all exceptions reported include an exception number.
This also applies to the adapter using the Async error handler to report messages it encounters synchronously. The SonicMQ adapter is just reporting what the SonicMQ client onException handler is reporting. It's not possible to determine how many ways this can be triggered.