done02: where did you go wrong? diagnostics and troubleshooting in openedge kris murphy senior...

DONE02: Where Did You Go Wrong? Diagnostics and Troubleshooting in OpenEdge

Kris MurphySenior Solution Engineer

2 DONE 02: Where Did You Go Wrong?© 2005 Progress Software Corporation

Agenda

Diagnostic & Troubleshooting Tools Overview

Common Troubleshooting Situations– Memory Leak

– Performance Issue

– Error in AppServer™ code Planned for OpenEdge™10.1A


Diagnostic & Troubleshooting Tools

GUI Debugger Logging Infrastructure LogRead Profiler Pro*Spy Plus


GUI Debugger

Modern Java™ graphical interface Initial Technology Preview 9.1D SP 05 First official release OpenEdge™ 10 Supports local and remote debugging Supported on Windows and all

versions of UNIX that support Java


For Your Application Safety…

Client – Start → Programs → OpenEdge → Proenv

AppServer™

Debugging is NOT enabled by default


GUI Debugger

AppBuilder or Procedure Editor– Compile → Debug

– Can step into AppServer code from Client session

DEFINE VARIABLE debug AS LOGICAL. debug = DEBUGGER:INITIATE().debug = DEBUGGER:SET-BREAK(“dordbug.p",6).

Programmatically– DEBUGGER system handle methods

– Initiate debugging in AppServer or WebSpeed® code


Main Debugger Window

Toolbar

Right Click - Dataviews

View\Hide Panes

Organized by type

Source Code

4GL

Procedure

Stack

VariablesWatches

Menubar


Source Code Pane

Shows code Breakpoints

– Set– Remove– Enable/Disable

Arrow current line of execution


4GL Procedure Stack Pane


Variables Pane

Variables Parameters Buffers Temp Tables DataSets


Watches Pane

Type variable directly in watches pane Keeps track of variables, buffer fields, attributes,

etc.


More Variable Detail - Dataview

Additional information Debug Dataview


Quick Dataviews

DataList of SYSTEM

HANDLES


Traversing NEXT-SIBLING


Conditional Breakpoints


Watchpoints


Logging Infrastructure We had logging in Progress® V9. We just

made it better in OpenEdge 10!– Easier to get rid of “noise” in the logs– Unified format– Control Log Size – New log entry types

Logging Infrastructure– Log entry types– Logging levels– Log size threshold– LOG-MANAGER


Log Entry Types

4GL Interpreter 4GLTrace DB.Connects DynObjects.* QryInfo SAX ProEvents.*

-logentrytypes DynObjects.DB,QryInfo

Client 4GLMessages

Other Components AS.Plumbing AS.Default MsgrTrace NameServer


Logging Levels

0 – None 1 – Errors 2 – Basic 3 – Verbose 4 – Extended

-logginglevel 2

-logentrytypes DynObjects.UI:3,qryInfo


Log File Has Size Threshold Startup Parameters

– Log Threshold

– Keep Log Files Progress Explorer

-numlogfiles

-logthreshold


LOG-MANAGER

Runtime access Setting log file name

LOG-MANAGER:LOGFILE-NAME = “Mylog.log”.

Setting logging levelLOG-MANAGER:LOGGING-LEVEL = 2.

StartingLOG-MANAGER:LOG-ENTRY-TYPES = “4GLTrace”.

StoppingLOG-MANAGER:LOGGING-LEVEL = 0.


LogRead

GUI utility to view, filter, sort, merge and translate Progress log files

Not officially supported– On-line Help

Available on PSDN


Loading a Log File

Log file format Date format

Time adjustment Promsgs

translation Date Range Filter


LogRead

Log View Utilities Queries


Sample


Analyze the Merge


LogRead Planned Enhancement

Users can write their own:– Utilities to help analyze log files– Handlers to load other types of log files

Microsoft IIS log file


Profiler

Provides profile of procedure execution Analyze where most time is spent Not officially supported Available on PSDN


Profiler


Pro*Spy Plus

Debugging tool used to trace the execution of a 4GL program

Can be turned on and off at the beginning or during execution

Results of tracing, which include all procedures, triggers, and functions appear in a browse widget


Pro*Spy Plus – Example


Agenda




– Error in AppServer™ code Planned for OpenEdge 10.1A


Memory Leak

Memory is allocated and never freed Application may slow down, and it may affect

the system as a whole Dynamic Objects, Memptrs Tools for diagnosing

– Logging -LogEntryType DynObjects.* LogRead

– Debugger Dynamic Object Tracker


Memory Leak - LoggingLOG-MANAGER:LOGFILE-NAME = “memleak.log”.LOG-MANAGER:LOG-ENTRY-TYPES = “DynObjects.*”.LOG-MANAGER:LOGGING-LEVEL = 3.

CREATE TEMP-TABLE tth.bufHdl = BUFFER customer:HANDLE.tth:CREATE-LIKE(bufHdl).

CREATE TEMP-TABLE tth2.bufhdl2 = BUFFER order:HANDLE.tth2:CREATE-LIKE(bufhdl2).

CREATE QUERY qh.

DELETE OBJECT tth.DELETE OBJECT qh.LOG-MANAGER:LOGFILE-NAME = “”.

LOG-MANAGER:LOGFILE-NAME = “memleak.log”.LOG-MANAGER:LOG-ENTRY-TYPES = “DynObjects.*”.LOG-MANAGER:LOGGING-LEVEL = 3.



CREATE QUERY qh.


LOG-MANAGER:LOGFILE-NAME = “memleak.log”.LOG-MANAGER:LOG-ENTRY-TYPES = “DynObjects.*”.LOG-MANAGER:LOGGING-LEVEL = 3.



CREATE QUERY qh.



Memory Leak - Logging


Memory Leak - LogRead

Utilities FindDynObjLeak


Memory Leak - Dynamic Object Tracking

Diagnostics

Monitor Dynamic Objects


Dynamic Object Tracking

/* ttdelay.p */

CREATE TEMP-TABLE ttHdl1.

bufHdl = BUFFER customer:HANDLE.

ttHdl1:CREATE-LIKE(bufHdl).

ttHdl1:TEMP-TABLE-PREPARE("ttcust").

RUN dyn (TABLE-HANDLE ttHdl1,

OUTPUT TABLE-HANDLE ttHdl2).

…


Dynamic Object Tracking/* ttdelay.p Continued*/

Procedure dyn: DEFINE INPUT PARAM TABLE-HANDLE inhdl. DEFINE OUTPUT PARAM TABLE-HANDLE outHdl. … CREATE TEMP-TABLE outHdl. … outHdl:TEMP-TABLE-

PREPARE(“ttorder”). DELETE OBJECT inhdl.

END.


If you forgot to cleanup

/* ttdelay.p Continued*/

DELETE OBJECT ttHdl1.

DELETE OBJECT ttHdl2.

RETURN.

What did we forget

to delete?

/* ttdelay.p Continued*/

Procedure dyn: DEFINE INPUT PARAM TABLE-HANDLE inhdl. DEFINE OUTPUT PARAM TABLE-HANDLE outHdl. … CREATE TEMP-TABLE outHdl. … outHdl:TEMP-TABLE-

PREPARE(“ttorder”). DELETE OBJECT inhdl. DELETE OBJECT outhdl.END.


If you forgot to cleanup

Dynamic Object tracking allows you to quickly identify your failure to delete objects


Agenda




– Error in AppServer™ code Planned for OpenEdge 10.1A


Performance Issues in the 4GL

Application is slow, queries take a long time to run

Inefficient index usage Diagnostic Tools

– INDEX-INFORMATION Attribute

– Query-Info Logging

– Profiler


Performance – INDEX-INFORMATION Attribute

qh:QUERY-PREPARE("FOR EACH customer WHERE name MATCHES ‘A*’”).

qh:QUERY-OPEN.

message qh:INDEX-INFORMATION(1) view-as alert-box.

qh2:QUERY-PREPARE("FOR EACH item WHERE name BEGINS ‘A’”).

qh2:QUERY-OPEN.

message qh2:INDEX-INFORMATION(1) view-as alert-box.


Performance – Query-Info Logging

LOG-MANAGER:LOGFILE-NAME = “Query.log”.

LOG-MANAGER:LOG-ENTRY-TYPES = “QryInfo:3”.

RUN runQuery(INPUT "for each customer where name begins 'A'").

RUN runQuery(INPUT "for each customer where name matches 'A*'").

PROCEDURE runQuery:

…

hqry:QUERY-PREPARE(cQry).

hqry:QUERY-OPEN().

…

hqry:QUERY-CLOSE().

…

END.

LOG-MANAGER:LOGGING-LEVEL=0.


Performance – Query-Info Logging – Query Plan

Query-Plan: how we extract information for the query including: – Query Type, Prepare String, Sorted, Scrolling


Performance –Query-Info Logging Query Statistics

Query Statistics: information on the query as it extracts data from the database including: – Times prepared (Dynamic only)– Time to prepare (Dynamic only)– Database blocks accessed– Records sent from server

Useful Failed


Performance –Query-Info Logging Query Statistics

Name BEGINS ‘A’ Name MATCHES ‘A*’


Performance - Profiler


Agenda




– Error in AppServer code Planned for OpenEdge 10.1A


Error in AppServer code

Attachable Debugger– Server in another office / building

– No monitor attached

– Easier to debug from where you are


Attachable Debugger

Start Attachable Debugger – Start → Programs → OpenEdge → Debugger

Ready the Client process for debugging– -debugReady port-number– proDebugConfig– Attachable Debugger


Attachable Debugger


Break on Error Message

From within the debugger: Edit Breakpoints


Attachable Debugger


Agenda Diagnostic & Troubleshooting

Tools Overview Common Troubleshooting

Situations– Memory Leak


– Remote Debugging Planned for OpenEdge 10.1A


D I S C L A I M E R

Coming in OpenEdge™ 10.1A

This talk includes information about potential future products and/or product enhancements.

What I am going to say reflects our current thinking, but the information contained herein is preliminary and subject to change. Any future products we ultimately deliver may be materially different from what is described here.

D I S C L A I M E R


Planned for OpenEdge 10.1A

User Logging 4GL Tracing: Log “return” from procedure Query-Info Logging Enhancements


In Summary

Diagnostic Tools Overview Common Debugging &

Troubleshooting Situations To Learn More:

– Debugging & Troubleshooting Guide

– PSDN

– On-line Help


Questions?


Thank you for your time!

done02: where did you go wrong? diagnostics and troubleshooting in openedge kris murphy senior...

Documents

progress software corporation

appserver code n

code n breakpoints

remote debugging n

source code pane n

gui debugger n appbuilder

application safety n

java slide