Kbase P131771: Remote debugging doesn't work with OpenEdge Architect
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
27/05/2009 |
|
Status: Unverified
SYMPTOM(s):
Remote debugging doesn't work with OpenEdge Architect
Debugging remotely terminates the remote procedure with OpenEdge Architect.
Remote debugging fails when the procedure is located on an AppServer.
The remote procedure fails on the Appserver with:
TRACE: cso4GL: In execProc() - before execution. (8458)
P-002848 T-005252 3 AS AS -- TRACE: Non-PERSISTENT Procedure END ERROR.(8397)
P-002848 T-005252 4 AS AS -- TRACE: cso4GL: In execProc() - execution failed. (8458)
P-002848 T-005252 4 AS AS -- TRACE: cso4GL: In execCall() - execProc() failed. (8458)
FACT(s) (Environment):
Windows
OpenEdge 10.1x
OpenEdge 10.2x
CAUSE:
Bug# OE00169116
CAUSE:
The OpenEdge Architect Debugger does not support the following operations:
- Attaching to a running process
- Debugging a remote procedure
FIX:
You can use the standalone (non-eclipse) OpenEdge Debugger if you need to perform these operations.
To launch this tool, select Debugger from the OpenEdge program group on the Windows Start> Programs menu.