Re: WDSC lockup (was: Rational Updater)

Dean, Robert wrote:
> With all due respect, what you've written shows exactly what the
> disconnect was.  No knowledgeable person would think that an app can
> block the system UI thread (we're not talking OS/2's single kernel
> msgq after all), so I didn't see how what I wrote would be
> misinterpretted.

Um, how many people understand OS/2's single kernel msgq?  I certainly
don't.  One wouldn't think that a single app could cause an entire
system to crash, but I've seen it happen.

I would request that everyone be civil & polite in all aspects of list
interaction.  We're all professionals.

None the less ...

> The bottom line is that the RSE blocks the WDSC UI thread without the
> courtesy of at least a progress bar with a Cancel button.  It should
> provide that at the very least.  As an Eclipse 3.x plugin, it should
> also provide a "Run in Background" button on said progress bar.  On
> my previous PC, this behavior had more serious consequences than it
> does on most PCs (I blamed the PC, which is why we never opened a PMR
> on this issue).

I don't think it's a the blocking of the UI thread is something that RSE
is doing deliberately.  I've talked to some of the the WDSC developers
and they indicated this was something that is NOT normal.

I think opening a PMR would be the right course of action ... sadly,
this is going to be one of those problems that is really hard to track
down because it's so intermittent.

Personally, I see it happen frequently ... but I couldn't tell you what
I was doing that might have caused it.

david