On 10/23/05, Christoph Zwerschke <[EMAIL PROTECTED]> wrote:
> The problem with DebugAppServer was that it finished without stopping
> the "close thread" when an exception was raised and not handled. I've
> just checked in a fix for the DebugAppServer so that it shuts down
> properly. Please check w
The problem with DebugAppServer was that it finished without stopping
the "close thread" when an exception was raised and not handled. I've
just checked in a fix for the DebugAppServer so that it shuts down
properly. Please check whether it is ok that way.
-- Christoph
--
On 10/22/05, Christoph Zwerschke <[EMAIL PROTECTED]> wrote:
> >> In the new workspace there are 2 problems. The output isn't nearly as
> >> friendly and my command window is completely frozen.
>
> The problem seems to be that the DebugAppServer freezes always when an
> exception is raised - in this
In the new workspace there are 2 problems. The output isn't nearly as
friendly and my command window is completely frozen.
The problem seems to be that the DebugAppServer freezes always when an
exception is raised - in this case, a KeyboardInterrupt exception. In
the old version, the Ctrl-C wa
Woops. I spoke too soon. Under my old Webware workspace, which could
be several weeks old or older, hitting Ctrl-C to stop the app server
worked fine (I do this when developing, not in production):
Yes, I made some changes here, because I got exceptions when hitting
Ctrl-C with the *old* versio
