Errors when debugging
At times,
you might encounter errors when you start debugging an application or
when your application is stored on a server system.
Error while starting
If the Web server is not ready, an error can occur when you
start debugging. If the Web server is configured to preload databases
when it starts–which takes some time–debugging
can start before the Web server is ready and the browser will show
an error. This can happen even on an NT machine where PowerDynamo
starts the Personal Web Server automatically.
If this happens, you can simply start debugging again. The
error will not occur again because the Web server is already running.
To avoid generating an error, you can:
- Start
the Web server manually before starting your debugging session.
The Personal Web Server is installed in the PowerDynamo program
group. - Configure the Personal Web Server so that it does
not preload databases. In Sybase Central, you can find the preload
settings by selecting PowerDynamo>Utilities>Configuration>Mapping,
double-clicking the mapping, then clicking the Browse button.
Timeouts while debugging
Debugging uses Microsoft Internet Explorer (IE 5.5) as the
browser environment for debugging. When IE requests a page from
the server, it expects to receive the page within about a minute.
If it does not, it times out and the page is not delivered to the
browser.
When you stop at a breakpoint in a server script, IE can time
out while you are examining the server script. You can finish debugging
server scripts on the page, because the server is not affected by
the timeout. However, the page will not be delivered to the browser
and the application flow will be disrupted.
Depending on the complexity of your application, it can be
simple or cumbersome to continue debugging:
- If
the next page is not dependent on data supplied by preceding pages,
you can remove breakpoints from the current page and request it
again. When it is delivered, proceed to the next page. - If the application flow depends on data from other
pages, you might need to restart the whole application and log in
again.